bcssTommy
Guest
|
 Posted:
Mon Jan 17, 2005 5:41 am Post subject:
RE: attachments not available in OWA2K3 with certain mime co |
|
|
I am having the same problem with my unified messaging server. It will show
up correctly in O2k3 client but like you, only shows the paper clip in
OWA2003. This is a major issue for use since a majority of our voice mails
are deployed from the UM server and end-user's are needing to use OWA2003 to
view them. Any help/information would be greatly appreciated.
Thanks
Tommy
"Jsteinberg" wrote:
| Quote: | I am having a problem where my OWA2003 users are unable to view attachments
sent by my fax2email application.
The application sends emails using the following in the main header section:
MIME-Version: 1.0
Content-Type multipart/fax-message
and the following in the attachment section:
--_----------=_10167391557129230
Content-Transfer-Encoding: base64
Content-Type: image/tiff; name="direcfax.tif"
These attachments are not available on OWA 2003. I can see the paper clip
in the inbox list but the attachment is not there when you view the email.
If i add the following mime header in the attachment section
Content-Disposition: attachment; filename="direcfax.tif"
or if i change the mime content-type in the main headers to:
MIME-Version: 1.0
Content-Type: multipart/mixed
I can read the attachment in owa 2003. This issue does not cause problems
for FAT clients. The problem is that I can not modify the way the fax
application sends mail to exchange smtp. I assume either OWA2003 or my fax
app is not adhering to RFC's properly. Anyone experiencing a similiar
problem?
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in