[ David Champion Wrote On Sun 25.Nov'12 at 23:26:49 GMT ] > * On 25 Nov 2012, Jamie Paul Griffin wrote: > > > > The script works on all messages except those with Content-Type: > > Multipart/* > > This doesn't ring a bell to me, and I'm finding that it works with > single samples of multipart/alternative and of multipart/related. Could > you provide the message you're having trouble with -- off-list if you > prefer? > > In the end the new version of the message is generated by formail, so > it's subject to formail's limitations, if it has any. (I don't know of > any.) It would be possible to update the python script to handle the > rewrite with python core modules instead of depending on formail. Maybe > that's worth a try. > > The actual replacement of content is done by mutt itself, using same > <edit> function as when you edit in vi, so there should be no issue > while using this script that you don't usually see while editing a > message. > > > > I thought it was a permissions problem because the messages i had issues > > with were in my spoolfile in /var - most mailing list messages, i.e. > > messages in mailboxes in my home directory are not in that format, > > leading me to believe the script was having issues executing on messages > > located under /var. > > This gives me a thought. Are you using mbox for some folders, and > maildir for others? Formail will always produce output with a UNIXv7 > (mbox) "From " pseudo-header. That could be a factor.
I am using mbox for all folders currently. I will send the mail to you off-list. Jamie
