Re: mutt + procmail + qmail
* Michael P. Soulier [EMAIL PROTECTED] [020911 01:58]: Can I see a filtering example from your .procmailrc? Say, to filter this mailing list? * Johan Almqvist [EMAIL PROTECTED] [2002-09-11 05:46]: No, because the address subscribed to this list is johan-mutt and I have #cat .qmail-mutt ~/Maildir/.mutt/ That's a lot better that filtering based on some header... huh? since when does this list get distributed via johan-mutt? Sven
Re: mutt + procmail + qmail
* Sven Guckes [EMAIL PROTECTED] [020911 13:32]: * Michael P. Soulier [EMAIL PROTECTED] [020911 01:58]: Can I see a filtering example from your .procmailrc? Say, to filter this mailing list? * Johan Almqvist [EMAIL PROTECTED] [2002-09-11 05:46]: No, because the address subscribed to this list is johan-mutt and I have #cat .qmail-mutt ~/Maildir/.mutt/ That's a lot better that filtering based on some header... huh? since when does this list get distributed via johan-mutt? It doesn't. That's not what I'm saying either. What I'm saying is that the address I have subscribed to the list is [EMAIL PROTECTED], so list mail to me gets handled by my .qmail-mutt file. Thus, no need for filtering. HTC, -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: mutt + procmail + qmail
On Wed, Sep 11, 2002 at 10:11:22AM +1000, Iain Truskett wrote: :0: * ^Sender: owner-mutt-(dev|users)mutt.org apps-mutt/ the first line can actually be written as follows: :0 the second colon tells procmail to lock an mbox file which isn't necessary for maildir. -- Peter Abplanalp PGP: pgp.mit.edu msg30867/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
On Wed, Sep 11, 2002 at 01:32:19PM +0200, Sven Guckes wrote: * Johan Almqvist [EMAIL PROTECTED] [2002-09-11 05:46]: No, because the address subscribed to this list is johan-mutt and I have #cat .qmail-mutt ~/Maildir/.mutt/ That's a lot better that filtering based on some header... huh? since when does this list get distributed via johan-mutt? he is talking about the qmail extension addresses. if you use qmail as your mta, you can create infinite extension addresses of the form system-id-extension@domain which correspond to delivery instruction files of the form ~/.qmail-extension. for example, i might have an extension address for the foobar list which is [EMAIL PROTECTED] which corresponds to a ~/.qmail-foobar delivery instruction file much like the one above that tells qmail to drop the mail in my foobar maildir. it is a handy feature of qmail. -- Peter Abplanalp PGP: pgp.mit.edu msg30868/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
* Peter T. Abplanalp [EMAIL PROTECTED] [2002-09-11 13:45]: On Wed, Sep 11, 2002 at 01:32:19PM +0200, Sven Guckes wrote: * Johan Almqvist [EMAIL PROTECTED] [2002-09-11 05:46]: No, because the address subscribed to this list is johan-mutt and I have #cat .qmail-mutt ~/Maildir/.mutt/ That's a lot better that filtering based on some header... huh? since when does this list get distributed via johan-mutt? he is talking about the qmail extension addresses. if you use qmail as your mta, you can create infinite extension addresses of the form system-id-extension@domain which correspond to delivery instruction files of the form ~/.qmail-extension. i know - but obviously i was under the impression that qmail would only use this when the address appears in the address lines (Cc:/To:) - but i was wrong there. i'd have looked it up - but those qmail man pages are not available on this system (or they moved.. whatever). it is a handy feature of qmail. been using it for *years*. (check my webpages! :-) Sven
Re: mutt + procmail + qmail
On Wed, Sep 11, 2002 at 07:44:44AM -0600 or thereabouts, Peter T. Abplanalp wrote: On Wed, Sep 11, 2002 at 01:32:19PM +0200, Sven Guckes wrote: qmail has totally eliminated the need for procmail on my mailserver by using .qmail files. Still use it after poping mail to my box, where Mutt reads it, althought I probably will be switching to maildir on that box too. Mutt is getting a little slow on opening the existing mboxs.. -- Best regards, Gary * Johan Almqvist [EMAIL PROTECTED] [2002-09-11 05:46]: #cat .qmail-mutt ~/Maildir/.mutt/ That's a lot better that filtering based on some header... huh? since when does this list get distributed via johan-mutt? he is talking about the qmail extension addresses. if you use qmail as your mta, you can create infinite extension addresses of the form system-id-extension@domain which which corresponds to a ~/.qmail-foobar delivery instruction file much like the one above that tells qmail to drop the mail in my foobar maildir. it is a handy feature of qmail.
mutt + procmail + qmail
Hey people, I just starting using qmail with Maildir format. I'm a long-time Mutt, Procmail and mbox user. Does anyone have an example .procmailrc file, and .muttrc file, for working with Maildir format? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED], GnuPG pub key: 5BC8BE08 ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to Unix HTML Email Considered Harmful: http://expita.com/nomime.html msg30852/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
* Michael P. Soulier [EMAIL PROTECTED] [020911 01:13]: I just starting using qmail with Maildir format. I'm a long-time Mutt, Procmail and mbox user. Does anyone have an example .procmailrc file, and .muttrc file, for working with Maildir format? # cat ~/.qmail |preline procmail -t ~/.procmailrc # cat ~/.procmailrc DEFAULT=~/Maildir/ #cat ~/.muttrc mailboxes ~/Maildir/ This requires a version of procmail that understands Maildir and an existing Maildir (use maildirmake). Note that procmail has a slightly non-standard way of handling Maildirs (at least the version I'm using...) -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: mutt + procmail + qmail
On 11/09/02 Johan Almqvist did speaketh: # cat ~/.qmail |preline procmail -t ~/.procmailrc # cat ~/.procmailrc DEFAULT=~/Maildir/ #cat ~/.muttrc mailboxes ~/Maildir/ I take it that your other mail folders then would be sub-folders of ~/Maildir? My sysadmin recently told me that was a bad idea. Can I see a filtering example from your .procmailrc? Say, to filter this mailing list? Mike -- Michael P. Soulier [EMAIL PROTECTED], GnuPG pub key: 5BC8BE08 ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to Unix HTML Email Considered Harmful: http://expita.com/nomime.html msg30854/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
* Michael P. Soulier ([EMAIL PROTECTED]) [11 Sep 2002 09:58]: On 11/09/02 Johan Almqvist did speaketh: [...] Can I see a filtering example from your .procmailrc? Say, to filter this mailing list? :0: * ^Sender: owner-mutt-(dev|users)@mutt.org apps-mutt/ Basically, it's just like an mbox line, only you have the slash at the end. It's also important that you create any maildirs rather than just assume procmail will create them. cheers, -- Iain.
Re: mutt + procmail + qmail
- On Tue, 10.Sep.2002, 22:00EDT, Keith R. John Warno uttered: (Every dir below ~/Mail is assumed to be in maildir format; this picks up things like sent-mail and postponed and other fcc locations, so mutt winds up claiming things like 'new mail in =sent-mail' after sending a mail out, but this is OK for me.) Hrmm well actually not for =sent-mail, which is a good thing. But it does alert about 'new mail' in =postponed which is not a bad thing either. :) Ciao, Keith. -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
Re: mutt + procmail + qmail
- On Tue, 10.Sep.2002, 19:58EDT, Michael P. Soulier uttered: On 11/09/02 Johan Almqvist did speaketh: # cat ~/.qmail |preline procmail -t ~/.procmailrc # cat ~/.procmailrc DEFAULT=~/Maildir/ #cat ~/.muttrc mailboxes ~/Maildir/ I take it that your other mail folders then would be sub-folders of ~/Maildir? My sysadmin recently told me that was a bad idea. [snip] Smack your sysadmin. Maildir format, that is 'extended maildir' format, happily allows for nested maildirs. You wind up with structure that looks like: foo/ foo/cur/ foo/new/ foo/tmp/ foo/.bar/ foo/.bar/cur/ foo/.bar/new/ foo/.bar/tmp/ .bar is obviously a 'sub-folder' of foo; extended-maildir-aware mail clients should strip the dot and just show it to you as 'bar'. mutt, from what I've seen, doesn't do this. It shows you verbatim: foo/.bar/, which is fine for me. :) I don't use procmail but rather maildrop which knows about maildirs (extended), along with qmail. My ~/.qmail: $ cat .qmail # simple one-liner |maildrop I've got maildrop delivering to ~/Mail/INBOX/ by default (ie, when no other rule is satisfied). List mail winds up in a structure like: ~/Mail/lists/.mutt/ ~/Mail/lists/.kernel/ ...etc Note that ~/Mail/lists/ is itself a maildir (although I don't use it for receiving mail currently). The ~/.mutt/muttrc contains: set folder=~/Mail set mbox_type=Maildir set spoolfile=~/Mail/INBOX mailboxes `mdirs` `mdirs` is a simple shell script to find all the maildirs: #!/bin/bash # exec find ~/Mail -type d -mindepth 1 \ \( -name tmp -o -name cur -o -name new \ -prune \) \ -o \ \( -type d -mindepth 1 -printf '%p ' \) (Every dir below ~/Mail is assumed to be in maildir format; this picks up things like sent-mail and postponed and other fcc locations, so mutt winds up claiming things like 'new mail in =sent-mail' after sending a mail out, but this is OK for me.) Anyway, good luck! Sorry I don't have any procmail recipes. :/ Regards, Keith.
[Q] mutt with qmail
I like using mutt. Recently I changed the MTA from exim to qmail, and experience a little bit of confusing because it now does not move the read mails to other mailbox. Is there any one who uses qmail with mutt, and lives comfortable? Warm regards to all, Joo-Yung
Re: [Q] mutt with qmail
On Fri, Oct 26, 2001 at 10:32:26PM +0900, YOON, Joo-Yung wrote: I like using mutt. Recently I changed the MTA from exim to qmail, and experience a little bit of confusing because it now does not move the read mails to other mailbox. What do you mean by that? Is there any one who uses qmail with mutt, and lives comfortable? Yes. It works fine. What can be a problem is queueing outgoing mail. Nothing else. /magnus
Re: mutt and qmail: child exited 127
On Tue, Oct 10, 2000 at 11:29:30PM +0200, Horacio MG wrote: hmmm ... i've had problems with this when mutt was using the wrong sendmail binary (= or i've forgotten to replace the OEM sendmail with a link to qmail's sendmail binary. make sure that /usr/sbin/sendmail is a link to /var/qmail/bin/sendmail (or whereever you installed qmail) and try again. Both /usr/sbin/sendmail and /usr/libexec/sendmail/sendmail are symlinks to /var/qmail/bin/sendmail If you are running OpenBSD 2.7, then you shouldn't replace /usr/sbin/sendmail, as it will get overwritten the next time you upgrade it with a 'make build' from source. Instead, place relevant entries in /etc/mailer.conf to point the sendmail wrapper (mailwrapper) to the correct place for qmail. This could be the cause of your exec problem. Check that the symlinks are in place, and if not, read mailer.conf(5) I use the following /etc/mailer.conf on OpenBSD-current: sendmail/var/qmail/bin/sendmail send-mail /var/qmail/bin/sendmail mailq /var/qmail/bin/qmail-qread newaliases /usr/bin/true hoststat/usr/bin/true purgestat /usr/bin/true -- Anil Madhavapeddy, [EMAIL PROTECTED]
mutt and qmail: child exited 127
I've compiled and installed the latest version of mutt on OpenBSD 2.7. The MTA I'm using is qmail 1.03. I use fetchmail to retrieve the mail, and procmail to deliver it. I set both procmail and mutt to use maildir instead of mbox (it seems that mutt won't recognize the mbox style messages since they lack a from field on the first line). I can send mail through the 'mail' command, but if I try to send from the mutt compose menu, I get this warning Error sending message, child exited 127 (Exec error.). when i press y to send. i read the mailing list archives looking for this error, and i found some directions like upgrading to the latest procmail (which i did) and installing mutt after installing/configuring qmail (so i recompiled and reinstalled). but i still get the same error. Could anyone help with this, please? TIA. more info (well, in my latest build I didn't enable exact_address, nor pop or gnu_regex, nor did I used compressed): $ mutt -v Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: OpenBSD 2.7 [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE +EXACT_ADDRESS +ENABLE_NLS +COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. -- Horacio Anno MMDCCLIII A.U.C. [EMAIL PROTECTED]Valencia - ESPAÑA Key fingerprint = F4EE AE5E 2F01 0DB3 62F2 A9F4 AD31 7093 4233 7AE6
Re: mutt and qmail: child exited 127
hmmm ... i've had problems with this when mutt was using the wrong sendmail binary (or i've forgotten to replace the OEM sendmail with a link to qmail's sendmail binary. make sure that /usr/sbin/sendmail is a link to /var/qmail/bin/sendmail (or whereever you installed qmail) and try again. -- michael On Tue, 10 Oct 2000, Horacio MG wrote: I've compiled and installed the latest version of mutt on OpenBSD 2.7. The MTA I'm using is qmail 1.03. I use fetchmail to retrieve the mail, and procmail to deliver it. I set both procmail and mutt to use maildir instead of mbox (it seems that mutt won't recognize the mbox style messages since they lack a from field on the first line). I can send mail through the 'mail' command, but if I try to send from the mutt compose menu, I get this warning Error sending message, child exited 127 (Exec error.). when i press y to send. i read the mailing list archives looking for this error, and i found some directions like upgrading to the latest procmail (which i did) and installing mutt after installing/configuring qmail (so i recompiled and reinstalled). but i still get the same error. Could anyone help with this, please? TIA. more info (well, in my latest build I didn't enable exact_address, nor pop or gnu_regex, nor did I used compressed): $ mutt -v Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: OpenBSD 2.7 [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE +EXACT_ADDRESS +ENABLE_NLS +COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. -- Horacio Anno MMDCCLIII A.U.C. [EMAIL PROTECTED] Valencia - ESPAÑA Key fingerprint = F4EE AE5E 2F01 0DB3 62F2 A9F4 AD31 7093 4233 7AE6
Re: mutt and qmail: child exited 127
On 10 Oct 2000, at 23:29, Horacio MG wrote: Both /usr/sbin/sendmail and /usr/libexec/sendmail/sendmail are symlinks to /var/qmail/bin/sendmail I've even tried to change the muttrc line set sendmail="/usr/lib/sendmail -oi -oem -f [EMAIL PROTECTED]" to others more suitable... could this be related? Hi, I don't use qmail, but the first thing I would check is that qmail's /var/qmail/bin/sendmail actually supports all the options you are passing it. In particular, I would verify that the -f option is supported. If it isn't, then this could be why you are getting a child exited 127 error. -Harold -- "Life sucks, deal with it!"
Re: mutt and qmail: child exited 127
Horacio MG [EMAIL PROTECTED] wrote on Tue, 10 Oct 2000: Both /usr/sbin/sendmail and /usr/libexec/sendmail/sendmail are symlinks to /var/qmail/bin/sendmail I've even tried to change the muttrc line set sendmail="/usr/lib/sendmail -oi -oem -f [EMAIL PROTECTED]" I use qmail and I use simply: set sendmail="/var/qmail/bin/qmail-inject" This works just fine. However, the sendmail wrapper should work just as well, so I'm not sure if this will actually fix anything for you. You're not meant to have the -oi -oem things on the sendmail wrapper command line though, I think they're not supported by qmail's wrapper (although I forget, and the wrapper is unfortunately not well documented). I would recommend trying something like "cat /tmp/file" as the $sendmail command in Mutt, and then see if you can send mail from the command line: "sendmail a@recipient -f your@address /tmp/file" That's actually the same as what Mutt is doing, so maybe you can reproduce the problem on the command line too. Harold Oga [EMAIL PROTECTED] wrote on Tue, 10 Oct 2000: I don't use qmail, but the first thing I would check is that qmail's /var/qmail/bin/sendmail actually supports all the options you are passing it. In particular, I would verify that the -f option is supported. If it isn't, then this could be why you are getting a child exited 127 error. qmail does support -f for both qmail-inject and the sendmail wrapper, I'm fairly sure of that. Hope this helps, Mikko PS. Please use the address [EMAIL PROTECTED] when posting to the list, not the @gbnet.net address, thanks. -- // 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 / Driver's mantra: To slow is to falter, to brake is to fail, to stop is defeat.
Mutt and Qmail problems
Good evening,
I've installed q-mail,vpopmail but actually i haven't any virtualdomain
on my LAN.
I've followed the installation istruction and then i've tried qmail.
I send a mail by MUTT from a user("Ghisu") that is the postmaster to
another user("Elena"). Naturally both are on the same PC that is called
EDVX.But there is a problem. It seems that Mutt or Qmail cannot find the
host. Have you got any idea where can be the error?
SYS:
LINUX release RedHat6.2
Apache Web server
qmail 1.03
vpopmail 4.8.9
qmailadmin 0.35
sqwebmail 1.00
MUTT 1.2.5
This is the mail that the postmaster received:
Delivered-To: ghisu@EDVX
Delivered-To: postmaster@EDVX
Date: 20 Sep 2000 08:05:28 -
From: MAILER-DAEMON@EDVX
To: postmaster@EDVX
Subject: failure notice
Hi. This is the qmail-send program at EDVX.
I tried to deliver a bounce message to this address, but the bounce
bounced!
[EMAIL PROTECTED]:
Sorry, I couldn't find any host named EDVX.EDVX. (#5.1.2)
--- Below this line is the original bounce.
Return-Path:
Received: (qmail 1339 invoked for bounce); 20 Sep 2000 08:05:28 -
Date: 20 Sep 2000 08:05:28 -
From: MAILER-DAEMON@EDVX
To: [EMAIL PROTECTED]
Subject: failure notice
- - 1/1: MAILER-DAEMON@EDVX failure notice
Hi. This is the qmail-send program at EDVX.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
[EMAIL PROTECTED]:
Sorry, I couldn't find any host named EDVX.EDVX. (#5.1.2)
--- Below this line is a copy of the message.
Return-Path: [EMAIL PROTECTED]
Received: (qmail 1337 invoked by uid 518); 20 Sep 2000 08:05:27 -
Date: Wed, 20 Sep 2000 10:05:27 +0200
From: ghisu [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: prova
Message-ID: 2920100527.A1331@EDVX
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Thanks a lot
Re: Mutt and Qmail problems
Hello,
Stefano Ghisolfi [EMAIL PROTECTED] wrote on Wed, 20 Sep 2000:
I've followed the installation istruction and then i've tried qmail.
I send a mail by MUTT from a user("Ghisu") that is the postmaster to
another user("Elena"). Naturally both are on the same PC that is called
EDVX.But there is a problem. It seems that Mutt or Qmail cannot find the
host. Have you got any idea where can be the error?
Yes, this is a qmail configuration issue, not related to Mutt.
Since I'm writing, I can give you my take on the problem and a possible
fix.
[EMAIL PROTECTED]:
Sorry, I couldn't find any host named EDVX.EDVX. (#5.1.2)
qmail doesn't consult /etc/hosts, it only uses DNS for delivery.
EDVX.EDVX isn't a valid hostname, so it can't be delivered to.
But because you get this error message, it means that qmail is already
treating that domain as a remote domain. You can get around that by
placing "EDVX.EDVX" in the /var/qmail/control/locals file.
Hope this helps. If you need more help, I suggest you read the various
qmail documents if you haven't already, and then try asking on the qmail
list.
Regards,
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 /
If it weren't for the last minute, nothing would get done.
Re: Mutt and Qmail problems
Have you set up your /etc/hosts properly? I had about the same problem with Sendmail and this was because Sendmail ALWAYS queries the DNS first. Since I don't have my own DNS-server, I had to put this in my /etc/sendmail.cf: O ServiceSwitchFile=/etc/service.switch The /etc/service.switch file contains: hosts files aliases files The word "files" means to look in /etc/hosts. Sorry, but I don't have any experiences with Qmail, but I thought the problem my just be more or less the same. -- Wouter Verheijen [EMAIL PROTECTED] - If Microsoft built cars, the Linux community would make a car that was powered by the sun, was reliable, twice as fast, and available freely - but only 5 percent of the people would use it. PGP signature
Re: Mutt and Qmail problems
Yes, i think the problem is here. Qmail doesn't look at /etc/hosts. I think that I should configure a DNS server on my own PC on the LAN. I'll try it. Bye Thanks Stefano - Original Message - From: "Wouter Verheijen" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 20, 2000 6:56 PM Subject: Re: Mutt and Qmail problems Have you set up your /etc/hosts properly? I had about the same problem with Sendmail and this was because Sendmail ALWAYS queries the DNS first. Since I don't have my own DNS-server, I had to put this in my /etc/sendmail.cf: O ServiceSwitchFile=/etc/service.switch The /etc/service.switch file contains: hosts files aliases files The word "files" means to look in /etc/hosts. Sorry, but I don't have any experiences with Qmail, but I thought the problem my just be more or less the same. -- Wouter Verheijen [EMAIL PROTECTED] - If Microsoft built cars, the Linux community would make a car that was powered by the sun, was reliable, twice as fast, and available freely - but only 5 percent of the people would use it.
'Maildir/' vs. 'Maildir' (was: Re: mutt and qmail)
Timothy Legant muttered: On Thu, Aug 31, 2000 at 12:10:31PM -0700, Jason Helfman wrote: don't you find the file structure of this just horrid though? My (shortened) 'subscribe' and 'mailboxes' lines are as follows. Note that there are no references to ./cur or ./new or ./tmp. subscribe qmail mutt-users freebsd-stable mailboxes +Inbox +Bedtime +Qmail +Mutt-Users +FreeBSD-STABLE When I hit cTab, Mutt shows me the top-level Maildiers, 'Inbox', 'Bedtime', etc. Interessting, with 1.2.5i I see 'Maildir/' and 'mbox' is there any folder_format expando I am missing? I would prefere to have Maildirs displayed the same way as mboxes just to not mix them with 'normal' dirs. TIA, Michael -- Staff meeting in the conference room in %d minutes. PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: 'Maildir/' vs. 'Maildir' (was: Re: mutt and qmail)
Michael Tatge [EMAIL PROTECTED] wrote on Sat, 02 Sep 2000: Interessting, with 1.2.5i I see 'Maildir/' and 'mbox' is there any folder_format expando I am missing? I would prefere to have Maildirs displayed the same way as mboxes just to not mix them with 'normal' dirs. Not that I know of, Maildir folders will always have that trailing / because they are dirs, after all. I suppose it would be nice if Mutt auto-detected and indicated in the directory listing which files and directories are in fact recognised mail folders, however doing that might be potentially time-consuming. Of course, if the folder is listed in a "mailboxes" command, then it can be assumed to be a folder and there is no need to check, but you can see a list of the "mailboxes" folders with ctabtab anyway. There's quite a few things in the directory/folder browser that could be improved, but many of them are potentially time-consuming, so they should all be optional. If anyone ever thinks of doing them... :-) Regards, 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 / 2B OR NOT 2B == FF
Re: mutt and qmail
On Thu, Aug 31, 2000 at 12:10:31PM -0700, Jason Helfman wrote:
don't you find the file structure of this just horrid though?
To be perfectly honest, I don't ever see the structure during normal
use. The *only* time I have to think about it is when I write a script
that manipulates the files in those directories (./cur, primarily).
My (shortened) 'subscribe' and 'mailboxes' lines are as follows. Note
that there are no references to ./cur or ./new or ./tmp.
subscribe qmail mutt-users freebsd-stable
mailboxes +Inbox +Bedtime +Qmail +Mutt-Users +FreeBSD-STABLE
When I hit cTab, Mutt shows me the top-level Maildiers, 'Inbox',
'Bedtime', etc.
The only time I can imagine you'd notice the directory structure is if
you read your mail with /usr/bin/more!
On the other hand, what you don't see is what gives the advantages so
ably detailed by Charles and Mikko in other responses (thanks guys!).
It's just a choice; it's not the end of the world either way. For me, I
live in an apartment where the landlord turns the power off at random
intervals to "fix" things. I'd rather not lose the mail and Maildirs
can guarantee that.
To have new/ tmp/ cur/ for every mailing list? I would like to and would
perfer to use maildir for the mailing lists, I don't know why...
What shows up in Mutt is the normal index, with mail that is in the
./new directory threaded appropriately and marked with a 'N'. You don't
see ./new, ./cur or ./tmp. So, ultimately, who cares?
What are the advantages to this... I have all my mailing lists still
The advantages have been explained in other messages (Charles and
Mikko). I won't make this long message even longer repeating them.
going to mbox, whereas anything that doesn't pass through the filters
goes to Maildir format. I would like to see the scripts that you have in
both procmail and your backing procedure.
Sure. My $HOME/.qmail file reads:
| preline /usr/local/bin/procmail
A snippet from the message list recipes:
:0
* ^TO_qmail
Qmail/
:0
* ^TO.*stable
FreeBSD-STABLE/
:0
* ^TO_mutt-users
Mutt-Users/
Notice that, again, there is no reference to ./new, ./cur or ./tmp. This
is because procmail, as of version 3.14, delivers to Maildirs - it
understands how to move messages into ./new. It identifies destination
Maildirs by the trailing '/' on the folder name.
Finally, here's a very simple script I run from cron (around 3am Monday
mornings, IIRC) that just copies messages older than 3 weeks into a
gzipped tar with the same name as the Maildir. You may have noticed I
always capitalize my Maildirs - the script uses that assumption to
generate the list of Maildirs to archive ([A-Z]*). For any use other
than personal, this could be cleaned up/enhanced a lot. Anyhow, for what
it's worth...
#!/bin/sh
# mailarc.sh
tmpdir=$HOME/tmp/temp$$
mkdir $tmpdir
cd $HOME/Mail
for mdir in [A-Z]* ; do
/usr/bin/find $mdir/cur -mtime +21 -exec /bin/mv {} $tmpdir/ \;
archive=$HOME/Mail/archive/$mdir.tar
if [ -f $archive.gz ] ; then
createorappend=r ;
/usr/bin/gunzip $archive.gz ;
else
createorappend=c ;
fi
/usr/bin/tar -$createorappend -f $archive --directory $tmpdir .
/usr/bin/gzip $archive
rm -f $tmpdir/*
done
rmdir $tmpdir
I find this system quite workable. As always, YMMV :-)
Tim
--
Tim Legant
[EMAIL PROTECTED]
Re: mutt and qmail
don't you find the file structure of this just horrid though? To have new/ tmp/ cur/ for every mailing list? I would like to and would perfer to use maildir for the mailing lists, I don't know why... What are the advantages to this... I have all my mailing lists still going to mbox, whereas anything that doesn't pass through the filters goes to Maildir format. I would like to see the scripts that you have in both procmail and your backing procedure. On Thu, Aug 31, 2000 at 01:03:19AM -0500, Timothy Legant muttered: | On Tue, Aug 29, 2000 at 10:48:38PM -0600, Vincent Danen wrote: | I've finally taken the plunge and put qmail on my personal system after | having used it on my server forever. I've got a rather strange mix | here and some odd errors... | | Cool! | | As others have noted, you can deliver to Maildirs directly from | procmail. The suggestions I've seen simply make the default delivery go | to your spool, which is a Maildir (named Maildir). | | As another option, you can make each of your mailing lists use a Maildir | for delivery. I do this and am quite happy with procmail and Mutt's | behavior. The clue for procmail is that the delivery instruction needs | to end with a '/' (no quotes). | | I have a $HOME/Mail directory with a number of Maildir subdirectories, | such as Mutt-Users, Inbox, etc. to which procmail directs the incoming | mail. The qmail command 'maildirmake' will create these for you. The 'c' | command in Mutt works perfectly, taking me to Maildirs with new mail and | correctly marking the New messages. | | The value of this is that using a simple bash or perl script run once | weekly from cron, you can move all files older than a certain date | (since each email is in a separate file) to an temporary directory, tar | and gzip or [insert your favorite archiver here] and archive these | things. If you want to get a little fancier, each time the script runs | it can update a master archive file, either per list or 1 gigantic | thing. The file-oriented nature of Maildirs makes this trivial. | | Just another example of qmail/procmail/Mutt flexibility... | | Tim | -- | Tim Legant | [EMAIL PROTECTED] -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: mutt and qmail
Jason Helfman [EMAIL PROTECTED] wrote: don't you find the file structure of this just horrid though? To have new/ tmp/ cur/ for every mailing list? I would like to and would perfer to use maildir for the mailing lists, I don't know why... What are the advantages to this... Maildirs are safe for multiple concurrent writers and readers simultaneously, with no file locking, even over NFS -- so you can't corrupt a Maildir by having it open for writing by your MUA and the MDA which tries to stick a new message in it, etc. Not needing file locks is also good for performance on busy maildirs. Charles -- -- Charles Cazabon [EMAIL PROTECTED] QCC Communications Corporation Saskatoon, SK My opinions do not necessarily represent those of my employer. --
Re: mutt and qmail
Are there any other advantages with this setup? On Thu, Aug 31, 2000 at 01:28:07PM -0600, Charles Cazabon muttered: | Jason Helfman [EMAIL PROTECTED] wrote: | don't you find the file structure of this just horrid though? | | To have new/ tmp/ cur/ for every mailing list? I would like to and would | perfer to use maildir for the mailing lists, I don't know why... | | What are the advantages to this... | | Maildirs are safe for multiple concurrent writers and readers simultaneously, | with no file locking, even over NFS -- so you can't corrupt a Maildir by | having it open for writing by your MUA and the MDA which tries to stick a | new message in it, etc. Not needing file locks is also good for | performance on busy maildirs. | | Charles | -- | -- | Charles Cazabon [EMAIL PROTECTED] | QCC Communications Corporation Saskatoon, SK | My opinions do not necessarily represent those of my employer. | -- -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: mutt and qmail
Jason Helfman [EMAIL PROTECTED] wrote: Are there any other advantages with this setup? You mean, besides not silently corrupting your stored and incoming mail, and being higher-performance, working over NFS properly, and generally behaving properly? No, no advantages at all. Yes, this is sarcasm. Charles | Jason Helfman [EMAIL PROTECTED] wrote: | don't you find the file structure of this just horrid though? | | To have new/ tmp/ cur/ for every mailing list? I would like to and would | perfer to use maildir for the mailing lists, I don't know why... | | What are the advantages to this... | | Maildirs are safe for multiple concurrent writers and readers simultaneously, | with no file locking, even over NFS -- so you can't corrupt a Maildir by | having it open for writing by your MUA and the MDA which tries to stick a | new message in it, etc. Not needing file locks is also good for | performance on busy maildirs. -- -- Charles Cazabon [EMAIL PROTECTED] QCC Communications Corporation Saskatoon, SK My opinions do not necessarily represent those of my employer. --
Re: mutt and qmail
Jason Helfman [EMAIL PROTECTED] wrote on Thu, 31 Aug 2000: To have new/ tmp/ cur/ for every mailing list? So what? It's 3 extra dirs, it's not like any modern computer will likely run out of inodes or disk space with current disk sizes... Normally, it's all hidden by the application anyway. What are the advantages to this... Other than what's been listed, Maildirs also allow for each per-message handling by external scripts. You don't need to detect message boundaries like in mbox. For some situations, that's a big simplification. But if you don't tend to write your own tools (scripts, perl stuff, etc. etc.) then you likely won't care. But I would consider it an advantate of Maildirs, in a general sense... And oh, deleting or otherwise modifying a message from/in a large Maildir folder is fast, whereas from mbox if you delete the first message the whole file has to be re-written. On average, half of the folder has to be re-written back to disk (of course, you usually operate on the last few messages, so statistically it might not be even half...) But this is contrasted by the slower opening time for large Maildir folders, as compared against mbox. Overall, I'd say the NFS/no-locking issue is the biggest and perhaps only reason which should be considered for a normal user, when choosing whether to use Maildir or not. Regards, 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 / "Attitude is more important than reality"
Re: mutt and qmail
On Tue, Aug 29, 2000 at 10:48:38PM -0600, Vincent Danen wrote: I've finally taken the plunge and put qmail on my personal system after having used it on my server forever. I've got a rather strange mix here and some odd errors... This is what my log looks like when I send out a message: [Log] The hostname on this machine is devel.danen.net, but I don't understand where this "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" stuff is coming from. Any ideas? I'm calling qmail like this: set sendmail="/var/qmail/bin/qmail-inject" That should work fine. (With and without the -f option). I would suggest to insert the SMTP logging tool. Details are in the life with qmail document. Then you should be able to see all the stuff sent by mutt. Did you disable the delivery status notification? HTH Frank -- Frank Derichsweiler
Re: mutt and qmail
On Tue, Aug 29, 2000 at 10:48:38PM -0600, Vincent Danen muttered: | I've finally taken the plunge and put qmail on my personal system after | having used it on my server forever. I've got a rather strange mix | here and some odd errors... | not sure about this | This is what my log looks like when I send out a message: | | @400039ac8fb70cda2b34 new msg 190666 | @400039ac8fb70cdaa834 info msg 190666: bytes 773 from [EMAIL PROTECTED] |qp 24619 uid 501 | @400039ac8fb70dc7f24c starting delivery 229: msg 190666 to local |failure,[EMAIL PROTECTED] | @400039ac8fb70dc9cedc status: local 1/10 remote 0/20 | @400039ac8fb70dcd12cc starting delivery 230: msg 190666 to remote |[EMAIL PROTECTED] | @400039ac8fb7113cc204 delivery 231: failure: |Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ | @400039ac8fb71140679c status: local 2/10 remote 0/20 | @400039ac8fb712bd33fc delivery 232: failure: |Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ | | The hostname on this machine is devel.danen.net, but I don't understand | where this "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" | stuff is coming from. Any ideas? /var/qmail/control files | | I'm calling qmail like this: | | set sendmail="/var/qmail/bin/qmail-inject" | as am i | I'm specifying the Return-Path: header in every message that goes out. | I would use qmail-inject -f except that I write from about 3-4 | different email accounts and I need to be able to send from each one | (which I use macros to setup). | | I also have a problem delivering to my Maildirs. I use procmail and | have my .qmail look like this: | | | preline /usr/bin/procmail | | procmail works awesome... it filters everything like it used to, but it | still delivers to /var/spool/mail/vdanen. I need it to deliver to | ~/Maildir/ or (at the very least) to ~/mail/inbox because I also use my to do this you need to set /etc/profile up as well.. add/modify lines: MAIL="/home/$USER/Maildir/" MAILDIR="/home/$USER/Maildir/" | laptop mounted via nfs to this machine and I need to have everything | sitting in my home directory so that when I fire up mutt on the laptop | it doesn't try to look in /var/spool/mail/vdanen on that machine. | | I tried using safecat with the following .procmailrc: | | | #:0 | #|maildir MAILDIR this is my last procmail recipe :0 $HOME/Maildir/ | | I tried using the last recipe which is something mentioned on the | safecat website. I assumed that since procmail works from top to | bottom, it would filter everything into the maildir. It doesn't seem | to be doing this. it should filter anything that does pass through the heirarchial ladder to the last filter, that would put it into Maildir format | | I know this is a lot of questions all in one message but any help would | be appreciated. I can send mail fine (but I get those silly bounce | messages), and I can receive mail fine (just not in Maildirs). | | Thanks a million in advance. | sure.. i've done this a few times, and have gotten pretty good about teching it myself, so talk to me offline if you have further issues/... | -- | [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net | // Danen Consulting Serviceswww.danen.net, www.freezer-burn.org | // MandrakeSoft, Inc. www.linux-mandrake.com | 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD | | Current Linux uptime: 8 days 8 hours 12 minutes. -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: mutt and qmail
Jim Breton [EMAIL PROTECTED] wrote on Wed, 30 Aug 2000: set sendmail="/var/qmail/bin/qmail-inject" Hmm.. I'm not sure where all that stuff is coming from... but (someone correct me if I'm wrong) I don't believe you can use the typical sendmail command syntax with qmail-inject. For the record, having set sendmail="qmail-inject" is just fine. It's true that qmail-inject doesn't really work the exact same way as sendmail, or even the qmail sendmail replacement, however the usage is similar enough that it will work just fine with Mutt. Even the -f switch to set sender address is supported by qmail-inject. On the other hand, there should be no harm in using the qmail sendmail replacement, either... Regards, 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 / Living on Earth includes an annual free trip around the Sun.
Re: mutt and qmail
On Wed Aug 30, 2000 at 08:11:51AM +0200, Frank Derichsweiler wrote: The hostname on this machine is devel.danen.net, but I don't understand where this "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" stuff is coming from. Any ideas? I'm calling qmail like this: set sendmail="/var/qmail/bin/qmail-inject" That should work fine. (With and without the -f option). I would suggest to insert the SMTP logging tool. Details are in the life with qmail document. Then you should be able to see all the stuff sent by mutt. Did you disable the delivery status notification? I did now... we'll see how it works. I noticed that dsn_notify is set to "failure,delay" and dsn_return is set to "hdrs"... these look familiar... =) Let's see if I get some bounce messages when I send this message out... -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net // Danen Consulting Serviceswww.danen.net, www.freezer-burn.org // MandrakeSoft, Inc. www.linux-mandrake.com 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux uptime: 8 days 19 hours 41 minutes.
Re: mutt and qmail
On Wed Aug 30, 2000 at 12:27:45AM -0700, Jason Helfman wrote: | The hostname on this machine is devel.danen.net, but I don't understand | where this "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" | stuff is coming from. Any ideas? /var/qmail/control files Nothing about that in there. The control files just say localhost and devel.danen.net... (which is correct) | I'm calling qmail like this: | | set sendmail="/var/qmail/bin/qmail-inject" | as am i Good to hear... =) | I also have a problem delivering to my Maildirs. I use procmail and | have my .qmail look like this: | | | preline /usr/bin/procmail | | procmail works awesome... it filters everything like it used to, but it | still delivers to /var/spool/mail/vdanen. I need it to deliver to | ~/Maildir/ or (at the very least) to ~/mail/inbox because I also use my to do this you need to set /etc/profile up as well.. add/modify lines: MAIL="/home/$USER/Maildir/" MAILDIR="/home/$USER/Maildir/" I had MAILDIR in there, but I didn't change MAIL. I've changed that now. | I tried using safecat with the following .procmailrc: | | | #:0 | #|maildir MAILDIR this is my last procmail recipe :0 $HOME/Maildir/ This works! I guess it makes safecat somewhat useless for me... =) | I tried using the last recipe which is something mentioned on the | safecat website. I assumed that since procmail works from top to | bottom, it would filter everything into the maildir. It doesn't seem | to be doing this. it should filter anything that does pass through the heirarchial ladder to the last filter, that would put it into Maildir format Yup. This totally works. Thank you! | I know this is a lot of questions all in one message but any help would | be appreciated. I can send mail fine (but I get those silly bounce | messages), and I can receive mail fine (just not in Maildirs). | | Thanks a million in advance. | sure.. i've done this a few times, and have gotten pretty good about teching it myself, so talk to me offline if you have further issues/... I think it's all fixed up now... I appreciate the help! -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net // Danen Consulting Serviceswww.danen.net, www.freezer-burn.org // MandrakeSoft, Inc. www.linux-mandrake.com 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux uptime: 8 days 19 hours 47 minutes.
Re: mutt and qmail
On Wed Aug 30, 2000 at 07:32:35AM +, Jim Breton wrote: I'm calling qmail like this: set sendmail="/var/qmail/bin/qmail-inject" Hmm.. I'm not sure where all that stuff is coming from... but (someone correct me if I'm wrong) I don't believe you can use the typical sendmail command syntax with qmail-inject. In fact, DJB provides the /var/qmail/bin/sendmail binary (it wraps qmail-inject IIRC) for exactly this purpose. So you will want to use that as your "sendmail" setting for mutt. Or, make a symlink to it into /usr/sbin/sendmail and use that. You shouldn't need to do this. I know because I've used qmail-inject on the wife's machine (which uses qmail) and it works fine. We just have a few configuration differences, (ie. I passed the -f on her config cuz she only uses one email address). I'm specifying the Return-Path: header in every message that goes out. I would use qmail-inject -f except that I write from about 3-4 different email accounts and I need to be able to send from each one (which I use macros to setup). I also filter my mail into different folders, and then use folder-hooks in my .muttrc to change the From address, Return-Path, etc... just another way to do the same thing. :) Gotta love mutt's flexibility... =) I also have a problem delivering to my Maildirs. I use procmail and have my .qmail look like this: | preline /usr/bin/procmail procmail works awesome... it filters everything like it used to, but it still delivers to /var/spool/mail/vdanen. I need it to deliver to ~/Maildir/ or (at the very least) to ~/mail/inbox because I also use my I haven't used procmail or Mutt with Maildirs yet (still using regular mboxes for now) but mine was also trying to deliver to /v/s/m/ until I defined $DEFAULT in my .procmailrc. DEFAULT=$HOME/Maildir/ may do the trick. The procmail that comes with Debian supports Maildirs, I'm going to take a wild guess ;) that you're using Mandrake and that it also will deliver to Maildirs... I'm not sure how the code works, but I think it looks for the existence of the tmp new and cur subdirs so make sure they exist if it is supposed to work and still doesn't. I added :0 $HOME/Maildir/ at the end of the config and it works awesome now. But I imagine that setting DEFAULT may accomplish the same thing. -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net // Danen Consulting Serviceswww.danen.net, www.freezer-burn.org // MandrakeSoft, Inc. www.linux-mandrake.com 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux uptime: 8 days 20 hours 3 minutes.
Re: mutt and qmail
On Tue, Aug 29, 2000 at 10:48:38PM -0600, Vincent Danen wrote: I've finally taken the plunge and put qmail on my personal system after having used it on my server forever. I've got a rather strange mix here and some odd errors... Cool! As others have noted, you can deliver to Maildirs directly from procmail. The suggestions I've seen simply make the default delivery go to your spool, which is a Maildir (named Maildir). As another option, you can make each of your mailing lists use a Maildir for delivery. I do this and am quite happy with procmail and Mutt's behavior. The clue for procmail is that the delivery instruction needs to end with a '/' (no quotes). I have a $HOME/Mail directory with a number of Maildir subdirectories, such as Mutt-Users, Inbox, etc. to which procmail directs the incoming mail. The qmail command 'maildirmake' will create these for you. The 'c' command in Mutt works perfectly, taking me to Maildirs with new mail and correctly marking the New messages. The value of this is that using a simple bash or perl script run once weekly from cron, you can move all files older than a certain date (since each email is in a separate file) to an temporary directory, tar and gzip or [insert your favorite archiver here] and archive these things. If you want to get a little fancier, each time the script runs it can update a master archive file, either per list or 1 gigantic thing. The file-oriented nature of Maildirs makes this trivial. Just another example of qmail/procmail/Mutt flexibility... Tim -- Tim Legant [EMAIL PROTECTED]
mutt and qmail
I've finally taken the plunge and put qmail on my personal system after
having used it on my server forever. I've got a rather strange mix
here and some odd errors...
This is what my log looks like when I send out a message:
@400039ac8fb70cda2b34 new msg 190666
@400039ac8fb70cdaa834 info msg 190666: bytes 773 from [EMAIL PROTECTED] qp
24619 uid 501
@400039ac8fb70dc7f24c starting delivery 229: msg 190666 to local
failure,[EMAIL PROTECTED]
@400039ac8fb70dc9cedc status: local 1/10 remote 0/20
@400039ac8fb70dcd12cc starting delivery 230: msg 190666 to remote
[EMAIL PROTECTED]
@400039ac8fb70dceb4c4 status: local 1/10 remote 1/20
@400039ac8fb70dd83274 starting delivery 231: msg 190666 to local [EMAIL PROTECTED]
@400039ac8fb70dda034c status: local 2/10 remote 1/20
@400039ac8fb70dddef34 starting delivery 232: msg 190666 to local
[EMAIL PROTECTED]
@400039ac8fb70ddfc7dc status: local 3/10 remote 1/20
@400039ac8fb70e2010e4 starting delivery 233: msg 190666 to local [EMAIL PROTECTED]
@400039ac8fb70e21f15c status: local 4/10 remote 1/20
@400039ac8fb70f958274 delivery 230: success:
209.115.163.67_accepted_message./Remote_host_said:_250_ok_967610148_qp_20216/
@400039ac8fb70f9e44a4 status: local 4/10 remote 0/20
@400039ac8fb71132a42c delivery 229: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400039ac8fb7113985e4 status: local 3/10 remote 0/20
@400039ac8fb7113cc204 delivery 231: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400039ac8fb71140679c status: local 2/10 remote 0/20
@400039ac8fb712bd33fc delivery 232: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400039ac8fb712bd66c4 status: local 1/10 remote 0/20
@400039ac8fb712fa4c9c delivery 233: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400039ac8fb712fa7794 status: local 0/10 remote 0/20
@400039ac8fb7148ee2d4 bounce msg 190666 qp 24630
@400039ac8fb7149445bc end msg 190666
The hostname on this machine is devel.danen.net, but I don't understand
where this "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]"
stuff is coming from. Any ideas?
I'm calling qmail like this:
set sendmail="/var/qmail/bin/qmail-inject"
I'm specifying the Return-Path: header in every message that goes out.
I would use qmail-inject -f except that I write from about 3-4
different email accounts and I need to be able to send from each one
(which I use macros to setup).
I also have a problem delivering to my Maildirs. I use procmail and
have my .qmail look like this:
| preline /usr/bin/procmail
procmail works awesome... it filters everything like it used to, but it
still delivers to /var/spool/mail/vdanen. I need it to deliver to
~/Maildir/ or (at the very least) to ~/mail/inbox because I also use my
laptop mounted via nfs to this machine and I need to have everything
sitting in my home directory so that when I fire up mutt on the laptop
it doesn't try to look in /var/spool/mail/vdanen on that machine.
I tried using safecat with the following .procmailrc:
## Set to on when debugging
VERBOSE=on
## Set Procmail directory for logs, etc.
PMDIR=$HOME/Procmail
MAIL=$HOME/mail
## Set shell
SHELL=/bin/bash
## Set line buffer
LINEBUF=4096
## Set location for formail
FORMAIL=/usr/bin/formail
## Remove # when debugging; set to no if you want nothing logged
LOGABSTRACT=all
## Set logfile
LOGFILE=$PMDIR/log
## Replace $HOME/Msgs with your message directory
## mutt and elm use $HOME/Mail; pine uses $HOME/mail
MAILDIR=$HOME/mail
# Recipies ##
## Create backup cache of 100 most recent messages
#:0 c
#backup/.
# :0 ic
# | cd $MAIL/backup rm -f dummy `ls -t msg.* | sed -e 1,100d`
## Nuke duplicate messages
:0 Wh: .msgid.lock
| formail -D 8192 .msgid.cache
## Regenerate "From" lines to make sure they are valid
:0 fhw
| formail -I "From " -a "From "
# Add a "Content-Type: application/pgp" header so Mutt will know the mail
# is encrypted
:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
:0 fBw
* ^--BEGIN PGP MESSAGE--
* ^--END PGP MESSAGE--
| formail -i "Content-Type: application/pgp; format=text; x-action=encrypt"
:0 fBw
* ^--BEGIN PGP SIGNED MESSAGE--
* ^--BEGIN PGP SIGNATURE--
* ^--END PGP SIGNATURE--
| formail -i "Content-Type: application/pgp; format=text; x-action=sign"
}
# Mailing Lists
## Linux Mandrake Cooker mailing list
:0:
* (^To.*|cc:.*)[EMAIL PROTECTED]
mdk-changelog
:0:
* (^Reply-To:.*|^TO_|cc:.*)[EMAIL PROTECTED]
mdk-cooker
## Linux Mandrake Expert mailing list
:0:
* (^Reply-To:.*|^TO_|cc:.*)[EMAIL PROTECTED]
mdk-expert
## Linux Mandrake Security Discussions mailing list
:0:
* (^Reply-To:.*|^TO_|cc:.*)[EMAIL PROTECTED]
mdk-security
## Linux Mandrake Security Announcements mailing list
:0:
*
Re: mutt and qmail
Jason Helfman [EMAIL PROTECTED] wrote on Fri, 14 Apr 2000: looking into qmail options, is their anything I should know ahead of time in regards to the way mutt reads files/folders/configs...? Well, IIRC qmail uses flock *only* as the locking mechanism, so you should configure Mutt to use that as well. This is, of course, only relevant with incoming mbox folders. If you use qmail you might be better off with Maildir anyway. Other than that, there's no other issues really. You may want to look at the man page for qmail-inject for means of setting up the Return Path (envelope sender) info. Also, I use just the plain setting "set sendmail=qmail-inject" for Mutt. Hope this helps, 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 / Microsoft is not the answer. Microsoft is the question. Linux is the answer.
mutt and qmail
looking into qmail options, is their anything I should know ahead of time in regards to the way mutt reads files/folders/configs...? --- /helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private!
Re: mutt and qmail
Jason -- ...and then Jason Helfman said... % looking into qmail options, is their anything I should know ahead of % time in regards to the way mutt reads files/folders/configs...? We use qmail for our MTA, and I simply had to update to set sendmail="/var/qmail/bin/sendmail -oem -oi" in my .muttrc file -- but my mail-by-pager script needed $qmail = "/var/qmail/bin/qmail-inject"; # how to give to qmail? $qmailargs = '[EMAIL PROTECTED]'; # any args? open (QMAIL, "|$qmail $qmailargs $pager");# hand off to qmail for some reason; calling sendmail (before even getting to the -f flag) always bombed. Does qmail want to deliver to any special format, like the dreaded mbx, or just drop into mbox files like it does for me? % % --- % /helfman % "At any given moment, you may find the ticket to the circus that has % always been in your possession." % % Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 % GnuPG http://www.gnupg.org Get Private! :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: mutt with Qmail
Subba Rao [EMAIL PROTECTED] wrote on Sun, 10 Oct 1999: Is anyone using this combination, on their Linux system? I am. Works great. :-) Qmail is delivering the mail to ~/Maildir, as it is supposed to. I want to read the mail. How do I configure mutt to read these notes? Well, there are many ways to do it. I set my MAIL environment variable: MAIL=~/Mail/INBOX (You would, naturally, use MAIL=~/Maildir) Another way would be to use the $spoolfile variable in your .muttrc, set spoolfile=~/Maildir But I think it's better to make sure the MAIL variable is pointing to the right place. 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 / ==/==/==/== Police tagline ==/==/== Do not cross ==/==/==/==
