>> [MIME message structure description] > Are you sure, you have closed every part properly?
I used the swiftmailer library to construct the mail and mutt properly recognizes the parts when it receives the mail via a bounce, so I suspect the mail is well-formed but of course there might be subtleties. > I do some things similary, BUT I use commandline tools, to create > the multipart/alternative and then I move the complete file to > the ~/Maildir/.Drafts/new/ folder, where mutt can find it if I > recall a message. I'm happy it seems to work for you, and that the problem's probably in my chair. Would you be kind enough to send me a direct email to mutt.wa...@ptaff.ca using your method? That may help me figure out what's so different between your mail structure and mine. Just out of curiosity, when you recall the message, does the editor show only the text/plain part? It seems I always get an improperly unwrapped version of the multipart/alternative part. And when you exit the editor, are you saying all MIME parts left unchanged? > You can use sendmail or ssmtp to send the file without using mutt. It > is much easier, specially from a script. I get that, but I'd prefer dealing with GPG inside mutt, I want to avoid recreating mutt's perfectly fine interface for it (selecting keys for instance). Thanks, and have a nice day, -- · Patrice Levesque · http://ptaff.ca/ · mutt.wa...@ptaff.ca --
signature.asc
Description: Digital signature
