9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Maildrop: Complet...
FromSent OnAttachments
Matt SavigearApr 21, 2004 1:51 am 
Zoran MilojkovicApr 21, 2004 2:47 am 
Matt SavigearApr 21, 2004 2:55 am 
Matt SavigearApr 21, 2004 2:57 am 
Jeff JansenApr 21, 2004 3:45 am 
Bill TaroliApr 21, 2004 5:22 am 
cour...@gmx.netApr 21, 2004 8:16 am 
Matt SavigearApr 21, 2004 9:07 am 
Jon NelsonApr 21, 2004 10:49 am 
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:Re: [courier-users] Maildrop: Completely unable to delete mail.Actions...
From:Bill Taroli (bill@billsden.org)
Date:Apr 21, 2004 5:22:47 am
List:net.sourceforge.lists.courier-users

Jeff Jansen wrote:

On Wednesday 21 April 2004 08:52, Matt Savigear wrote:

I'm getting to the point where I am entirely happy to grovel for assistance. As with many folk I'm using SpamAssassin and want to delete certain mails. I have checked the lists, and come up with a number of methods. None of them actually work - whatever I try, the mail _always_ gets requeued for another delivery attempt. Eventually it bounces, which given the fact that most headers are faked gives me some problems.

I've got a user in my userdb called "null". In null's $HOME directory there's a .courier file with a single newline (\n) in it (a NON-empty .courier file). When I want to drop a message I send it to "null" and it disappears. Hope that helps.

WRT preventing spam from being delivered, I think another option that many people use are global filters... especially relating to amavis. Being that spam trapping is a not-so-precise art, however, I personally tend to just drop them into a common folder (ala Junk) and have jobs to monitor them and clean up on a regular basis -- allows me to ignore if I wish or review in case of false positives.

But back to my original point: the amavis/global filter approach, while it can't modify the content of the message when used as a global filter, enables the rejection of spam much earlier in the process. The only possible drawback would be that it might not be capable of rejecting it without returning an error to the client during SMTP submission... but if this is not an issue, it might be a useful alternative.

Bill