[Discuss] MailRoute anti-spam MX

[Tom Metro]

Daniel Hagerty wrote:
> Jack Coats <jack at coats.org> writes:
>>    But in the future you might configure a 'secondary email server'.
> 
>     With a really important addition for modern mail servers: You
> must, must, must ensure that any mail the secondaries accepts will
> deliver, without bounce, on the primary.

Yes, and generally speaking, your MX needs to implement anti-spam
measures that are as strong as your primary.

The server that has direct contact with the client machine is in the
best position to determine the authenticity of the client, can implement
the least resource intensive anti-spam measures, and can reject the
message without queuing and taking delivery responsibility for it, thus
avoiding backscatter bounces.

Anyone tried out the MailRoute (http://mailroute.info/) anti-spam MX
service? Compared it to DynDNS's offering?

The MailRoute marketing materials don't explain how they address
managing the list of valid mailboxes for your domain. I can see this as
being a potential maintenance hassle. And possibly a road block if their
system isn't sophisticated enough to handle address extensions. (i.e. in
addition to user at domain, user-ext at domain and user-ext-ext2 at domain might
also need to be considered valid. In some case you might want to
explicitly specify the latter two cases, and in others you might want
wild card behavior plus an explicit blacklist.)

 -Tom

-- 
Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/