Email SPoofing Block Help with SPF in Mailscanner

David Jones djones at
Mon May 6 05:39:24 UTC 2019


I knew you wouldn't have done that which is why I removed your name from the top of the reply.  My response was for the OP and others that might have done that.  :)


From: MailScanner < at> on behalf of Martin Hepworth <maxsec at>
Sent: Sunday, May 5, 2019 10:47 AM
To: MailScanner Discussion
Subject: Re: Email SPoofing Block Help with SPF in Mailscanner

Was a question not an instruction, the whitelist of your own domain is a common configuration error and will make sure spoofed emails allegedly from your own domain will get through.


On Sun, 5 May 2019 at 14:45, David Jones via MailScanner <mailscanner at<mailto:mailscanner at>> wrote:
Never, ever, ever whitelist either in MailScanner or SpamAssassin any
domains that your MTA is configured to accept.  This will definitely let
spoofed emails through.

> On Sat, 4 May 2019 at 20:38, <bilal.ahmed at<mailto:bilal.ahmed at>
> <mailto:bilal.ahmed at<mailto:bilal.ahmed at>>> wrote:
>     Kindly I need a help someone is spoofing address of my domain and
>     forwarding email to my own domain.____

We need an example email with headers lightly redacted posted to
someplace like<>.  It would also help to see the maillog
entries for that queue ID.

There are multiple ways to block this based on the email headers.

We aren't even sure what domain to check the SPF record for without any

You should consider setting these values in MailScanner.conf if not
already to help with troubleshooting:

Add Envelope From Header = yes
Detailed Spam Report = yes
Include Scores In SpamAssassin Report = yes
Always Include SpamAssassin Report = yes
Spam Score = yes

These must be on based on what information you provided but make sure:
Spam Checks = yes
Use SpamAssassin = yes

>     My SPF is already added in Public DNS.____

Your own SPF setting in DNS will help prevent spoofing to others but
will not necessarily help spoofing to your own mail server running
MailScanner/SpamAssassin depending on your mail flow setup.  For
example, does outbound mail flow for your domain go through this same
mail server unauthenticated from an internal mail server?  Does an
internal mail server smarthost to or run locally on this MailScanner

If your outbound mail does not go through this MailScanner instance,
then you have options like this in your /etc/mail/spamassassin/<>
or /etc/mail/spamassassin/<>:

blacklist_from *<>

It appears that your outbound mail does flow through this MailScanner
box based on the "score SPF_FAIL 15.0" so the entry above would block
legit email just like the "score SPF_FAIL 15.0" entry.

You might be able to add this to the etc/mail/spamassassin/<> or

whitelist_from_rcvd *<> []

where the "" is the internal IP address of your mail server.
  Note this is not ideal since you will no longer be filtering outbound

NOTE: this would only be temporary until a better solution is determined
after seeing the email headers of a spoofed email and knowing more about
the mail flow.

>     __ __
>     Please Any solution to block invalid SPF record address in my
>     Mailscanner/spamassasian.____

Please provide more detail.  Mail filtering is very complex so we can't
help without details.

- original email lightly redacted posted to<>
- what is the MTA?
- what RBLs are configured in the MTA?
- version of MailScanner
- version of SpamAssassin

>     Because I have seen the spoof address with no SPF record are passing
>     through Mainscanner.____

This may be more of a question for the SpamAssassin Users mailing list
if MailScanner is properly using SpamAssassin.

David Jones

MailScanner mailing list
mailscanner at<mailto:mailscanner at>

Martin Hepworth, CISSP
Oxford, UK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the MailScanner mailing list