ALT Linux Bugzilla
– Attachment 2247 Details for
Bug 13281
Некорректный шаблон /etc/amavis/notify_sender.txt
New bug
|
Search
|
[?]
|
Help
Register
|
Log In
[x]
|
Forgot Password
Login:
[x]
|
EN
|
RU
Шаблон DSN на русском языке
notify_dsn.txt (text/plain), 8.48 KB, created by
Alexander Andreev
on 2007-10-31 16:32:06 MSK
(
hide
)
Description:
Шаблон DSN на русском языке
Filename:
MIME Type:
Creator:
Alexander Andreev
Created:
2007-10-31 16:32:06 MSK
Size:
8.48 KB
patch
obsolete
># ># ============================================================================= ># This is a template for (neutral: non-virus, non-spam, non-banned) ># DELIVERY STATUS NOTIFICATIONS to sender. ># For syntax and customization instructions see README.customize. ># The From, To and Date header fields will be provided automatically. ># Long header fields will be automatically wrapped by the program. ># >Subject: [?%#D|Undeliverable mail|Delivery status notification]\ >[? [:ccat_maj] |, CLEAN (other)||, TEMPFAIL\ >|, OVERSIZED message\ >|, invalid header[?[:ccat_min]||: bad MIME|: unencoded 8-bit character\ >|: improper use of control char|: all-whitespace header field|]\ >|, UNSOLICITED BULK EMAIL apparently from you\ >|, UNSOLICITED BULK EMAIL apparently from you\ >|, contents UNCHECKED\ >|, BANNED contents type (%F)\ >|, VIRUS in message apparently from you (%V)\ >] >Message-ID: <DSN%i@%h> > >[? %#D |#|÷ÁÛÅ ÐÉÓØÍÏ âùìï õóðåûîï ðåòåîáðòá÷ìåîï ÓÌÅÄÕÀÝÉÍ ÁÄÒÅÓÁÔÁÍ:[\n %D] >] >[? %#N |#|óÏÏÂÝÅÎÉÅ îå âùìï ÐÅÒÅÎÁÐÒÁ×ÌÅÎÏ ÓÌÅÄÕÀÝÉÍ ÁÄÒÅÓÁÔÁÍ:[\n %N] >] >[:wrap|78|||üÔÏÔ ÏÔÞÅÔ Ï [?%#D|ÎÅ×ÏÚÍÏÖÎÏÓÔÉ ÄÏÓÔÁ×ÉÔØ ÐÉÓØÍÏ|ÄÏÓÔÁ×ËÅ ÐÉÓØÍÁ] \ >Á×ÔÏÍÁÔÉÞÅÓËÉ ÓÏÚÄÁÎ ÐÒÏÇÒÁÍÍÏÊ amavisd-new ÎÁ ÓÅÒ×ÅÒÅ %h. \ >ëÏÄ ×ÁÛÅÇÏ ÐÉÓØÍÁ × ÎÁÛÅÊ ÓÉÓÔÅÍÅ %n/%i] > ># ccat_min 0: other, 1: bad MIME, 2: 8-bit char, 3: NUL/CR, ># 4: empty, 5: long, 6: syntax >[? %#X ||[? [:ccat_min] >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá > (INVALID HEADER:) >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá: îÅÐÒÁ×ÉÌØÎÙÊ ÚÁÇÏÌÏ×ÏË MIME ÉÌÉ ÎÅÐÒÁ×ÉÌØÎÁÑ MIME ÓÔÒÕËÔÕÒÁ > (INVALID HEADER: BAD MIME HEADERS OR BAD MIME STRUCTURE) >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá: ÷ ÚÁÇÏÌÏ×ËÅ ÐÒÉÓÕÔÓÔ×ÕÀÔ ÚÁÐÒÅÝÅÎÎÙÅ 8-ÂÉÔÎÙÅ ÓÉÍ×ÏÌÙ > (INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER) >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá: ÷ ÚÁÇÏÌÏ×ËÅ ÐÒÉÓÕÔÓÔ×ÕÀÔ ÕÐÒÁ×ÌÑÀÝÉÅ ÓÉÍ×ÏÌÙ > (INVALID HEADER: INVALID CONTROL CHARACTERS IN HEADER) >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá: FOLDED HEADER FIELD MADE UP ENTIRELY OF WHITESPACE >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá: äÌÉÎÁ ÓÔÒÏËÉ ÚÁÇÏÌÏ×ËÁ ÐÉÓØÍÁ ÐÒÅ×ÙÛÁÅÔ ÏÇÒÁÎÉÞÅÎÉÅ × 998 ÓÉÍ×ÏÌÏ× ÏÐÉÓÁÎÎÙÊ × RFC2822 > (INVALID HEADER: HEADER LINE LONGER THAN RFC2822 LIMIT OF 998 CHARACTERS) >|îåðòá÷éìøîùê úáçïìï÷ïë ðéóøíá > (INVALID HEADER:) >] >[[:wrap|78| | |%X]\n] >]\ >#[? %a |#|[:wrap|78|| |First upstream SMTP client IP address: \[%a\] %g]] >#[? %e |#|[:wrap|78|| |According to a 'Received:' trace,\ ># the message originated at: \[%e\], %t]] >[? %s |#|[:wrap|78|| |Return-Path: %s]] >[? %m |#|[:wrap|78|| |Message-ID: %m]] >[? %r |#|[:wrap|78|| |Resent-Message-ID: %r]] >[? %j |#|[:wrap|78|| |Subject: %j]] > ># ccat_min 0: other, 1: bad MIME, 2: 8-bit char, 3: NUL/CR, ># 4: empty, 5: long, 6: syntax >[? %#X ||[? [:ccat_min] >|# 0: other >|# 1: bad MIME >|# 2: 8-bit char >þÔÏ ÔÁËÏÅ ÚÁÐÒÅÝÅÎÎÙÅ 8-ÂÉÔÎÙÅ ÓÉÍ×ÏÌÙ × ÚÁÇÏÌÏ×ËÅ ÐÉÓØÍÁ? > > úÁÇÏÌÏ×ÏË ÐÉÓØÍÁ Ï ËÏÔÏÒÏÍ ÉÄÅÔ ÒÅÞØ, ÏÔÎÏÓÉÔÓÑ Ë ÔÅÈÎÉÞÅÓËÏÊ ÞÁÓÔÉ ÐÉÓØÍÁ > É ÚÁ ÅÇÏ ÆÏÒÍÉÒÏ×ÁÎÉÅ ÏÔ×ÅÞÁÅÔ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ. åÓÌÉ ÷Ù ÐÏÌÕÞÉÌÉ > ÜÔÏ ÓÏÏÂÝÅÎÉÅ, ÔÏ ÚÎÁÞÉÔ ÌÉÂÏ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÎÅ ÐÒÁ×ÉÌØÎÏ ÎÁÓÔÒÏÅÎÁ, > ÌÉÂÏ ÏÎÁ ÎÅ ÓÏÂÌÀÄÁÅÔ ÓÔÁÎÄÁÒÔÙ ÉÎÔÅÒÎÅÔÁ. > > óÔÁÎÄÁÒÔ RFC 2822 ÏÐÒÅÄÅÌÑÅÔ ÐÒÁ×ÉÌÁ × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó ËÏÔÏÒÙÍÉ ÓÏÚÄÁÀÔÓÑ > ÐÉÓØÍÁ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. üÔÉ ÐÒÁ×ÉÌÁ ÎÅ ÄÏÐÕÓËÁÀÔ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÓÉÍ×ÏÌÏ× > Ó ËÏÄÁÍÉ ÂÏÌÅÅ 127 ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ (Ô.Å. ÎÅ ÚÁËÏÄÉÒÏ×ÁÎÎÙÍÉ ÓÐÅÃÉÁÌØÎÙÍ > ÏÂÒÁÚÏÍ) × ÚÁÇÏÌÏ×ËÅ ÐÉÓØÍÁ. ë ÔÁËÉÍ ÓÉÍ×ÏÌÁÍ ÏÔÎÏÓÑÔÓÑ ÒÕÓÓËÉÅ ÂÕË×Ù > × ÌÀÂÏÊ ÉÚ ËÏÄÉÒÏ×ÏË. > > åÓÌÉ ÔÁËÉÅ ÓÉÍ×ÏÌÙ ÄÏÌÖÎÙ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÙ × ÚÁÇÏÌÏ×ËÅ ÐÉÓØÍÁ, ÔÏ ÐÏÞÔÏ×ÁÑ > ÐÒÏÇÒÁÍÍÁ ÄÏÌÖÎÁ ÉÈ ÚÁËÏÄÉÒÏ×ÁÔØ × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó RFC 2047. > > éÎÏÇÄÁ ÔÁËÉÅ ÎÅÐÒÁ×ÉÌØÎÙÅ ÐÏÌÑ ÚÁÇÏÌÏ×ËÁ ÐÉÓØÍÁ Á×ÔÏÍÁÔÉÞÅÓËÉ ÄÏÂÁ×ÌÑÀÔÓÑ > ÎÅËÏÔÏÒÙÍÉ ÐÏÞÔÏ×ÙÍÉ ÐÒÏÇÒÁÍÍÁÍÉ, ÐÏÞÔÏ×ÙÍÉ ÓÅÒ×ÅÒÁÍÉ, ÁÎÁÌÉÚÁÔÏÒÁÍÉ > ÓÏÄÅÒÖÉÍÏÇÏ ÐÉÓØÍÁ ÉÌÉ ÄÒÕÇÉÍÉ ÓÉÓÔÅÍÁÍÉ ÒÁÂÏÔÁÀÝÉÍÉ Ó ÐÏÞÔÏÊ. ÷ ÜÔÏÍ ÓÌÕÞÁÅ > ÔÁËÁÑ ÓÉÓÔÅÍÁ ÄÏÌÖÎÁ ÂÙÔØ ÉÓÐÒÁ×ÌÅÎÁ ÉÌÉ ÐÒÁ×ÉÌØÎÏ ÎÁÓÔÒÏÅÎÁ. > > ïÂÙÞÎÏ, ÐÒÁ×ÉÌÁ ÎÁÒÕÛÁÀÔÓÑ × ÔÁËÉÈ ÚÁÇÏÌÏ×ËÁÈ ËÁË 'Date', 'Received', 'X-Mailer', > 'X-Priority', 'X-Scanned' É ÄÒ. > > åÓÌÉ ÷Ù ÎÅ ÚÎÁÅÔÅ ËÁË ÉÓÐÒÁ×ÉÔØ ÉÌÉ ÏÂÏÊÔÉ ÜÔÕ ÐÒÏÂÌÅÍÕ, ÔÏ ÏÂÒÁÔÉÔÅÓØ ÐÏÖÁÌÕÊÓÔÁ > Ë ÷ÁÛÅÍÕ ÓÉÓÔÅÍÎÏÍÕ ÁÄÍÉÎÉÓÔÒÁÔÏÒÕ ÏÔ×ÅÞÁÀÝÅÍÕ ÚÁ ÐÏÞÔÏ×ÕÀ ÓÉÓÔÅÍÕ. > >WHAT IS AN INVALID CHARACTER IN MAIL HEADER? > > The RFC 2822 standard specifies rules for forming internet messages. > It does not allow the use of characters with codes above 127 to be > used directly (non-encoded) in mail header. > > If such characters (e.g. with diacritics) from ISO Latin or other > alphabets need to be included in the header, these characters need > to be properly encoded according to RFC 2047. This encoding is often > done transparently by mail reader (MUA), but if automatic encoding is > not available (e.g. by some older MUA) it is the user's responsibility > to avoid the use of such characters in mail header, or to encode them > manually. Typically the offending header fields in this category are > 'Subject', 'Organization', and comment fields in e-mail addresses of > the 'From', 'To' and 'Cc'. > > Sometimes such invalid header fields are inserted automatically > by some MUA, MTA, content checker, or other mail handling service. > If this is the case, that service needs to be fixed or properly > configured. Typically the offending header fields in this category > are 'Date', 'Received', 'X-Mailer', 'X-Priority', 'X-Scanned', etc. > > If you don't know how to fix or avoid the problem, please report it > to _your_ postmaster or system manager. ># >[~[:x-mailer]|^Microsoft Outlook Express 6\\.00|[" > åÓÌÉ × ËÁÞÅÓÔ×Å ÐÏÞÔÏ×ÏÇÏ ËÌÉÅÎÔÁ ÷Ù ÉÓÐÏÌØÚÕÅÔÅ Microsoft Outlook Express, > ÕÂÅÄÉÔÅÓØ, ÞÔÏ ÕÓÔÁÎÏ×ÌÅÎÙ ÓÌÅÄÕÀÝÉÅ ÏÐÃÉÉ: > > óÅÒ×ÉÓ -> ðÁÒÁÍÅÔÒÙ... -> ïÔÐÒÁ×ËÁ ÓÏÏÂÝÅÎÉÊ -> æÏÒÍÁÔ ÏÔÐÒÁ×ÌÑÅÍÙÈ ÓÏÏÂÝÅÎÉÊ -> > îÁÓÔÒÏÊËÁ HTML... > óÎÑÔÁ ÇÁÌËÁ "òÁÚÒÅÛÉÔØ ÉÓÐÏÌØÚÏ×ÁÎÉÅ 8-ÂÉÔÏ×ÙÈ ÚÎÁËÏ× × ÚÁÇÏÌÏ×ËÁÈ" > îÁÓÔÒÏÊËÁ ÏÂÙÞÎÏÇÏ ÔÅËÓÔÁ... > åÓÌÉ ÆÏÒÍÁÔ ÓÏÏÂÝÅÎÉÑ "ëÏÄÉÒÏ×ËÁ MIME", ÔÏ ÄÏÌÖÅÎ ÂÙÔØ ÕËÁÚÁÎ ×ÉÄ ÉÓÐÏÌØÚÕÅÍÏÊ ËÏÄÉÒÏ×ËÉ. > óÎÑÔÁ ÇÁÌËÁ "òÁÚÒÅÛÉÔØ ÉÓÐÏÌØÚÏ×ÁÎÉÅ 8-ÂÉÔÏ×ÙÈ ÚÎÁËÏ× × ÚÁÇÏÌÏ×ËÁÈ" >"]]# >|# 3: NUL/CR >îÅÐÒÁ×ÏÌØÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÕÐÒÁ×ÌÑÀÝÉÈ ÓÉÍ×ÏÌÏ× × ÚÁÇÏÌÏ×ËÅ ÐÉÓØÍÁ. > > úÁÇÏÌÏ×ÏË ÐÉÓØÍÁ Ï ËÏÔÏÒÏÍ ÉÄÅÔ ÒÅÞØ, ÏÔÎÏÓÉÔÓÑ Ë ÔÅÈÎÉÞÅÓËÏÊ ÞÁÓÔÉ ÐÉÓØÍÁ > É ÚÁ ÅÇÏ ÆÏÒÍÉÒÏ×ÁÎÉÅ ÏÔ×ÅÞÁÅÔ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ. åÓÌÉ ÷Ù ÐÏÌÕÞÉÌÉ > ÜÔÏ ÓÏÏÂÝÅÎÉÅ, ÔÏ ÚÎÁÞÉÔ ÌÉÂÏ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÎÅ ÐÒÁ×ÉÌØÎÏ ÎÁÓÔÒÏÅÎÁ, > ÌÉÂÏ ÏÎÁ ÎÅ ÓÏÂÌÀÄÁÅÔ ÓÔÁÎÄÁÒÔÙ ÉÎÔÅÒÎÅÔÁ. > > óÔÁÎÄÁÒÔ RFC 2822 ÏÐÒÅÄÅÌÑÅÔ ÐÒÁ×ÉÌÁ × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó ËÏÔÏÒÙÍÉ ÓÏÚÄÁÀÔÓÑ > ÐÉÓØÍÁ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. üÔÉ ÐÒÁ×ÉÌÁ ÎÅ ÄÏÐÕÓËÁÀÔ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÕÐÒÁ×ÌÑÀÝÉÈ > ÓÉÍ×ÏÌÏ× NUL É ÏÄÉÎÏÞÎÏÇÏ CR ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ × ÚÁÇÏÌÏ×ËÅ ÐÉÓØÍÁ. > >IMPROPER USE OF CONTROL CHARACTER IN MESSAGE HEADER > > The RFC 2822 standard specifies rules for forming internet messages. > It does not allow the use of control characters NUL and bare CR > to be used directly in mail header. >|# 4: empty >îÅÐÒÁ×ÏÌØÎÏÅ ÐÅÒÅÎÅÓÅÎÎÁÑ ÓÔÒÏËÁ ÚÁÇÏÌÏ×ËÁ. > > úÁÇÏÌÏ×ÏË ÐÉÓØÍÁ Ï ËÏÔÏÒÏÍ ÉÄÅÔ ÒÅÞØ, ÏÔÎÏÓÉÔÓÑ Ë ÔÅÈÎÉÞÅÓËÏÊ ÞÁÓÔÉ ÐÉÓØÍÁ > É ÚÁ ÅÇÏ ÆÏÒÍÉÒÏ×ÁÎÉÅ ÏÔ×ÅÞÁÅÔ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ. åÓÌÉ ÷Ù ÐÏÌÕÞÉÌÉ > ÜÔÏ ÓÏÏÂÝÅÎÉÅ, ÔÏ ÚÎÁÞÉÔ ÌÉÂÏ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÎÅ ÐÒÁ×ÉÌØÎÏ ÎÁÓÔÒÏÅÎÁ, > ÌÉÂÏ ÏÎÁ ÎÅ ÓÏÂÌÀÄÁÅÔ ÓÔÁÎÄÁÒÔÙ ÉÎÔÅÒÎÅÔÁ. > > óÔÁÎÄÁÒÔ RFC 2822 ÏÐÒÅÄÅÌÑÅÔ ÐÒÁ×ÉÌÁ × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó ËÏÔÏÒÙÍÉ ÓÏÚÄÁÀÔÓÑ > ÐÉÓØÍÁ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. òÁÚÄÅÌ '3.2.3. Folding white space and comments' > ÚÁÐÒÅÝÁÅÔ ÐÅÒÅÎÏÓÉÔØ ÓÔÒÏËÉ ÚÁÇÏÌÏ×ËÁ ÔÁËÉÍ ÏÂÒÁÚÏÍ, ÞÔÏ ÒÅÚÕÌØÔÉÒÕÀÝÁÑ ÓÔÒÏËÁ > ÂÕÄÅÔ ÓÏÓÔÏÑÔØ ÔÏÌØËÏ ÉÚ ÐÒÏÂÅÌØÎÙÈ ÓÉÍ×ÏÌÏ× (ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÐÒÏÂÅÌ ÉÌÉ > ÓÉÍ×ÏÌ ÔÁÂÕÌÑÃÉÉ). > >IMPROPER FOLDED HEADER FIELD MADE UP ENTIRELY OF WHITESPACE > > The RFC 2822 standard specifies rules for forming internet messages. > In section '3.2.3. Folding white space and comments' it explicitly > prohibits folding of header fields in such a way that any line of a > folded header field is made up entirely of white-space characters > (control characters SP and HTAB) and nothing else. >|# 5: long >ðÒÅ×ÙÛÅÎÉÅ ÏÇÒÁÎÉÞÅÎÉÑ ÄÌÉÎÙ ÓÔÒÏËÉ ÚÁÇÏÌÏ×ËÁ × 998 ÓÉÍ×ÏÌÏ× ÏÐÒÅÄÅÌÎÎÏÇÏ × RFC2822. > > úÁÇÏÌÏ×ÏË ÐÉÓØÍÁ Ï ËÏÔÏÒÏÍ ÉÄÅÔ ÒÅÞØ, ÏÔÎÏÓÉÔÓÑ Ë ÔÅÈÎÉÞÅÓËÏÊ ÞÁÓÔÉ ÐÉÓØÍÁ > É ÚÁ ÅÇÏ ÆÏÒÍÉÒÏ×ÁÎÉÅ ÏÔ×ÅÞÁÅÔ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ. åÓÌÉ ÷Ù ÐÏÌÕÞÉÌÉ > ÜÔÏ ÓÏÏÂÝÅÎÉÅ, ÔÏ ÚÎÁÞÉÔ ÌÉÂÏ ÷ÁÛÁ ÐÏÞÔÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÎÅ ÐÒÁ×ÉÌØÎÏ ÎÁÓÔÒÏÅÎÁ, > ÌÉÂÏ ÏÎÁ ÎÅ ÓÏÂÌÀÄÁÅÔ ÓÔÁÎÄÁÒÔÙ ÉÎÔÅÒÎÅÔÁ. > > óÔÁÎÄÁÒÔ RFC 2822 ÏÐÒÅÄÅÌÑÅÔ ÐÒÁ×ÉÌÁ × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó ËÏÔÏÒÙÍÉ ÓÏÚÄÁÀÔÓÑ > ÐÉÓØÍÁ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. òÁÚÄÅÌ '2.1.1. Line Length Limits' ÚÁÐÒÅÝÁÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ > × ÚÁÇÏÌÏ×ËÅ ÐÉÓØÍÁ ÓÔÒÏËÉ, ÄÌÉÎÁ ËÏÔÏÒÙÈ ÐÒÉ×ÙÛÁÅÔ 998 ÓÉÍ×ÏÌÏ× (ÂÅÚ ÕÞÅÔÁ CRLF). > >HEADER LINE LONGER THAN RFC2822 LIMIT OF 998 CHARACTERS > > The RFC 2822 standard specifies rules for forming internet messages. > Section '2.1.1. Line Length Limits' prohibits each line of a header > to be more than 998 characters in length (excluding the CRLF). >|# 6: syntax >|# other >]]#
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 13281
: 2247