Re: .procmailrc configurations
On Wed, Jan 23, 2013 at 12:29:47PM -0500, Patrick Shanahan wrote: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ AFAIR, maildir doesn't need locking whereas mbox does, so compare: :0: to :0 i.e. no trailing semicolon. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: .procmailrc configurations
On Sat, Jan 26, 2013 at 02:18:37AM +1300, Chris Bannister wrote: On Wed, Jan 23, 2013 at 12:29:47PM -0500, Patrick Shanahan wrote: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ AFAIR, maildir doesn't need locking whereas mbox does, so compare: :0: to :0 i.e. no trailing semicolon. Thanks! To make procmail wok fine . is a .forward file in my home dir a must ? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [01-25-13 08:50]: On Sat, Jan 26, 2013 at 02:18:37AM +1300, Chris Bannister wrote: [...] AFAIR, maildir doesn't need locking whereas mbox does, so compare: :0: to :0 i.e. no trailing semicolon. Thanks! To make procmail wok fine . is a .forward file in my home dir a must ? man procmail -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
Incoming from Patrick Shanahan:
* horseriver horseriv...@gmail.com [01-25-13 08:50]:
To make procmail wok fine . is a .forward file in my home dir a
must ?
man procmail
Even better: http://www.procmail.org/era/lists.html
If we discussed everything that works with mutt on the mutt-users
list, any mention of mutt itself would be difficult to find. That
would be unfortunate.
I apologize if I've done anything to encourage that (and I likely
have; stopping now).
Have a lovely weekend! :-)
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: .procmailrc configurations
On Thu, Jan 24, 2013 at 12:18:21AM -0700, s. keeling wrote:
Incoming from horseriver:
On Wed, Jan 23, 2013 at 01:46:54PM -0700, Robert Holtzman wrote:
On Wed, Jan 23, 2013 at 10:58:37AM +0800, horseriver wrote:
How to edit my .procmailrc to put mails from different mail
list into different maildir?
can this work :
:0
* ^to: mutt-users@mutt.org
mutt-users@mutt.org
Read this:
http://www.ii.com/internet/robots/procmail/qs/
Is your mutt directory really named mutt-users@mutt.org? Why?
In your recipe, ^to should be ^TO_
As far as I know, both work. ^TO is special in procmail, but ^to: (as
a regexp) works too.
I have modified my procmailrc like this .
Like what?
Then, Need I retrieve mails from pop server ? or just restart mutt
to see the result?
Too many questions. I used fetchmail to pop mails before. It
supports a keep directive. You can pop and pop and pop, and still
all your mail will be left on the server. Delete the keep from your
config, and they'll be deleted when popped.
Another question: How does mutt call procmail to sort mails ? In
mutt doesn't call procmail. They're separate processes. In my case
(before), fetchmail pops from my ISP's Smarthost, that hands it to local
Mail Delivery Agent (procmail), and mutt picks it up from there once
it's delivered into ~mail.
my muttrc file , I have not tell mutt to call procmail to sort
mails .so how mutt know that?
procmail can sort incoming mails. mutt just looks for them
(mailboxes) once they arrive.
OK!
Here is my config:
:0
* ^TO_: mutt-users@mutt.org
$MAILDIR/mutt
can it works ?
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [01-24-13 05:07]: OK! Here is my config: :0 * ^TO_: mutt-users@mutt.org $MAILDIR/mutt can it works ? it would be better: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ = reference: man procmail man proxmailsc man procmailex man procmailrc -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
On Thu, Jan 24, 2013 at 08:38:08AM -0500, Patrick Shanahan wrote: * horseriver horseriv...@gmail.com [01-24-13 05:07]: OK! Here is my config: :0 * ^TO_: mutt-users@mutt.org $MAILDIR/mutt can it works ? it would be better: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ = Thanks! But I really do not know what is mdir and maildir , what is the difference between them ? reference: man procmail man proxmailsc man procmailex man procmailrc -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [01-24-13 09:57]: On Thu, Jan 24, 2013 at 08:38:08AM -0500, Patrick Shanahan wrote: * horseriver horseriv...@gmail.com [01-24-13 05:07]: OK! Here is my config: :0 * ^TO_: mutt-users@mutt.org $MAILDIR/mutt can it works ? it would be better: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ = Thanks! But I really do not know what is mdir and maildir , what is the difference between them ? reference: man procmail man proxmailsc man procmailex man procmailrc sorry, that mdir s/b mbox mbox stores multiple emails in a single file while maildir separates each email into separate files. There are advantages and dis-advantages to each format. Personally, I use mbox but have a great number of locally stored emails. spending some time reading the above references for procmail, reading the mutt documentation and googling for mbox and maildir formats will greatly enhance your understanding and make it possible for you to make intelligent decisions rather than just jumping on-board whatever happens to be in front of you. google *is* your friend. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
Incoming from Patrick Shanahan:
* horseriver horseriv...@gmail.com [01-24-13 09:57]:
But I really do not know what is mdir and maildir , what is the
difference between them ?
That was confusing me too. Fneh. :-|
You really should do this, btw. Good advice. It's all good reading:
reference: man procmail
man proxmailsc
man procmailex
man procmailrc
sorry, that mdir s/b mbox
mbox stores multiple emails in a single file while maildir separates each
email into separate files. There are advantages and dis-advantages to
each format. Personally, I use mbox but have a great number of locally
stored emails.
Additionally, procmail *may* work best with mbox (both work though),
but IMAP is maildir.
spending some time reading the above references for procmail, reading the
mutt documentation and googling for mbox and maildir formats will greatly
enhance your understanding and make it possible for you to make
intelligent decisions rather than just jumping on-board whatever happens
to be in front of you.
Good advice.
google *is* your friend.
Alternatively, https://www.ixquick.com/ - It has a do it via
google feature built into it.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: .procmailrc configurations
On Thu, Jan 24, 2013 at 12:18:21AM -0700, s. keeling wrote: Incoming from horseriver: On Wed, Jan 23, 2013 at 01:46:54PM -0700, Robert Holtzman wrote: snip Read this: http://www.ii.com/internet/robots/procmail/qs/ Is your mutt directory really named mutt-users@mutt.org? Why? In your recipe, ^to should be ^TO_ As far as I know, both work. ^TO is special in procmail, but ^to: (as a regexp) works too. I tried that once by mistake (I had meant to write *TO_) and it didn't work until I changed it. Too long ago for me to remember the procmail version. .snip -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: .procmailrc configurations
* s. keeling keel...@nucleus.com [01-24-13 12:06]: Incoming from Patrick Shanahan: mbox stores multiple emails in a single file while maildir separates each email into separate files. There are advantages and dis-advantages to each format. Personally, I use mbox but have a great number of locally stored emails. Additionally, procmail *may* work best with mbox (both work though), but IMAP is maildir. moxnix, procmail *works* equally well with either as long as procedure is followed, esp. trailing slash for dirs. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
On Thu, Jan 24, 2013 at 08:23:02AM +0800, horseriver wrote: snip. OK! Here is my config: :0 * ^TO_: mutt-users@mutt.org $MAILDIR/mutt can it works ? Did you try it? If not, why? You're not doing your homework. -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: .procmailrc configurations
* Robert Holtzman hol...@cox.net [01-24-13 13:27]: On Thu, Jan 24, 2013 at 08:23:02AM +0800, horseriver wrote: snip. OK! Here is my config: :0 * ^TO_: mutt-users@mutt.org $MAILDIR/mutt can it works ? Did you try it? If not, why? You're not doing your homework. em, just noticed trailing : missing on recipie declaration. A *necessary* lock for mbox delivery. Do not see where $MAILDIR points. No one can tell you when you continually provide insufficient information for valuation. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
Incoming from Robert Holtzman:
On Thu, Jan 24, 2013 at 08:23:02AM +0800, horseriver wrote:
Here is my config:
:0
* ^TO_: mutt-users@mutt.org
$MAILDIR/mutt
can it works ?
Did you try it? If not, why? You're not doing your homework.
Specifically:
VERBOSE=yes
in your .procmailrc, then tail -N $your_procmail_log_file where N
== number of lines to display. Note you can wrap each recipe in your
.procmailrc with VERBOSE=yes VERBOSE=no pairs to test each new
recipe by itself.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: .procmailrc configurations
Thanks! There is no log file generated in the $PMDIR/. Here is my .procmailrc: VERBOSE=yes # Upon debugging remove the # LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/procmail #procmail home dir LOGFILE=$PMDIR/log INCLUDERC=$PMDIR/test.rc INCLUDERC=$PMDIR/lists.rc what is the reason ? I am googling for this answer .
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [01-24-13 23:25]: Thanks! There is no log file generated in the $PMDIR/. Here is my .procmailrc: VERBOSE=yes # Upon debugging remove the # LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/procmail #procmail home dir LOGFILE=$PMDIR/log INCLUDERC=$PMDIR/test.rc INCLUDERC=$PMDIR/lists.rc what is the reason ? I am googling for this answer . is $HOME/procmail actually a directory or a file do $PMDIR/test.rc and $PMDIR/lists.rc actually exist? please provide: ls -lad ~/procmail then try with: LOGFILE=$PMDIR/log good idea: enclose in quotes any chars that would normally be escaped, ie: / as $PMDIR/log -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
* Patrick Shanahan ptilopt...@gmail.com [01-24-13 23:36]: * horseriver horseriv...@gmail.com [01-24-13 23:25]: Thanks! There is no log file generated in the $PMDIR/. Here is my .procmailrc: VERBOSE=yes # Upon debugging remove the # LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/procmail #procmail home dir LOGFILE=$PMDIR/log INCLUDERC=$PMDIR/test.rc INCLUDERC=$PMDIR/lists.rc what is the reason ? I am googling for this answer . is $HOME/procmail actually a directory or a file do $PMDIR/test.rc and $PMDIR/lists.rc actually exist? please provide: ls -lad ~/procmail then try with: LOGFILE=$PMDIR/log good idea: enclose in quotes any chars that would normally be escaped, ie: / as $PMDIR/log Also: I would declare LOGFILE before VERBOSE and LOGABSTRACT, although it may make no diff. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
.procmailrc configurations
hi: How to edit my .procmailrc to put mails from different mail list into different maildir? can this work : :0 * ^to: mutt-users@mutt.org mutt-users@mutt.org thanks
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [2013-01-23 13:42]: hi: How to edit my .procmailrc to put mails from different mail list into different maildir? can this work : :0 * ^to: mutt-users@mutt.org mutt-users@mutt.org thanks I use a more generic approach for this since years: # 'Simple' mailing-lists :0 * ^List-Post:.*mailto:\/[^@]+ $MAILSPOOL/.Mailinglists.$MATCH/ # generic filter for yahoogroups lists :0 * ^Mailing-List: list .*@yahoogroups\..*; * ^Mailing-List: list \/[a-z_0-9-]+ $MAILSPOOL/.Mailinglists.$MATCH/ Note that this is *on* the IMAP server itself! Your mileage may vary ... HTH Stefan pgpVLU0l0MOCA.pgp Description: PGP signature
Re: .procmailrc configurations
Incoming from horseriver:
How to edit my .procmailrc to put mails from different mail list
into different maildir?
can this work :
:0
* ^to: mutt-users@mutt.org
mutt-users@mutt.org
.^^^
That should be a file (mbox) or folder (maildir). Otherwise it looks
good.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: .procmailrc configurations
* horseriver horseriv...@gmail.com [01-01-70 12:34]: How to edit my .procmailrc to put mails from different mail list into different maildir? can this work : :0 * ^to: mutt-users@mutt.org mutt-users@mutt.org it would be better: for mdir = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users = for maildir, note trailing / in the assigned location = MAILDIR=$HOME/mail ## your mail dir below /home/user :0: * ^TO_mutt/-users/@mutt/.org $MAILDIR/mutt-users/ = reference: man procmail man proxmailsc man procmailex man procmailrc -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: .procmailrc configurations
On Wed, Jan 23, 2013 at 10:58:37AM +0800, horseriver wrote:
hi:
How to edit my .procmailrc to put mails from different mail list into
different maildir?
can this work :
:0
* ^to: mutt-users@mutt.org
mutt-users@mutt.org
thanks
This is a configuration that I used to use:
# Mailing List Classification {{{
# This is a method/recipe that I ganked from [1]. I liked the idea of #
# separating filtering out into 'classicifation' and 'delivery' # phases.
#
# Sources
# ---
# [1]: http://aperiodic.net/phil/configs/procmailrc
# most lists; RFC-2919
:0 fhw
* ^((List-Id|X-(Mailing-)?List):(.*[]\/[^@\.\/]*))
| formail -I X-List-Classify: $MATCH
# majordomo
:0 fhw
* ^Sender: owner-[^@]+@[^@\+]+
* ^Sender: owner-\/[^@\+\.\/]+
| formail -I X-List-Classify: $MATCH
# librelist.com mailing lists
:0 fhw
* ^List-Id: \/[^@]+@librelist\.(com|org)
{
LISTID=cho $MATCH | sed -e 's/@librelist\.\(com\|org\)//'
:0 fhw
|formail -I X-List-Classify: $LISTID
}
# yahoogroups
:0 fhw
* ^Mailing-List: list \/[^@\.\/]+
| formail -I X-List-Classify: $MATCH
# ezmlm
:0
* ^Mailing-List: contact \/[^@\+\.\/]+
{
LISTID=cho $MATCH | sed -e 's/-help$//'
:0 fhw
| formail -I X-List-Classify: $LISTID
}
Even with that, some things specific required intervention. Some lists have
generic names like 'alerts':
# All of the CERT listnames are generic (e.g. 'alerts') so, just throw
# them all under a single listname that makes sense.
:0 fhw
* ^List-Id: .*us-cert\.gov
| formail -I X-List-Classify: us-cert
Or:
:0 fhw
* ^Reply-To: *Bug [0-9]+ [0-9]+@bugs\.launchpad\.net
| formail -I X-List-Classify: launchpad
Then there was mailing list delivery (after using X-List-Classify to sort):
# Mailing List Delivery {{{
# This is a method/recipe that I ganked from [1]. I liked the idea of
# separating filtering out into 'classicifation' and 'delivery' phases.
#
# Sources
# ---
# [1]: http://aperiodic.net/phil/configs/procmailrc
:0
* ^X-List-Classify: \/[0-9a-z-]+
{
LIST=$MATCH
LOG=[list=$LIST]
# Short-Ciruit {{{
##
# Short-Circuit
# Deal with mailing list emails that should end up in the inbox
# instead of on the mailing list.
#
#
# List management email go to the inbox
:0
* ^Message-ID: mailman
$DEFAULT/
#
# List management emails from ezmlm go to the inbox
:0
* ^Message-ID: [0-9.]+.ezmlm-warn@
$DEFAULT/
#
# zsh-users doesn't match the pattern above, so look for the
# LISTNAME-help pattern
:0
* ^Mailing-List: contact $LIST-help
$DEFAULT/
# }}}
[...]
# For reading.
:0 c
lists.$LIST/
# Prepare for the archive.
:0 fhw
| formail -I Received -I Delivered-To
# Archive locally.
:0
archives.$LIST/
}
# }}}
In general though, I just cut back on most of the mailing lists that I was on
(as I rarely read them all). Now everything just hits my inbox.
Note: This setup is stupidly complex, but it should give you some ideas of what
you can do and some of the general header patterns that some mailing list
software follows. I also clipped out some of the mailing list cleanup recipes I
had (i.e. removing [LIST-NAME] from the subject; compressing strands of Re:s
down to a single one; etc).
--
Brandon Sandrowicz
Re: .procmailrc configurations
On Wed, Jan 23, 2013 at 10:58:37AM +0800, horseriver wrote: hi: How to edit my .procmailrc to put mails from different mail list into different maildir? can this work : :0 * ^to: mutt-users@mutt.org mutt-users@mutt.org Read this: http://www.ii.com/internet/robots/procmail/qs/ Is your mutt directory really named mutt-users@mutt.org? Why? In your recipe, ^to should be ^TO_ -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: .procmailrc configurations
On Wed, Jan 23, 2013 at 10:17:45AM -0700, s. keeling wrote: Incoming from horseriver: How to edit my .procmailrc to put mails from different mail list into different maildir? can this work : :0 * ^to: mutt-users@mutt.org mutt-users@mutt.org .^^^ That should be a file (mbox) or folder (maildir). Otherwise it looks good. Not true. ^to should be ^TO_ -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: .procmailrc configurations
On Wed, Jan 23, 2013 at 01:46:54PM -0700, Robert Holtzman wrote: On Wed, Jan 23, 2013 at 10:58:37AM +0800, horseriver wrote: hi: How to edit my .procmailrc to put mails from different mail list into different maildir? can this work : :0 * ^to: mutt-users@mutt.org mutt-users@mutt.org Read this: http://www.ii.com/internet/robots/procmail/qs/ Is your mutt directory really named mutt-users@mutt.org? Why? In your recipe, ^to should be ^TO_ Thanks! I have modified my procmailrc like this . Then, Need I retrive mails from pop server ? or just restart mutt to see the result? Another question: How does mutt call procmail to sort mails ? In my muttrc file , I have not tell mutt to call procmail to sort mails .so how mutt know that? -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279
Re: .procmailrc configurations
Incoming from horseriver:
On Wed, Jan 23, 2013 at 01:46:54PM -0700, Robert Holtzman wrote:
On Wed, Jan 23, 2013 at 10:58:37AM +0800, horseriver wrote:
How to edit my .procmailrc to put mails from different mail
list into different maildir?
can this work :
:0
* ^to: mutt-users@mutt.org
mutt-users@mutt.org
Read this:
http://www.ii.com/internet/robots/procmail/qs/
Is your mutt directory really named mutt-users@mutt.org? Why?
In your recipe, ^to should be ^TO_
As far as I know, both work. ^TO is special in procmail, but ^to: (as
a regexp) works too.
I have modified my procmailrc like this .
Like what?
Then, Need I retrieve mails from pop server ? or just restart mutt
to see the result?
Too many questions. I used fetchmail to pop mails before. It
supports a keep directive. You can pop and pop and pop, and still
all your mail will be left on the server. Delete the keep from your
config, and they'll be deleted when popped.
Another question: How does mutt call procmail to sort mails ? In
mutt doesn't call procmail. They're separate processes. In my case
(before), fetchmail pops from my ISP's Smarthost, that hands it to local
Mail Delivery Agent (procmail), and mutt picks it up from there once
it's delivered into ~mail.
my muttrc file , I have not tell mutt to call procmail to sort
mails .so how mutt know that?
procmail can sort incoming mails. mutt just looks for them
(mailboxes) once they arrive.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: which 7 other common list headers? (was: Re: .procmailrc)
* Gregor Zattler ([EMAIL PROTECTED]) wrote: Hi Thomas, which 7 other ml headers did you mean? Mailing-List: list Sender: owner- X-BeenThere: Delivered-To: mailing list X-Mailing-List: X-Loop: X-List: X-ML-Name: My full lists.rc is at http://voi.aagh.net/code/lists.rc if you want a real example. It puts messages in lists/listname. Probably also worth adding the rfc2919 List-Id: header or so, although it appears to like to use evil message-id-ish names. -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/ - MONOTONY: Marriage to one woman at a time.
which 7 other common list headers? (was: Re: .procmailrc)
Hi Thomas, * Thomas Hurst [EMAIL PROTECTED] [02. Okt. 2002]: [mailing list filter] Nice generalised solution: :0: * ^Sender: owner-\/[^@]+ lists/`echo $MATCH | sed -e 's/[\/]/_/g'` Repeat for the 7 other common mailing list headers, and you're all done, assuming you don't want to get more fancy with determining the target mailspool. Hmm, i have: Sender and: X-Mailing-List X-BeenThere Delivered-To X-Loop which 7 other ml headers did you mean? Ciao, Gregor -- The future is here. It's just not widely distributed yet. -- William Gibson
Re: .procmailrc
* savanna ([EMAIL PROTECTED]) wrote: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. Nice generalised solution: :0: * ^Sender: owner-\/[^@]+ lists/`echo $MATCH | sed -e 's/[\/]/_/g'` Repeat for the 7 other common mailing list headers, and you're all done, assuming you don't want to get more fancy with determining the target mailspool. -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/ - APL hackers do it in the quad.
Re: .procmailrc: thanks
* Patrick [EMAIL PROTECTED] wrote: * Oliver Fuchs [EMAIL PROTECTED] [09-30-02 18:56]: On Mon, 30 Sep 2002, savanna wrote: A slightly offtopic question - I'm using procmail for my mail filtering, .. You might find this easier/simpler: :0: * ^Sender:.*owner\-mutt\- mutt Thanks everyone for your help - I'll have a play with TO_ and using the ^Sender pattern. -- Savanna | Free as in 'free speech', GnuPG Pub Key E40FAE08 | not 'free beer'. msg31405/pgp0.pgp Description: PGP signature
.procmailrc
A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users An better recipe out there? (procmail recipes aren't my strength). -- Savanna | Free as in 'free speech', GnuPG Pub Key E40FAE08 | not 'free beer'. msg31311/pgp0.pgp Description: PGP signature
Re: .procmailrc
* savanna [EMAIL PROTECTED] [2002-09-30 15:51]: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: [-- snip --] An better recipe out there? I've been using: # Mutt users :0: * ^TO_mutt-users lists/mutt-users And haven't seen any messages pass through. (procmail recipes aren't my strength). They aren't anyone's strength. (darren) -- Although I can accept talking scarecrows, lions, and great wizards of emerald cities, I find it hard to believe there is no paperwork involved when your house lands on a witch.
Re: .procmailrc
On Mon, Sep 30, 2002 at 01:19:54PM +1000, savanna wrote: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users An better recipe out there? (procmail recipes aren't my strength). I'm using this one : :0: * ^TO.*mutt-users(mutt.org|.*gbnet.net) ML/mutt-users search ^TO in procmailrc's man page -- Bernard Massot msg31324/pgp0.pgp Description: PGP signature
Re: .procmailrc
On Mon, 30 Sep 2002 the mental interface of savanna told: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users man procmailrc. search for TO. HTH -- .~. /V\ L I N U X /( )\ Phear the Penguin ^^-^^ msg31327/pgp0.pgp Description: PGP signature
Re: .procmailrc
* at 30. Sep. 2002 wrote savanna: An better recipe out there? (procmail recipes aren't my strength). Yes, i use :0 H * Sender:.*[EMAIL PROTECTED] | rcvstore +Foren/Mutt-Users Bye Michael -- Bash ist zwar nur trocken Brot und Wasser, aber Tcl ist Nutella mit Maggi ;) -- Christian Perle in d.c.o.u.l.m ___ Registered Linux User #228306http://counter.li.org ICQ #151172379
Re: .procmailrc
On Mon, 30 Sep 2002, savanna wrote: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users An better recipe out there? (procmail recipes aren't my strength). An erlier mail by Sven Guckes shows this alternatives: * From: Sven Guckes * Subject: Re: procmail filerting for mutt lists * Date: Fri, 06 Sep 2002 13:22:39 -0700 [...] :0: * ^TO_mutt-(announce|users)(mutt\.org|gbnet\.net) mutt [...] Oliver -- ... don't touch the bang-bang fruit
Re: .procmailrc
On Mon, 30 Sep 2002, savanna wrote: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users An better recipe out there? (procmail recipes aren't my strength). An erlier mail by Sven Guckes shows this alternatives: * From: Sven Guckes * Subject: Re: procmail filerting for mutt lists * Date: Fri, 06 Sep 2002 13:22:39 -0700 [...] :0: * ^TO_mutt-(announce|users)(mutt\.org|gbnet\.net) mutt [...] Oliver -- ... don't touch the bang-bang fruit
Re: .procmailrc
* On Mon, 30 Sep 2002, savanna wrote: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users An better recipe out there? (procmail recipes aren't my strength). :0: * ^Sender: owner-mutt-users@mutt mutt-users Or, to catch both copies if someone CCs you as well as sending to the list: :0: * ^TO_mutt-users mutt-users -- John
Re: .procmailrc
Bernard Massot wrote: I'm using this one : :0: * ^TO.*mutt-users(mutt.org|.*gbnet.net) ML/mutt-users I believe that TO.* is redundant, since there's already a .* built in to ^TO and ^TO_ -- Will Yardley input: william hq . newdream . net .
Re: .procmailrc
On Mon, Sep 30, 2002 at 11:53:10PM +0200, Oliver Fuchs wrote: An erlier mail by Sven Guckes shows this alternatives: * From: Sven Guckes * Subject: Re: procmail filerting for mutt lists * Date: Fri, 06 Sep 2002 13:22:39 -0700 [...] :0: * ^TO_mutt-(announce|users)@(mutt\.org|gbnet\.net) doesn't always works, see message [EMAIL PROTECTED]: To: [EMAIL PROTECTED] -- Bernard Massot msg31373/pgp0.pgp Description: PGP signature
Re: .procmailrc
* Oliver Fuchs [EMAIL PROTECTED] [09-30-02 18:56]: On Mon, 30 Sep 2002, savanna wrote: A slightly offtopic question - I'm using procmail for my mail filtering, just wondering what people are using to catch all of the mutt-users email. I'm currently using: :0 : * ^To:.*(mutt-.*) mutt-users :0 : * ^Cc:.*(mutt-.*) mutt-users :0 : * ^From:.*(mutt-.*) mutt-users An better recipe out there? (procmail recipes aren't my strength). An erlier mail by Sven Guckes shows this alternatives: * From: Sven Guckes * Subject: Re: procmail filerting for mutt lists * Date: Fri, 06 Sep 2002 13:22:39 -0700 [...] :0: * ^TO_mutt-(announce|users)@(mutt\.org|gbnet\.net) mutt [...] You might find this easier/simpler: :0: * ^Sender:.*owner\-mutt\- mutt -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
OT: .procmailrc
Isn't that supposed to be * ^TO_.*@...? Aren't you missing an underscore there? From the procmailrc man page: If the regular expression contains `^TO_' it will be sub stituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X- Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)', which should catch all destination specifications containing a specific address. If the regular expression contains `^TO' it will be sub stituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X- Envelope|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)', which should catch all destination specifications containing a specific word. -- Mike Schiraldi VeriSign Applied Research msg27316/pgp0.pgp Description: PGP signature
pop with mutt and procmailrc
hello, has someone tried procmailrc when you use the pop functionnality of mutt? mutt fetches all my mail in /var/spool/mail/$LOGNAME I made a .forward and .procmailrc checked the permissions of these files I made a small test so if I sent a mail with test in the subject it should go to the test inbox. Well this doesn't happen?? When I check mail with mutt all the mail is in the sppool and I read from the spool. I found out howto save the mail in the right boxes after closing, but i want to filter the mail before that. When I fetch mail with mutt is it possible to use procmail on it, or do I have to use fetchmail(which I hate) Friendly greetings... Geert Theys.
Re: Macro to edit procmailrc?
Andre Bonhote proclaimed on mutt-users that: is there a way to kinda automatically add an entry to my procmailrc from within mutt? someting like this: Try www.spambouncer.org - it keeps updating a set of procmail recipes to stop spam ... or try http://razor.sourceforge.net -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Macro to edit procmailrc?
if what you want is just to send the (previously unfiltered) spam to /dev/null, there is no need to interact with procmail. no, that's not exactly what i want. i'd rather like to have a script/macro/program which can be used to populate my .procmailrc. no matter if it's spam or not! this was actually just an example. it'd be nice to have filtering done from within mutt. right now, when a message arrives, i have to open .procmailrc and edit it by hand. this could be done automatically, i think This also cuts on phone bills, if any. :) no phone bill. btw: what is a phone? thx andr -- Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.
Re: Macro to edit procmailrc?
Andre Bonhote wrote: hi out there i am using mutt 1.2.5i together with fetchmail and procmail. is there a way to kinda automatically add an entry to my procmailrc from within mutt? someting like this: Andre, if what you want is just to send the (previously unfiltered) spam to /dev/null, there is no need to interact with procmail. The right solution is to tell from mutt that, from now on, messages with that (sender, header...) must be destroyed ON THE POP3 server before ever downloading them. This also cuts on phone bills, if any. Look on http://web.tiscalinet.it/marco_web/popfilter.html The scripts and methods there may even be extended to do what you say. Let us know if you modify them. Ciao, Marco Fioretti
Re: Macro to edit procmailrc?
Marco Fioretti proclaimed on mutt-users that: The right solution is to tell from mutt that, from now on, messages with that (sender, header...) must be destroyed ON THE POP3 server before ever downloading them. This also cuts on phone bills, if any. You'd do better to 1. Enable spamfilters on the remote account (very easy if it's a shell account and you can run procmail on it, or your ISP does some spamfiltering / allows you to set your own filters) 2. Put addresses in your local access.db so that fetchmail will reject those mails instead of downloading them 3. Take a few (standard) precautions when posting on usenet / lists Try my article at http://www.pcquest.com/content/linux/100061911.asp -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Macro to edit procmailrc?
hi out there i am using mutt 1.2.5i together with fetchmail and procmail. is there a way to kinda automatically add an entry to my procmailrc from within mutt? someting like this: - mail arrives - ah, it's spam - hit ^k (or something else, of course) - let me decide, what procmail will be looking for (subject, body text) - if subject or from-address is chosen, automatically fill in the content of the actual mail - let me choose a folder - write procmailrc i know, this is quite a lot. but i am almost sure that this is possible with mutt (for mutt is something like fvwm2 to me: there's nothing which CAN'T be done with it :) thanks in advance yours andr -- Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.
Re: Nuking duplicate messages (from Telsa's .procmailrc)
# Nuke duplicate messages :0 Wh: msgid.lock | $FORMAIL -D 8192 msgid.cache This recipe should not be used. It can cause mail loss. Read the _complete_ example in the procmailex man page. Now, this works nicely most of the time but I find that about 50% of postings from mutt-users are coming directly from the authors rather than from the list. I suspect that this is to do with how long the list takes to turn around a message and so I'm receiving the post from the author before I get it from the list. Anyone come across this problem before (I know it's more procmail related than mutt related but us mutterers should be familiar with procmail too! :-). I have no good solution for this. I'm saving duplicates to a folder, and I check the headers to decide which copy to delete. Anyway, shouldn't all of us be using the "L" key to reply to the list rather than reply to all, thereby eliminating this problem in the first place??!! Some people apparently use "g". Even if you specifically say "Please don't carbon copy on replies."
Re: Nuking duplicate messages (from Telsa's .procmailrc)
On 2000.10.16 11:03:17, you, the extraordinary Lars Hecking, opined: (quoting someone) # Nuke duplicate messages :0 Wh: msgid.lock | $FORMAIL -D 8192 msgid.cache This recipe should not be used. It can cause mail loss. Read the _complete_ example in the procmailex man page. Is this also a problem with nodupmail? (http://nodupmail.sourceforge.net/) Cheers, N. -- Nollaig MacKenzie [EMAIL PROTECTED] http://www.amhuinnsuidhe.cx Oppose renaming Mt Logan!! http://www.savemtlogan.com
Re: Nuking duplicate messages (from Telsa's .procmailrc)
Conor Daly [EMAIL PROTECTED] wrote on Sun, 15 Oct 2000: Now, this works nicely most of the time but I find that about 50% of postings from mutt-users are coming directly from the authors rather than from the list. I suspect that this is to do with how long the list takes to turn around a message and so I'm receiving the post from the author before I get it from the list. Actually, you're much more likely to get the copy sent to you directly first, before the list copy. This is because the list server, even if it's quick, can't hope to send the few hundred (or thousand) copies of emails to everyone faster than a single email gets to you. Anyone come across this problem before (I know it's more procmail related than mutt related but us mutterers should be familiar with procmail too! :-). Yes, I've run into this problem too. I don't currently do duplicate filtering, but when I did I remember it being sort of a pain. Anyway, shouldn't all of us be using the "L" key to reply to the list rather than reply to all, thereby eliminating this problem in the first place??!! Well, in fact everyone should be using Mutt, with $followup_to set, $honor_followup_to set to "yes", and then it doesn't matter whether the person doing a reply uses L or g... As long as they're using Mutt. :-) Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / ZAP! Process discontinued. Enter any 12-digit prime number to resume.
