How to deal with spam where "From" email is spoofed and does not match return-path

Hello,

I am using a Windows 2008 server and manage all our emails using MailEnable professional. We also use Magic Spam to trap most spam emails.

Unfortunately we are getting a lot of emails which are obvious spams and they have been spoofing our own emails in the "FROM" part. When I look at the message header I can see the return-path points to a completely different email address which clearly does not match the FROM part.

Is there any effective way to reject these emails using MailEnable by rejecting emails where the FROM email and return-path do not match?

Also are there legitimate cases where they will differ?

Thanks in advance
mike99cAsked:
Who is Participating?
 
designxpertsConnect With a Mentor Commented:
I would recommend setting up an SPF record for your domain and enable SPF checking on your mail server. SPF validates the IP address of the sender, this helps protect from email spoofing for all incoming email as well.

http://www.mailenable.com/documentation/6.0/Professional/Sender%20Policy%20Framework%20%28SPF%29.html

http://en.wikipedia.org/wiki/Sender_Policy_Framework
0
 
SlagwagConnect With a Mentor Commented:
I would first check if you are whitelisting your own domain somewhere in MailEnable Spam filtering or Magic Spam. If not, look for a setting called IP Lock with Magic Spam. I am not familiar with this product but what IP lock does is let you specify what IP ranges can send e-mail through your server.

Example: with an IP lock on yourcompany.com set to your servers public IP of 64.15.3.21 - all traffic your server receives from your own domain will be checked to see if that IP address in the message header that it is coming from matches the server IP (this can be a range as well). This will prevent these spoofed e-mails.

However, it does raise another potential issue. Some users may have Outlook setup from their home and use their ISP to send e-mail out because of port 25 being blocked or may use send on behalf settings from personal e-mails. This might not be allowed in your company but I just wanted to make you aware of it in case this happens.
0
 
mike99cAuthor Commented:
re: comment from designxperts

I have looked into the SPF record syntax and this may be ok for us. We use SMTP authentication for our emails hence the outgoing mail server is fixed for each domain.

Can I check the following with you?

If we have a domain called mydomain.com and the mail server is mail.mydomain.com, does this mean we can setup the SPF record as follows:

"v=spf1 mx mx:mail.mydomain.com -all"
0
 
designxpertsCommented:
Sorry, didn't notice your question till now.

Basically that syntax is correct, you have many options when it comes to writing the SPF record, the following link covers them:

http://www.openspf.org/SPF_Record_Syntax
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.