Jeff Abrahamson on 20 Jan 2006 19:17:28 -0000

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] procmail and matching on split lines

On Fri, Jan 20, 2006 at 11:42:47AM -0500, Michael C. Toren wrote:
>   [26 lines, 163 words, 1212 characters]  Top characters: entailso
> On Fri, Jan 20, 2006 at 08:31:58AM -0500, Jeff Abrahamson wrote:
> > I didn't realize subject lines could contain hard breaks.  I'm not
> > sure how to match this without matching anything containing "post" and
> > "requires".  Indeed, an even longer email address could push
> > "requires" to the next line, and I'm not clear how to match that.
> Are you sure that this has actually presented a problem in practice,
> or are you anticipating that it may be a problem in the future?  The
> procmail man page states in the BUGS section:
>     The embedded newlines in a continued header should be skipped
>     when matching instead of being treated as a single space as
>     they are now.
> And in the MISCELLANEOUS section:
>     To make `egrepping' of headers more consistent, procmail
>     concatenates all continued header fields; but only internally.
>     When delivering the mail, line breaks will appear as before.

It did come up in practice: the mail in question was missed by my spam
exception filter, whose procmail rule was in my previous email to this

The procmail log entry is this:

From Fri Jan 20 00:24:24 2006
 Subject: Cs260-200502 post from requires
  Folder: bogofilter-unsure						   5347

I'll have to look at formail some, as suggested by Mark Bergman.  I'm
reluctant to concatenate all continued headers (To:, CC:) but maybe I
can get it to do what I want nontheless.

Thanks much.


 Jeff Abrahamson  <>    +1 215/837-2287
 GPG fingerprint: 1A1A BA95 D082 A558 A276  63C6 16BF 8C4C 0D1D AE4B

Attachment: signature.asc
Description: Digital signature

Philadelphia Linux Users Group         --
Announcements -
General Discussion  --