Topic: Problems with qmail doublebounce control

[Quade]

I've been working with the understanding that if I create an alias file in /var/qmail/alias called .qmail-devnull by typing:
echo "| dd of=/dev/null" > ~alias/.qmail-devnull

and changing the doublebounceto control file in /var/qmail/control to 'devnull' by typing:
echo devnull > /var/qmail/control/doublebounceto

then I create an account called devnull by typing:
/sbin/e-smith/db accounts set devnull system

here's what should happen:

Some spammer sends an e-mail to a non-existant account, it bounces back to them, but since spammers are immoral little tunts, that account doesn't exist, and it bounces back to me. My qmail receives it as a doublebounce, and calls the doublebounceto control to ditermine who should get the e-mail.

Doublebounceto contains the alias 'devnull', and the alias file points qmail to just pipe the e-mail to /dev/null which just makes the double-bounce go away.

Unfortunately, that's not happening on my machine.

I've seen about 5 different ways of handling double-bounces, but none have worked.

I've tried:
- setting doublebounceto to an e-mail address that doesn't exist
- setting doublebounce to devnul and aliasing devnull to a forced pipe to /dev/null
- editing the e-smith template file for doublebounceto and expanding that template
- setting the doublebounceto control to another e-mail account, and setting a cron to delete that account's mail

In all cases, the double-bounce comes to my admin account.

Obviously, there's something that's causing my qmail to behave differently than expected. Other than these doublebounceto changes, I've made no change to the way that qmail functions.

The doublebounceto control file does contain the devnull alias, yet it bounces the bounce to me.

I've read the user docs on qmail, and still see no reason why this should continue to happen. What could possibly cause qmail to ignore that control file? Is there a way to find out if anything is routing the doublebounce'd e-mail to me *before* it looks up the appropriate control?

[Nate]

what you need is :
http://myezserver.com/downloads/mitel/contrib/smtpdcheckrules-0.0.1/
Email that is going to a non-existant email address is denied by smtp--that way qmail will never see it.  It takes a little custom templating to ezmlm with smtpcheckrules, but it can be done(I use ezmlm).

[Cyrus Bharda]

Except this does not work with 5.5 as smtpdcheckrules has been replaced with mailfront.

[Quade]

I installed the RPM, and that had no effect.

I'm using SME 5.1, so qmail is still in effect.

I still don't know why it does this. It's as if it's ignoring that particular control.

So, does SME server use a different set of controls? Is there some modification that causes qmail to ignore that (or possible other) controls?

Using expand-template *does* expand my changes into the proper control directory, but the double bounces still harangue me.