forum avatar

Exchange 2003 and Outlook 2007 issues

By
Published 7th October 2009 |
Read latest comment - 13th October 2009

have posted eslewhere, but will try here as well.

we have an annoying bug with our office mail server, that when we send emails to some accounts, the formatting seems to be lost, and line breaks become huge gaps. Assuming it must be a setting somewhere either in outlook or exchange.

more of an annoyance rather than an actual problem, but would be nice to get sorted!
Comments
forum avatarServer Guy
7th October 2009 10:47 AM
in outlook, if you go to options, there should be a tickbox that say - remove extra line breaks in plain text messages

make sure this is ticked, that should work.

forum avatarJonesy
7th October 2009 2:40 PM
thanks, but that option is ticked, and we still seem to have the same issue. Not on all browsers, but gmail is a good example that adds too many lines.

Thsiis usual caused by multiple content scanners adding check point page breaks.
can you PM me with an example of what you are seeing.

Stavros

forum avatarJonesy
12th October 2009 12:23 PM
PM sent, many thanks!!

forum avatarGreg
13th October 2009 2:13 PM
Exchange can be over complicated, I've heard all sorts of problems. Why not goto Open source, loads of good stable freeware out there

42 of the Best Free Linux Email Software - LinuxLinks News

forum avatarJonesy
13th October 2009 4:10 PM
Thanks Greg, but office wise, we're a Microsoft shop. The actual webservers are all Redhat though

For info, in case anyones interested, Stavros has fixed the problem.

I'll paste what he PM'd me

"Content-Type: text/plain;
ch****t="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

321

=20

Outlook is still trying to use QP which is not mime compliant.
the =20 means the mime scanners have scanned your mail and cannot understand the character set and has added the page breaks.

You can make sure it's not on in Outlook at Tools>Options>Mail Format>Settings. The "Encode text as" item lets you choose none, quoted-printable or base64 encoding."


This didn't work, so Stavros suggested a registry fix, which did the job, although the client machines needed to be rebooted before it took effect.

"The following registry key exists:
In Microsoft Office Outlook 2007:
HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0OutlookOptionsMail
The registry key contains a DWORD Value that is named InternetMailTextEncoding
If the value data is 2, Outlook uses Base 64 encoding.

If its not there, then create it"


Thanks to Stavros for his help!

This Thread is now closed for comments