bitmaelum-suite

bitmaelum-suite copied to clipboard

Instead, it should deploy the public key to DNS, and use that key. THis way, the original organisation key is never used.

jaytaph

Make sure we cannot register organisation accounts to whereever we like

1

There are two ways to register an account to a mail server: - server invitation token - organisation invitation token it's not possible to register on a server that you...

jaytaph

This makes things much cleaner.

jaytaph

Implement the multi-recipient setup (see wiki https://github.com/bitmaelum/bitmaelum-suite/wiki/Multiple-recipients-(CC-and-BCC) and https://github.com/bitmaelum/bitmaelum-suite/wiki/Proposal-multi-recipients). - [ ] delivery pool configurable pool of workers that will deliver a block either remotely or locally. - [ ]...

jaytaph

Implement e2e test suite

1

We should implement an e2e suite: - use sqlite resolver for storing/routing key data - setup 2 mailservers - send email from 1 account to another locally - send email...

jaytaph

seed phrase BIP32 only allows us 128-256 bits

4

Since we will have an irregular number of bits, we need to find a way to achieve this.

jaytaph

Skip proof-of-work for local and organisation messages

1

If a message is located on the same server, we could skip the proof-of-work (configurable) If a message is send to somebody from the same organisation, we could skip the...

jaytaph

Revoke your account/keys

1

Proposal: we do a soft-delete (deleted_at column to the db). Later we can see if we want to hard-delete old records (say > 6months) We also need some kind of...

jaytaph

We should not discard errors with `_`, but handle them accordingly. All code should handle errors. If there is a solid reason not to do this then document on the...

jaytaph

Cleanup code smells from sonarcloud

4

Take some time to do a cleanup of the code smells as found in sonarcloud: https://sonarcloud.io/project/issues?id=bitmaelum_bitmaelum-suite&resolved=false

jaytaph