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

Procmail recipe problems



Hi All,

I've got a strange problem with my procmail setup, and it's presently
affecting my handling of the debian-user list. I suspect I've made
some stupid error I just can't see.

The goal - filter all mailing lists into their own mailboxes,
particularly lists like this one, which combine high volume with a
complete lack of any identifying tag in the subject line.

The recipe that *usually* works, indented here for convenient reading.

    # Debian User List
    :0H:
    * ^(To|Cc):.*debian-user
    -debian-user

The behavior - a given list will suddenly stop sorting correctly, and
wind up in my unclassified mailbox, with the probable spam. It is
likely that some messages continue to be correctly classified, but
many do not, and the result is a strong temptation to unsubscribe. 

The recipe I tried in the hopes that something was merely confusing
procmail as to where to find the boundary between header and body:

    # Debian User List
    :0HB:
    * ^(To|Cc):.*debian-user
    -debian-user

This did not appear to help, and certainly failed to solce the
problem.

I've looked at the messages that are being mis-classified, using emacs
in case mutt's show-header mode was kindly concealing special
characters embedded somewhere inconvenient.

They all have lines like:

     To: debian-user@lists.debian.org

(I haven't noticed one where the list was CC'd, though I do see those
in the correctly-filed list traffic. However, I'm sampling only a very
few of the misfiled messages, which are unfortunately extremely
plentiful.)

This has happened before. The last time, it was a very high volume
list hosted on yahoogroups.com. The problem with that list eventually
cleared up, but lasted long enough to be extremely annoying. 

So what on earth am I doing wrong? I figure this has got to be my very
own regex botch, but I'm just about completely unable to see it.

The system is running sarge, not updated to the latest and greatest
fixes (naughty me), and the procmail filter is associated with the
user receiving the mail, rather than being applied to all mail
received. (There's no practical difference, since it's a single user
system, but I suppose the configuration might matter.) 

-- 
Arlie

(Arlie Stephens	                              arlie@worldash.org)



Reply to: