J
Jarryd
Hi,
I have been battling with this problem for ages now, and have finally come
to the conclusion that this is an OL2007 issue.
Since we upgraded to OL2007 I noticed a few emails bouncing back from a
specific domain. As this external domain belongs to a company in our group
I know the sys admin and what he has set up. They have a Watchguard
firewall with an SMTP proxy configured for incoming email traffic. This
proxy checks for emails with lines containing more than 1000 characters and
rejects them:
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<srvr3.toray-tel.co.uk #5.5.0 smtp;500 Line too long>
After turning on logging for OL 2007, SMTP logging for my server, messing
around with Internet Message Formats in ESM, and sending multiple variations
of known problematic emails from OL2007 (Actions>Resend this message) and
other clients (OWA, OL2003) I am quite sure that the problem lies with
Oultook 2007. If I inspect the underlying code in these emails, which in
HTML formatted (converting to plain text solves the problem), I can see that
the ones created in OL2007 have HTML code in the source that is way way
longer than that created by OWA and OL2003:
________________________
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns
="urn:schemas-microsoft-comfficeffice"
xmlns:w="urn:schemas-microsoft-comffice:word"
xmlns:x="urn:schemas-microsoft-comffice:excel"
xmlns
="urn:schemas-microsoft-comfficeowerpoint"
xmlns:a="urn:schemas-microsoft-comffice:access"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema"
xmlns:b="urn:schemas-microsoft-comfficeublisher"
xmlns:ss="urn:schemas-microsoft-comffice:spreadsheet"
xmlns:c="urn:schemas-microsoft-comffice:component:spreadsheet"
xmlnsdc="urn:schemas-microsoft-comfficedc"
xmlnsa="urn:schemas-microsoft-comffice:activation"
xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns
="DAV:"
xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml"
xmlnsis="http://schemas.microsoft.com/sharepoint/soap/ois/"
xmlns:dir="http://schemas.microsoft.com/
________________________
That's all in one line, and I don't think its the longest one.
Why does OL2007 (MS Word email editor) have to use so much code in one line,
and is there a way to stop it from doing this, i.e. start new line after 999
characters, either in Outlook or Exchange. The only thing I can think of is
doing something with VBA, but what a mission. I really need to be able to
send to this site and these bounce backs are really annoying. It doesn't
always create these lengthy lines of code, so the problem was erratic and a
pattern hard to determine. Anyway, I have soldiered on and I am pretty sure
I have found the cause, but now I am worried that I might have pretty much
wasted my time as a simple solution may not exist. I am not a programmer by
trade, but I can do it... slowly. Obviously I am reluctant to start down a
looooong and winding road that might not lead me to a positive result.
Please help, I have spent a shed load of time on this and really need to get
it sorted. At the moment I have told users to change the format of the
message to Plain Text when they encounter this problem, but this will not
always be an ideal permanent solution.
TIA,
Jarryd
I have been battling with this problem for ages now, and have finally come
to the conclusion that this is an OL2007 issue.
Since we upgraded to OL2007 I noticed a few emails bouncing back from a
specific domain. As this external domain belongs to a company in our group
I know the sys admin and what he has set up. They have a Watchguard
firewall with an SMTP proxy configured for incoming email traffic. This
proxy checks for emails with lines containing more than 1000 characters and
rejects them:
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<srvr3.toray-tel.co.uk #5.5.0 smtp;500 Line too long>
After turning on logging for OL 2007, SMTP logging for my server, messing
around with Internet Message Formats in ESM, and sending multiple variations
of known problematic emails from OL2007 (Actions>Resend this message) and
other clients (OWA, OL2003) I am quite sure that the problem lies with
Oultook 2007. If I inspect the underlying code in these emails, which in
HTML formatted (converting to plain text solves the problem), I can see that
the ones created in OL2007 have HTML code in the source that is way way
longer than that created by OWA and OL2003:
________________________
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns
="urn:schemas-microsoft-comfficeffice"xmlns:w="urn:schemas-microsoft-com
ffice:word"xmlns:x="urn:schemas-microsoft-com
ffice:excel"xmlns
="urn:schemas-microsoft-comfficeowerpoint"xmlns:a="urn:schemas-microsoft-com
ffice:access"xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema"
xmlns:b="urn:schemas-microsoft-com
fficeublisher"xmlns:ss="urn:schemas-microsoft-com
ffice:spreadsheet"xmlns:c="urn:schemas-microsoft-com
ffice:component:spreadsheet"xmlns
dc="urn:schemas-microsoft-comfficedc"xmlns
a="urn:schemas-microsoft-comffice:activation"xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns
="DAV:"xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml"
xmlns
is="http://schemas.microsoft.com/sharepoint/soap/ois/"xmlns:dir="http://schemas.microsoft.com/
________________________
That's all in one line, and I don't think its the longest one.
Why does OL2007 (MS Word email editor) have to use so much code in one line,
and is there a way to stop it from doing this, i.e. start new line after 999
characters, either in Outlook or Exchange. The only thing I can think of is
doing something with VBA, but what a mission. I really need to be able to
send to this site and these bounce backs are really annoying. It doesn't
always create these lengthy lines of code, so the problem was erratic and a
pattern hard to determine. Anyway, I have soldiered on and I am pretty sure
I have found the cause, but now I am worried that I might have pretty much
wasted my time as a simple solution may not exist. I am not a programmer by
trade, but I can do it... slowly. Obviously I am reluctant to start down a
looooong and winding road that might not lead me to a positive result.
Please help, I have spent a shed load of time on this and really need to get
it sorted. At the moment I have told users to change the format of the
message to Plain Text when they encounter this problem, but this will not
always be an ideal permanent solution.
TIA,
Jarryd