From: "David W. Tamkin" <dattier(_at_)ripco(_dot_)com>
I used to file one of my subscriptions by
the From_ header, . . .
But one subscriber to that list had a private domain and, for every
list he joined, he created a username matching the name of the list,
so he would subscribe to the foo list as foo(_at_)his(_dot_)domain, to the
gurble-l list as gurble-l(_at_)his(_dot_)domain, and so forth. If he had been
on this list, he'd have subscribed to it as
procmail(_at_)his(_dot_)domain(_dot_)
. . . .
This just happened last week to me on another list I get. I had to
figure out why the private response suddenly ended up with the list
mail. I then had to kludge my recipe to keep the listname@ address
from screwing up my folder assignments. I thought about it, and tried
to pick a method that, while still a kludge, was the least "kludgey"
or offensive that I could muster while still keeping my recipes
"elegant." I did find it irritating to have to deal with it.
In a given week I seem to get 1-3 emails that don't do what I'd
expected or planned for, and I have to fine-tune my recipes to deal
with them. I call it "teething pains." Right now there are two that
I've saved to look at more carefully later today. Luckily, ones that
do not only unexpected, but also *dangerous*, things are essentially
nonexistent these days. :-)
--
\ .-. .-. .-. .-. .-. .-. .-. /
\-d-/-m-\-a-/-n-\-(_at_)-/-n-\-e-/-t-\-c-/-o-\-m-/-.-\-c-/-o-\-m-/
'-' '-' '-' '-' '-' '-' '-' '-'
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail