SPAM coming in direct or through secondary MX?

I have been doing some reading about spam and secondary MXs recently.  We currently use our ISPs backup MX service, simply because we are a small business at one location and we don't have backup mail servers.  I'm told that often spammers will send to the second MX in order to bypass the spam checking on the main mail server.  Our mail server is an Exchange 2003 SP2 (under SBS 2003) box.

So the questions I have are:

1.  Why would sending to the secondary MX allow spammers to evade spam filters?  The backup MX server eventually has to send those e-mail to the main server, so wouldn't the main server just filter the incoming e-mails at that point, regardless of the source?

2.  How do I tell which e-mails came through the secondary MX and which came in directly to primary?  I'd like to check to see if we are acutally receiving any e-mail  through our secondary MX on a regular basis.

Any insight on this would be much appreciated.
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

bevhostConnect With a Mentor Commented:
I have a postfix server which acts as the only MX for downstream exchange servers and it CAN do Unknown user Errors.


It uses a scheme called address verification, where it connects the the primary server to find out if a user exists if it has never been seen before.  So Secondary MX servers can have access to user lists to verify emails.

So far as exchange servers are concerned, I haven't found the built in tools very good at stopping spam, so I generally don't have any MX records pointing directly at them, in favour of a front end server with better anti spam controls.
ccnsConnect With a Mentor Commented:
as long as your exchange/mail server has some sort of email filtering it will be stopped. regardless of which mx the spammers send the emails on.
I reccomend symantecs SEP and MAIL security for microsoft exchange.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Please read the following links - i am sure this would answer every bit of your doubts.

If you still have doubts over spamming / relaying - go ahead and post them here. :)
Is your secondary MX capable of the error message "Unknown User or Mailbox"?  
or does it blindly accept anything addressed to your domain?

When you bounce these, then they probably are spam and you just bounced them back to some poor person who had their email address forged.  It would have been better to refuse to accept the message in the first place.

Secondary MX servers are good for extremely high load situations or if you have a dial up link and aren't online all the time.

Remember the Sending MTA has a queue and will store the message anyway if you go down for a day or so.
So you really don't need them to be queued at the ISP.  Why would it make any different whether the sender queues it or your ISP queues it?

Secondary MX is also very good if you have two internet links.

I_play_with_DNAAuthor Commented:

I would assume the secondary MX accepts everything addressed to the domain.  The secondary MX is controlled by our ISP, so they would have no access to our user lists in order to validate e-mails.
I_play_with_DNAAuthor Commented:
@Exchange geek

Those articles really don't address anything asked in my questions.
I have provided those articles which talk in detail about how to control spam and relay. Also, if the secondary MX is accepting those emails - how are they forwarding those emails to your exchange server ? via firewall / smtp gateway or directly ?
I_play_with_DNAAuthor Commented:
@Exchange geek

I think it must be via SMTP gateway since the secondary MX is not part of our network.  It's been a long time since I've had to administer an e-mail server, but I'm pretty sure this is correct.
Exchange_GeekConnect With a Mentor Commented:

I agree fighting with spam is best done by "other" server rather than Exchange - even though Exchange 2003 IMF is built with anti-spam features - it is not the best in the world - hence having a smtp gateway / front-end box / firewall are the best configuration to receive (in other words MX records) / send emails (smart host setting).
All Courses

From novice to tech pro — start learning today.