_______________________________________________This topic came up at EC. Here’s more info on the two issues:
We continue to struggle with the ever changing and advancing anti-SPAM measures that ISPs are putting into place. Kristin raised an interesting point in the Zoom Chat that I’m not sure everyone read, so I will repeat it here: MIT has abandoned the forwarding-only side of their alumni “email for life” service and now require anyone desiring this service to use their Office 365 in the cloud for email. You can select to forward the email from there, but here’s what MIT said in reference to this:
You should note, though, that new spam rules and policies make it very difficult to offer a reliable forwarding-only service at this point. We have found that email forwarding is becoming less reliable as spam filtering policies get more aggressive. In other words, forwarded mail looks suspicious and causes a red flag in spam filtering systems where mail is forwarded to. This results in the forwarded mail getting flagged as spam or silently dropped (the latter of which is becoming more common). This is why we are now offering the alumni Outlook mailbox. Unfortunately email forwarding alone is no longer a viable option and you run the risk of losing/missing mail if you use it strictly as a forwarding address.
I would submit that if with MIT’s vast resources they cannot provide a “reliable forwarding-only service” why would anyone think that we could? This is an ongoing major problem for us to manage and we will need to take action at some point. One way or another.
We are working with consultants to determine how we can use DNS records and whitelisting services to keep ARRL.ORG emails out of SPAM folders on people’s email clients – which is what we frequently find happening – or blocked entirely by ISPs who determine that something we have originated or forwarded causes us to be blacklisted. Again, if a user is forwarding their ARRL.ORG email to their personal email, the exact same results apply as described above. This was why I did not continue the conversation at EC. We are fully aware of SPF, DMARC, and DKIM in relation to not only our ARRL.ORG email configuration but also the knock on effect of using other services that send email on behalf of ARRL.
This is not an easy fix to an ongoing problem that has existed at ARRL, and gotten worse, over the past decade. We are working to make ARRL.ORG email more reliable on a forwarding basis, but the very best advice is for anyone who has a .ORG address to login via web or client and access their ARRL email that way.
Please address your email concerns to me directly and I will keep you apprised of what efforts and results we are achieving as we move forward managing these issues. I also want to echo what Bill Morine said and not let it get lost in the comments made or that likely will follow: Jim Schaum has been extremely responsive and very aggressive at working to solve the email delivery issues that have been brought to his attention. He is deeply ingrained in getting this solved to the extent that we can. These problems are not a result of inaction or lack of using a silver bullet to solve the problems.
Thanks
David
arrl-odv mailing list
arrl-odv@reflector.arrl.org
https://reflector.arrl.org/mailman/listinfo/arrl-odv