On Sunday 02 November 2003 14:34, Martin Furmanski wrote:
I have a problem. When an attachments name contains an o with
two dots above it, courier reformats the whole mail to an error and the
original mail is attached in a file called message.txt.
<short answer>
Put "opt BOFHBADMIME=accept" into the "bofh" file in your courier 'etc'
directory. That will solve the problem.
</short answer>
<long answer>
This is a very common problem. The o umlaut character is a high ascii
character, that is 8-bit, not normal 7-bit. So the mail client should create
the proper MIME headers explaining that this message contains 8-bit content
and should be treated appropriately. But many clients don't bother. They
label the message standard "text", which is it NOT.
Courier sees that the message itself does not match the stated encoding and
wraps the message as an attachment. This is "The Right Thing" to do.
Unfortunately it's a case where doing the right thing will get you lots of
support calls from users who don't care that their messages are wrongly
encoded - they just want to see them, even if a wrongly encoded message can
cause their client to choke. (They'll call you about that too! ;-)
So put "opt BOFHBADMIME=accept" into the "bofh" file in your courier 'etc'
directory and courier will simply pass these wrongly encoded message on as
is. This can (and does occasionally) cause mail clients to choke but it's
the lesser of two evils in most people's minds.
</long answer>
10 messages in net.sourceforge.lists.courier-users[courier-users] Umlauts choke messages
