Key Generation during login is a feature not a bug.

[CANAWEN]

From the FAQ:

For logins this would be simple. Just generate key on first login, encrypt it with password and store it on ETHMail server in encrypted form (much like how ProtonMail does it). That’s ok and probably the best for initial implementation, but what about email coming to your mailbox even before you logged in for the first time?

Email coming into your mailbox before account creation should be treated like original email treats messages sent to accounts that aren’t created yet, it trips an error and the sender gets a message saying “no address exists / is invalid”.

I see nothing wrong with this. In fact, imagine the spam waiting for if you senders could send emails to any email account before you create it, it’d be madness.

[gkapkowski]

That's actually against ETHMail most important principle. There is no account creation. All Ethereum addresses have associated mailbox and anyone can send an email to any address even before the owner of the account has any knowledge of ETHMail.

The spam problem is a different one. It's a matte of filtering and marking messages appropriately.

[iceguru]

The downside ofc is that these emails still follow the 45 day term to my knowledge. So I'll never know if I had emails I missed.

[gkapkowski]

Yes, I might actually change that, I would probably be able to change the 45 days into deleting largest messages (keeping some grace period before actual removal) when the inbox space reaches above 5-10MB for free accounts. This should be plenty of space for normal communication to sit and wait for the recipient while not costing me too much. What do you think?