Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 11:26:29PM +1000, Erik Christiansen wrote: # Avoid logging clashes. Separate log records. MAILDIR=/home/erik/mail # Thanks to Bart Schaefer Ruud H.G. van Tol: LOGFILE=$MAILDIR/tmp_log.$$ # - Each process uses a temporary log. FINAL_LOG=$MAILDIR/log# - Append here, via TRAP, at process exit: TRAP='procmail -p DEFAULT=$FINAL_LOG /dev/null $LOGFILE rm -f $LOGFILE' Off-topic, but an easier way to log everything to one file which leaves your TRAP variable free for other purposes is to use a global lockfile so only 1 procmail can run at a time: # Global lockfile LOCKFILE=$PMDIR/globallock Theoretically this could impact performance but I can't imagine anyone receiving enough mail to make this an actual problem on any modern machine. Vincent van Leeuwen Media Design - http://www.mediadesign.nl/
Re: Mutt problem, probably with procmail
On Sat, 13 Sep 2008, Aleksandar D. Balalovski wrote: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks I may be completely off track here (I am using mbox - you seem to be using maildir) but when this particular thing happened to me, it was the fault of postfix. There is a maximum mailbox size setting somewhere in /etc/postfix/main.cf. I have this mailbox_size_limit = 10240 I had changed it to this number from the original value (5120). It drove me nuts because my mailbox size went over 100mb at exactly the same time I had upgraded (or was it changed) my distro. :( ymmv, hth, Sharukh. -- Dr. Sharukh K R Pavri. Mutter Homoeopath, Linuxer. Is there another word for synonym?
Mutt problem, probably with procmail
hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 02:53:08PM +0200, Aleksandar D. Balalovski wrote: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks Why aren't you typing 'mutt' instead of 'mail'?
Re: Mutt problem, probably with procmail
* Aleksandar D. Balalovski [EMAIL PROTECTED] [09-13-08 08:55]: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ and you can use the log files to determine problems in procmail but you need to set the verbosity, ie: VERBOSE=on :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ VERBOSE=off this should place *any* msg to lugola-info-center@anywhere.anyplace in your ~/.Mail/lugola/ directory. DEFAULT setting, $HOME/.Mail/mbox, would put your lugola mail in ~/.Mail/mbox/lugola if anything *would* match your recipe. AND it does not appear that you have told mutt to look for new mail in the lugola directory set mailboxes=lugola you have multiple settings for spoolfile, set spoolfile=+INBOX set spoolfile = ~/.Mail I suggest you spend some time with the fine manual delivered with mutt and at http://mutt.org and for procmail, Nancy McGough's page: http://www.ii.com/internet/robots/procmail/qs/ note: there may be other problems with your configuration as I did not really analyze it very closely. -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 02:53:08PM +0200, Aleksandar D. Balalovski wrote:
hello, I've been using Mutt for half a year now, everything was fine.
Yesterday I changed some of the recipes in procmailrc and since than
fetchmail/procmail won't put the mail in the preferred mailbox. It
puts it in /var/spool/mail/myusername.
To see what procmail is doing, just log its actions, grab a coffee, and
sit down to some reading. I have it permanently enabled, just in case:
# Avoid logging clashes. Separate log records.
MAILDIR=/home/erik/mail # Thanks to Bart Schaefer Ruud H.G. van Tol:
LOGFILE=$MAILDIR/tmp_log.$$ # - Each process uses a temporary log.
FINAL_LOG=$MAILDIR/log# - Append here, via TRAP, at process exit:
TRAP='procmail -p DEFAULT=$FINAL_LOG /dev/null $LOGFILE rm -f $LOGFILE'
If implicated in your recipes, it may be useful to also log some
specifics, such as:
:0 # Unconditionally extract Message-id:
{ MSG_ID=`formail -xMessage-id:` }
LOG=$MSG_ID
:0
{ TO=`formail -xTo:` }
LOG=$TO
If logging is left enabled, it's good to delete or rotate the log file every
few months, when it grows over a few tens of megabytes.
I'll let somone else advise on the mutt side of things. (Mine isn't
involved in mail delivery, and I can't see why it should be, at least
when procmail is in use.)
Erik
--
When one person suffers from a delusion, it is called insanity.
When many people suffer from a delusion, it is called Religion.
-- Robert M. Pirsig in Zen and the Art of Motorcycle Maintenance
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 07:15:42AM -0600, Michael wrote: On Sat, Sep 13, 2008 at 02:53:08PM +0200, Aleksandar D. Balalovski wrote: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks Why aren't you typing 'mutt' instead of 'mail'? My bad. I misunderstood you last statement and what you meant. Sigh Most sorry.
Re: Mutt problem, probably with procmail
++ 13/09/08 09:20 -0400 - Patrick Shanahan: Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ If this would be the recipe you settle with, you should remove the second colon on the first line. The second colon tells procmail to lock the mailbox it wants to write to. This is required for mbox mailboxes, but for maildir mailboxes it is useless (as you never have two processes writing to the same file). -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Mutt problem, probably with procmail
* Rejo Zenger [EMAIL PROTECTED] [09-13-08 15:15]: ++ 13/09/08 09:20 -0400 - Patrick Shanahan: Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ If this would be the recipe you settle with, you should remove the second colon on the first line. The second colon tells procmail to lock the mailbox it wants to write to. This is required for mbox mailboxes, but for maildir mailboxes it is useless (as you never have two processes writing to the same file). Yes, that is correct. I didn't change the recipe to Maildir format until reading his .muttrc and should have removed the unnecessary lock. -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
