Re: vim procmail recipe
How about: :0 Whc: msgid.lock | formail -D 8192 msgid.cache :0 a: dupes.lock $HOME/Mail/duplicates This is the super safe version; if you're confident w/ this, you can drop the second recipe and the c flag from the first. It's not a matter of confidence. This _is_ the safe version. Read procmailrc(5), and if the above recipe (or some variation of it) is not there, upgrade to a newer version of procmail.
Re: vim procmail recipe
* Joshua Haberman ([EMAIL PROTECTED]) [20010404 02:36]: [...] But then I get both in my inbox. Ideally, I'd like to have the one that arrived via the mailing list to go in the mailing list's folder, and the one delivered directly to me to go in my spoolfile. :0: * ^Delivered-To: mailing list [EMAIL PROTECTED] vim That will trap any to the list. Anything to the list *and* yourself will appear in 'vim' if it came from the list server, or your inbox if it didn't. It works for me =) -- iain.
Re: vim procmail recipe
* Dale Morris [EMAIL PROTECTED] [010403 00:54]: Could someone post a procmail recipe for vim? I've been dabbling with the following, but they don't seem to work.. :0: * [EMAIL PROTECTED] vim :0: * ^From:.*[EMAIL PROTECTED] vim-help :0: * ^X-Mailing-List:.*[EMAIL PROTECTED] vim :0: * ^Sender:.*[EMAIL PROTECTED] vim Here's mine. :0: * ^TO_vim vim -- "Rascals are always sociable - more's the pity! and the chief sign that a man has any nobility in his character is the little pleasure he takes in others' company." -- Schopenhauer, Exerpts from Parerga and Paralipomena, Vol.1, ch.5, sct.9 --
Re: vim procmail recipe
* Dale Morris ([EMAIL PROTECTED]) wrote: Could someone post a procmail recipe for vim? I've been dabbling with the following, but they don't seem to work.. :0: * [EMAIL PROTECTED] vim try: :0: * ^TOvim@vim\.org vim or (untested, just came across it in the manpage): :0: * ^TO_vim@vim\.org vim $ man procmailrc The only problem I have with the above rule is that if someone mails the list and cc's you, both mails end up in the list's folder. If anyone knows of a good, simple way to prevent this, please let me know. Joshua -- Joshua Haberman [EMAIL PROTECTED], University of Puget Sound "Delaying decisions" is too often a euphemism for "avoiding thinking." -Bjarne Stroustrup
Re: vim procmail recipe
* Joshua Haberman [EMAIL PROTECTED] [010403 09:24]: try: :0: * ^TOvim@vim\.org vim or (untested, just came across it in the manpage): :0: * ^TO_vim@vim\.org vim $ man procmailrc The only problem I have with the above rule is that if someone mails the list and cc's you, both mails end up in the list's folder. If anyone knows of a good, simple way to prevent this, please let me know. Maybe something like this. :0: * ^TO_joshua@haberman\.com $DEFAULT :0: * ^TO_vim@vim\.org vim -- All the days of the poor are evil: a secure mind is like a continual feast. -- Proverbs 15:14 --
procmail mailing list strategy (was Re: vim procmail recipe)
On Tue, Apr 03, 2001 at 09:36:12AM +, Matt Dunford wrote:
* Joshua Haberman [EMAIL PROTECTED] [010403 09:24]:
try:
:0:
* ^TOvim@vim\.org
vim
or (untested, just came across it in the manpage):
:0:
* ^TO_vim@vim\.org
vim
$ man procmailrc
The only problem I have with the above rule is that if someone mails the
list and cc's you, both mails end up in the list's folder. If anyone
knows of a good, simple way to prevent this, please let me know.
Maybe something like this.
:0:
* ^TO_joshua@haberman\.com
$DEFAULT
:0:
* ^TO_vim@vim\.org
vim
Here is how I deal with mailing lists in my .procmailrc:
# define all my possible addresses
ALTERNATES=(mito|ldm)@(aparima|apartia)\.(com|fr|org|net|ch)|(mito|ldm)@(lncsa\.com|premier\.fr)
# all mailing lists I read
LISTS = "(\
mason-devel|\
mason|\
pamldap|\
nssldap|\
abook-devel|\
isdn4linux|\
apartia-auction|\
postfix-users|\
pgsql-general|\
pgsql-hackers|\
pgsql-sql|\
openldap-general|\
openldap-software|\
quikwrite-talk|\
info-cvs|\
ldap-nis|\
vlan|\
pptp-server|\
dbi-users|\
debian-devel|\
debian-firewall|\
debian-consultants|\
debian-french|\
quotegrabber|\
zsh-users|\
membres|\
linux-raid|\
acting-pro|\
linux-laptop|\
linux-ipsec|\
gtkmm|\
linux-on-portege|\
yaoifrance|\
java-linux|\
lftp|\
mutt-users|\
modperl)"
# mailing lists recipe: test to|cc AND return-path in case the message
# is a bcc
:0
*$! ^TO_\/$LISTS()@
*$! ^Return-Path: [^@]*\\/$LISTS\
{ }
:0E
*$ MATCH ?? ()\/[-a-z0-9]+[a-z0-9]
*$ LISTS ?? ()\/$\MATCH
{
FOLDER=$MATCH
# if to|cc me OR from me OR contains references to a previous mail of
# mine OR body contains my name then drop directly mail spool
:0
*$! ^TO_$ALTERNATES
*$! ^From:.*$ALTERNATES
* ! ^References:.*(ldm|cunctator|mito|vindex)@styx\
* ! HB ?? (Louis-David|Mitterrand)
{ }
:0E:
$DEFAULT
# Correct wrong sig-dashes: add a space for lines with only "--" in them
:0 fBw
* ^--$
| sed -e 's/^--$/-- /'
# eliminate duplicate messages
:0Wh: msgid.lock
| formail -D 16384 archive/msgid.cache
# match the characters left of a '-' in list name, preparing for its
# possible elimination on the subject line
:0
*$ FOLDER ?? [^-]+-\/[^-]+
{
FOLDER_PART=$MATCH
}
# eliminate [list] name in subject, often added by clueless mailing list
# admins
:0
*$! ^Subject: *($REPLY: *|)\[$FOLDER\]\/.*
*$! ^Subject: *($REPLY: *|)\[$FOLDER_PART\]\/.*
*$! ^Subject: *($REPLY: *|)$FOLDER:\/.*
*$! ^Subject: *($REPLY: *|)\[ACT-PRO\]\/.*
{ }
:0E
{
:0f
*$ ^Subject: *$REPLY:
| formail -i "Subject: Re:$MATCH"
:0Ef
| formail -i "Subject:$MATCH"
}
# eliminate stupid "tip" footer on pgsql-* mailing lists
:0 bf
* ^TO_pgsql-
| sed -n -e '/^---(end of
broadcast)---$/q' -e p
# kill ugly three-line warning at beginning of message in dbi-users
# :0 fbwi
# * ^TO_dbi-users@
# * B ?? ^^ *\*\*\* From dbi-users
# * 1^1 B ?? ^.*$
# * -11^0
# | sed -e 1,3d -e "$="q
# finally, store in folder named after list
:0:
$FOLDER
}
--
"When I give food to the poor I am called a saint, when I ask why
they go hungry I am called a communist"
--Bishop Helder Camara
Re: procmail mailing list strategy (was Re: vim procmail recipe)
Here is how I deal with mailing lists in my .procmailrc: # eliminate duplicate messages :0Wh: msgid.lock | formail -D 16384 archive/msgid.cache This is *bad*. If procmail fails somewhere after dupes checking and the message is requeued, the next delivery attempt will detect that message as duplicate and silently nuke it. Recommended reading: the c_o_m_p_l_e_t_e_ entry for duplicate filtering in the procmailex man page!
Re: procmail mailing list strategy (was Re: vim procmail recipe)
On Tue, Apr 03, 2001 at 11:50:57AM +0100, Lars Hecking wrote: Here is how I deal with mailing lists in my .procmailrc: # eliminate duplicate messages :0Wh: msgid.lock | formail -D 16384 archive/msgid.cache This is *bad*. If procmail fails somewhere after dupes checking and the message is requeued, the next delivery attempt will detect that message as duplicate and silently nuke it. That's why I only apply dupe-killing to mailing list traffic. It's not a tragedy If I miss a message. Recommended reading: the c_o_m_p_l_e_t_e_ entry for duplicate filtering in the procmailex man page! (oops, vim doesn't like your markup, or is my mutt misconfigured?) That "Beware" section has been added recently in the procmailex page, thanks for pointing it out! -- How's my posting? Call 1-800-DEV-NULL
Re: vim procmail recipe
On Tue, Apr 03, 2001 at 02:12:15AM -0700, Joshua Haberman wrote: The only problem I have with [the rule] is that if someone mails the list and cc's you, both mails end up in the list's folder. If anyone knows of a good, simple way to prevent this, please let me know. How about: :0 Whc: msgid.lock | formail -D 8192 msgid.cache :0 a: dupes.lock $HOME/Mail/duplicates This is the super safe version; if you're confident w/ this, you can drop the second recipe and the c flag from the first. -- Oo---o, Oo---o, O-weem-oh-wum-ooo-ayyy In the jungle, the silicon jungle, the process sleeps tonight. Joe Philipps joe -a-t- philippsfamily.org, http://www.philippsfamily.org/Joe/ public PGP/GPG key 0xFA029353 available via http://www.keyserver.net PGP signature
Re: vim procmail recipe
* Matt Dunford ([EMAIL PROTECTED]) wrote: The only problem I have with the above rule is that if someone mails the list and cc's you, both mails end up in the list's folder. If anyone knows of a good, simple way to prevent this, please let me know. Maybe something like this. :0: * ^TO_joshua@haberman\.com $DEFAULT :0: * ^TO_vim@vim\.org vim But then I get both in my inbox. Ideally, I'd like to have the one that arrived via the mailing list to go in the mailing list's folder, and the one delivered directly to me to go in my spoolfile. I'm awfully picky, aren't I? :-) Joshua -- Joshua Haberman [EMAIL PROTECTED], University of Puget Sound "Delaying decisions" is too often a euphemism for "avoiding thinking." -Bjarne Stroustrup
vim procmail recipe
Could someone post a procmail recipe for vim? I've been dabbling with the following, but they don't seem to work.. :0: * [EMAIL PROTECTED] vim :0: * ^From:.*[EMAIL PROTECTED] vim-help :0: * ^X-Mailing-List:.*[EMAIL PROTECTED] vim :0: * ^Sender:.*[EMAIL PROTECTED] vim duh... thanks
Re: vim procmail recipe
I use this for the vim help/user list, which seems to work: :0: * 1^0 ^from.*vim@vim\.org * 1^0 ^to.*vim@vim\.org * 1^0 ^cc.*vim@vim\.org vim On Mon, Apr 02, 2001 at 05:51:53PM -0700, Dale Morris wrote: Could someone post a procmail recipe for vim? I've been dabbling with the following, but they don't seem to work.. :0: * [EMAIL PROTECTED] vim :0: * ^From:.*[EMAIL PROTECTED] vim-help :0: * ^X-Mailing-List:.*[EMAIL PROTECTED] vim :0: * ^Sender:.*[EMAIL PROTECTED] vim duh... thanks -- John Patton [EMAIL PROTECTED] Get my GnuPG public key: finger [EMAIL PROTECTED] "I believe in God, only I spell it Nature." - Frank Lloyd Wright
