>>> :0:
>>> * ^Sender: owner-linux-kernel@vger.rutgers.edu
>>> mail/linux-kernel
>>> That'll chuck all your linux-kernel mail into a file called
>>> mail/linux-kernel in your home directory. Far better than
>>> using the To: or Cc: headers.
>> I've just checked, and that particular procmail rule would
>> merge the mail from both the Linux-Kernel and the Linux-Admin
>> mailing lists, as the latter for some reason uses the same
>> sender...
> Hmm..
> I've been using the following rule for ages and it has yet to
> miss a message...
> # Store linux kernel messages into a different folder.
> :0:
> * ^TOlinux-kernel@vger
> LINUX-KERNEL
As written, that should miss EVERY message. The probable correct
version thereof would be...
Q> * ^TO.*linux-kernel@vger
...but that will only catch emails with linux-kernel in the TO list,
not those with it in the CC or BCC lists - nor, for that matter, those
with "To" lines instead of "TO" lines - both regularly occur. OK, you
can add a set to catch the "To", "CC" and "Cc" versions thereof, but
not the BCC version...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/