On 6/22/05, Henrik Andreasen <[EMAIL PROTECTED]> wrote: > On 6/20/05, Robert Mortimer <[EMAIL PROTECTED]> wrote: > > > The problem should not reside with the Exchange server. The email > > clients should be the ones to put the HTML together. That said both > > active directory and exchange can boss Outlook clients around. Try > > sending some mail through the exchange server using different clients > > I don't have access to the server, so I can't really test it with > other clients – don't know if the people running it, will test it with > other clients tho, but I'll defiantly ask them
If you have the IMAP settings for SM you can use them to get an IMAP connection from an alternate client. > > > and try viewing mails using a different IMAP client. > > I've been playing around with outlook express, it displays the mails just > fine. > OE hasn't got any problems decoding the mail and showing it, so it's > probably something in the mails Squirrelmail don't understand. > > > I would suggest looking at client machine localisation and exchange > > server localisation. > > Do you know or have any ideas, what they shall look after? You could try setting SM's default character set $default_charset = 'iso-8859-1'; to $default_charset = 'us-ascii'; in the config file > > > IMHO Exchange and Outlook are groupware applications with some mail > > functions integrated. Traditionally they had poor support for Internet > > standard mail protocols > > It's made the M$ way - use it as we want you to, if you don't, you'll > get at shitload of problems:-D > > > Thanks for the reply Robert. > Hope I'll get this problem solved, as I really like SM and will hate > to have to change my webmail, just because of this. > > > -- > Henrik >
