I think this is a question for Ben - but if anyone else can help I’d appreciate it.
I’ve written an agent that combines text fields, rich text, and computed html into multipart/alternative MIME messages with a text/plain, and multipart/related text/html section. It even works with attachments.
Now, my code is ugly, but it’s still a work in progress. Part of the work is of course testing. This is where I’ve run into an issue - If I run the agent by itself it’s fine, if I use ‘tell amgr run’ on the console it’s fine, but If I run the agent with agent.runonserver, it does not appear to handle base64 encoded MIME parts (the appear to be quoted-printable encoded when the agent runs this way).
Does anyone know why this is?
I’ve tried setting the s.convertmime in the calling script, but that didn’t work.
The only work-around I can see is to look for non-text/mulipart MIME parts and decode them and recode them as base64, but if they are stored base64 to begin with, why are they being changed?