Forum Discussion
messg spam from my office email to yahoo
It seems like until someone at Microsoft wakes up and fixes their reputation or whatever else is causing this issue, we are all stuck in the middle of the end users complaining their emails aren't getting delivered and hoping the recipients will add the sender to their address book (which kind of works).
Has anyone found a reputable smtp relay service that is compatible with 365/Exchange Online? I had thought I'd just route outbound mail through SendGrid till this gets resolved, but that requires a password on the send connector and I'm not aware of any way to specify a password on the send connector with Exchange online.
I suppose the problem with a service that works without a password is that in theory is a quasi open relay and it would take anything from your domain and deliver it. If that service was more basic and didn't touch the email, DKIM signing from MS should continue to work to differentiate legitimate from illegitimate email, I think.
That being said, if you're desperate for a workaround in the meantime, check out smtp2go. They will allow you to whitelist specific sender addresses and then they will act as an open relay for that mail. (After you go through the proper setup, authenticate the domain, etc.)
Most services won't seem to work as they want some way to authenticate the email with IP or password.
- Hi.
We are doing similar things. We have a gravity zone acct and i just routed email destined to yahoo addresses through that service for now. This does seem to get the email to the inbox on yahoo instead of spam.
We also have an smtp2go account and i will try the address auth option for the next tenant that asks for a fix.
I don't really know whose issue this is, presumably it's a spam filter update on yahoos side. I'm curious why some believe this to be Microsoft's problem. Is it based on the HELO/EHLO issue? I haven't seen a change in my headers over the past month that indicates anything changed, but maybe I'm missing something? Just curious. scottchester
profputr I'm pretty convinced this is NOT Microsoft's fault. I have run multiple tests from various email sources, and only Microsoft's email gets processed as spam.
I also turned on DMARC reporting on two different servers (one Microsoft, one non-Microsoft) and sent email to Yahoo from those services. Both DMARC reports came back with all messages as 'PASS'. Yet again, only email from Microsoft went to spam.
Here is my suggestion to everyone: Start sending messages to people in tech media about this.
Does anyone have experience migrating from Yahoo Small Business email to either Google Workspace or Zoho Mail? I'm thinking it's time to change hosts, but dreading the process. Curious to hear if anyone has been successful/
- profputr To me it seems the reputation of Microsofts servers has gone down the crapper. While yahoo is the most prevalent issue, we have had flat out bounces to Spectrum. While this is a pain, it's somewhat more useful because it at least tells you why and you know your message won't get read.
Reason: [{LED=550 5.1.0 sender rejected. Please see https://www.spectrum.net/support/internet/understanding-email-error-codes for more information. AUP#In-1310};{MSG=};{FQDN=mx0.charter.net};{IP=47.43.18.9};{LRT=6/12/2022 6:49:37 PM}]. OutboundProxyTargetIP: 47.43.18.9. OutboundProxyTargetHostName: mx0.charter.net
From Charter: Spectrum limits the number of concurrent connections from a sender, as well as the total number of connections allowed. Limits vary based on the reputation of the IP address. Reduce your number of connections and try again later.
At Yahoo, even when you add a sender to your address book, the message that comes through will say they think it is spam, but because the sender is in your contacts they left it in the inbox.
If you change nothing but the IP address the message is coming from, i..e a non Microsoft IP, the message is delivered. It seems that Microsoft has let too much spam get sent and Yahoo is the most vocal (by silently treating it all as spam). Charter it seems to vary based on the IP as you can't seem to predict if a message will get through or not.
I would think someone somewhere at Microsoft would be monitoring the reputation of their sending IPs and be able to see what has changed.
