1 message in net.sourceforge.lists.courier-users[courier-users] couriermlm spam filte...
FromSent OnAttachments
Alan MilliganApr 11, 2004 10:13 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] couriermlm spam filteringActions...
From:Alan Milligan (al@balclutha.org)
Date:Apr 11, 2004 10:13:44 pm
List:net.sourceforge.lists.courier-users

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

People,

I am getting a little bored having spammers sending junk to lots of my list-subscribe mailboxes, and it seems to me a simple solution to drop on the floor any subscription request which has a non-empty subject (if present at all).

I am trying to decide upon the best way to implement this, and am quite probably spoilt for choice.

My .courier-default file presently kicks off couriermlm ctlmsg to handle the delivery after my site-wide local maildrop spamchecks the message. However, the dotcourier functionality is not feature rich.

I think I somehow need to invoke another maildrop delivery instead to check if $EXT == 'subscribe' and query the Subject header before accepting with an xfilter or dropping with an exit 99, but am I perhaps missing something more cunning (like a local extension from the first maildrop)?

I also get a load of DSN bounces in my postmaster's mailbox about 550 User Unknown when couriermlm bounces posts from unsubscribed ficticous users spamming my lists. Is there any way to get couriermlm to just silently ignore these bounced DSN's - or should I have a default delivery on my postmaster too??

Cheers, Alan

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.3.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org Comment:

iD8DBQFAeiVsCfroLk4EZpkRAmcmAJ9rAeg285vpksCNGKSImuZ+yALswQCfY+7S bL420WwNUGqRQ1+KhcvOHXw= =LIpX -----END PGP SIGNATURE-----