Cloudron Forum

nice i eventually figure it out thanks

OK, I finally worked on this AGAIN and remembered how messed up this is conceptually.

username: groupname@domain
password: (any one of the passwords of the people that have access)

This is also makes Freescout work for me https://forum.cloudron.io/topic/12976/connection-could-not-be-established-with-host-mail-domain-com-connection-timed-out-110/43

A single "username" having multiple passwords is what messes me up every time.

Hooray! Thank you, @girish ! 🙂

@girish Thanks for clarification, this suits my needs. Have a great day!

have you stress test your mail server .. sending more emails to see its limits ( in 1 gb ram small vps) ?

I have made the slider start from 500M for a start.

This is fixed now, thanks for reporting.

@robi yes!

Just found the solution here: https://forum.cloudron.io/topic/1279/receive-email/4

The problem was that AWS EC2 instances close port 25 by default. As soon as I opened it in the AWS console, I was able to receive emails.

This is implemented in Cloudron 6 ! https://forum.cloudron.io/topic/3205/what-s-coming-in-6-0-take-2/99

If this is disabled or archived, this also means that it is still "known" to the system, currently the data simply is not removed from the disk, but other relevant information is purged from the database.
So I agree, that deleting an account should also delete the mailbox data, if there is no proper way to restore that (currently you have to create a new mailbox record with the same mailbox handle and magically the data comes back). For that some archived state could be the solution to have a structured way to restore.