Mails goes directly to spam - Only outoook/hotmail/msn etc - Critical issue

lowprofile

Verified User
Joined
May 26, 2019
Messages
17
Hi,


We are experiencing huge email issues to Microsoft email accounts despite valid SPF, DKIM and DMARC setups. Mail goes directly into SPAM for only outlook/hotmail etc addresses - No problem with GMail or other providers.

We have also valid PTR/rDNS and our IP is not blocked on any public RBL. We have minimal email traffic and no spam issues.
We have contacted Microsoft and awaiting reply - We even tried to use a brand new IP address (thought maybe IP was blocked in their internal lists) but neither that helped.
We also tried to test on a server which was on another IP block - Same issue.

After spending enormous of time, i now suspect the headers in EXIM to trigger a this false spamflag at outlook. A quick google search reveals many identical issues.
One post from a guy gave me a hint that it is due to exim headers. See last comment in this thread: https://github.com/MicrosoftDocs/OfficeDocs-o365seccomp/issues/211#issuecomment-523865562

So anyone else having issues and tried similar? I havent changed anything.

Running:
DA latest version CB2
EXIM latest version
blockcracking yes
easy_spam_fighter yes

A typical standard setup with no relay or smarthouse etc.
 

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
14,255
Location
GMT +7.00
Seeing this issues on many servers nowadays, the outlook/hotmail are marking incoming emails as SPAM, when no other service marks them as spam. We suggest using 3rd party email services (free or paid) for sending emails to outlook/hotmail as the most simple solution.

If anybody else has another solution please let us know.
 

lowprofile

Verified User
Joined
May 26, 2019
Messages
17
I am in contact with Microsoft and when i get a better and specific reply on why it goes to spam i will notify you.
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,541
Location
Maastricht
We had the same issue. For our volume 3rd party are too expensive and we just want to send mail our self.

A good choice is to become a member of there Smart Network Data Service )SNDS) which is totally free. Also join the Junk Mail Report Program from there (there is a link present).
This way, if people are making complaints, your quicker in preventing getting blocked.

There's always the dynamic spamfilter which is the worst. But you can create a good argument to ask for delisting if you are not on any blacklist with your ip and you are also member of SNDS and JMRP and had no complaints via those (tell them).
Still... it's no guarantee you will be delisted but there is a fair chance.

As said, the dynamic spamfilter is the worst. Especially if you host things like forums. People register their and if they stop using it, they don't ask to remove their account or something, but post notifications and even birthday messages will be just marked as spam by them.
This blunt behaviour of asocials often causes ip's with forums to get on their dynamic spamlist, it seems it does not take a lot of complaints to get on there.

Anyway, if you want to create -any- chance, follow MS's rules and RFC's and join SNDS and JMRP.
And... keep polite when writing to MS employees which answer your mail, even if their answers are short. As soon as people get impolite, you can forget about it.
 

lowprofile

Verified User
Joined
May 26, 2019
Messages
17
Yes i have joined SNDS and the junk mail report program - I dont see any complaints there either. I am on it and will get back with feedback.
Thanks for your suggestions.
 

mxroute

Verified User
Joined
Sep 24, 2019
Messages
32
Frankly, the best way to avoid this is to send mail through Office 365 Business. One might go as far as to suggest that this is an anti-competition practice on their part, but it's easily argued as simply being excessively militant spam filters.

The good news is you're in good company in the spam folder at Hotmail/Outlook. You can often find some of Microsoft's own email in that folder, ironically. The bad news is that there is nothing you can do to undo this, and here are some reasons:

1. SNDS can report everything fine, and likely will unless you are actively sending them spam.
2. Only SOME IP ranges actually get reports about emails that MS customers mark as spam through SNDS, others receive none (1 out of 3 of our /24s get this treatment, the other two do not). But taking action one way or the other won't help this unless, again, you're actively sending real spam.
3. Microsoft will not talk about their spam filters, and will only talk to you if they are returning a message declaring that they have blocked your IP. Instead they will repeatedly tell you that everything is fine.

Your best options are these:

1. Use mail-tester.com and aim for a 10/10 for your outbound mail.
2. Ask your recipients to mark your emails as not spam.
3. Recognize that it's not up to you what Microsoft does, and don't let you or your users hold yourself accountable for their failures.

Ultimately, when recipients continue to use an email service that consistently marks legitimate and clean email as spam, they have to take some responsibility for their situation. I hope the perspective helps, because it can be really frustrating when you consider it your job to fix something that a third party won't even talk to you about.
 
Last edited:

lowprofile

Verified User
Joined
May 26, 2019
Messages
17
Frankly, the best way to avoid this is to send mail through Office 365 Business. One might go as far as to suggest that this is an anti-competition practice on their part, but it's easily argued as simply being excessively militant spam filters.

The good news is you're in good company in the spam folder at Hotmail/Outlook. You can often find some of Microsoft's own email in that folder, ironically. The bad news is that there is nothing you can do to undo this, and here are some reasons:

1. SNDS can report everything fine, and likely will unless you are actively sending them spam.
2. Only SOME IP ranges actually get reports about emails that MS customers mark as spam through SNDS, others receive none (1 out of 3 of our /24s get this treatment, the other two do not). But taking action one way or the other won't help this unless, again, you're actively sending real spam.
3. Microsoft will not talk about their spam filters, and will only talk to you if they are returning a message declaring that they have blocked your IP. Instead they will repeatedly tell you that everything is fine.

Your best options are these:

1. Use mail-tester.com and aim for a 10/10 for your outbound mail.
2. Ask your recipients to mark your emails as not spam.
3. Recognize that it's not up to you what Microsoft does, and don't let you or your users hold yourself accountable for their failures.

Ultimately, when recipients continue to use an email service that consistently marks legitimate and clean email as spam, they have to take some responsibility for their situation. I hope the perspective helps, because it can be really frustrating when you consider it your job to fix something that a third party won't even talk to you about.
Thanks for your suggestion but in this case options 1, 2 and 3 didn't help. What did help was contacting Microsoft and explaining them the issue. The main reason for our IP was blacklisted in their internal systems was due to spam. I remember one of my client once got hacked and the limit of daily outbound mail was set to 1000 - His account managed to send out 3000 emails before it got suspended until everything was clean.

This 1 single occasion seemed to be enough to be blacklisted in Microsoft only.

Now the solution and pre-cautions was to tell them this and our IP was finally whitelisted again:

1. We now joined SNDS and the anti-mail junk program.
2. We lowered the outbound mail sending to maximum 100 pr. account (daily) in DirectAdmin to avoid any script go bananas.
3. We also never was or is registered on any DNSBL/RBL
4. Type of clients - What type of hosting etc (in our case WordPress hosting)
5. We always make use of SPF, DKIM and now also DMARC
6. No delivery problems to other providers.

These above pre-cautions and explanations was enough to start the mitigation of the IPs.
It took almost 7 days from start to finish - so one should have patience when communicating.


I was almost going to start using mail-gun for external smtp service, but thanksfully i didnt do that. Too much work when clients have external DNS (new DKIM, SPF settings etc)
 
Top