David W. Tamkin said
I feel the same way; when someone answers a post of mine by writing to me
and carboning the list, I like to get the direct copy in $DEFAULT and the
list-distributed copy in my folder for the list. (There are others here who
feel very differently, considering the two copies to be an annoyance or even
an insult.)
The easiest way is to file mail in the folder for the list by testing whether
it came *via* the list instead of testing whether it was sent *to* the list.
Look at the headers of items from that list and find something that was added
by the list software, such as an X-Mailing-List: header, or Resent-Sender: or
Sender:, or even the Unix From_ line at the top ...
I agree.
I have used this in the past (by simply looking at the spool file and
seeing the first `From' line of the message):
:0
* ^From debian-user-request(_at_)lists(_dot_)debian(_dot_)org
debian
:0
* ^From procmail-request(_at_)Informatik(_dot_)RWTH-Aachen(_dot_)DE
procmail
Now, I collect specific high-volume mailing lists (like Debian) into their
own spool files like above, and let other recipes catch all other mailing
lists (like procmail and fvwm) into a single spool file with later rules:
#Majordomo lists
:0:
* ^Sender: owner-\/[-a-zA-Z0-9_.]*
maillists
#SmartList lists
:0:
* ^X-Mailing-List: <\/[-a-zA-Z0-9_.]*
maillists
So Debian mailing list mail goes to `Debian', procmail and fvwm mail go to
`maillists' and mail addressed to me yet CC'ed to a list go to my main
spool file.
--
Peter Galbraith, research scientist
<galbraith(_at_)mixing(_dot_)qc(_dot_)dfo(_dot_)ca>
Maurice-Lamontagne Institute, Department of Fisheries and Oceans Canada
P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada 418-775-0852 - FAX 418-775-0546