Email sending broken after updating to 8.2.x (due to IPv6 issues)

[joseph]

@privsec if you update to 8.2.4, the ipv6 check is already in place. Check the status tab after update. What does it say?

[jdaviescoates]

@privsec not netcup specific but the most in depth guide is this post by @avatar1024 :

https://forum.cloudron.io/topic/13072/gmail-ipv6-anyone-else-with-this-experience/22?_=1738857946551

[sponch]

Also got massive problems sending mails for 2 days now. Possible that 8.2.4 was released that day?

[jdaviescoates]

@sponch have you sorted out your IPv6 stuff?

[sponch]

Yes. Worked well after doing so for some days. Then „out of the blue“ sending not possible anymore on both of my instances.
„Email not configured properly“ errors in notifications when I go to email-overview page it takes 30-40 seconds until the domains get green. All values are set correctly for every single domain…
Log says: Delivery failure, will retry in 65536s.. DNS lookup failure: Error: queryMx ESERVFAIL

[joseph]

@sponch they might be old emails. You can just delete the old mail queue (to check if these are fresh failures) from /home/yellowtent/boxdata/mail/haraka-queue/ (files inside it). Restart mail container after deleting files.

[sponch]

will try that.
Just found that issue on Hetzner: can that be the reason??
Due to a missing DKIM signature (DomainKey), external mail servers reject your e-mails as spam. For this reason, we have activated DKIM for your domains.

If you use our DNS servers for these domains, the DKIM record has been automatically set in the DNS. If you use external DNS servers for these domains, you must also store the displayed DNS record there accordingly. To do this, open the ‘Products’ tab, select the domain in question and click on ‘Advanced settings’ under the menu items ‘E-Mail; DKIM / SPF / DMARC’.

[sponch]

@Joseph did that an deleted 15 Mails (these were all test mails I tried to send) an restarted mail. No difference still have the same problems..

[jdaviescoates]

@sponch said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

Just found that issue on Hetzner: can that be the reason??

Could be. Have you hit resync dns after enabling and doing all the ipv6 stuff? I think that should auto generate this stuff for you (presuming you're using a supported DNS provider)

[avatar1024]

I've started to have this issue again randomly (emails only sometimes bounce...helpful I know) despite having IPv6 is disabled on both Cloudron and on the Network interface for that server.

[jdaviescoates]

@avatar1024 said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

having IPv6 is disabled on both Cloudron and on the Network interface for that server.

I think the solution is not to disable IPv6 but to fully set it all up. Seems to me this has basically become a requirement Big Tech is forcing on us all.

[avatar1024]

@jdaviescoates said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

I think the solution is not to disable IPv6 but to fully set it all up.

I'm afraid this is still not working, I keep getting weird intermittent bounce even though it's all set-up...

[jdaviescoates]

@avatar1024 said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

@jdaviescoates said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

I think the solution is not to disable IPv6 but to fully set it all up.

I'm afraid this is still not working, I keep getting weird intermittent bounce even though it's all set-up...

[AartJansen]

So with a self hosted install I would need to ask the ISP to set up the ipv6 PTR like they ip4 record ?

[avatar1024]

Ok so I've now noticed that the bounce are only when someone with a Gmail address email say user1@mydomain (mailbox hosted on Cloudron) which then forwards to user1@gmail (redirect through roundcube).

• anyuser@mydomain > user1@gmail works (
• anyuser@posteo > user1@mydomain > user1@gmail works
• anyuser@gmail > user1@mydomain > user1@gmail fails

So something seem to be up with redirect specifically when the sender is a Gmail user and the recipient of the redirect is Gmail user.

Error is the usual IPv6 Google BS:

"Upstream error: 421 4.7.23 [2a03:xxxx:xx:xxx:xxxx:xxxx:xxxx:51af]
The IP address sending this 4.7.23 message does not have a PTR record, or the corresponding forward DNS 4.7.23 entry does not match the sending IP. 
To protect our users from spam, 4.7.23 mail has been temporarily rate limited. To learn more about IP 4.7.23 address requirements for sending to Gmail, visit  4.7.23  https://support.google.com/a?p=sender-guidelines-ip  4.7.23 
To learn more about Gmail requirements for bulk senders, visit 4.7.23  https://support.google.com/a?p=sender-guidelines. a640c23a62f3a-ab7d06caa39si398649666b.93 - gsmtp",  "delay": 128

[jdaviescoates]

@avatar1024 said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

Ok so I've now noticed that the bounce are only when someone with a Gmail address email say user1@mydomain (mailbox hosted on Cloudron) which then forwards to user1@gmail (redirect through roundcube).

anyuser@mydomain > user1@gmail works ☑ (
anyuser@posteo > user1@mydomain > user1@gmail works ☑
anyuser@gmail > user1@mydomain > user1@gmail fails ❎

So something seem to be up with redirect specifically when the sender is a Gmail user and the recipient of the redirect is Gmail user.

This sounds like the same or very similar problem as @fengchang is having too https://forum.cloudron.io/topic/13277/forward-email-with-ses-got-554-message-rejected-email-address-is-not-verified?_=1739395101471

[avatar1024]

@jdaviescoates Indeed that looks very similar...thanks I'll post there. In my case I'm using the Cloudron built SMTP server

I wonder if it is also linked to this: https://forum.cloudron.io/post/99711

[scooke]

@avatar1024 Is 421 4.7.23 your VPS IP?

[avatar1024]

@scooke nope 421 4.7.23 is the Google error code I believe, see https://support.google.com/a/answer/81126?visit_id=638750398959602051-541616874&p=sender-guidelines&rd=1 .

The IP(v6) of the server is the one in the error message right after 421 4.7.23 in [] which I've hidden with xxx.

[avatar1024]

Given this only happens with forwards it seems it might have to do with the SRS rewrite. The weird thing is why does it only happens if the original sender is Gmail?