list-REPLY: easy, "L". But SAVE to list<-file>? - Mutt

On 23 Feb 2005 12:57:04 -0500, David Combs <dkcombs@panix.com>
wrote:

> The manual makes it quite clear how to *reply* to *only* the
> list: simply use "L" (given that mail-list is listed on "lists"
> line).
>
> But nothing so direct about how to *save* a msg from an
> mailing-list, to a file named for the list.

Hit "s" then "?" and pick the mailbox you want to save it to.

Or "s" then "=" then type in the name of the mailbox.

>
> Now, I saw in some doc, maybe the manual, maybe some other
> piece of (someone's) doc on mutt, that although one could use
> save-hook, he preferred doing it some *other* way.
>
> -------
>
> Please, maybe a tutorial on this subject (saving email) can be
> kludged together from one or more responses to this post -- and
> then that tutorial INSERTED INTO THE MUTT MANUAL.
>

I use procmail to deliver mails from a particular list to their
own mbox, and list that with the mailboxes command:

mailboxes =foolist@foo.net =foo2list@foo2.net

....and invoke Mutt with mutt -y.

They are _already_ saved in their own mailboxes by the time
Mutt sees them.

[ Procmail is also handy here because there are always a few
idiots on every mailing list that Cc a copy of every mail
of theirs to the list to the individual they are replying to,
and I have procmail send these to /dev/null. ]

In my ~/.muttrc, each mailing list is included like so:

lists foolist@foo.net

subscribe foolist@foo.net

For myself, I wish there was a way to *initiate* a post to
a particular list with a keybinding.

AC

In article <tX3Td.3747$MY6.2206@newsread1.news.pas.earthlink.net>,
Alan Connor <xxxx@yyy.zzz> wrote:
>On 23 Feb 2005 12:57:04 -0500, David Combs <dkcombs@panix.com>
>wrote:
>>...
>
>I use procmail to deliver mails from a particular list to their
>own mbox, and list that with the mailboxes command:
>
>mailboxes =foolist@foo.net =foo2list@foo2.net
>
>...and invoke Mutt with mutt -y.
>
>They are _already_ saved in their own mailboxes by the time
>Mutt sees them.
>
>[ Procmail is also handy here because there are always a few
>idiots on every mailing list that Cc a copy of every mail
>of theirs to the list to the individual they are replying to,
>and I have procmail send these to /dev/null. ]
>
>In my ~/.muttrc, each mailing list is included like so:
>
>lists foolist@foo.net
>
>subscribe foolist@foo.net

Thanks so much!

Now, I've never even tried to use procmail (although I did
purhase a book on it).

Maybe you could show how *you* setup procmail, and
by what means it hooks (if it does) to mutt?

Would really be *super* if there were some simple cut-n-paste
scheme by which I could just give a (simple) command or two,
install a (simple) .procmailrc file -- and have everything
just start running, say, the same as before (still use
mutt the same way), and have "s" do the "right" thing
(ie, save to a list-named file).

(Probably I'm just dreaming!)

David

On Tue, 1 Mar 2005 01:50:28 +0000 (UTC), David Combs
<dkcombs@panix.com> wrote:

> In article
> <tX3Td.3747$MY6.2206@newsread1.news.pas.earthlink.net>, Alan
> Connor <xxxx@yyy.zzz> wrote:
>
>>On 23 Feb 2005 12:57:04 -0500, David Combs <dkcombs@panix.com>
>>wrote:
>>
>>>...
>>
>>I use procmail to deliver mails from a particular list to their
>>own mbox, and list that with the mailboxes command:
>>
>>mailboxes =foolist@foo.net =foo2list@foo2.net
>>
>>...and invoke Mutt with mutt -y.
>>
>>They are _already_ saved in their own mailboxes by the time
>>Mutt sees them.
>>
>>[ Procmail is also handy here because there are always a few
>>idiots on every mailing list that Cc a copy of every mail of
>>theirs to the list to the individual they are replying to, and
>>I have procmail send these to /dev/null. ]
>>
>>In my ~/.muttrc, each mailing list is included like so:
>>
>>lists foolist@foo.net
>>
>>subscribe foolist@foo.net
>
> Thanks so much!
>
> Now, I've never even tried to use procmail (although I did
> purhase a book on it).
>
> Maybe you could show how *you* setup procmail, and by what
> means it hooks (if it does) to mutt?
>
> Would really be *super* if there were some simple cut-n-paste
> scheme by which I could just give a (simple) command or two,
> install a (simple) .procmailrc file -- and have everything just
> start running, say, the same as before (still use mutt the
> same way), and have "s" do the "right" thing (ie, save to a
> list-named file).
>
> (Probably I'm just dreaming!)
>
> David
>
>
>

You'll be amazed at how simple it is, David.

Super post:

:-)

First of all, you'll need fetchmail (not Mutt's fetch mail
function; if you are using it, edit it out of your muttrc).

Your basic ~/.fetchmailrc will look like this:


poll pop.isp.whatever
proto pop3
user "you@your.isp"
pass "XXXXX"
is your_login_name here
and wants mda "/usr/bin/formail -ds /usr/bin/procmail
fetchall


Here's your basic ~/.procmailrc:

PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin
SHELL=/bin/sh
MAILDIR=$HOME/Mail
DEFAULT=$MAILDIR/inbox
LOGFILE=$HOME/.proclog
VERBOSE=no

# Switch to VERBOSE=yes if you need to troubleshoot recipes.

# It's usually the Return-Path header that is
# easiest to use to identify mail from a list.

:0
* ^Return-Path:.*list1@list1\.net
list1

# Repeat as needed and put those mailboxes in the mailboxes
# command in your muttrc as per my first post.

# everthing else goes to your inbox

:0
${DEFAULT}

That should be it. Any problems/challenges, post them on
comp.mail.misc.

(Wouldn't want Gven Suckes [whom I greatly admire, actually] to
have a cow!)

I have this alias in my .bashrc:

alias fm='fetchmail && mutt -y'


AC

On Tue, 01 Mar 2005 03:09:45 GMT, Alan Connor <zzzzzz@xxx.yyy> wrote:
>
>
> On Tue, 1 Mar 2005 01:50:28 +0000 (UTC), David Combs
><dkcombs@panix.com> wrote:
>

<snip>

>
> poll pop.isp.whatever
> proto pop3
> user "you@your.isp"
> pass "XXXXX"
> is your_login_name here
> and wants mda "/usr/bin/formail -ds /usr/bin/procmail
> fetchall
>

Oops.

and wants mda "/usr/bin/formail -ds /usr/bin/procmail"

Close parentheses...

(You probably don't need to be told that, but newbies are
reading this thread, or will be, in the Archives.)

<snip>

AC