Has anyone found any sort of fix for this issue? It seems when any of
my clients sends a message with a vcard from one network to another,
the vcard is changed to a blank message. This doesn't happen within a
network/domain.

If they force Rich Text Format on the recipient's address, doe it work then?

--�
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, centre21 asked:

| Has anyone found any sort of fix for this issue? It seems when any of
| my clients sends a message with a vcard from one network to another,
| the vcard is changed to a blank message. This doesn't happen within a
| network/domain.

We did and it doesn't seem to matter what format the message is sent
in, it still comes out that way.

It seems that they weren't listening to me when I told them to use the
"forward as vcard" option off the Action menu. Now that things have
been cleared up, it's working just fine. Thanks for all your help.

Are you using an Exchange server?

If so, launch system manager, Go to Global Settings, Internet Message format.

Now, you have two options he
1.) Modify the default domain rule
2.) Or create a domain rule to target a domain you know is an Exchange domain

in either case, you want to edit the properties so that on the message
format tab, you have selected UUEncode and on the advanced tab in the
exchange rich-text format tab, you have selected always use.

Caveat:
If you change the default rule to these settings, then foreign messaging
systems that cannot handle exchange rich-text will convert the message to
plain text and all extra formatting and attachments will be rolled into a
"windmail.dat" file on the recipient system, so use this option judiciously.

What I've done in my environment is change my default and then I've created
rules for email domains I know to be HTML based (google, yahoo, etc) and set
mail bound for those domains to force html.


"centre21" wrote:

It seems that they weren't listening to me when I told them to use the
"forward as vcard" option off the Action menu. Now that things have
been cleared up, it's working just fine. Thanks for all your help.