SDP & Exchange 2007, still not working with attachments
Hi All.
There appears to be an issue with SDP and the way it create attachments sent via e-mail, from requests.
The problem occurs under these following conditions.
a) The e-mailserver is a Exchange 2007 SP1 installation
b) The Client is running Outlook 2003.
The User can see that there is an attached document (it has a paperclip), but if he opens the e-mail there does not appear to be any attached document.
If the user opens OWA 2007, it allows him to both see and open the document correctly.
The reason why this doesnt work:
SDP initiates a SMTP connection to the server, and when it inserts the attachment, it uses the wrong code for attachments, namely multipart/related message type.
How for Adventnet to fix this for its users:
SDP needs to initiate the attachment process in SMTP by using the mutlipart/mixed message type instead.
It should be a fast fix, and possible to have put into the 7505 patch, we really need it since it is not a bug in Exchange, its just that Exchange 2007 SP1 actually have started to following correct RFCs
Regards
Christian
There appears to be an issue with SDP and the way it create attachments sent via e-mail, from requests.
The problem occurs under these following conditions.
a) The e-mailserver is a Exchange 2007 SP1 installation
b) The Client is running Outlook 2003.
The User can see that there is an attached document (it has a paperclip), but if he opens the e-mail there does not appear to be any attached document.
If the user opens OWA 2007, it allows him to both see and open the document correctly.
The reason why this doesnt work:
SDP initiates a SMTP connection to the server, and when it inserts the attachment, it uses the wrong code for attachments, namely multipart/related message type.
How for Adventnet to fix this for its users:
SDP needs to initiate the attachment process in SMTP by using the mutlipart/mixed message type instead.
It should be a fast fix, and possible to have put into the 7505 patch, we really need it since it is not a bug in Exchange, its just that Exchange 2007 SP1 actually have started to following correct RFCs
Regards
Christian