Cloudron Forum

@humptydumpty Nothing more difficult than getting family to accept your help and acknowledge that perhaps you know something that they don't:) To your point, perhaps during signup a warning about mail delivery to these inbox providers and a suggestion to use another email address. Caveat emptor.

Thanks, I can confirm this. The mails just did not show up in the queue on the web frontend which I find a bit confusing.

@girish Excellent! It‘s working in the latest release. Thank you very much 🙏!

Thank you! A local installation of imapsync on the server did a great and fast job in transfering the emails from one account to the other.

This is done by now.

OK, with @NCKNE 's help we got this figured out. Cloudron has a anti-spoof check where we don't allow external servers to send email with FROM address set to any incoming domain. In this case, a backup MX is relaying email to Cloudron and it is correctly detected as spoof-ed email.

The workaround is to simply whitelist the MX's IP in the SPF record. With this Cloudron has the "authorization" that the server is allowed to relay such email and accepts the mail. I have added a section in our doc here - https://cloudron.io/documentation/email/#alternate-mx

@NCKNE Which app did you use the sieve filters in. Often, the filter in one app is not visible in another!

The sieve filters are located at /home/yellowtent/boxdata/mail/vmail/<mailbox>/sieve. Can you check if they are there on the filesystem atleast?

I have succeeded in installing Heimdall in the LAMP app.
Installs and runs quite easily.

So far I am struggling to get a working package for Cloudron.