Ondrej,

> Every mail passing through the mailserver gets its characters corrupted. I
> experimented with unicode character "ลก" (a common letter in czech
> alphabet), which is normally encoded in 2 bytes (utf-8). However, after
> passing through mailserver, resulting character occupies 4 bytes (!)

Upgrade Net::Cmd (from libnet)
(or amavisd-new to eliminate the need for libnet).


amavisd-new-2.5.0 release notes

- abandon the use of libnet (modules Net::SMTP and Net::Cmd), replaced by
  own code to implement client-side SMTP and LMTP protocol support, with a
  full support for pipelining and IPv6. Some of my issues with Net::SMTP go
  back to year 2002, but the one that broke camel's back is a 3+ months
  status quo in not fixing a serious misfeature introduced in 1.20, which
  mangles 8-bit characters in mail, causing a series of support questions,
  and even affecting some larger service providers without them realizing
  there is a problem. Here are some relevant bug reports:
    http://rt.cpan.org/Public/Bug/Display.html?id=24835
    http://rt.cpan.org/Public/Bug/Display.html?id=2608
    http://rt.cpan.org/Public/Bug/Display.html?id=2607
    http://rt.cpan.org/Public/Bug/Display.html?id=14875
    http://rt.cpan.org/Public/Bug/Display.html?id=9394

  P.S. libnet-1.21 eventually fixed the UTF8 encoding problem and
  added support for ENVID and AUTH options; other issues are still open
  (e.g. split code/text in smtp status, no pipelining support, no LMTP);


Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to