Forgot to add...
Ideal solution would be to disable XEXCH50 'protocol' on 5.5 server - but have never found a way to do this. Apparently it can be done on 2000, but not 5.5
Added this in case someone knows of a way...
We have been having similar problem - specifically related to XEXCH50 505 Authentication Required... Appears that Exchange servers unable to correctly exchange XEXCH50 binary info. Result is usually garbled message stream with sender/subject often blank and when message is opened it is starts...
Some more info...
This is related to problem when Exchange 2000 came out...
XEXCH50...354 Send Binary would not pass through firewall when Exchange2000 came out.
The sites with whom we have receipt problems are wanting XEXCH50 and are getting a 505 Authentication Required...
Unlike before...
Messages from certain sites arrive corrupted - OE client cannot determine sender/subject/attachement.
Viewing 'message' via OE or in 'archive' shows browsing activity and occasional merging of 2 messages (not an OE problem).
Not definitive, but there also appears to be an SMTP Interface...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.