You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog Suppressing backscatter bounces on secondaries

#1 Re: Suppressing backscatter bounces on secondaries Posted by simonw (84.45.xx.xx) on Fri 8 Feb 2008 at 20:51 Secondaries outside your administrative control almost certainly should die. The folks saying they are mostly worse than useless are right! Best single change I ever made was removing all the brainless secondary servers from our email config. It only took one SQL query! You must generate DSN or risk unreliable email. To only send DSN on non-spam you'd need a 100% reliable way to identify spam, and if you had one of those you wouldn't be asking the question would you. Folks who silently drop email when someone mistypes an email address, should consider giving up email admin - hotmail may have an opening for folk who don't think reliable email delivery (or non-delivery) is important. If you must have a secondary (do give us the reason for why you think you need one), things like Postfix make it relatively easy to maintain a cache of working addresses on the secondary so you can validate addresses easily. I dare say Exim can be made to do something similar, or just rsync the relevant files every 5 minutes. The fact that lots of folk generate spurious spam bounces is no excuse, loads of folk litter public spaces, you don't have to do it. I agree the situation with forwarding email to servers outside your control is more difficult, and my own problem since my employer hosts many websites and the email for those domain is often forwarded to the owners email address. Yes we generate too many DSN for spam, but I've worked hard to try and mitigate this, and I bet I have less spurious queued messages for several thousand domains, then any admin who runs a dumb secondary for a typical single domain. Have you looked at the proportion of ham to spam received by secondary servers compared to the primary (assuming the primary mail server is even vaguely reliable)?

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account