Re: mark_old friends
Quoting Andre Klärner (kan...@ak-online.be): So my final question is: How do I get mutt to consider old and new mail the same. For as far as i know the short answer is: you can't. I do the same as you, create maildir folders on the fly, need to restart mutt to find these new folders - but this also triggers my folderhook script so i don't really mind. I also read my mail on my phone, messages i 'mark as unread' in the phone client are shown as 'O'ld mail in mutt and do not pop up as 'N' or 'O' on the mailbox overview. I have 'set nomark_old' in my configs. Does anyone have an idea how I could achieve this? I've gotten used to the way it is. ;-) -Sndr. -- | Not one shred of evidence supports the notion that life is serious. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 signature.asc Description: Digital signature
resend
Due to a misconfiguration in my mail server, I sent several messages that were not delivered but were sent back to me enclosed in a failure notification . Now that I have fixed the problem I want to send those messages again. What is the best procedure to do it? Does mutt have something similar to the emacs function 'rmail-retry-failure' to strip away the failure notification of a returned message and resend the original message? Regards, Luis -- o W. Luis Mochán, | tel:(52)(777)329-1734 /(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `/ /\ Apdo. Postal 48-3, 62251 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ O ascii ribbon campaign - stop html mail - www.asciiribbon.org
Re: resend
On Wed, Aug 08, 2012 at 12:58:05PM -0500, Luis Mochan wrote: Due to a misconfiguration in my mail server, I sent several messages that were not delivered but were sent back to me enclosed in a failure notification . Now that I have fixed the problem I want to send those messages again. What is the best procedure to do it? Does mutt have something similar to the emacs function 'rmail-retry-failure' to strip away the failure notification of a returned message and resend the original message? That sounds like what mutt calls a bounce. From the manual: | 7. Forwarding and Bouncing Mail | | Bouncing and forwarding let you send an existing message to recipients | that you specify. Bouncing a message sends a verbatim copy of a | message to alternative addresses as if they were the message's | original recipients specified in the Bcc header. Forwarding a message, | on the other hand, allows you to modify the message before it is | resent (for example, by adding your own comments). Bouncing is done | using the bounce function and forwarding using the forward | function bound to b and f respectively. Regards, Luis HTH, Paul. -- Paul Hoffman nkui...@nkuitse.com
Re: resend
On Wed, Aug 08, 2012 at 12:58:05 -0500, Luis Mochan wrote: send those messages again. What is the best procedure to do it? Does mutt have something similar to the emacs function 'rmail-retry-failure' to strip away the failure notification of a returned message and resend the original message? Are the original messages included in the bounce messages as MIME message/rfc822 attachments? If so, you can use the view-attachments menu (i.e. hit v while viewing the bounce message), then navigate down to the attachment containing the original message and use either bounce-message or resend-message (bound to b and Esce by default) to resend that message. Nathan
Re: resend
On Wed, Aug 08, 2012 at 03:35:35PM -0400, Nathan Stratton Treadway wrote: On Wed, Aug 08, 2012 at 12:58:05 -0500, Luis Mochan wrote: send those messages again. What is the best procedure to do it? Does mutt have something similar to the emacs function 'rmail-retry-failure' to strip away the failure notification of a returned message and resend the original message? Are the original messages included in the bounce messages as MIME message/rfc822 attachments? Yes. If so, you can use the view-attachments menu (i.e. hit v while viewing the bounce message), then navigate down to the attachment containing the original message and use either bounce-message or resend-message (bound to b and Esce by default) to resend that message. Thanks Nathan! I was not aware that you could bounce or resend individual attachments. However, it seems that the failed message comes in the same part as the failure message, preceded by a message such as: ... -- This is a copy of the message, including all the headers. -- Return-path: ... Received: from... ... I wonder if simply typing Esc e and deleting whatever comes before the copy of the message and the original headers would work, i.e., everything above 'Return-path:' above would work. Regards, Luis
Re: resend
Thanks Paul, The problem is that I don't want to bounce the complete message; first I want to strip the failure notification part. Regards, Luis On Wed, Aug 08, 2012 at 03:16:29PM -0400, Paul Hoffman wrote: On Wed, Aug 08, 2012 at 12:58:05PM -0500, Luis Mochan wrote: Due to a misconfiguration in my mail server, I sent several messages that were not delivered but were sent back to me enclosed in a failure notification . Now that I have fixed the problem I want to send those messages again. What is the best procedure to do it? Does mutt have something similar to the emacs function 'rmail-retry-failure' to strip away the failure notification of a returned message and resend the original message? That sounds like what mutt calls a bounce. From the manual: | 7. Forwarding and Bouncing Mail | | Bouncing and forwarding let you send an existing message to recipients | that you specify. Bouncing a message sends a verbatim copy of a | message to alternative addresses as if they were the message's | original recipients specified in the Bcc header. Forwarding a message, | on the other hand, allows you to modify the message before it is | resent (for example, by adding your own comments). Bouncing is done | using the bounce function and forwarding using the forward | function bound to b and f respectively. Regards, Luis HTH, Paul. -- Paul Hoffman nkui...@nkuitse.com
Re: resend
On Wed, Aug 08, 2012 at 04:05:29PM -0500, Luis Mochan wrote: On Wed, Aug 08, 2012 at 03:35:35PM -0400, Nathan Stratton Treadway wrote: On Wed, Aug 08, 2012 at 12:58:05 -0500, Luis Mochan wrote: send those messages again. What is the best procedure to do it? Does mutt have something similar to the emacs function 'rmail-retry-failure' to strip away the failure notification of a returned message and resend the original message? Are the original messages included in the bounce messages as MIME message/rfc822 attachments? Yes. Sorry, I meant no. Some messages include mime attachments, somes do not. Regards, Luis
Re: mark_old friends
On Wed, Aug 1, 2012 at 3:04 PM, Andre Klärner kan...@ak-online.be wrote: How do I really get mutt to consider mails marked as old and marked as new to be the same thing when I am using maildir. HI Andre, I was able to that, but, not via control of mutt, via control of the Mail-server (Dovecot) , (its been a while since I've done that, and it's not an active solution, I can dig the .conf files from backup if needed. ) AFAIK, mutt interfaces with Exim upon its sending email, when you 'open' mutt for reading, then you're interfacing with the mail server, qpop/dovecot or Gmail. I tuned the refresh rate of the Maildir on dovecot to be slower ( it was 10 seconds on default, if I remember right ) , then, say, Thunderbird read an email, and considered it as read , the mail server (Dovecot) did not tag it as old and moved it to /cur , while (to my pleasant surprise ) mutt and my android phone where smart enough to know that the messages were read. I was mainly doing this so I'll be able to run some scripts on the server's side and wanted email-files to be left under /new and not moved to /cur . -- Guy Gold
