Another pain of maildir
How can you save a message in a findable and readable format if you're using maildir? I have a message in my sentmail folder that I want to save as a text file so I can use it elsewhere. So I save the message from mutt as 'fred' and the result is a horrible maildir folder with the message buried somewhere in it as a file with an unmentionable name, aarrgghh!! If I was using mbox the file would be called fred in the place where I saved it. -- Chris Green
Re: Another pain of maildir
Re: Eur Ing Chris Green 2007-03-15 <[EMAIL PROTECTED]> > How can you save a message in a findable and readable format if you're > using maildir? Half an hour ago on #mutt: 12:54 how can i store an email as a textfile? 12:55 explicitly 12:57 s~/file.txt 12:57 or C~/file.txt 12:58 's' would mark the mail for deletion, 'C' would not. 12:58 thx ft 12:58 you're welcome. 12:59 although it creates a maildir :) but at least i don't have to search through 100s of mails ;) 13:00 mmh, and the umlauts get screwed up, sometimes i wish i had mutt running localhost :D i'm trying to print the mail :p 13:01 ':set mbox_type=mbox' should help with the maildir creation. 13:01 but i do have my mails in maildirs 13:02 so do I. 13:02 kk 13:03 'mbox_type' is the default type used when mutt tries to _create_ a mailbox. 13:06 Personally, I got fdm, which fetches my mails and sorts them into mailboxes. And if I want mutt to create a mailbox, I want it to create a mbox. So, that's fine for me. If your setup needs mutt to create maildirs, you'll have to create a macro, that sets mbox_type, saves the mail and resets 'mbox_type'. The other way is to go to 'v'iew attachments and 's'ave the body from there. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: forwarding messages with attachments
* Derek Martin [2007.03.14 19:30]: > I consider this to be utterly and completely > broken, and I'm considering reporting it as a > bug, but I'm waiting to see what other people > think. >From my limited understanding, when a message is mime-encoded, the *whole body* is a set of attachments, including what you refer to as the body, which is the part you composed before sending the message. So when you set mime_forward=yes, it's *consistent* to put the body of the original message as an attachment. I agree it's annoying, because we, as users, distinguish between the body and the attachments. But, and again if I'm wrong somebody correct me, mime doesn't make that distinction. So the behavior you (and I) want is actually a special case where you want the *first* attachment to be quoted but not the others, regardless of their mime type. Note that the behavior is perfectly ok when the attachments are not of type text/*. I guess what we need is a bit of control into the "heuristics" mutt uses to determine whether or not to quote the message when forwarding/replying. Note also that mutt is not *always* consistent. For example when in the attach menu, if there are multiple text attachments and I press "e" to edit the message, I get only the part I composed. Not the text attachments. I agree with Gary this is not a bug, but would be a nice feature. -- JR
Re: Another pain of maildir
On Thu, Mar 15, 2007 at 01:35:36PM +0100, Christoph Berg wrote: > Re: Eur Ing Chris Green 2007-03-15 <[EMAIL PROTECTED]> > > How can you save a message in a findable and readable format if you're > > using maildir? > 13:01 ':set mbox_type=mbox' should help with the maildir creation. > 13:01 but i do have my mails in maildirs > 13:02 so do I. > 13:02 kk > 13:03 'mbox_type' is the default type used when mutt tries to _create_ a > mailbox. right... :set mbox_type=mbox and then reset if you want to create new mailboxes as Maildir. > The other way is to go to 'v'iew attachments and 's'ave the body from > there. Or "e" (edit) the message, and then save in your editor. w
howto convert Mbox to Mh
Hi, I seek a solution to convert from Mbox to Mh : -a) /var/mail/$USER => " Mbox /Mbx " -b) $HOME/Mail/Mh. what is the best way : -a) use Procmail to convert -b) use mutt to read and stock the message kindest regard bernard
Re: howto convert Mbox to Mh
On Thu, Mar 15, 2007 at 11:25:04PM +0100, [EMAIL PROTECTED] wrote: > > I seek a solution to convert from Mbox to Mh : > > -a) /var/mail/$USER => " Mbox /Mbx " > -b) $HOME/Mail/Mh. > > > what is the best way : > > -a) use Procmail to convert > -b) use mutt to read and stock the message It's pretty easy in mutt - tag all messages, set mbox_type to mh, and save. Haven't tested this with mh, but works great converting between Maildir and mbox. You could also look at mailutil, which is part of the UW IMAP and Pine distribution. See also this FAQ entry, which looks outdated but might help: http://www.faqs.org/faqs/mail/mh-faq/part1/section-11.html w
Re: forwarding messages with attachments
On Thu, Mar 15, 2007 at 12:51:55PM -0400, Jean-Rene David wrote: > * Derek Martin [2007.03.14 19:30]: > > I consider this to be utterly and completely > > broken, and I'm considering reporting it as a > > bug, but I'm waiting to see what other people > > think. > > From my limited understanding, when a message is > mime-encoded, the *whole body* is a set of > attachments, including what you refer to as the > body, which is the part you composed before > sending the message. It's not the encoding that I care about... it's the behavior of Mutt as I'm responding to the mail. When READING a mime-encoded message, mutt essentially treats the first plain text attachment as the message body, and does the right thing. However, when FORWARDING such a message, it does not treat this same attachment as a message body that you can respond to. How it gets encoded after I'm done with it is really irrelevant to me. The second issue is that it actually does include the HEADERS of the message in the editable body, along with the usual ---forwarded message--- blah blah... but it does not include the actual message body. I think that's definitely a bug, on both counts. If you're not going to give me the original body, what possible reason would I have for wanting the headers in the body? Including them goes against every reasonable standard for how to quote e-mail messages... If you're not sure what I mean, send yourself a message with attachments, and put something in the body. Then set mime_forward, and forward the message to yourself, and look at the message you get. I can't see any use case for the results being desirable. it's just plain yucky. CCing mutt-dev, since it seems this discussion needs to go there instead of here. Please REMOVE mutt-users if you reply. Thanks -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail. Sorry for the inconvenience. Thank the spammers. pgpxHQFpfP6HO.pgp Description: PGP signature
