On Tue, 02 Jun 2015 07:07:24 -0400 Sam Varshavchik <mr...@courier-mta.com> wrote:
> Milan Obuch writes: > > > I would like to modify templates so that all server generated mails > > will be both in local language (Slovak in my case) and English. Is > > something limiting me in what I can use here? Is something hardcoded > > somewhere or all text is pulled from templates? > > All text comes from the *.txt template files. The only part that does > not is the log of the actual SMTP commands. > > > Also is there any way to test it? I don't know all condition when > > such message is generated, I hope someone could help with this. > > There are only four types of DSN messages. There are multiple reasons > for some of them, but in all cases the only difference are the logged > SMTP commands. > > A delivery failure > > A warning message if message could not be delivered for several hours > > A successful delivery, if the sender requested a return receipt > > A notification that a successful delivery receipt cannot be provided > because the message was forwarded to the recipient's mail server > which does not implement delivery confirmation receipts. > > In all cases, dsnheader.txt gives the header portion of all DSNs, so > your obvious first step would be to change charset=us-ascii to > charset=UTF-8, so that you can rewrite the rest of the templates in > the UTF-8 codeset. > Thanks. After some testing I modified all dsn*.txt files with acceptable results. Report generated is a bit weird given it is created in more parts, each one separatelly translated, so two languages are interlaced. But it works. Just a minor nit - after modifying any file, 'courier restart' was necessary for changes to become effective. Another question - what about rfcerr*.txt files? They are more technical in nature, but still it should be usefull to make them localised the same way, i. e. bilingual. IS there anything special? What makes me asking that is following in rfcerrheader.txt: Content-Type: text/plain; format=flowed; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Comment: The following content can be customized provided that: Comment: 1) These MIME headers are preserved (you may change the charset Comment: or drop format=flowed). Comment: 2) This content is manually quoted-printable encoded, it MUST NOT Comment: contain 8-bit text. Comment: '~' below is replaced by server name. Are they different in content encoding? Regards, Milan ------------------------------------------------------------------------------ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
