pre-generate accounts

[missytake]

To reduce latency we can pre-generate a number of accounts (say always keep 20 accounts available for each token, checked in a prune loop) and then hand them out at new_email request.

This will be more reliable, because the mailcow API does not get load bursts. The onboarding still needs mailcow be available to complete though, as the configure process only completes if logging in works.

[brabo]

it sounds like an option.

how would the burners be handled then? some may have a very short lifespan, say 1 day. if they get added to the db upon creation, they may have expired before handing out? i guess they could be kept in ram, but then need to keep track of lifetime.

[link2xt]

@brabo We can create mailcow account in advance, but start counting their expiration from the time when they are given to some user. E.g. set date=0 for these accounts on creation, then set date to actual timestamp when needed.

Expiration is handled on the mailadm side, not mailcow.

[link2xt]

We don't have overloading of mailadm problem now because we have switched to chatmail.