Re: Honor X-Mutt-PGP with resend-message
Hello everyone, On Sun, Jul 27, 2014 at 09:48:08PM +0200, Antoine Amarilli wrote: The short version of my question is: Is there a way for the resend-message command to honor PGP signature/encryption settings stored in the target message in the X-Mutt-PGP header? The reason why I ask: I want to have postponed messages appear in my inbox, and be able to recall them by selecting them in the index view and hitting the 'R' key. For reference, I managed to make this work, by switching to a different hack which uses recall-message rather than resend-message, but saves the message to recall in a temporary mailbox first. Mere is my configuration: # save postponed mail in the inbox set postponed==inbox # ugly hack to resume the currently highlighted mail # may fail messily if you do not create =draft_tmp first macro index,pager R \ enter-commandset postponed='=draft_tmp' my_old_maildir_trash=\$maildir_trash nomaildir_trashenter\ s=draft_tmpenterrecall-messageenter-commandset postponed='=inbox' maildir_trash=\$my_old_maildir_trashenter \ recall current message # unmodified drafts should be saved back to the inbox, not discarded set noabort_unmodified It seems to work for my purposes. Best, -- Antoine Amarilli signature.asc Description: Digital signature
Honor X-Mutt-PGP with resend-message
Hello everyone, I'm new to this list, I hope that this is the right kind of questions and the right place where to ask them. The short version of my question is: Is there a way for the resend-message command to honor PGP signature/encryption settings stored in the target message in the X-Mutt-PGP header? The reason why I ask: I want to have postponed messages appear in my inbox, and be able to recall them by selecting them in the index view and hitting the 'R' key. I accordingly set postponed=inbox, but then the recall-message commands insists on opening its own prompt to select the message to recall (in other words, I found no way to recall the selected message in the index). I accordingly use the resend-message command (following the manual's description of it as recall from arbitrary folders), but then this command ignores the encryption settings for the postponed message (and chooses to have no encryption/signature instead). Indeed, postponing the message stores a message without encryption or signature, and merely indiates in a X-Mutt-PGP header what the message setting was, and resend-messages looks at the message itself to decide whether to sign or encrypt, rather than using this header. Hence the question above; but maybe my way to use =inbox as the postponed folder is not the right way to obtain the behavior I want. Thanks in advance for any advice! Regards, -- Antoine Amarilli 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: How to resend message multiple times effectively
On 25.09.2007 (01:10), Jiang Qian wrote: I'm sure we can write some kind of poor man's python script or shell/sed/awk script to add or remove address from this. You can then invoke this on the BCC field. But the question was how to make them appear, one by one, in separate mails, in the TO field. Something like: 1. Have a file with a list of addresses, 2. Have a message ready to be sent, only waiting for the TO line, 3. Have a script (sed?) which scans the address file line by line, and for each line inserts it in the appropriate place in the mail, sends it off, and goes to the next item. In other words some kind of mail-merge function, right? -- We are Pentium of Borg. Division is futile. You will be approximated. (seen in someone's .signature)
How to resend message multiple times effectively
Hi all, I need to send the same message to multiple recipients. So what I am currently doing is invoking resend-message repeatedly and changing the to address. Is it possible to do this in one shot? As in fire multiple emails, one for each address containing the same body. Thanks -- Regards, Ajeet pgpItvKLlKwt1.pgp Description: PGP signature
Re: How to resend message multiple times effectively
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, September 24 at 07:57 PM, quoth Ajeet: I need to send the same message to multiple recipients. So what I am currently doing is invoking resend-message repeatedly and changing the to address. Is it possible to do this in one shot? As in fire multiple emails, one for each address containing the same body. What's wrong with including them all in the To, CC, or Bcc headers? ~Kyle - -- The whole art of government consists in the art of being honest. -- Thomas Jefferson: Rights of British America, 1774 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG+IfzBkIOoMqOI14RAvlwAJ95tAjjxl4HkYbBHahBFOxXW05o4wCeNlQx Bs+nNCUX/cTh+b95JnSuXNo= =ZT6L -END PGP SIGNATURE-
Re: How to resend message multiple times effectively
On Mon, 24 Sep 2007 23:00:51 -0500, Kyle Wheeler wrote: What's wrong with including them all in the To, CC, or Bcc headers? Well the concern may seem vague to you and you may not agree. I think that in certain situations, it pays to make your email seem personal. If I receive an email in which I am not any of the addresses (when I am Bcc'ed) or when I am one of a large number of recipients, it feels to me like a public broadcast. I guess its more of etiquette issue. -- Regards, Ajeet pgpyNCYutf2Ac.pgp Description: PGP signature
Re: How to resend message multiple times effectively
For a few dozen recipients or less, place all the recipient addresses (comma-delimited) on the BCC: line, and place your own address on the TO: line. About a year ago, I had need to make a periodic mailing to a few hundred email addresses. I tried several approaches, but I did not find a satisfactory open-source package. Maybe I'm missing something obvious here, but what's wrong with having an alias file of this kind of content and the source it on .muttrc: alias mailinglist1 New List \ email address 1,\ email address 2,\ . . . email address n,\ my own address I'm sure we can write some kind of poor man's python script or shell/sed/awk script to add or remove address from this. You can then invoke this on the BCC field. Is this some sort of a performance problem? If so, that's not the fault of mutt but of $sendmail you're using, since that's what's handling it. But I serious doubt that a few hundred email can choke, say, postfix on a decently powerful machine. Let me know what I'm missing here. Jiang It appears that most of the mass mailing software has been written for Window$, and must be purchased. And some of the mass mailing software for Window$ is very good. If you have need to make a mass mailing on a regular basis, you may find that the best approach is to devote an old Window$ machine to the task, and shop around for a Window$ application. RLH
X-Mailer Header Not Being Picked Up With Resend Command
When I resend a message, using esc e, I find that my X-Mailer header is not picked up from the original message. The manual indicates that weeding is used when resending. My .muttrc contains: ignore unignorefrom: subject to cc mail-followup-to \ date x-mailer x-url weed in not set, so should default to yes, per the manual. What obvious thing am I missing? TIA John
Re: X-Mailer Header Not Being Picked Up With Resend Command
* John P Verel [EMAIL PROTECTED] [2002-07-24 14:54]: When I resend a message, using esc e, I find that my X-Mailer header is not picked up from the original message. The manual indicates that weeding is used when resending. .. What obvious thing am I missing? resending takes the message as is. no hooks or whatever get applied. feature. period. Sven
Re: X-Mailer Header Not Being Picked Up With Resend Command
On 07/24/02 21:12 +0200, Sven Guckes wrote: resending takes the message as is. no hooks or whatever get applied. feature. period. Not to be difficult, but to quote the on-line manual: 'With resend-message, mutt takes the current message as a template for a new message. This function is best described as recall from arbitrary folders. It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. John
Re: X-Mailer Header Not Being Picked Up With Resend Command
John P Verel ([EMAIL PROTECTED]) muttered: 'With resend-message, mutt takes the current message as a template for a new message. This function is best described as recall from arbitrary folders. It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. I seem to recall a previous discussion on this topic. Please grep the archives for further details. To summarize: Mutt will delete any X-Mailer header. HTH, Michael -- PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: X-Mailer Header Not Being Picked Up With Resend Command
* John P Verel [EMAIL PROTECTED] [2002-07-24 20:03]: On 07/24/02 21:12 +0200, Sven Guckes wrote: resending takes the message as is. no hooks or whatever get applied. feature. period. Not to be difficult, but to quote the on-line manual: 'With resend-message.. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? a valid question! thanks for pointing it out - i did not see this. As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. I assume that if you do no specifically unignore X-* lines then they will be weeded out. let's test this: $ mutt -f mutt.testmail :unignore x- resend-message bingo - X-Test: line *included*! :-) Sven === mutt.testmail From mutt-testers Wed Jul 24 23:22:21 2002 From: Sven Guckes [EMAIL PROTECTED] To: Mutt Users' List [EMAIL PROTECTED] Subject: Re: X-Mailer Header Not Being Picked Up With Resend Command Message-ID: [EMAIL PROTECTED] In-Reply-To: 20020724200253.GB1775@Verdi X-Test: does resend-message weed headers or not?
Re: X-Mailer Header Not Being Picked Up With Resend Command
I assume that if you do no specifically unignore X-* lines then they will be weeded out. let's test this: $ mutt -f mutt.testmail :unignore x- resend-message bingo - X-Test: line *included*! :-) That does not work with x-mailer sven. Why didn't you test the header in question? Michael -- Whip me. Beat me. Make me maintain AIX. (By Stephan Zielinski) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: X-Mailer Header Not Being Picked Up With Resend Command
* Michael Tatge [EMAIL PROTECTED] [2002-07-24 20:45]: I assume that if you do no specifically unignore X-* lines then they will be weeded out. let's test this: $ mutt -f mutt.testmail :unignore x- resend-message bingo - X-Test: line *included*! :-) That does not work with x-mailer sven. Why didn't you test the header in question? because it should be self-evident that mutt will not send with an identification other than the one it adds itself. that's why. you can complain to the developers for not documenting their code enough on this point, of course. Sven [off to see a sneak preview]
Re: X-Mailer Header Not Being Picked Up With Resend Command
On 07/24/02 22:11 +0200, Michael Tatge wrote: To summarize: Mutt will delete any X-Mailer header. Confirmed. Thanks.
Re: fcc and resend message
Nicolas -- ...and then Nicolas Rachinsky said... % On Wed, Nov 07, 2001 at 10:58:09PM -0500, David T-G [EMAIL PROTECTED] wrote: % % Use Mikko Hanninen's patch-1.2.mha.resend-fcc.1 feature patch to tell % mutt to set the fcc according to your usual rules. % % Where can I get this patch? I don't know where Mikko might really keep it, but you can find it in my cocktail at http://mutt.justpickone.org/mutt-build-cocktail/ as patch-1.2.mha.resend-fcc.1 in the list of files. Enjoy! % % Nicolas :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20336/pgp0.pgp Description: PGP signature
Re: resend-message (esc e) not honouring $record
On 2001-10-01 12:12 -0700, Ben Reser wrote: On Mon, Oct 01, 2001 at 03:37:42PM +0200, Andre Majorel wrote: When I send a new message using an older one as a template (esc e), the new message is not saved to $record. Is that deliberate or an overlook ? It's deliberate. Search the archives this discussion has been had several times. All I found was posts by other people complaining about it, but no message explaining why it's done that way. Do you have a pointer ? -- André Majorel URL:http://www.teaser.fr/~amajorel/ (Not speaking for my employer, etc.)
Re: resend-message (esc e) not honouring $record
* On Mon Oct 01, Ben Reser wrote: It's deliberate. Search the archives this discussion has been had several times. Well, I have yet to see a good explanation why this choice has been made. I am also still searching for a convenient way to use an old message as template for a new one, without having to remember to manually save the new one. IMO, this is a quite serious problem, as it in fact makes the user lose data if he's not careful every time he uses this functionality. I have lost a handful of e-mails this way, meaning that short of sending the recipient another e-mail demanding the he send me back what I wrote to him, I have no way of recording what I have written. At least, I would very much appreciate a configuration variable by which you could choose which behavior is desirable. Jesper -- Jesper Holmberg|But how can | [EMAIL PROTECTED] | one be warm | ENST Br, BP 832, 29285 Brest, FRANCE | alone? |
Re: resend-message (esc e) not honouring $record
I'm new at this but, ?? perhaps ?? cc yourself ?? On Tue, Oct 02, 2001 at 01:36:40PM +0200, Jesper Holmberg wrote: * On Mon Oct 01, Ben Reser wrote: It's deliberate. Search the archives this discussion has been had several times. Well, I have yet to see a good explanation why this choice has been made. I am also still searching for a convenient way to use an old message as template for a new one, without having to remember to manually save the new one. IMO, this is a quite serious problem, as it in fact makes the user lose data if he's not careful every time he uses this functionality. I have lost a handful of e-mails this way, meaning that short of sending the recipient another e-mail demanding the he send me back what I wrote to him, I have no way of recording what I have written. At least, I would very much appreciate a configuration variable by which you could choose which behavior is desirable. Jesper -- Jesper Holmberg|But how can | [EMAIL PROTECTED] | one be warm | ENST Br, BP 832, 29285 Brest, FRANCE | alone? | -- Pat Shanahan ***[EMAIL PROTECTED]*** Registered Linux User #207535 (Registered at: http://counter.li.org)
Re: resend-message (esc e) not honouring $record
* Jesper Holmberg [EMAIL PROTECTED] [02-10-2001 13:38]: | * On Mon Oct 01, Ben Reser wrote: | It's deliberate. Search the archives this discussion has been had | several times. | | Well, I have yet to see a good explanation why this choice has been | made. I am also still searching for a convenient way to use an old | message as template for a new one, without having to remember to | manually save the new one. I'm also interested in a good explanation ;) But, fact is that you don't need your memory on this one... (look down) | IMO, this is a quite serious problem, as it in fact makes the user lose | data if he's not careful every time he uses this functionality. I have | lost a handful of e-mails this way, meaning that short of sending the | recipient another e-mail demanding the he send me back what I wrote to | him, I have no way of recording what I have written. | | At least, I would very much appreciate a configuration variable by which | you could choose which behavior is desirable. macro index \ee resend-messagefsent_mail\n does the trick for me. But I agree that it's a workaround. I'm not sure whether you'll want another configuration variable; let's just turn it on by default. -- René Clerc - ([EMAIL PROTECTED]) There are painters who transform the sun to a yellow spot, but there are others who with the help of their art and their intelligence, transform a yellow spot into sun. -Pablo Picasso
Re: resend-message (esc e) not honouring $record
* On Tue Oct 02, pat wrote: I'm new at this but, ?? perhaps ?? cc yourself ?? You're right, that is one solution to getting my own copy of what I send. But my problem was more specific: to automatically make mutt record the fact that I've sent a new message, something it does in all cases except when I have used an older message as template. Jesper -- Jesper Holmberg|But how can | [EMAIL PROTECTED] | one be warm | ENST Br, BP 832, 29285 Brest, FRANCE | alone? |
Re: resend-message (esc e) not honouring $record
* On Tue Oct 02, René Clerc wrote: macro index \ee resend-messagefsent_mail\n does the trick for me. This does indeed do the trick. I should have been able to find that one out by myself, shouldn't I? *Blushing* But I still think this workaround should not be needed. Jesper -- Jesper Holmberg|But how can | [EMAIL PROTECTED] | one be warm | ENST Br, BP 832, 29285 Brest, FRANCE | alone? |
Re: resend-message (esc e) not honouring $record
On Tue, Oct 02, 2001 at 06:20:54PM +0200, Jesper Holmberg wrote: * On Tue Oct 02, pat wrote: I'm new at this but, ?? perhaps ?? cc yourself ?? You're right, that is one solution to getting my own copy of what I send. But my problem was more specific: to automatically make mutt record the fact that I've sent a new message, something it does in all cases except when I have used an older message as template. Jesper What's wrong with the copy in the 'outgoing' folder? Why does it have to show up in your Inboxor I guess you want the message filed into a specific directory? /rc -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin Linux-Mandrake 7.1 - 2.2.15-4mdk / Uptime: 7 days 17 hours 55 minutes
Re: resend-message (esc e) not honouring $record
* On Tue Oct 02, Ryan Cook wrote: What's wrong with the copy in the 'outgoing' folder? Why does it have to show up in your Inboxor I guess you want the message filed into a specific directory? Eh...what? I get the impression you've misunderstood something I wrote. I just want my outgoing e-mail to always show up in my outgoing folder, i.e. the folder $record points to, regardless of if I used an older message as template or not. Jesper -- Jesper Holmberg|But how can | [EMAIL PROTECTED] | one be warm | ENST Br, BP 832, 29285 Brest, FRANCE | alone? |
Re: resend-message (esc e) not honouring $record
On Tue, Oct 02, 2001 at 06:46:15PM +0200, Jesper Holmberg wrote: Date: Tue, 2 Oct 2001 18:46:15 +0200 From: Jesper Holmberg [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: resend-message (esc e) not honouring $record Message-ID: [EMAIL PROTECTED] User-Agent: Mutt/1.3.22i * On Tue Oct 02, Ryan Cook wrote: What's wrong with the copy in the 'outgoing' folder? Why does it have to show up in your Inboxor I guess you want the message filed into a specific directory? Eh...what? I get the impression you've misunderstood something I wrote. I just want my outgoing e-mail to always show up in my outgoing folder, i.e. the folder $record points to, regardless of if I used an older message as template or not. Ahhh...that was what I wasn't getting. /rc -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin Linux-Mandrake 7.1 - 2.2.15-4mdk / Uptime: 7 days 18 hours 15 minutes
resend-message (esc e) not honouring $record
When I send a new message using an older one as a template (esc e), the new message is not saved to $record. Is that deliberate or an overlook ? -- André Majorel URL:http://www.teaser.fr/~amajorel/ (Not speaking for my employer, etc.)
Re: resend-message (esc e) not honouring $record
Thus spake Andre Majorel ([EMAIL PROTECTED]): When I send a new message using an older one as a template (esc e), the new message is not saved to $record. Is that deliberate or an overlook ? Yeah, I've noticed that with both mbox and IMAP setups in Mutt. -- | Justin R. Miller / [EMAIL PROTECTED] / 0xC9C40C31 | Of all the things I've lost, I miss my pants the most. -- PGP signature
Re: resend-message (esc e) not honouring $record
On Mon, Oct 01, 2001 at 03:37:42PM +0200, Andre Majorel wrote: When I send a new message using an older one as a template (esc e), the new message is not saved to $record. Is that deliberate or an overlook ? It's deliberate. Search the archives this discussion has been had several times. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org Before you set out for revenge dig two graves. - Chinese Saying
resend-message problem with bcc
Hi Mutters, I have a problem when resending a message via resend-message: When I also specify a Bcc-address the message doesn't get sent but sendmail puts it into /var/spool/mqueue-client and there it stays forever and ever. At first this sounded like a sendmail problem to me, but it works perfectly when I leave the Bcc line empty. So maybe it's a combination of both? Ah, wait! I just experimented a bit more and found that this option seems to trigger it: set dsn_notify=failure,delay After removing this line from .muttrc it works as it should. Any clues? Andy. PS: While at it: after resend-message mutt leaves the Fcc line empty. How can I change that? -- Dr. Andy Spiegl, Radio Marañón, Jaén, Perú E-Mail: [EMAIL PROTECTED], [EMAIL PROTECTED] URL: http://spiegl.de, http://radiomaranon.org.pe PGP/GPG: see headers o _ _ _ --- __o __o /\_ _ \\o (_)\__/o (_) -o) - _`\,__`\,__(_) (_)/_\_| \ _|/' \/ /\\ (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o__\_v ~~
[1.2.5] resend-message
The resend-message function isn't documented in the manual. Moreover, it doesn't set the Bcc and Fcc fields (unlike the other send functions). -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / PolKA research team at LORIA
Re: [1.2.5] resend-message
Vincent Lefevre writes: The resend-message function isn't documented in the manual. I submitted a patch for this back in August. It went straight into cvs (and 1.3.x). Moreover, it doesn't set the Bcc and Fcc fields (unlike the other send functions).
Re: segmentation fault with resend-message
On Mon, 20 Nov 2000, Thomas Roessler wrote: Could you please look for a core dump and send us a stack trace? Here it is: (gdb) bt #0 0x28113e71 in fclose () from /usr/lib/libc.so.3 #1 0x807c759 in ci_send_message (flags=256, msg=0x80fb180, tempfile=0x0, ctx=0x80d3300, cur=0x80f5f80) at send.c:1209 #2 0x807c2f8 in mutt_resend_message (fp=0x0, ctx=0x80d3300, cur=0x80f5f80) at send.c:994 #3 0x8057f6d in mutt_index_menu () at curs_main.c:1739 #4 0x80651d5 in main (argc=1, argv=0xbfbfd858) at main.c:709 #5 0x804a17d in _start () (gdb) On 2000-11-19 13:26:51 +0800, lang wrote: I get a "segmentation fault-core dumped" message when I try to use the resend-message function from the index. -- Greg MathesonThe funniest practical jokes are Chinmin College, those you play unsuspectingly on Taiwan yourself.
segmentation fault with resend-message
I get a "segmentation fault-core dumped" message when I try to use the resend-message function from the index. I am using mutt-1.2.5, but I also had the same problem with 1.2. What do I do to fix this? lang@ms$ 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: FreeBSD 3.4-RELEASE [using ncurses 5.1] 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 SENDMAIL="/usr/sbin/sendmail" MAILPATH="Maildir" SHAREDIR="/usr/home/lang/share/mutt" SYSCONFDIR="/usr/home/lang/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. -- Greg MathesonThe funniest practical jokes are Chinmin College, those you play unsuspectingly on Taiwan yourself.
Re: segmentation fault with resend-message
Could you please look for a core dump and send us a stack trace? You can generate it like this: gdb -c core mutt bt On 2000-11-19 13:26:51 +0800, lang wrote: Date: Sun, 19 Nov 2000 13:26:51 +0800 From: lang [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: segmentation fault with resend-message Mail-Followup-To: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i I get a "segmentation fault-core dumped" message when I try to use the resend-message function from the index. I am using mutt-1.2.5, but I also had the same problem with 1.2. What do I do to fix this? lang@ms$ 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: FreeBSD 3.4-RELEASE [using ncurses 5.1] 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 SENDMAIL="/usr/sbin/sendmail" MAILPATH="Maildir" SHAREDIR="/usr/home/lang/share/mutt" SYSCONFDIR="/usr/home/lang/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. -- Greg MathesonThe funniest practical jokes are Chinmin College, those you play unsuspectingly on Taiwan yourself. -- Thomas Roessler [EMAIL PROTECTED]
Re: resend-message
Jesper Holmberg [EMAIL PROTECTED] wrote on Tue, 24 Oct 2000: So: what I would have expected to happen is that the newly sent message be saved to my out-mailbox, since it is in effect a new message sent from me. What am I missing? You're missing that there's no default Fcc value provided with resend-message. This is certainly something I think should be changed, it could even be called a bug. So: There is no Fcc unless you remember to manually add one in the compose menu. 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 / These aren't the droids you're looking for. Move along.
Re: resend-message
* On Tuesday, October 24, Mikko Hänninen wrote: You're missing that there's no default Fcc value provided with resend-message. This is certainly something I think should be changed, it could even be called a bug. Hey, a mutt bug, I didn't think those existed! Anyway, I've been trying to solve this with various variants of macros, but is hasn't worked. Not: macro generic \eu "resend-messagef=sentmailenter" Not: macro generic \eu ":my_hdr Fcc: =sentmailenterresend-message" Not even the generic setting: my_hdr Fcc: =sentmail The Fcc: header stays empty, no matter what I do. Is there a way to solve this, so that I don't need to add it manually every time? Jesper -- "But how can one be warm alone?" Jesper Holmberg [EMAIL PROTECTED]
Re: resend-message
On Tue, Oct 24, 2000 at 08:48:31PM +0200, Jesper Holmberg muttered: * On Tuesday, October 24, Mikko Hänninen wrote: You're missing that there's no default Fcc value provided with resend-message. This is certainly something I think should be changed, it could even be called a bug. Hey, a mutt bug, I didn't think those existed! Anyway, I've been Of course mutt bugs exist. They're called "fleas." ... Hey, why'd everyone run away? -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley PGP signature
Re: resend-message
On Tue, Oct 24, 2000 at 20:48:31 +0200, Jesper Holmberg wrote: * On Tuesday, October 24, Mikko Hänninen wrote: You're missing that there's no default Fcc value provided with resend-message. This is certainly something I think should be changed, it could even be called a bug. Hey, a mutt bug, I didn't think those existed! Anyway, I've been trying to solve this with various variants of macros, but is hasn't worked. Not: macro generic \eu "resend-messagef=sentmailenter" This should in theory work if you have remembered to remove the default key bindings for escu in the various menus which otherwise will take precedence over the generic definition. However, I think that there may be some problems (yet another bug?!) with generic macro definitions. Try instead: macro index \eu "resend-messagef=sentmailenter" macro pager \eu "resend-messagef=sentmailenter" macro attach \eu "resend-messagef=sentmailenter" -- Byrial http://home.worldonline.dk/~byrial/
Re: resend-message
* On Tuesday, October 24, Byrial Jensen wrote: Not: macro generic \eu "resend-messagef=sentmailenter" This should in theory work if you have remembered to remove the default key bindings for escu in the various menus which otherwise will take precedence over the generic definition. No, I don't have any such conflict. However, I think that there may be some problems (yet another bug?!) with generic macro definitions. Try instead: macro index \eu "resend-messagef=sentmailenter" macro pager \eu "resend-messagef=sentmailenter" macro attach \eu "resend-messagef=sentmailenter" No, that didn't solve the problem, unfortunately. Thanks for your suggestions, but I'm still out of luck. Jesper -- "But how can one be warm alone?" Jesper Holmberg [EMAIL PROTECTED]
Re: resend-message
On Tue, Oct 24, 2000 at 02:25:22PM +0300, Mikko Hänninen wrote: You're missing that there's no default Fcc value provided with resend-message. This is certainly something I think should be changed, it could even be called a bug. So: There is no Fcc unless you remember to manually add one in the compose menu. Depends on what you're using the resend feature for. If you're resending a message that you already sent it should already be in your Fcc and what's the point of adding it again? Frankly, I think it'd make more sense to make a templates setup. Like a reply with template. You could specify a template mailbox and then select a message from the template mailbox that would be used as the default reply. etc etc etc More complex but much more flexible in my mind. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org Maslow's Maxim: If the only tool you have is a hammer, you treat everything like a nail.
Re: resend-message
Ben Reser [EMAIL PROTECTED] wrote on Tue, 24 Oct 2000: Depends on what you're using the resend feature for. If you're resending a message that you already sent it should already be in your Fcc and what's the point of adding it again? True, but in that case you can delete the Fcc from the compose menu. The point is that apparently the intuitive thing is to expect that every outgoing message is saved to the =sent folder (or whatever $record has), unless you explicitly clear the Fcc header. It can be a nasty surprise to find this isn't so for the resent messages. And conversely, adding an extra Fcc only copies one extra message to the sent folder, which usually is much less of a nuisance. You can delete extra messages, but you can't re-create something that got never saved. It is largely a user preference whether they want to keep an outgoing copy of every message they sent, or just each unique message they send. The headers in the two emails will be slightly different, at least, so some people may prefer to keep both copies. It should also be noted that resend-message is meant for situations where you want to use the original email as a base for the new email, but do want to alter it. If you want to send the exact same message, you're better off using the b(ounce) command. (Which, BTW, *does* add a new copy of the message to the Fcc folder...) Since the new message is likely going to be different from the old message in some way, it makes sense to store a copy of that too. Frankly, I think it'd make more sense to make a templates setup. Like a reply with template. You could specify a template mailbox and then select a message from the template mailbox that would be used as the default reply. etc etc etc I don't see how that is any different from what resend-message provides, actually? 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 / 10.0 times 0.1 is hardly ever 1.0.
Re: New mutt user, resend
I think you may be referring to Eterm. Eterm is a modern replacement for
Xterm, as I understand it. On the links page of the mutt home page,
their is a link to get that menu, however I know it only works with the
0.8.10 version of Eterm, and not the most recent of 0.9.x version.
I just did an ls. Here it is.
On Sun, Aug 20, 2000 at 01:38:43PM -0400, Dave Kufta muttered:
| Hello List,
| I am new to mutt and still trying to figure out all the options that
| are available and that
| I would like to use.I am running a Linux -Mandrake-7.1 system and have
| pgp-6.5.1I . I noticed in some screenshots a very nice interface for
| mutt in xwindow enviroment which
| had very nice color and a menu bar at the top which included a button
| for pgp among
| others. Could someone on the list possibly suggest where I may find a
| muttrc file that would allow these features. I found the screenshot I'm
| referring to at the main web site for mutt but don't see in any of the
| muttrc files that are there a way to enable the menu bar. I am currently
| using mutt-1.2.4i version. Possibly I would need a newer version to
| enable the features Iv'e mentioned.
|
| Thank you for any help,
| Dave
--
/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
[menu:mutt]
# This isn't really done... there aren't quick ways to do some of the things
# listed, so they don't really work. Also, I used :exec where possible to be
# portable across different keybindings, but it didn't work for all things, and
# you'll need at least Mutt 0.95 for it to work.
# http://jblosser.firinn.org/pub/config/eterm/mutt.menu
# standard settings for an Eterm control menu
/Eterm/*
./Font/*
{Normal}^@\e]50;#
{Larger}^@\e]50;#+
{Smaller} ^@\e]50;#-
{-}
{Font 1}^@\e]50;#1
{Font 2}^@\e]50;#2
{Font 3}^@\e]50;#3
{Font 4}^@\e]50;#4
../Terminal/*
./Toggles/*
{Cursor Visible}^@\e[?25t
{Home on Echo} ^@\e[?1010t
{Home on Refresh} ^@\e[?1011t
{Home on Input} ^@\e[?1012t
{Map Alert} ^@\e]6;21\a
{Primary/Secondary Screen} ^@\e[?47t
{Reverse Video} ^@\e[?5t
{Select Trailing Spaces}^@\e]6;25\a
{Select Whole Line on Triple-click} ^@\e]6;23\a
{Visual Bell} ^@\e]6;20\a
{X11 Mouse Reporting} ^@\e[?1000t
{Xterm Selection Behavior} ^@\e]6;22\a
../Keys/*
{Application Arrow Keys}^@\e[?1t
{Application Keypad}^@\e[?66t
{Backspace/Delete} ^@\e[?67t
{Xterm Shift-Keys} ^@\e[?35t
../Menubar/*
{Toggle Visibility}{Ctrl-Button3} ^@\e[?10t
{Refresh Menubar} ^@\e[?10h
{Toggle Window Move by Menubar} ^@\e]6;15\a
../Scrollbar/*
{Toggle Visibility}{Ctrl-Button2} ^@\e[?30t
{Swap Sides}^@\e]6;11\a
{Toggle Floating} ^@\e]6;12\a
{Toggle Popup Mode} ^@\e]6;13\a
{-}
{Motif (Traditional) Style} ^@\e]6;10;motif;;\a
{NeXT Style}^@\e]6;10;next;;\a
{Xterm Style} ^@\e]6;10;xterm;;\a
./Width/*
{5} ^@\e]6;10;;5;\a
{6} ^@\e]6;10;;6;\a
{7} ^@\e]6;10;;7;\a
{8} ^@\e]6;10;;8;\a
{9} ^@\e]6;10;;9;\a
{10}^@\e]6;10;;10;\a
{11}^@\e]6;10;;11;\a
{12}^@\e]6;10;;12;\a
{13}^@\e]6;10;;13;\a
{14}^@\e]6;10;;14;\a
{15}^@\e]6;10;;15;\a
{16}^@\e]6;10;;16;\a
{17}^@\e]6;10;;17;\a
{18}^@\e]6;10;;18;\a
{19}^@\e]6;10;;19;\a
{20}^@\e]6;10;;20;\a
../
../Move to Desktop/*
{0} ^@\e]6;50;0;\a
{1} ^@\e]6;50;1;\a
{2} ^@\e]6;50;2;\a
{3} ^@\e]6;50;3;\a
{4} ^@\e]6;50;4;\a
{5} ^@\e]6;50;5;\a
{6}
Re: resend-message and FCC
-kevin- [EMAIL PROTECTED] wrote: It also seems to preserve the date of the original email, instead of giving it a new date. Yes, 'Date:' is correct but the 'From' line without a colon contains the date of the original email, which happens to be what tagging by date looks at. Not quite. The "From " header (ie, the "envelope separator") contains the date/time when the mail was received by the final delivery agent. That time is usually close to the time that the message was sent, but it is not the same. And Mutt does not look at that timestamp unless you sort by "date-received". Likewise, when tagging by date, ~d examines the Date: header, while ~r examines the enevelope separator time. Once again, IMHO, if the edited mail is sent, this date should be changed as well. I tend to agree with this sentiment. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: resend-message and FCC
On 00-05-26 10:41, -kevin- [EMAIL PROTECTED] wrote:
The Short:
I notice that when I 'resend-message' (ESCe) that it doesn't get
copied to my 'sent' folder.
Additional Note:
It also seems to preserve the date of the original email, instead
of giving it a new date. Yes, 'Date:' is correct but the
'From' line without a colon contains the date of the original
email, which happens to be what tagging by date looks at. Once
again, IMHO, if the edited mail is sent, this date should be
changed as well.
In short, my preference would be that if you send a message,
regarless of its origin, it should be treated as a new message, as
though composed in the usual manner.
The Long:
I'm a bad typist. Sometimes I mistype an address and send the
mail off. I get the bounce message.
Crack open mutt (v1.2) on my 'sent' folder where copies of all my
emails go. I find the message and hit ESCe (resend-message).
(NOTE: not 'e' (edit), this just edits the raw message and
doesn't offer to send it off again.) Usually, I don't change the
text, but I come back to the compose menu and fix up the 'To:'
address. Hit 'y' and off it goes, but it never shows up in my
'sent' folder.
My preference would be to have the both copies of the message.
Why? Because sometimes, I forget to forward a copy of the message
to someone else and I need to quickly resend the identical message
to one other address. I need to have both messages, the one to
the original recipients and the new one to the forgotten
recipient.
A bad solution: First edit the message ('e'). Then undelete the
old message. Then resend the new message. Very ugly, especially
when IMHO 'resend' should FCC just like every other send.
--
-* -kevin-*-
-* sick with the good infection *-
-* [EMAIL PROTECTED] *-
-* http://www.pobox.com/~kathey *-
Re: resend-message and FCC
-kevin- [EMAIL PROTECTED] wrote on Thu, 01 Jun 2000:
In short, my preference would be that if you send a message,
regarless of its origin, it should be treated as a new message, as
though composed in the usual manner.
I don't know about the date stuff, but here's an untested patch for
making Mutt put default Fcc headers for messages that are being sent
with resend-message.
Untested due to lack of time. :-) So if someone does try it out, I'd
be happy to hear of the results. The change itself is simple enough.
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 /
When I try to get a life... I always get either 404 or server timeout. :-(
--- send.c.orig Tue Mar 14 00:36:56 2000
+++ send.c Mon May 29 04:17:18 2000
@@ -1267,7 +1267,7 @@
/* specify a default fcc. if we are in batchmode, only save a copy of
* the message if the value of $copy is yes or ask-yes */
- if (!fcc[0] !(flags (SENDRESEND|SENDPOSTPONED)) (!(flags SENDBATCH) ||
(quadoption (OPT_COPY) 0x1)))
+ if (!fcc[0] !(flags SENDPOSTPONED) (!(flags SENDBATCH) || (quadoption
+(OPT_COPY) 0x1)))
{
/* set the default FCC */
if (!msg-env-from)
Re: resend-message and FCC
On Fri, May 26, 2000 at 09:32:20PM +0300, Mikko Hänninen wrote: But yes, there should be an option as to whether resend-message will default to Fcc'ing or not -- or if there's no option, the default should be yes. ACK. This bite me several days ago :-((( Best regards, Daniel PGP signature
resend-message and FCC
The Short:
I notice that when I 'resend-message' (ESCe) that it doesn't get
copied to my 'sent' folder.
The Long:
I'm a bad typist. Sometimes I mistype an address and send the
mail off. I get the bounce message.
Crack open mutt (v1.2) on my 'sent' folder where copies of all my
emails go. I find the message and hit ESCe (resend-message).
(NOTE: not 'e' (edit), this just edits the raw message and
doesn't offer to send it off again.) Usually, I don't change the
text, but I come back to the compose menu and fix up the 'To:'
address. Hit 'y' and off it goes, but it never shows up in my
'sent' folder.
My preference would be to have the both copies of the message.
Why? Because sometimes, I forget to forward a copy of the message
to someone else and I need to quickly resend the identical message
to one other address. I need to have both messages, the one to
the original recipients and the new one to the forgotten
recipient.
A bad solution: First edit the message ('e'). Then undelete the
old message. Then resend the new message. Very ugly, especially
when IMHO 'resend' should FCC just like every other send.
--
-* -kevin-*-
-* sick with the good infection *-
-* [EMAIL PROTECTED] *-
-* http://www.pobox.com/~kathey *-
Re: resend-message and FCC
-kevin- [EMAIL PROTECTED] wrote on Fri, 26 May 2000: I notice that when I 'resend-message' (ESCe) that it doesn't get copied to my 'sent' folder. I think that this is only because resend-message doesn't fill the Fcc header by default. If you add a folder in there, it'll work... But yes, there should be an option as to whether resend-message will default to Fcc'ing or not -- or if there's no option, the default should be yes. 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 / Be nice to other people. They outnumber you 6 billion to one.
Re: What `resend-message' do?? (It's not in 1.2 manual)
clemensF [EMAIL PROTECTED] wrote on Tue, 16 May 2000: It will take the current message and start composing a new message using that as a "template" -- your email will have the same headers and the same body (and attachements) as that email. so this is the former (1.0.1) edit function? The former edit has been split into to, depending on what you want to do: edit for message editing, resend-message for resending. So yes, in a way it's the former edit function. Sort of. 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 / "The last good thing written in C was Franz Schubert's Symphony #9."
Re: What `resend-message' do??
» Mikko Hänninen wrote: It *sounds* like what's happening is that you're running the "edit" function, which recalls the raw message into your editor (with every header, you can tell easily if there are Received headers, although if it's a Fcc message then there wouldn't be any), saves any changes you make and replaces the original in the mailbox with your edited message. With this, you're not supposed to go to the compose menu at all after you exit the editor. Could that be it? ... Maybe you have some strange keybindings left over from a pre-1.2 setup? Ok, that's it, I got it! I have: e edit edit the raw message Esceresend-messageuse the current message as a template for a new one but I didn't had: set meta_key so I guess I was using the ``edit''function, when hitting Metae. Thank you very much for the help. PS. Your Mail-Followup-To header is a bit messed up in your emails... Hum, that's true. I've set the ``subscribe'' thing now, I hope it will do. cheers, -- Francisco. São Paulo, Brasil. __o `\, _(*)/(*)_
Re: What `resend-message' do?? Mail-followup
» Mikko Hänninen wrote: PS. Your Mail-Followup-To header is a bit messed up in your emails... Ok ok, pretty stupid... I had: unset use_domain I guess it's better to change it (since I can't remember why I unsetted it in the first place) cheers, -- Francisco. São Paulo, Brasil. __o `\, _(*)/(*)_
Re: What `resend-message' do?? (It's not in 1.2 manual)
» Mikko Hänninen wrote: Francisco D. Borges [EMAIL PROTECTED] wrote on Mon, 15 May 2000: Shouldn't it REsend the edited message??? I'm sending one message to myself (which I receive accordingly) but if I go the sent-mail folder and ``resend-message'' I don't receive a new copy. You should, if you actually sent the message. the message was not sent, that I know for sure (I looked at the mail log's). The weird thing here is that after editing the message, I was delivered at the index of the folder where I was, not to the compose_mode of that message. Is there some variable that might be causing this? I already have: set abort_unmodified=no # Let me send empty messages What exactly does the `resend-message' function?? It will take the current message and start composing a new message using that as a "template" -- your email will have the same headers and the same body (and attachements) as that email. Also note that there is no Fcc set for the email by default. That could be considered a bug, or a mis-feature at least... Thank you for the info, now I just got to learn how to do it... cheers, -- Francisco. São Paulo, Brasil. __o `\, _(*)/(*)_
Re: How to resend a mail?
Mikko Hänninen [EMAIL PROTECTED] wrote: First save the email to a separate file. Then just call sendmail on the file: sendmail -t [EMAIL PROTECTED] /path/to/folder/file What you describe is exactly what the (b)ounce command does in Mutt. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: How to resend a mail?
David DeSimone [EMAIL PROTECTED] wrote on Thu, 30 Mar 2000: Mikko Hänninen [EMAIL PROTECTED] wrote: First save the email to a separate file. Then just call sendmail on the file: sendmail -t [EMAIL PROTECTED] /path/to/folder/file What you describe is exactly what the (b)ounce command does in Mutt. Yes, err, right -- but the user wanted to do this from a script, "non-interactively". Sure Mutt could be made to do a bounce with "push" but would you really recommend that? :-) 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 / Happiness is always just a remembrance away.
How to resend a mail?
Hello all, I am wondering how to resend a mail to another person? Here is my situation: I send a mail to someone, and the sent mail is stored in the directory which $record designates. Now I want to send the same mail to another person, can i do it with command options of mutt, without interactively invoking mutt. I have tried doing it with the following tricks: At first i run mutt interactively, compose the mail, and postpone the mail. I find the mail in the file "$postponed". When i enter "mutt -p", mutt will ask me several questions and display the postponed on screen. How can i let mutt send it immediately? -- Best regards, Song mailto:[EMAIL PROTECTED]
Re: How to resend a mail?
you could make a macro of it, i guess ... but I am not sure, i am a newbie and by hitting, "b", and putting your address in seems less of a problem then making a shell script.. unless you intend on bouncing to the same person all the time... On Thu, Mar 30, 2000 at 09:55:40AM +0800, [EMAIL PROTECTED] said: i guess you can "b"ounce it? is this an option for you? Can i do it within a shell script? That is, can i resend the mail without invoking mutt interactively? Thanks. -- »¶ÓʹÓà 21CN µç×ÓÓʼþϵͳhttp://www.21cn.com Thank you for using 21CN Email system -- /helfman "At any given moment, you may find the ticket to the circus that has always beenin your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private! 1024D/D75E0A36
Re: How to resend a mail?
Song Jianping [EMAIL PROTECTED] wrote on Thu, 30 Mar 2000: I am wondering how to resend a mail to another person? Here is my situation: I send a mail to someone, and the sent mail is stored in the directory which $record designates. Now I want to send the same mail to another person, can i do it with command options of mutt, without interactively invoking mutt. If you're not looking for necessarily a Mutt-specific answer, you could do this: First save the email to a separate file. Just making a Fcc to a folder that doesn't exist (and making sure your $mbox_type is mbox) should do it. Then just call sendmail on the file: sendmail -t [EMAIL PROTECTED] /path/to/folder/file That ought to re-send it... I forget the exact sendmail arguments for specifying the recipient list on the command line, but man sendmail is your friend for that. 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 / All I ask is a chance to prove that money can't make me happy.
Re: resend-message, $copy
* David T-G [EMAIL PROTECTED], Mon Mar 27 13:58 -0500: % Why does resend-message (ESC-e) not respect $copy? Presumably if % $copy is set, one wants a copy saved, of all messages sent. While I accept your argument, I think that the general premise is that you already have a copy of the message (since you're resending it) and you're not making any changes (like adding the recipient to the headers) and so a copy would be superfluous. No, not superfluous. A new (edited) message is sent out, not a cc. Now, I don't have esc-e in my copy, so that must be new (as alluded to below), and maybe I don't understand the resend-message function yet. resend-message pulls the message "as a template for a new message" into the editor, for editing, and on exiting the editor it is presented in the compose window, for sending. Handled as such, those who have $copy/$record set would naturally expect a copy of this new message to be saved, and until they notice that's not the case no record is kept of anything sent via this method. Either there was a rationale for not recording such messages, the coding was problematic, or bypassing $copy was an oversight. Perhaps one of the developers can offer insight. P. From the 1.1.x NEWS.gz, for those unfamiliar with the function: - The old edit-message command has been split into two commands, edit-message and resend-message. With edit-message (bound to e by default), mutt makes a copy of the raw message, and gives you the possibility to manipulate it with your favorite editor. This is ideal for fixing messed-up MIME headers and the like. After you have left the editor, the edited version of the message is copied back to the current folder, and the original message is marked for deletion. With resend-message (bound to ESC e by default), mutt takes the current message as a template for a new message. This function is best described as "recall from arbitrary folders". Note that the amount of headers included here depends on the value of the weed option. -- Patrick Walsh Edmonton AB CA
resend-message, $copy
Why does resend-message (ESC-e) not respect $copy? Presumably if $copy is set, one wants a copy saved, of all messages sent. (this function is not listed in the 1.1.9i manual.txt) -- Patrick Walsh Edmonton AB CA
Re: resend-message, $copy
Patrick -- ...and then Patrick Walsh said... % Why does resend-message (ESC-e) not respect $copy? Presumably if % $copy is set, one wants a copy saved, of all messages sent. While I accept your argument, I think that the general premise is that you already have a copy of the message (since you're resending it) and you're not making any changes (like adding the recipient to the headers) and so a copy would be superfluous. Now, I don't have esc-e in my copy, so that must be new (as alluded to below), and maybe I don't understand the resend-message function yet. I'm thinking of bounce-message at the moment, but could also consider edit (for editing an existing message and then shipping -- but I believe that edit - send *does* honor $copy). % % (this function is not listed in the 1.1.9i manual.txt) Can't help ya with that; haven't been there yet :-) % % -- % Patrick Walsh % Edmonton AB CA :-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: resend-message, $copy
David T-G [EMAIL PROTECTED] wrote on Mon, 27 Mar 2000: While I accept your argument, I think that the general premise is that you already have a copy of the message (since you're resending it) and you're not making any changes (like adding the recipient to the headers) and so a copy would be superfluous. Yes, except the resend-message drops you in the editor to edit the message text, and after that you're returned to the compose menu as usual. However Fcc is empty, even if you've modified the message contents. You can manuall add a Fcc but it would be nice if it was there automatically. There might be some tricky issues there with regards to fcc-hooks and such that I'm not thinking of here, though. Now, I don't have esc-e in my copy, so that must be new (as alluded to below), and maybe I don't understand the resend-message function yet. I'm thinking of bounce-message at the moment, but could also consider edit (for editing an existing message and then shipping -- but I believe that edit - send *does* honor $copy). Yes, this has changed in the developement versions. The functions of edit-message and resend-message have been separated. With edit-message you get the full message text and all headers in your editor, and when you exit the editor, the message is re-read and placed in the index. No more w(rite) function calling from the compose menu. It works much better this way. :-) 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 / Who has the user's manual for Spaceship Earth -- please return it AT ONCE!
ignore [RESEND]
Hi! First of all, thanks for developing such a great piece of software! I am interested in seeing all the mail headers and then pruning them down. However, this doesn't seem to work: unignore * ignore X-Filter In-Reply-To Autoforwarded X-UID After 'unignore *', mutt seems to forget about the ignores. Am I doing something wrong? Thanks. -- "Does `competition' have a purpose?"
binding [] [RESEND]
The [ and ] keys are bound to half-page scrolling at the message list view. Can they do the same when viewing individual messages? What is the proper magic to make this happen? Thanks! -- "Does `competition' have a purpose?"
