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:05:23 am
List:net.sourceforge.lists.courier-maildrop

Paul L. Allen wrote:

Henk van Lingen writes:

On Thu, Oct 06, 2005 at 03:31:00AM +0100, Paul L. Allen wrote:

Really, really, really, really. If you understand regexps then you ought to understand EOL conventions.

This may all be true, but it's besides my point that maildrop shouldn't fail on a silly DOS format.

If you're going to take the attitude that maildrop should cope with users editing files with a Windoze editor then you also ought to cope with them using Word to do so and ending up with directed single or double quotes, either at the character positions where Microsoft put them or at the Unicode character positions. And you probably ought to cope with Word's "smart quotes" not always being that smart and sometimes pairing them in the wrong order. It is unconscionable that maildrop should not protect users who edit files using broken software. Oh, and don't forget to support Hindic- speaking users who insist on using Hindic digits instead of 0-9. Etc. I still think that anybody who understands maildrop's syntax well enough to be able to create a working filter file ought to be bright enough to figure out that EOL characters need to be converted. Or that if you're going to let them do this sort of thing, and presumably have given them instructions and examples, your documentation could include text saying that they have to run dos2unix after uploading.

I agree, it does not make sense to extend maildrop to understand every possible syntax end users might happen to throw at it. maildrop is a programming language and as such, it has strict requirements about what it should see. However, I do agree with OP that it is somewhat annoying to the end user to discover that all their mail is bouncing simply because they forgot a ' or a ( in their .mailfilter file. I wonder if it'd make sense to make .mailfilter compiling errors result in maildrop not using the .mailfilter instead of failing the message? Maybe a command line option? Or 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...

Jay