|
|||||||
| Computers, Coding, Websites or anything techie Help, assistance, advice and discussions on anything to do with computers, hosting, web coding or anything technical! |
|
|
LinkBack | Thread Tools | Display Modes |
|
||||
|
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 |
|
||||
|
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_USER\Software\Microsoft\Office\12.0\O utlook\Options\Mail 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! |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|