Thanks for your quick reply, > > I'm not sure who adds the full name (MUA? courier?) but I suspect it > > is done inside courier-mta, because in the logfile I see a line like: > No, your mail client sends a "MAIL FROM:" command with your email > address, which you see in your logs. It later sends the message, > including the headers, with your name improperly encoded. > > What can be done about it? > Ask the vendor for your mail client about the problem. Perhaps it is > simply misconfigured.
I use a local mutt in its standard config as "mail client". And indeed, by customizing the "From"-header mutt sends I can solve the problem. But I don't quite understand why courier doesn't do the RFC-2047-encoding of the from-header. In this way each and every MUA of every user (with non-ascii-characters in their full names) has to be configured to send the encoded header. By default, they seem to send "Full Name <address>" in their default config without further encoding. Wouldn't the mta be a better place to do the encoding? Or would that violate the appropriate standards? Thanks, Murx -- Paul Bläsi St.Ida-Str. 3 - 89171 Illerkirchberg [EMAIL PROTECTED] Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
