| Server IP : 85.214.239.14 / Your IP : 3.15.34.105 Web Server : Apache/2.4.62 (Debian) System : Linux h2886529.stratoserver.net 4.9.0 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.18 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /proc/2/task/2/cwd/proc/3/root/etc/amavis/ |
Upload File : |
$Id: README.l10n 742 2005-12-26 17:15:22Z hmh $ First of all, read /usr/share/doc/amavisd-new/README.customize.gz Amavisd-new is UTF8-aware, and it will do character-set conversion when dealing with DSN templates. The full unicode codespace is available, if used with the proper encodings... and you have to use the proper encodings if you don't want your DSNs to be flagged as more charset-challenged SPAM by other systems. ALWAYS respect the charset when adding l10n files. Amavisd-new does charset conversion twice: one when reading the text files with localized templates (to internal perl UTF8), and another when writing the email notification (from internal perl UTF8 to $hdr_encoding and $bdy_encoding). Headers will be RFC2047-encoded if they have any codepoints not allowed by RFC2822 after the charset conversions. The body text charset encoding is inserted in the proper MIME header. More details are available in /usr/share/doc/amavisd-new/RELEASE_NOTES.gz