Help configuring procmail (was: Help configuring fetchmail)

[Brian Densmore]

Also, I think you could use this to capture mail from kclug
(although I haven't tested it and it may be slightly wrong):

:0: *
^Delivered To: * kclug at kclug.org
.kclug/

If you just wanted to do the single thing. I really didn't grok
Jeremy's snippet. I understand what it's doing and why, but I
still have a really hard time reading string processing syntax
and mapping into an actual example of what it translate to.
And I don't like using things I can't easily modify to use to
a different purpose. I suppose it's time I took a shell string
processing class. Actually it's just the "\/[^@]+" and the 
"/[\/]/_/g'`" that confuse me.


> -----Original Message-----
> From: Jeremy Turner 
> 
> 
> On Fri, October 15, 2004 10:38 am, linux at bizniche.com said:
> > To: KCLUG<kclug at kclug.org>
> > Envelope-To: linux at bizniche.com
> >
> > That makes for easy filtering...either by the kclug addy, or by the
> > Envelope-To address, which would be more comprehensive it seems.
> >
> > When I use fetchmail to get the same message, I see:
> > To: KCLUG<kclug at kclug.org>
> > Envelope-To: mdg at localhost
> >
> > So, when that 'Envelope-To' changes, I lose any idea (from 
> the headers)
> > as to what address it was fetched from.  There is no more record of
> > linux at bizniche.com anywhere.
> 
> Here's a question: for a mailing list, do you care what 
> mailbox/address it
> came in as?  Consider the following procmailrc snippet:
> 
>   #  Used by the perl6-all list to break out into seperate mailboxes
>   :0:
>   * ^X-Mailing-List-Name: \/[^@]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   #  Majordomo uses Sender header to tell when it is coming from
>   :0:
>   * ^Sender: owner-\/[^@]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   :0:
>   * ^X-BeenThere: \/[^@]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   :0:
>   * ^Delivered-To: mailing list \/[^@]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   :0:
>   * ^X-Mailing-List: <\/[^@]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   :0:
>   * ^X-Loop: \/[^@]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   :0:
>   * ^X-List-ID: <\/[^@\.]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
>   :0:
>   * ^X-list: \/[^@\.]+
>   lists/`echo $MATCH | sed -e 's/[\/]/_/g'`
> 
> This procmailrc tries to identify mailing lists (mailman, 
> Yahoo groups,
> etc) by using various headers that they use.  You can subscribe to new
> lists, and it would automatically create the new folder for you.
> 
> For your multi-mailbox setup you could have a structure 
> something like:
> 
> INBOX
> INBOX.mailacct1
> INBOX.mailacct1.somefolder
> INBOX.mailacct2
> INBOX.mailacct2.somefolder
> INBOX.mailacct3
> INBOX.mailacct3.somefolder
> INBOX.lists
> INBOX.lists.kclug
> 
> Is this something of what you're looking for?
> 
> Jeremy
> 
> -- 
> Jeremy Turner <jeremy at linuxwebguy.com>
> Linux Tips and News! ---> http://linuxwebguy.com
> 
> _______________________________________________
> Kclug mailing list
> Kclug at kclug.org
> http://kclug.org/mailman/listinfo/kclug
>