On Mon, 29 Dec 2003 17:54:55 -0500, Bill Cole <[EMAIL PROTECTED]> wrote
In other words, Exchange is misdesigned, and when it sees a message whose character set it does not understand, it freaks out and does this. There's no good reason for an MTA to care about what character set a message uses, but Exchange does.
I whole heartily agree. Talking with MS Exchange administrators usually ends with their saying "We're running the latest MS version so your mail server must be causing the problem." The misleading to novices error message Exchange gives its users isn't helpful at all.
Content-Type: text/plain; charset="0"; format=flowed
Oh really? What is the '0' charset???
[...]Something, either MIMEDefang (doubt it) or Windows Eudora (likely) or one of the sendmail hops (extremely unlikely) is putting 'charset="0"' into the Content-Type header and screwing this mail up. That should say something like 'charset="us-ascii"' or 'charset="iso-8859-1"' or leave out the charset altogether, but something is putting a bogus charset there. Whatever is doing that is bad and wrong and needs a spanking.
Bill, once again you prove you are an astute man. I've seen the ="0" but not knowing what is acceptable, I presumed this was fine. Telling folks who are using Eudora 6 (and need to talk with those on Exchange) to downgrade to Eudora 5 seems to have "fixed" the problem. I had read nothing about that issue on Eudora's website...strange.
Thanks,
Joe
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
