--- Joachim Schipper <[EMAIL PROTECTED]> wrote:
> On Mon, May 28, 2007 at 08:37:42PM -0600, Philip Guenther wrote:
> > On 5/28/07, Juan Miscaro <[EMAIL PROTECTED]> wrote:
> > >I am serving up email via imap (courier-imap) on OpenBSD 4.0.
> > >
> > >My users (with Outlook) complain of french characters being
> garbled.
> > >How can I fix this?
> >
> > The same way any problem is fixed: by determining which part isn't
> > behaving correctly and fixing it. In this case, the possible
> guilty
> > parties include
> > A) the sending party: are the messages being marked with the
> correct
> > charset in
> > the Content-Type header field?
> > B) the IMAP server: is it returning the message accurately and
> calculating
> > the
> > ENVELOPE and BODYSTRUCTURE FETCH items correctly?
> > C) Outlook: is it presenting the messages accurately as it was
> received
> > from the
> > IMAP server?
> >
> > However, this is all off-topic to OpenBSD, as the IMAP server
> behavior
> > should not dependend on the OS. I suggest you take your question
> to
> > the comp.mail.imap newgroup after doing your best to answer the
> > questions suggested above.
> >
> > Note that when you post there you should, at a *minimum*, clarify
> what
> > is garbled (subjects, bodies, or both) and to what extent they are
> > "garbled": is it just the non-ASCII characters (those with accents
> and
> > cedilla and accents), all letters but not numbers or punctuation,
> or
> > all characters?
>
> Nah, misc@ does handle more off-topic questions; that's not a reason
> to
> tell someone off to a more specialized group, though it's true that
> the
> people there might be more capable of answering such a question.
>
> I'd try the following:
>
> 0. Get one of the complainers to provide you with a full
> (headers+body)
> e-mail and a copy that has been `fixed' (i.e., looks like it should).
> 1. Verify that the fixed version is properly formatted
> 2. Verify that Outlook can display it properly
> 3. Send it as-is to your mail server (nc mail.localdomain smtp <
> mail.fixed)
> 4. Look in the logs. Did anything interesting happen? If not, just
> get
> the message-id.
> 5. Retrieve the file directly from the mail spool. Is this already
> mangled? If so, good luck - that shouldn't happen. (And it's most
> likely
> a spam filter, not your MTA proper, that mangled it, as MTAs, at
> most,
> care for headers; try to disable the filter for a test account and
> run
> the test again.)
> 6. Retrieve the message via IMAP, using any known-good client. nc
> works
> fine; mutt might work, too. Is this mangled? If yes, fix the IMAP
> server, this shouldn't happen either.
> 7. Retrieve the message using Outlook. Is it broken? If so, something
> truly weird is going on, as the fixed version displated just fine in
> step 1...
>
> Post back with the information required by Philip and me, plus log
> files, and if at all possible complete copies of the messages.
Thank you for your pointers. It ended up being a bad Perl module
called by amavisd-new. I applied a patch to libnet 1.20 [1] and
everything is ok.
Juan
[1] It unwarrantedly attempts to convert 8-bit characters
to UTF-8 without considering a declared MIME type.
Ask a question on any topic and get answers from real people. Go to
Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
