Cloudron Forum

@trend-1 our mail server was having the same trouble. DO has blocked outbound port 25 (ipv6) wholesale on the network and it doesn't look like they make exceptions. So, the mail server tried to send via ipv6 (haraka prefers ipv6 by default) and wait for sometime to fail. It then tried ipv4 after. For my other VPS, which has IPv6, email was getting blocked in various places anyway because of the "open resolver" issue of IPv6. So, I think 9.0.12 fixes it. Works on both my servers.

Fixed in https://git.cloudron.io/platform/box/-/commit/3e6f3bd807a63e38711ace7e83eb5e2b722299b5 . Thanks for reporting!

I confirm. It work without 127.0.0.1

Can you give more context what you mean by that? Which API would one use for relaying there, since https://developers.brevo.com docs also refer to regular smtp relay for relaying purposes. Also what would be the benefit there? Like postmark or so, brevo also has an API to send/compose emails but I am not sure how this relates to the relay part here, but maybe I am missing something.

IMAP (are people still using POP?

You should see a summary in the email header just after the X-Spam-Status one, which explains how it came to this (ham) score. This should looks something like this, with different scores of course: X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [87.253.236.95 listed in list.dnswl.org] * 0.0 HTML_MESSAGE BODY: HTML included in message

Yeah, that makes sense. having a warning pop up before deleting an address that’s part of a mailing list would save a lot of confusion. even just a simple check and confirmation message would do the trick.

Given the confidential nature of this, please write to us at support@cloudron.io if they need some information on our side.

@webliska Is this resolved now?

@vjvanjungg not 100% sure but we got a similar report on Support and I replied there. The mail server is not responding after the initial SMTP EHLO. Can you check the raw mail server logs - https://docs.cloudron.io/email/#event-log ?

@jdaviescoates Yes I know, this was more of a general feature request lol

thank you for the help. I can mark this as resolved.

Are you saying you are getting SPF_SOFTFAIL for all your emails? Note that the SPF fail here is for the domain of the incoming mail and not your domain itself.

@affinity @girish as in set them a global profile which then get picked up by any apps via ENV VARs? Then you'd just need an app restart.

@girish Oh that is interesting, I didn’t realize we could customize the DNS server. This is helpful. Thanks so much!

Hi @fbartels You're right, double checked and it always defaults to smtp. instead of .my When manually changing on both PC and Mobile, the SMTP accounts can be added without the certificate error! Thanks Everyone!

@flaxxain RainLoop app is long deprecated . Consider using SnappyMail , Roundcube or SOGo

I changed the mail server here. The DNS was updated and no SSL errors.

Could you please convert that thread into a request to remove 'Cloudron' from the mail templates as well as from translation files, please?