"... inserted with HTML code" how? From the saved .htm signature file? Through some add-in?

In any case, you'll probably want to ask about this in the microsoft.public.exchange.clients or m.p.e.admin newsgroup. Since the problem is only with mail sent externally through Exchange 5.5, chances are that it's the source of the problem.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Andy" wrote in message ...
Ok,

Here is the situation:

- Outlook 2000 Workgroup Only format to send mail: HTML
- Exchange Server 5.5, provides messages for pop3 and imap: html.
- Outlook Express 6 (POP3 access) sends and receives as html.


all email clients have a png file as signature, inserted with html code.
(img src= /

Situations:
a) Outlook 2000 WO, sends email to another Outlook 2000 WO, signature Ok.
b) Outlook 2000 WO, sends email to Outlook Express 6 (or any other
client with pop3 access), signature NOT ok. (appears a red X telling me
that it can't find the file)

c) any other client (not our outlook clients) with signature sends email
to Outlook Express 6, signature Ok.

So, it seems that the problem is when an outlook inside exchange network
sends email to outside clients using pop3. so, what can i do ?

here is an example of the message format:

-------
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----_=_NextPart_000_01C65CA6.A3FBC2F0"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C65CA6.A3FBC2F0
Content-Type: text/html;
charset="iso-8859-1"

!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
HTMLHEAD
META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"


META content="MSHTML 6.00.2800.1505" name=GENERATOR/HEAD
BODY
IMG src="cid:796170914@10042006-3722"
/BODY/HTML

------_=_NextPart_000_01C65CA6.A3FBC2F0
Content-Type: image/png;
name="sign.png"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="sign.png"
Content-ID: 796170914@10042006-3722

[here the chunk of data follows...]

-------

Any advice will be really appreciated, thanks!