Hi, > Am 29.04.2024 um 20:28 schrieb Michael Peddemors via mailop > <mailop@mailop.org>: > > On 2024-04-29 08:02, Mendel Kucharzeck via mailop wrote: >> Hi, >> During my last email campaign, I’ve encountered issues with gmail – and >> after investigating this for a few days, I cannot make heads or tails of the >> results. Maybe anyone can shed any light on what is happening. >> Environment: Mailing list of around 150k subscribers, double opt-in. Using >> AWS SES for around 10 years to deliver emails. DKIM, SPF, DMARC and BIMI >> (with valid certificate) present. Custom MAIL-FROM domain set up on AWS SES >> (newsletter.syniumsoftware.com <http://newsletter.syniumsoftware.com>), >> sending mail address is newslet...@syniumsoftware.com >> <mailto:newslet...@syniumsoftware.com>. Sending pattern is irregular, I’m >> sending one newsletter every few months. >> Timeline: >> - A newsletter campaign on January, 18th was successful with high >> read-rates. DMARC and BIMI were not present during this campaign, but DKIM >> and SPF. MAIL FROM domain was amazonses.com >> - Another newsletter campaign was send on March 15th, which was also >> successful. DMARC was present, but set to „none" in order receive reports. >> BIMI was absent. MAIL FROM domain was amazonses.com <http://amazonses.com> >> - The most recent campaign was send on April 26th with way lower (30-40% >> lower) read-rates. DMARC and BIMI were present, DMARC was set to „reject“. >> MAIL FROM domain was for the first time newsletter.syniumsoftware.com >> <http://newsletter.syniumsoftware.com> > > Commend you for updating your MAIL FROM, but you 'might' want to consider > having a URL redirect from newsletter.syniumsoftware.com -> > syniumsoftware.com, just for trust, transparency, and and confidence factors. > > (http://newsletter.syniumsoftware.com cannot be reached)
Thanks for your suggestion, I’ll add a redirect shortly. > But this may be related to the drop in reputation of Amazon SES IP Space. Do > they offer a dedicated outgoing IP Address that you can try? It also helps > reduce any chance of forgeries.. Eg, smaller SPF footprint, that could have > poisoned your reputation. AWS SES offers dedicated static IP addresses at a reasonable cost. I’ve been in contact with them several years ago about a static dedicated IP, but they strongly suggested against it because of my irregular sending patterns (campaigns every few months, no steady flow of transactional emails etc). Using their shared IPs, we never had any issues in the past – delivery and read rates were very high up until now. Since we’re using AWS SES with shared IPs for 10 years, it would be a very unlikely coincidence that their reputation tanked this very instant. I highly suspect that one of the changes we’ve made since our last newsletter campaign is the culprit (like the new MAIL FROM domain, DMARC set to reject policy, BIMI…) but I am totally clueless on how to investigate it using the data that’s available to me. My guts tell me that the new MAIL FROM could be the issue. I know that email providers use IP reputation to calculate a spam score – what I don’t know is if providers are also using the MAIL FROM domain as a spam score indicator. For example, does an unknown MAIL FROM domain incur a spam penalty like a previously unknown IP address? Best, Mendel _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
