Cloudron Partner
Thanks for the report @d19dotca . It's fixed for 10.0.2.
The issue was that when having multiple internal forwards, sieve was adding multiple headers. The haraka code headers.get() was concatenating all the headers with '\n' and this caused a crash since I wasn't expecting haraka to concat it this way. There is a get_all() API which returns an array and I pick the latest forwarder from there.
Does that means one cannot use an external relay to replace the built in SMTP server if we use mailing lists (or the mailbox + forward implementation in Cloudron 10) - given most likely senders and mailing lists members with use random email providers?
Yes, with a typical smart host / relay you cannot keep the original sender on list/forward delivery to Gmail/Posteo/etc.
I want to mention that this is for the forwarding feature. Forwarding requires From address to be preserved. A mailing list behaves differently. It rewrites From/Reply-To etc and makes itself the originator of the email. This feature was never implemented in Cloudron. The forwarding feature was incorrectly labeled as mailing list and this misnaming is fixed in Cloudron 10.
I guess we have to look into Distribution lists/mailing lists for the next releases, if you are interested in this. But the From address will change, not sure if it will work for your use case. It's usually meant for group@example.com or list@example.com style workflows.
I think that message from gmail is the generic one saying it doesn't want your email from the IP. Are you actually sending 100s of emails to gmail ? Or is gmail rate limit so low? Happy to read up on some gmail docs, but I can't really find any note on specific limits.
@avatar1024 external relay services will only relay addresses that you added to them explicitly. So if you added foo.com into postmark, postmark will only relay email address which have From as *@foo.com .
The idea of mail forwarding is that the From address has to be that of the original. So, the From address has to set to say someone@posteo.com . Postmark will reject these emails (correctly).
So to summarize: domain-locked relays and keeping the original sender on forwards/lists do not go together. You can relay or you can transparently forward third-party mail, not both. There's nothing Cloudron can do about this from what I know.
@smilebasti in Cloudron 9, we decided to only accept STARTTLS servers which is the needed for some basic security . I guess for local intranet relays we can add an option to disable this.
In the meantime, you can edit /home/yellowtent/box/src/mail.js (depending on the version this can be mailserver.js or mailstatus.js). Look for requireTLS: true and just set this to false and systemctl restart box . That should let you add the relay. Haraka already support opportunistic STARTTLS .
I read the thread quickly but it relates to Gmail sending quotas. Not sure what Cloudron can do here?
|
296
Posts
277
Reputation
|
|
1,392
Posts
1,837
Reputation
|
