Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
I looked at a mbox that was entirely created under Ubuntu and there are blank lines at the end of each message before the From line. On Sat, Mar 23, 2013 at 03:28:29PM +, Chris Green wrote: > On Sun, Mar 24, 2013 at 01:22:56AM +1100, Erik Christiansen wrote: > > On 23.03.13 12:40, Chris Green wrote: > > > Well I first actually tried it and saw no blank line. > > > > > > I've now looked throught my archive (1845 mailboxes) and most of them, > > > saved with mutt, using S[ave], seem *not* to have a blank line either. > > > There are some with blank lines between but I suspect that's because of > > > migrating back and forth between various formats quite a lot over the > > > years. > > > > That is weird, because I'm using: > >Mutt 1.5.21+145 (2a1c5d3dd72e) (2012-12-30) > > but have used a whole string of older mutts over the years. And I've > > never made (or heard of) a related config setting which could explain > > the behavioural difference. > > > > > Certainly my current mutt 1.5.21 doesn't put a blank line in there and > > > it's quite standard from the Ubuntu repositories (though I suppose they > > > *might* have done something funny to it). > > > > So your mailboxes, viewed in vim or similar, have the /^From / line > > immediately following the last non-blank line of the previous message!!? > > That's something I've never seen ... in decades, mostly with mutt. > > > Here, I've just sent myself three test E-Mails and have saved them to a > mailbox called test, here is the result:- > > From MAILER-DAEMON Sat Mar 23 15:19:20 2013 > Return-Path: > X-Original-To: chris > Delivered-To: ch...@zbmc.eu > Received: by chris.zbmc.eu (Postfix, from userid 1000) > id 94F62380255; Sat, 23 Mar 2013 15:19:20 + (GMT) > Date: Sat, 23 Mar 2013 15:19:20 + > From: Chris Green > To: Chris Green > Subject: Test > Message-ID: <20130323151920.GC10234@chris> > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.21 (2010-09-15) > Content-Length: 31 > Lines: 3 > > This is test 3 > > -- > Chris Green > From MAILER-DAEMON Sat Mar 23 15:18:53 2013 > Return-Path: > X-Original-To: chris > Delivered-To: ch...@zbmc.eu > Received: by chris.zbmc.eu (Postfix, from userid 1000) > id B4267380255; Sat, 23 Mar 2013 15:18:53 + (GMT) > Date: Sat, 23 Mar 2013 15:18:53 + > From: Chris Green > To: Chris Green > Subject: Test1 > Message-ID: <20130323151853.GA10234@chris> > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.21 (2010-09-15) > Status: O > Content-Length: 31 > Lines: 3 > > This is test 1 > > -- > Chris Green > From MAILER-DAEMON Sat Mar 23 15:19:06 2013 > Return-Path: > X-Original-To: chris > Delivered-To: ch...@zbmc.eu > Received: by chris.zbmc.eu (Postfix, from userid 1000) > id 12196380255; Sat, 23 Mar 2013 15:19:06 + (GMT) > Date: Sat, 23 Mar 2013 15:19:06 + > From: Chris Green > To: Chris Green > Subject: Test2 > Message-ID: <20130323151905.GB10234@chris> > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.21 (2010-09-15) > Status: O > Content-Length: 31 > Lines: 3 > > This is test 2 > > -- > Chris Green > > > I saved them separately (i.e. I didn't do a tag-save), nothing else > special at all, as you can see I didn't save them in the order I > sent them. > > 'mutt -v' returns:- > > chris$ mutt -v > Mutt 1.5.21 (2010-09-15) > Copyright (C) 1996-2009 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: Linux 3.5.0-26-generic (x86_64) > ncurses: ncurses 5.9.20110404 (compiled with 5.9) > libidn: 1.25 (compiled with 1.25) > hcache backend: tokyocabinet 1.4.47 > Compile options: > -DOMAIN > +DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL > -USE_FLOCK > +USE_POP +USE_IMAP +USE_SMTP > -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS > +HAVE_GETADDRINFO > +HAVE_REGCOMP -USE_GNU_REGEX > +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET > +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM > +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME > +CRYPT_BACKEND_GPGME > -EXACT_ADDRESS -SUN_ATTACHMENT > +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS > +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR > +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
[- Sun 24.Mar'13 at 7:05:44 + Brian Salter-Duke :-] > I looked at a mbox that was entirely created under Ubuntu and there are > blank lines at the end of each message before the From line. I can confirm that my sent mbox, created by mutt (current version), also has a blank line at the end of each message. This is not Ubuntu OS, it's OpenBSD, but the OS shouldn't be relevent. So I don't think it's a "mutt" issue. The other mboxes, created by procmail, also show the correct format: with a blank line at the end of each message before the From: line of the proceeding message. It looks as though your python delivery program might be doing this? Have you tried taking the python program out of the process to test, to see if the messages are being appended to the mbox correctly? I know you've looked at it again and maybe made some changes to it. Jamie -- James Griffin: jmz at kontrol.kode5.net jmzgriffin at gmail.com A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote: > > It looks as though your python delivery program might be doing this? > Have you tried taking the python program out of the process to test, to > see if the messages are being appended to the mbox correctly? I know > you've looked at it again and maybe made some changes to it. > How could the python delivery program have anything to do with it? I simply s[aved] three messages using the mutt save command, no other program is involved, mutt is simply writing three messages to the same mbox. Are you all sure that mutt isn't simply saving what it's provided with by the incoming MDA? If the *delivered* message ends with a blank line (i.e. what's in the inbox) then what mutt saves will end with a blank line. To do exactly what I did:- Deliver some messages to a mbox file. Check that there is *no* blank line at the end of these messages. Use mutt to s[ave] (or c[opy]) the messages to another mbox. Look at the new mbox file. I think you'll find there's no added blank line. -- Chris Green
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 06:48:25PM +, Chris Green wrote: > On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote: > > > > It looks as though your python delivery program might be doing this? > > Have you tried taking the python program out of the process to test, to > > see if the messages are being appended to the mbox correctly? I know > > you've looked at it again and maybe made some changes to it. > > > How could the python delivery program have anything to do with it? > > I simply s[aved] three messages using the mutt save command, no other > program is involved, mutt is simply writing three messages to the same > mbox. > > Are you all sure that mutt isn't simply saving what it's provided with > by the incoming MDA? > > If the *delivered* message ends with a blank line (i.e. what's in the > inbox) then what mutt saves will end with a blank line. > > To do exactly what I did:- > > Deliver some messages to a mbox file. > > Check that there is *no* blank line at the end of these messages. > > Use mutt to s[ave] (or c[opy]) the messages to another mbox. > > Look at the new mbox file. > > I think you'll find there's no added blank line. When I use the mutt (on Solaris 11) copy function to copy three messages in an existing mbox file to an new mbox file I see a blank line before each new message's "From " line except for the first message. Maybe it's time to break out the debugging tools on your end? -- Will Fiveash
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 02:29:09PM -0500, Will Fiveash wrote: > On Sun, Mar 24, 2013 at 06:48:25PM +, Chris Green wrote: > > On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote: > > > > > > It looks as though your python delivery program might be doing this? > > > Have you tried taking the python program out of the process to test, to > > > see if the messages are being appended to the mbox correctly? I know > > > you've looked at it again and maybe made some changes to it. > > > > > How could the python delivery program have anything to do with it? > > > > I simply s[aved] three messages using the mutt save command, no other > > program is involved, mutt is simply writing three messages to the same > > mbox. > > > > Are you all sure that mutt isn't simply saving what it's provided with > > by the incoming MDA? > > > > If the *delivered* message ends with a blank line (i.e. what's in the > > inbox) then what mutt saves will end with a blank line. > > > > To do exactly what I did:- > > > > Deliver some messages to a mbox file. > > > > Check that there is *no* blank line at the end of these messages. > > > > Use mutt to s[ave] (or c[opy]) the messages to another mbox. > > > > Look at the new mbox file. > > > > I think you'll find there's no added blank line. > > When I use the mutt (on Solaris 11) copy function to copy three messages > in an existing mbox file to an new mbox file I see a blank line before > each new message's "From " line except for the first message. Maybe > it's time to break out the debugging tools on your end? > Yes, but did you look in the "existing mbox file" to see if there were blank lines betweeen the messages there? -- Chris Green
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 07:36:13PM +, Chris Green wrote: > On Sun, Mar 24, 2013 at 02:29:09PM -0500, Will Fiveash wrote: > > On Sun, Mar 24, 2013 at 06:48:25PM +, Chris Green wrote: > > > On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote: > > > > > > > > It looks as though your python delivery program might be doing this? > > > > Have you tried taking the python program out of the process to test, to > > > > see if the messages are being appended to the mbox correctly? I know > > > > you've looked at it again and maybe made some changes to it. > > > > > > > How could the python delivery program have anything to do with it? > > > > > > I simply s[aved] three messages using the mutt save command, no other > > > program is involved, mutt is simply writing three messages to the same > > > mbox. > > > > > > Are you all sure that mutt isn't simply saving what it's provided with > > > by the incoming MDA? > > > > > > If the *delivered* message ends with a blank line (i.e. what's in the > > > inbox) then what mutt saves will end with a blank line. > > > > > > To do exactly what I did:- > > > > > > Deliver some messages to a mbox file. > > > > > > Check that there is *no* blank line at the end of these messages. > > > > > > Use mutt to s[ave] (or c[opy]) the messages to another mbox. > > > > > > Look at the new mbox file. > > > > > > I think you'll find there's no added blank line. > > > > When I use the mutt (on Solaris 11) copy function to copy three messages > > in an existing mbox file to an new mbox file I see a blank line before > > each new message's "From " line except for the first message. Maybe > > it's time to break out the debugging tools on your end? > > > Yes, but did you look in the "existing mbox file" to see if there were > blank lines betweeen the messages there? If I edit an mbox file and remove the blank line preceding each "From ", run mutt on that mbox and have it save all the messages to an mbox it creates I see no blank lines preceding "From " in the new mbox. So you are correct in that mutt does not add a blank line. This mutt behavior hasn't been a problem for me because all my incoming mail is put into mbox files via fetchmail->procmail which appears to add the blank line. -- Will Fiveash
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 19:36:13 +, Chris Green wrote: > Yes, but did you look in the "existing mbox file" to see if there were > blank lines betweeen the messages there? For what it's worth, I took a simple test message, saved it into a new mailbox, and then used vi to make four copies of the message. I removed the Content-Length: and Lines: header lines from all four copies, and the trailing blank line from two of the copies. When I opened up this mbox file using "mutt -f" and saved each message to a new mailbox (in various orders), I found that the presence-or-not of a trailing blank line was preserved in the copies. I got the same results from these tests with both with a "current" version of mutt, v1.5.21 from the Ubuntu Precise package, and a "very old" one, v1.5.9i from the Debian Sarge package. So... it does appear that Mutt will preserve whatever trailing-blank- line situation was originally created by the MDA, even as it saves the messages into new mailboxes (and that it doesn't actually care what convention was used by other messages previously found in the mailbox being appended to). Nathan
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 03:28:28PM -0500, Will Fiveash wrote: > > > When I use the mutt (on Solaris 11) copy function to copy three messages > > > in an existing mbox file to an new mbox file I see a blank line before > > > each new message's "From " line except for the first message. Maybe > > > it's time to break out the debugging tools on your end? > > > > > Yes, but did you look in the "existing mbox file" to see if there were > > blank lines betweeen the messages there? > > If I edit an mbox file and remove the blank line preceding each "From ", > run mutt on that mbox and have it save all the messages to an mbox it > creates I see no blank lines preceding "From " in the new mbox. So you > are correct in that mutt does not add a blank line. This mutt behavior > hasn't been a problem for me because all my incoming mail is put into > mbox files via fetchmail->procmail which appears to add the blank line. > Exactly! So mutt *doesn't* add a blank line before the 'File ' if there wasn't one there already, in fact it doesn't do anything except copy what it's given by the MDA. This may be correct in that mutt isn't an MDA but it isn't what everyone here has being trying to tell me! :-) -- Chris Green
Re: Is it supposed to be possible to deliver mail while mutt has the mbox open?
On Sun, Mar 24, 2013 at 05:53:05PM -0400, Nathan Stratton Treadway wrote: > > So... it does appear that Mutt will preserve whatever trailing-blank- > line situation was originally created by the MDA, even as it saves the > messages into new mailboxes (and that it doesn't actually care what > convention was used by other messages previously found in the mailbox > being appended to). > Yes, exactly right, mutt just keeps what it's given but it *doesn't* add the "blank line before 'From '" itself. -- Chris Green
Mutt side/browsing is slow
Hi, I got mutt setup with offlineimap with MailDir and I'm having a blast getting more control over my inbox again. Things are pretty good overall but I got this weird slowness when navigating the sidebar. It takes ~.5 to 2 seconds for it to go up or down a line in the sidebar. And now that I'm checking it also seem to happen in mutt main index view of messages. Any idea why it is so slow to navigate up and down ? Thanks, -- /max http://about.me/maxandersen
Better folder navigation ?
With ~250 nested folders the 'c' change folder is rather tedious to use. Is there a command to search for a folder by name so I don't have to type/complte in the full name ? Or is it somehow possible to write a macro that uses find shell command to locate list of possible folders and then have me choose the right one ? Thanks, /max
