As I mentioned earlier, I modified rc.local.s00 to store a copy of the incoming email before it got processed by Smartlist so that I could compare the 'before' and the 'after' to see why base64-encoded messages were getting garbled.

I finally got a message that did get messed-up and on checking the headers, I found that everything was just fine. Smartlist didn't change anything that could have caused the problem. This was good because that's what I would have expected from a mailing list manager. This was bad because now I had to look a bit deeper as to why this was happening.

Anyway, I did look a bit closer and found that the problem had nothing to do with Smartlist. I add a header and a footer to all the messages sent on the mailing list and these were confusing the MUAs when they tried to decode the base64 message. The apps assumed that the plain-text header was part of the encoded message and tried to decode it and failed. Mystery solved!

I still don't know how to fix the problem but now I know what causes it. And that is good.

Regards, - Harshal

__________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/