* Togan Muftuoglu (toganm@users.sourceforge.net) [010505 14:34]: }=} }=}export MAIL=$HOME/Mail/incoming under my case do I still export MAIL }=}i as this one if not how do I define the ones like CRM gelecek padi }=}SLE Security I put rules in for each mail box and then after procmail goes through all those rules if it doesn't find a match it drops it in the default which would be ~/Mail/incoming. I general put rules in that look like this: -- # suse fix so that replies go to the list and not to the person. :0f ^X-Mailinglist: suse-linux-e | formail -bfi "Reply-To: SLE " # English Mailing List :0 * ^(To:|Cc:|From:|Re:).*suse-linux-e@suse.(com|de) Suse-linux-e # All other stuff goes directly to Inbox :0 * Incoming -- I think from this you should be able to figure it out. There are more creative rules that you can get into and do..but I don't want your mail bouncing all over the net if something goes wrong ;) Regards, -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.

* Togan Muftuoglu (toganm@users.sourceforge.net) [010505 14:59]: }=}On Sat, May 05, 2001 at 02:50:53PM -0700, Ben Rosenberg wrote: }=}> }=}> # suse fix so that replies go to the list and not to the person. }=}> }=}> :0f }=}> ^X-Mailinglist: suse-linux-e }=}> | formail -bfi "Reply-To: SLE " }=} }=}Why use formail when Mutt can do list reply Because this rule predates Mutt's ability to do this..and I rarely screw with stuff that works ;) Fix once and forget *grin* -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.

Ok I have basicly prepared my procmailrc and would really appreciate if someone can tell me if its Ok or not before I start bombing the net with bouncing messages Thanks in advance -- Togan Muftuoglu Thanks for the first 2 Ben # suse fix so that replies go to the list and not to the person. :0f ^X-Mailinglist: suse-linux-e | formail -bfi "Reply-To: SLE " # English Mailing List :0 * ^(To:|Cc:|From:|Re:).*suse-linux-e@suse.(com|de) Suse # Suse-Security :0 *^(To:|CC:|From:|Re:).*suse-security@suse.(com.de) Suse-Scurity # E-Smith :0 *^(To:|CC:|From:).*phorum-advanced@lists.e-smith.org esmith # KDE TR :0 *^(To:|From:|CC:).*kde-18n-tr@max.tat.physik.uni-tuebingen.de *^(From:|CC:).*gorkem@gelecek.com.tr KDE18TR #XFREE86 :0 *^(From:|To:|CC:).*xpert@xfree86.org) XFree86 #Linux Console :0 *^(To:|From:|CC:).*linuxconsole-dev@lists.sourceforge.net LinuxConsole #Newsletters :0 *^(From:|To:).*@(freshmeat.net|oreillynet.com|mailman.tucows.com) Newsletters #Aspell :0 *^(From:|To:|CC:).*aspell-user@lists.sourceforge.net Aspell #Xine :0 *^(From:|To:|CC:).*xine-user@lists.sourceforge.net Xine #i18n :0 *^(From:|To:|CC:).*i18n@xfree86.org i18n #RC82 :0 *^(To:|From:|CC:).*rc82@yahoogroups.com RC82 #Linux Router :0 *^(To:|From:|CC:).*@linuxrouter.org Router # Securityfocus :0 *^(To:|From:|CC:).*(SECURITY-BASICS|FOCUS-LINUX)@SECURITYFOCUS.COM Security #Applix :0 *^(To:|From:|CC:).*suse-applix@suse.(com|de) *^(To:|From:|CC:).*@vistasource.com Applix #Netfilter :0 *^(To:|From:|CC:).*netfilter-request@lists.samba.org Netfilter #Padi :0 *^(From:|CC:).*@padi.(com|co.uk) padi #CRM :0 *^(From:|To:|CC:).*@crm-forum.com *^(From:|To:|CC:).*@crm-guru.com *^(From:|To:|CC:).*@crminturkey.org *^(From:|To:|CC:).*@adaplatinum.com CRM #Turkce-imla :0 *^(From:|To:|CC:).*turkce-imla@lists.sourceforge.net turkce-imla #snort :0 *^(From:|To:|CC:).*snort-users@lists.sourceforge.net snort #Mediation :0 *^(From:|To:|CC:).*mediation-owner@listbot.com Mediation # # All other stuff goes directly to Inbox :0 * Incoming

Hi Tara,

* ^TO_random-maillist ^ is this with a space intentionlly there or typo

In case no one has pointed you at it, or you haven't found it yourself, man procmailrc is a good read.

Your timing is perfect as I was just reading man procmailrc yet had not came that far. So as you say switching to your example could save me time but I have to make sure it will work then I can always beautify. -- Togan Muftuoglu

On Sun, May 06, 2001 at 02:41:44PM -0400, Tara L Andrews wrote:

I have the spaces in my .procmailrc. I'm not sure whether they're required, but it works with them. I also note that the examples given in `man procmailex` include the spaces.

Ok first test first fail 1) I have placed mda "usr/bin/procmail -d " in the fetchmailrc 2) I have the .procmailrc in my home directory 3) I have set these in my .muttrc set mbox_type=mbox mailboxes =Incoming =Suse =Suse-Security =Xine =KDE18TR =i18n =xfree86 =CRM =padi =esmith =snort =Router =SecurityBasics =Netfilter =turkce-imla =Applix =Mediation set folder=/home/toganm/Mail/ #under Mail directory fcc-hook . $HOME/Mail/Sent Mutt complains /home/toganm/Mail is not a valid mbox procmail does not process anything mail is still going to /var/spool/mail/toganm What am I doing wrong ? -- Togan Muftuoglu

On Mon, May 07, 2001 at 10:22:34AM -0700, Ben Rosenberg wrote:

Hey, no problem. When things work it's all good. Hope you enjoy your setup. :)

I am actually:-) I have gkrellm also set up and I have changed netscape messenger to mutt with the altmail program if I can get it work with konsole rather tahn Xterm I'll feel better since with Xterm for some reason I can not use the arrow keys. The only other minor problem I have is vi everytime I have to type set tw=72 I have added that to my .vimrc but for some reason it does not take effect. Anyhow it is great pleasure to work with emails now -- Togan Muftuoglu