Auteur: Ron McKeating Date: À: Alan J. Flavell CC: Exim-Users \(E-mail\) Sujet: Re: [exim] Iconv
On Fri, 2005-09-30 at 16:35 +0100, Ron McKeating wrote: > On Fri, 2005-09-30 at 16:09 +0100, Alan J. Flavell wrote:
> > On Fri, 30 Sep 2005, Ron McKeating wrote:
> >
> > [...]
> > > 2005-09-30 00:29:23 1EL7q6-0000sg-Sw => >ÑîÏÈÉú <szyang8@???>
> > > <adpgt@???> R=vacation T=address_reply
> > >
> > > What I want to know is if I recompile exim with the
> > >
> > > # HAVE_ICONV=yes option, will this convert the foreign
> > > char set
> > ^^^^^^^^ <snip>
OK have done a little more investigation.
An email came in for a user with the following headers
From: =?GB2312?B?0e7PyMn6?= <szyang8@???>
Subject: =?GB2312?B?0rXO8aOhtPq/qrj3wOC3osaxo6E=?=
To: pgprospectus@???
Content-Type: text/plain;charset="GB2312"
The vacation script automatically replies to say this bod is on hols.
The log entry is
So, is this what exim is supposed to do, it seems to have converted the
address ?GB2312?B?0e7PyMn6?= <szyang8@???> on the from line into
ÑîÏÈÉú <szyang8@???> by the time it gets into the log. This latter
entry breaks exilog, which is why we discovered it.
The body of the email is unreadable and is probably Korean. Any thoughts
on how we can stop this happening?
Ron
>
> --
Ron McKeating
Senior IT Services Specialist
Computing Services
Loughborough University
01509 222329