14 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: Line endings / DO...
FromSent OnAttachments
Henk van LingenOct 5, 2005 7:05 am 
Jay LeeOct 5, 2005 7:24 am 
Tony EarnshawOct 5, 2005 8:50 am 
Tom DiehlOct 5, 2005 11:40 am 
Henk van LingenOct 5, 2005 2:58 pm 
Paul L. AllenOct 5, 2005 7:32 pm 
Henk van LingenOct 6, 2005 7:31 am 
Paul L. AllenOct 6, 2005 7:48 am 
Jay LeeOct 6, 2005 8:05 am 
Jay LeeOct 6, 2005 8:35 am 
Paul L. AllenOct 6, 2005 9:02 am 
moussOct 6, 2005 10:34 am 
Thorsten HaudeOct 6, 2005 12:33 pm 
Sam VarshavchikOct 6, 2005 3:31 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:Re: [maildropl] Re: Line endings / DOS formatActions...
From:Jay Lee (jl@pbu.edu)
Date:Oct 6, 2005 8:35:27 am
List:net.sourceforge.lists.courier-maildrop

Jay Lee wrote:

another possible way I can think of doing this is adding something like this the end of your global maildroprc:

exception { include '$HOME/.mailfilter' } exit

This would cause the global filter to execute individual users filters but ignore a failed compile (maybe?). The exit would prevent user's .mailfilter files from being executed again. I haven't tried this to see if it works yet, my test box is down right now, just an idea...

Oops! That final exit will consider the message delivered without ever having written it to the user's Maildir! Instead of exit, it should be something like:

to $MAILDIR

Otherwise, as far as I can tell in testing this works nicely. The failed compile of the include is reported in /var/log/maillog but maildrop will then continue processing the last line in maildroprc instead of deffering the message. User's with invalid .mailfilter files will simply get all mail to INBOX, when they come to ask their admin why that is, a simple grep of the maillog will show the syntax errors. Seems like a decent solution to the problem...

Jay