Forum Discussion
messg spam from my office email to yahoo
when i send a mesg from my office to yahoo , the message enter to inbox folder , then after 1min or 2min , the message fall to junk folder , can someone help me with this , or explain to me what going on
100 Replies
Kidd_Ip May 30, 2023 and the issue between Microsoft 365 Exchange and Yahoo still exists.
DKIM, DMARC, SPF all configured and they are still bouncing emails with their reverse PTR test.
Was anyone able to get through to Yahoo to whitelist the o365 Exchange servers to stop this stupidity.
Everything going to Yahoo is ending up in spam and dmarc reports **bleep** about PTR. Obviously Microsoft uses a server pool not a single IP address and we can't set a PTR but there is no way of reaching out to Yahoo.
The obvious solution is to tell people to stop using Yahoo but we are unable to send them the email to tell them. 😉
Does anyone have a productive answer to the problem of Yahoo being indifferent to their customers email?
I'm not having the same issues as before. I just sent a test and it seems to work normally.
- Interestingly enough for the past month we've been getting an uptick on emails going to the Junk folder in Outlook for reasons we couldn't understand.
- Like the last few replies have mentioned, all seems to be working again.
- Can confirm on my end as well. Just like it came, it has gone away.
- I just sent from 3 different microsoft tenants to my test yahoo account and all were delivered to inbox 🙂
- That's not what I'm seeing. Emails still going into Spam folder
- The domains I was testing had the SPF / DKIM configured correctly.
Yesterday were going to spam, today to the INbox.
- You can sign up for a trial of MailMonitor.com and we can give you a better understanding if this is due to content, DNS/Authentication issues or if its based on your sending reputation. We have a process we follow to fix these issues and can reach out ot the postmaster as well.
- adriandeliverability from MailMonitor - Your website says you have 400+ seed accounts on various services. Assuming you have Microsoft and Yahoo accounts, can you run a test and enlighten us all as to the results? That could be of value to the group here.
Solana_Beach Yes, happy to run a test across our seed network of 400 seed accounts that does in fact cover outlook and Microsoft SNDS. The test needs to come from the sending domain that's having the deliverability problem. Signup for a test account with me here: https://calendly.com/mailmonitor/test-deliv-microsoft-forum
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.- I'm actually about to set up with SendGrid as their salesperson stated that, people have used their services as an SMTP smart host with O365 services in the past..
Though a sales person from SMTP.com said the same exact crap, and I ran into a similar issue where IP Auth can only be used with O365 with their services. Though they also don't take DNS entries or IPv6.. Their support team also don't seem to have a handle on how email works either, and don't understand the concept of what we are doing here. Hopefully, I don't have a repeat with SendGrid.
But I think our only option is to setup this client with proofpoint or a 3rd party outbound spam filtering service, to circumvent this issue. As it seems like these SMTP relay companies are pretty old school with their methods, and were developed with email marketing in mind, not as a true SMTP Smart Relay.
It is extremely unfortunate that no one on Yahoo or Microsoft(even though I don't this its their problem) is taking accountability for this issue. Nor is this issue getting the attention that it deserves. For an entire month, this has been going on, with no resolution in sight. Wish I could be this incompetent at my job.- NLart, please keep us posted if SendGrid is able to support this, as they told me they don't have any possibility to accept a connection without credentials. The alternate way is to connect my "application" with Zapier. If someone from SendGrid is reading this, see ticket 8823518.
As you mentioned these smtp relay services were setup to send messages from applications, not a full scale smtp smarthost.
Of everyone I reached out to, smtp2go had the best response and gave me an immediate solution.
Proofpoint or something is certainly an option as well, but likely at additional per user costs. We've used services like that in the past, but have been trying to get all in on 365. However, if Microsoft doesn't even care to address a huge problem like email deliverability, it does make you wonder if we are moving in the correct direction.
- I did find a service that it seems possible to route outbound mail through to solve the delivery problem to yahoo and others, at least until MS fixes this. The issue is that because MS doesn't allow any kind of authentication on the connectors, you're going to somewhat open yourself to signing mail that might not be legitimate if someone determines the correct information.
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.
- Make a filter label of the email id so I Hope all emails would move to the Label you create instead of spam.
- I can confirm that this has also been tested (with this thread getting so long, I can't remember if it's been talked about before here or not) and is not working, or at least not working for everyone. It was one of the first things I tested with a friend that uses Yahoo and it still was directed to the spam folder.
- 3rd email (they are just getting lazy can copy/paste from a script):
Hi,
Thank you for reaching back out to us.
I understand that you're still having an issue with your spam emails. I'll do my best to help you.
We understand it's frustrating when things don't work as intended. At this moment, we can only advise that you have your recipients mark your mail as "not spam" or "ham" as you receive contacts regarding this issue.
Our engineering team has determined that there isn't a specific fix date for this issue, but we're still working diligently to find additional resolutions.
We appreciate your continued patience and value having you as a customer. Please let us know if there's anything else we can assist you with.
Warm Regards,
Joms
Yahoo Customer Care
Again, I can confirm, if a 3rd party outbound relay or spam filtering is used, the email will be received by yahoo and not end up in spam folder. Though with what Jeffrey Aucay posted, not for sure if related as this issue would be ongoing from 2016, and only started last month.
