tack
Damned Dirty Ape
I noticed at some point in November (somewhere between Nov 18 and 28), VI-C moved from Amazon SES for email to some fly-by-night mailer, and as a result spam scores have shot up and VI-C emails are now commonly getting flagged as spam. In my own case, the spam scores when VI-C notifications came through SES were -0.10, and since the transition, the scores are baselining at 5.9 and periodically tip over 6.0 (my threshold) based on Bayesian classification.
Nothing wrong with fly-by-night email servers (I myself host one), but they really need to be diligently maintained. The one VI-C is using doesn't seem to be. Specifically:
I can provide full mail headers and mail server logs via email/PM if needed.
Not a big deal really, missing email notifications from VI-C isn't going to keep me up at night, but just thought I'd flag it to the forum admins in case it's not already on your radar.
Nothing wrong with fly-by-night email servers (I myself host one), but they really need to be diligently maintained. The one VI-C is using doesn't seem to be. Specifically:
- The mail server is connecting from 51.81.67.29 and is announcing itself as roy.todo10.com. While 51.81.67.29 does reverse to roy.todo10.com, roy.todo10.com doesn't forward resolve to 51.81.67.29 so it's getting dinged on the spam score.
- 51.81.67.29 is listed on a few blacklists, most notably VirusFree's botnet RBL
- Use of DKIM and DMARC would help to lower the spam score. (SPF record is in use and is ok.)
I can provide full mail headers and mail server logs via email/PM if needed.
Not a big deal really, missing email notifications from VI-C isn't going to keep me up at night, but just thought I'd flag it to the forum admins in case it's not already on your radar.