Re: Is there a way to let mutt send rfc2047 encoded attachment?
As pointed by Kun Niu <[EMAIL PROTECTED]>, I finally get that one working. Although the patch is provided for mutt-1.5.10, it also works for mutt-1.5.16. See http://learn.tsinghua.edu.cn:8080/2002315162/muttpatched.html That webpage is written in Chinese. So I summarize it in the following: First you need download a patch for mutt, which is at http://www.emaillab.org/mutt/download1510.html. Then apply the patch. Finally you can set whether or not to send RFC 2047 encoded mail by setting the parameter "create_rfc2047_parameters" to yes or no. I also set some send-hook for convience: send-hook "\.ac\.cn" "set create_rfc2047_parameters=yes" send-hook "\.gmail\.com" "set create_rfc2047_parameters=yes" You can set your own hook like these. On Tue, Dec 02, 2008 at 10:38:50AM +0800, Shaochun Wang wrote: > Hi all: > > > I know RFC 2047 encoding MIME is explicitly prohibited by the > standard. But unfortunately, a lot of my correspondents use the email > client which only decoded RFC 2047 encoded attachment, not RFC 2231, > including gmail. > > So my question is that is there some way to let mutt sent RFC 2047 > encoding attachment? > -- Shaochun Wang <[EMAIL PROTECTED]> Jabber: [EMAIL PROTECTED]
Re: Is there a way to let mutt send rfc2047 encoded attachment?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, December 2 at 10:38 AM, quoth Shaochun Wang: > I know RFC 2047 encoding MIME is explicitly prohibited by the > standard. But unfortunately, a lot of my correspondents use the > email client which only decoded RFC 2047 encoded attachment, not RFC > 2231, Nope. According to the man page: "mutt will unconditionally use the encoding specified in RFC2231" ... for *sending*. I.e. mutt can *read* incorrect messages, but cannot *send* incorrect messages. > including gmail. Yikes! > So my question is that is there some way to let mutt sent RFC 2047 > encoding attachment? Not at the moment. You may want to make the request to mutt-dev ~Kyle - -- Most truths are so naked that people feel sorry for them and cover them up, at least a little bit. -- Edward R. Murrow -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkk0oakACgkQBkIOoMqOI17/JwCfSkFROD+nC8mzAEN8jz8qWXN/ fAEAoPUFnGJ6GzTh2QjxlPNogEZFv3MA =mDU/ -END PGP SIGNATURE-
Is there a way to let mutt send rfc2047 encoded attachment?
Hi all: I know RFC 2047 encoding MIME is explicitly prohibited by the standard. But unfortunately, a lot of my correspondents use the email client which only decoded RFC 2047 encoded attachment, not RFC 2231, including gmail. So my question is that is there some way to let mutt sent RFC 2047 encoding attachment? -- Shaochun Wang <[EMAIL PROTECTED]> Jabber: [EMAIL PROTECTED]
Re: save-message to ? and then sync the folder
* On 2008.11.27, in <[EMAIL PROTECTED]>, * "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > Hello > > how can I sync the mailbox after save a message to any folder like this: > > macro s "?" > > the above works great, but after this save mutt should sync > automatically. Like this: > > macro s "?" This works for me. macro index S 'set my_folder=`mutt-prompt "Save to folder" \\`; push $my_folder\' Be sure to enter it in only one line. The backslashes are wacky, but so are mutt's quoting rules. This is no typo; it really does work on my system. A "mutt-prompt" script is required; see attachment. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago #!/bin/sh ## ## usage: mutt-prompt "prompt text" ## ## In muttrc: ## set my_var=`mutt-prompt "Folder"` ## # save current tty state s=`stty -g` # redirect default i/o, saving current stdout in fd 5 exec 5>&1 exec >/dev/tty &5 # reset tty state stty "$s"
Re: save-message to ? and then sync the folder
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, November 27 at 02:20 PM, quoth [EMAIL PROTECTED]: >how can I sync the mailbox after save a message to any folder like >this: > >macro s "?" > >the above works great, but after this save mutt should sync >automatically. Like this: > >macro s "?" Well, the trick here is that you're giving mutt a bunch of things to do all at once, as others on this list have suggested. HOWEVER, I think this can be done if you're especially clever. The '?' part of the macro puts you into the browser. To then get mutt to do something as you *exit* the browser (i.e. after you've selected an entry), you'd need to tuck your desired behavior into the methods of exiting from the browser. For example: macro index s " macro browser \\ ''?" It would be even cooler if you could have the secondary macro clean up after itself: macro index s " macro browser \\ 'bind browser return'?" ... but there seems to be some problem with the handling of in the rebinding part that I can't quite figure out. ~Kyle - -- Look, I can surely say by now that I've got the antibodies to communism inside me. But when I think of consumer society, with all its tragedies, I wonder which of the two systems is better. -- Pope John Paul II, 1979 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkkz//EACgkQBkIOoMqOI14IBACfcx9aKGaIIgXGXKFLVxJ/uYCu 478AnRJNnUPwqMj4H8XIKyUjNIkN3ceP =ltLX -END PGP SIGNATURE-
Re: save-message to ? and then sync the folder
Hi, * [EMAIL PROTECTED] wrote: > macro s "?\n" > or > macro s "?" I think the issue is that he would like to select a mailbox using the folder browser, and then continue on executing the rest of the macro. yes, I want to using the browser, then after syncing the mailbox... Sorry, that won't work as Michael described. I already wondered why someone would name a mailbox "?" :) Rocco
