issue with email delivery going through Cloudron mailing lists.
-
I can't tell as I stopped using Cloudron mailing list a while ago because of this. But clearly others (e.g. @d19dotca) seem to still have the problem so looks like it hasn't been solved.
-
I can't tell as I stopped using Cloudron mailing list a while ago because of this. But clearly others (e.g. @d19dotca) seem to still have the problem so looks like it hasn't been solved.
@avatar1024 said in issue with email delivery going through Cloudron mailing lists.:
I stopped using Cloudron mailing list a while ago because of this
Out of interest, what you using instead?
-
J jdaviescoates referenced this topic on
-
@avatar1024 was this resolved?
@james said in issue with email delivery going through Cloudron mailing lists.:
@avatar1024 was this resolved?
No, this hasn’t been resolved. This still needs to be improved in Cloudron mailing lists, please.
-
@avatar1024 said in issue with email delivery going through Cloudron mailing lists.:
I stopped using Cloudron mailing list a while ago because of this
Out of interest, what you using instead?
@jdaviescoates said in issue with email delivery going through Cloudron mailing lists.:
@avatar1024 said in issue with email delivery going through Cloudron mailing lists.:
I stopped using Cloudron mailing list a while ago because of this
Out of interest, what you using instead?
I think they were using the workaround of creating a mailbox and logging into roundcube to setup mail forwarding, so it kind of acts like the Cloudron mailing list in a way, but seems to be more reliable and doesn’t trigger Gmail’s “mass mail” protections.
-
@jdaviescoates said in issue with email delivery going through Cloudron mailing lists.:
@avatar1024 said in issue with email delivery going through Cloudron mailing lists.:
I stopped using Cloudron mailing list a while ago because of this
Out of interest, what you using instead?
I think they were using the workaround of creating a mailbox and logging into roundcube to setup mail forwarding, so it kind of acts like the Cloudron mailing list in a way, but seems to be more reliable and doesn’t trigger Gmail’s “mass mail” protections.
@d19dotca said in issue with email delivery going through Cloudron mailing lists.:
I think they were using the workaround of creating a mailbox and logging into roundcube to setup mail forwarding, so it kind of acts like the Cloudron mailing list in a way, but seems to be more reliable and doesn’t trigger Gmail’s “mass mail” protections.
That's correct and also started using Lismonk for larger distribution lists.
-
Just to add, I've hit this too.
I've got a small Cloudron mailing list that includes a bunch of Gmail address. In the past I think it's been sending to them fine, but the most recent send to the list (which was sent from a Google Workspace email account that is also on the list) generated this error:
Upstream error: 421 4.7.28 Gmail has detected this message exceeded its quota for sending 4.7.28 messages with the same Message-ID. To best protect our users, the 4.7.28 message has been temporarily rejected. For more information, go to 4.7.28 https://support.google.com/mail/answer/188131 a640c23a62f3a-afcdd03a4b4si214278366b.769 - gsmtp
I guess I'll have to resort to sending these messages out another way too
-
@d19dotca said in issue with email delivery going through Cloudron mailing lists.:
I think they were using the workaround of creating a mailbox and logging into roundcube to setup mail forwarding, so it kind of acts like the Cloudron mailing list in a way, but seems to be more reliable and doesn’t trigger Gmail’s “mass mail” protections.
That's correct and also started using Lismonk for larger distribution lists.
@avatar1024 said in issue with email delivery going through Cloudron mailing lists.:
also started using Lismonk for larger distribution lists.
Is that what you're still doing? Do those somehow magically get through to Gmail addresses OK?
-
@avatar1024 said in issue with email delivery going through Cloudron mailing lists.:
also started using Lismonk for larger distribution lists.
Is that what you're still doing? Do those somehow magically get through to Gmail addresses OK?
@jdaviescoates Well, this is what I do for distribution list and it seems to work fine with Gmail addresses. But I have to say it isn't really a replacement for Cloudron lists. I find the current email situation really quite tricky on Cloudron, given:
- issues with delivery on forwards to some providers like Gmail
- issues with delivery when using an external SMTP (likely related to point 1) when trying to overcome bad IP rep (which with MS domains is a recurring issue with MS stupid IP range bans).
For work I have to now consider moving all our mailboxes out of Cloudron...which I would really want to avoid because of:
- faff
- because I love Cloudron and wanna promote it (but my users are getting pissed because of email problems).
@staff if you don;t really want to focus of changing the mailing function on Cloudron for now (and I totally respect and understand that this may not be your priority), can you advise on a working solution to use a address@domain.coop (with domain.coop being the Cloudron domain) which can be use as a list, where:
- some mailboxes on this domain being hosted on Cloudron (so the MX has to remain pointing to the Cloudron server)
- and while using an external SMTP server to ensure reliable email delivery