Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


MIME setting changing in some apps

By Tech-No ·
I have created HTML email 'signature' files for use in Outlook Express, MS Outlook and Lotus Notes. All work fine, showing pretty text and inline graphic...except on some computers, but not in all instances on those computers. In a couple of instances, when sending from Lotus Notes R5 (using MIME), the email is rec'd as plain text on Outlook Express 6, while the same email is rec'd perfectly by other Outlook Express 6 email clients. In those cases, the multipart/related has been changed to multipart/mixed and the text/html has been changed to text/plain. In one other situation, the inline graphic (which uses a URL address for the graphic) will not show the graphic on the originating computer or the receiver's computer although the text is 'pretty', but using the exact same signature file now loaded on the previously receiving computer, the graphic shows up on both that computer and the previously originating computer. I have searched and searched, but have not been able to determine where the problem is. I assume there is some inconsistent setting somewhere, but I don't know where. I have tried turning off the virus scanner on the receiving computer, but that has made no difference. I need to ensure the signature files are robust - can anybody help me?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by Bork Blatt In reply to MIME setting changing in ...

Signatures at the bottom of e-mails are a great idea.

Unfortunately, if you use fancy fonts and embedded images, you have no guarantee that the person on the other side is going to see it the way you designed it.

E-mail was designed as a plain text medium, and has recently been expanded to include HTML support, embedded images etc. Many e-mail clients however, don't support HTML, and many companies and users turn off HTML support and block attachments because of the security risks associated with these.

I recommend that you design your sig in such a way that if all else fails, the plain text version has all the info in and looks neat. There are just too many variables on the client side that are out of your control.

I'm sorry - this isn't the answer you were looking for, but I hope it helps anyway.

Related Discussions

Related Forums