Jump to content

Recommended Posts

Posted

Got an odd one at a site.

 

When they send emails out though Office 365 some of there emails are being marked as spam and end up in parents/students junk mail and never get seen / replied to.

 

Is there a way of monitoring or reducing the amount of emails that get marked as spam? (other than asking the parents/students to add the domain to their safe list/whitelist)

Posted

And this is the support help i get. Dont know how thats gonna work....

 

We can create a connector and tranport rule.

We have to create a connector using following settings:

1. Goto EAC->Mail->Connector.

2. Mailflow scenario as Office 365 to partner organization.

3. Provide a name to the connector and click Next.

4. Select second option which says "only when messages are sent to these domains" and add hotmail.com, click next.

5. Select first option which says "Use the MX record associated with the partner's", click Next.

6. Select the first option which says "Always use TLS to secure the connection (Recommended) and Issued by a trusted certificate authority (CA).

We have to create a tranport rule to bypass spam filtering policy when email is send to hotmail.com. Chcek the below mentioned steps:

1. Go to EAC->Mail->Rule.

2. Create a new rule and provide a name.

3. Click add more option.

4. Select recipient domain is Hotmail.com.

5. In action select bypass spam filtering.

Please check the behavior after creating both these rule.

 

Posted

Go to your office admin portal, click on domains choose your default domain and use the check DNS button at the top.

 

 

most (not all) spam filters will bounce emails they flag as spam so you (the sender) can troubleshoot.

Posted (edited)
[ATTACH=CONFIG]49672[/ATTACH]

 

Anyhelp?

 

The missing records will need inserting onto your domains DNS settings - this will be held by whoever your domain registrar is or your web-host depending on your setup.

 

If you run a WhoIs lookup on your domain, this should tell you what nameservers your domain is pointing at - this is where the missing info needs to be added. Ensure the SPF is there along with all the details outlined in the 365 admin center.

 

 

edit - If you're stuck, PM me the domain name and I may be able to help a bit further.

Edited by gtg93
Posted
The missing records will need inserting onto your domains DNS settings - this will be held by whoever your domain registrar is or your web-host depending on your setup.

 

If you run a WhoIs lookup on your domain, this should tell you what nameservers your domain is pointing at - this is where the missing info needs to be added. Ensure the SPF is there along with all the details outlined in the 365 admin center.

 

 

edit - If you're stuck, PM me the domain name and I may be able to help a bit further.

 

Just done it. It was with 123-reg.

 

Just refreshed and got no errors on that page now.

Posted

I don't think fixing those DNS record will help with your spam problem, they are for Skype for Business.

Looks like you already have the SPF record, but if they have an on-premises exchange server you'll need to account for that and add it's IP address to the SPF record.

  • Thanks 1
Posted
I don't think fixing those DNS record will help with your spam problem, they are for Skype for Business.

Looks like you already have the SPF record, but if they have an on-premises exchange server you'll need to account for that and add it's IP address to the SPF record.

 

They mostly have problems with emails going to...... hotmail and live (Yes there own domain....)

Posted
yes, nice to have those DNS records fixed but I can't imagine they'd affect your email. What you need is a copy of those spam bounced emails (either from the recipient or a reply to sender) Then you can look at the properties of the email and read the internet headers (a log file of where and why) a spam entry will be there with a reason.
  • Thanks 1
Posted
yes, nice to have those DNS records fixed but I can't imagine they'd affect your email. What you need is a copy of those spam bounced emails (either from the recipient or a reply to sender) Then you can look at the properties of the email and read the internet headers (a log file of where and why) a spam entry will be there with a reason.

 

Ive tired sending emails to my own hotmail account and they gone in to my inbox without problem.

 

although when i did connector validation test email that went in to my junk mail.

Posted
I don't think fixing those DNS record will help with your spam problem, they are for Skype for Business.

Looks like you already have the SPF record, but if they have an on-premises exchange server you'll need to account for that and add it's IP address to the SPF record.

 

yes, nice to have those DNS records fixed but I can't imagine they'd affect your email. What you need is a copy of those spam bounced emails (either from the recipient or a reply to sender) Then you can look at the properties of the email and read the internet headers (a log file of where and why) a spam entry will be there with a reason.

 

Well spotted, I didn't notice that!

 

 

 

 

Has this worked before and randomly stopped without changes? If so have you tried a blacklist check? https://mxtoolbox.com/blacklists.aspx - And it may be worth contact Microsoft direct. I had an issue recently where senders from my VPS were emailing outlook accounts and they were being marked as SPAM by Microsoft. They'd put certain domains of mine onto a blacklist for some unknown reason. I contacted support, and they removed them, however it took a while.

Posted
Rather than waiting for people to complain, setup a DMARC record in DNS. With this you can say 'hey internet, if you receive spam from me, let me know about it'. Not all email systems will do, but many will so every 24 hours you'll get a report from them via email. You will also see the odd spammer trying to spoof your domain.

 

https://blog.returnpath.com/build-your-dmarc-record-in-15-minutes-v2/

 

Can you even do that for o365?

Posted
Can you even do that for o365?

 

It's a setting in DNS, Microsoft couldn't stop it even if they want to. I have three o365 tennants with it setup.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...