If it helps... 1. We have trained our Zimbra users who want their email to be copied someplace else to configure the someplace else to log in and collect their email from Zimbra, after having educated them that Forwarding is problematic and can get their domain blocklisted.
2. Periodically we run a script to identify accounts that have Forwarding enabled to non-Zimbra (i.e. outside) accounts and have the same training conversation with the identified users, explaining that we will be turning that Forwarding off shortly. 3. Zimbra's web client has a nifty "Edit As New" option that, instead of Forwarding an email, copies the entire body of the email thread into a newly-composed email. Once we train users to do this instead of Forwarding, everyone is much calmer and they notice their Deliverability improves. This Edit As New feature is very helpful for one customer running a unique B2B services availability business for example. They are able to receive a notice of availability from a service provider, click "Edit As New" and send the notice to their own customers to see if any of their customers are interested in booking that availability. They used to do this via Forwarding, but no longer, and it seems to be working well for them as they are no longer getting "How come you didn't tell us about that availability last week?" complaints, (when in fact the complainer's ESP either blocked the email or put it in the recipient's Junk folder, because... Forwarding). To be fair, for years we have required our hosting customers to deploy meaningful SPF and DMARC records, and to do DKIM signing, all within 30 days' of onboarding, so we haven't had much in the way of resistance from our customers as regards not using Forwarding to external accounts. We appreciate that our mostly B2B customer base generally has a more enlightened (if that's the right word...) approach to email in general, so your customer education process around Forwarding may not be as easy as our conversations were with our customers. Best regards to all, Mark _________________________________________________________________ L. Mark Stone, Founder North America's Leading Zimbra VAR/BSP/Training Partner For Companies With Mission-Critical Email Needs ----- Original Message ----- From: "Archange via mailop" <mailop@mailop.org> To: "Hal Murray" <halmurray+mai...@sonic.net>, "Hal Murray via mailop" <mailop@mailop.org>, "Marco Moock" <m...@dorfdsl.de> Cc: "mailop" <mailop@mailop.org> Sent: Saturday, February 10, 2024 7:10:19 AM Subject: Re: [mailop] Why is mail forwarding such a mess? Le 10 février 2024 15:12:29 GMT+04:00, Hal Murray via mailop <mailop@mailop.org> a écrit : > >m...@dorfdsl.de said: >> Bypassing spam checking would make spammers use exactly that way to send >> spam. > >Sorry I wasn't clear enough. > >My "handshke to set things up" was meant to keep out spammers. > >The idea was that the final receiving MTA would know that it was expecting >forwarded mail for user@domain from a set of IP addresses. > >I was picturing something like: > user goes to final MTA and says I want you to accept forwarded mail for me >from example.com > then he goes to example.com and says "please forward my mail to > m...@final.com" >example.com would then contact final.com and say "OK if I forward me's mail to >you?" >If yes, then example.com says "Here are the IP addresses I use for >forwarding...." I had a similar idea but much more simple: we just keep the part where the user says to the final MTA with which they have u...@domain.org that they are “forwading from m...@forwarder.org”. Then, when receiving an email SRS rewritten from forwarder.org to that u...@domain.org, the final MTA could check DKIM against the original domain but SPF and ARC against the forwarder domain since it is expecting mail to be forwarded that way for that user. Kind of a new domain alignment. No need to tell the forwarding IP, they are provided by SPF for the forwarding domain. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
