| 1 |
# |
| 2 |
# ============================================================================= |
| 3 |
# This is a template for (neutral: non-virus, non-spam, non-banned) |
| 4 |
# DELIVERY STATUS NOTIFICATIONS to sender. |
| 5 |
# For syntax and customization instructions see README.customize. |
| 6 |
# The From, To and Date header fields will be provided automatically. |
| 7 |
# Long header fields will be automatically wrapped by the program. |
| 8 |
# |
| 9 |
Subject: [?%#D|Undeliverable mail|Delivery status notification]\ |
| 10 |
[? [:ccat|major] |||, MTA-BLOCKED\ |
| 11 |
|, OVERSIZED message\ |
| 12 |
|, invalid header section[=explain_badh|1]\ |
| 13 |
[?[:ccat|minor]||: bad MIME|: unencoded 8-bit character\ |
| 14 |
|: improper use of control char|: all-whitespace header line\ |
| 15 |
|: header line longer than 998 characters|: header field syntax error\ |
| 16 |
|: missing required header field|: duplicate header field|]\ |
| 17 |
|, UNSOLICITED BULK EMAIL apparently from you\ |
| 18 |
|, UNSOLICITED BULK EMAIL apparently from you\ |
| 19 |
|, contents UNCHECKED\ |
| 20 |
|, BANNED contents type (%F)\ |
| 21 |
|, VIRUS in message apparently from you (%V)\ |
| 22 |
] |
| 23 |
Message-ID: <DSN%i@%h> |
| 24 |
|
| 25 |
[? %#D |#|Your message WAS SUCCESSFULLY RELAYED to:[\n %D] |
| 26 |
[~[:dsn_notify]|["\\bSUCCESS\\b"]|\ |
| 27 |
and you explicitly requested a delivery status notification on success.\n]\ |
| 28 |
] |
| 29 |
[? %#N |#|The message WAS NOT relayed to:[\n %N] |
| 30 |
] |
| 31 |
[:wrap|78|||This [?%#D|nondelivery|delivery] report was \ |
| 32 |
generated by the program amavisd-new at host %h. \ |
| 33 |
Our internal reference code for your message is %n/%i] |
| 34 |
|
| 35 |
# ccat_min 0: other, 1: bad MIME, 2: 8-bit char, 3: NUL/CR, |
| 36 |
# 4: empty, 5: long, 6: syntax, 7: missing, 8: multiple |
| 37 |
[? [:explain_badh] ||[? [:ccat|minor] |
| 38 |
|INVALID HEADER |
| 39 |
|INVALID HEADER: BAD MIME HEADER SECTION OR BAD MIME STRUCTURE |
| 40 |
|INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER SECTION |
| 41 |
|INVALID HEADER: INVALID CONTROL CHARACTERS IN HEADER SECTION |
| 42 |
|INVALID HEADER: FOLDED HEADER FIELD LINE MADE UP ENTIRELY OF WHITESPACE |
| 43 |
|INVALID HEADER: HEADER LINE LONGER THAN RFC 5322 LIMIT OF 998 CHARACTERS |
| 44 |
|INVALID HEADER: HEADER FIELD SYNTAX ERROR |
| 45 |
|INVALID HEADER: MISSING REQUIRED HEADER FIELD |
| 46 |
|INVALID HEADER: DUPLICATE HEADER FIELD |
| 47 |
|INVALID HEADER |
| 48 |
] |
| 49 |
[[:wrap|78| | |%X]\n] |
| 50 |
]\ |
| 51 |
# |
| 52 |
[:wrap|78|| |Return-Path: %s[?[:dkim|envsender]|| (OK)]] |
| 53 |
[:wrap|78|| |From: [:header_field|From|100][?[:dkim|author]|| (dkim:AUTHOR)]] |
| 54 |
[? [:header_field|Sender]|#|\ |
| 55 |
[:wrap|78|| |Sender: [:header_field|Sender|100]\ |
| 56 |
[?[:dkim|sender]|| (dkim:SENDER)]]] |
| 57 |
[? %m |#|[:wrap|78|| |Message-ID: %m]] |
| 58 |
[? %r |#|[:wrap|78|| |Resent-Message-ID: %r]] |
| 59 |
[? %#X|#|[? [:useragent] |#|[:wrap|78|| |[:useragent]]]] |
| 60 |
[? %j |#|[:wrap|78|| |Subject: [:header_field|Subject|100]]] |
| 61 |
|
| 62 |
# ccat_min 0: other, 1: bad MIME, 2: 8-bit char, 3: NUL/CR, |
| 63 |
# 4: empty, 5: long, 6: syntax, 7: missing, 8: multiple |
| 64 |
[? [:explain_badh] ||[? [:ccat|minor] |
| 65 |
|# 0: other |
| 66 |
|# 1: bad MIME |
| 67 |
|# 2: 8-bit char |
| 68 |
WHAT IS AN INVALID CHARACTER IN A MAIL HEADER SECTION? |
| 69 |
|
| 70 |
The RFC 5322 document specifies rules for forming internet messages. |
| 71 |
It does not allow the use of characters with codes above 127 to be |
| 72 |
used directly (non-encoded) in a mail header section. |
| 73 |
|
| 74 |
If such characters (e.g. with diacritics) from ISO Latin or other |
| 75 |
alphabets need to be included in a header section, these characters |
| 76 |
need to be properly encoded according to RFC 2047. Such encoding |
| 77 |
is often done transparently by mail reader (MUA), but if automatic |
| 78 |
encoding is not available (e.g. by some older MUA) it is a user's |
| 79 |
responsibility to avoid using such characters in a header section, |
| 80 |
or to encode them manually. Typically the offending header fields |
| 81 |
in this category are 'Subject', 'Organization', and comment fields |
| 82 |
or display names in e-mail addresses of 'From', 'To' or 'Cc'. |
| 83 |
|
| 84 |
Sometimes such invalid header fields are inserted automatically |
| 85 |
by some MUA, MTA, content filter, or other mail handling service. |
| 86 |
If this is the case, such service needs to be fixed or properly |
| 87 |
configured. Typically the offending header fields in this category |
| 88 |
are 'Date', 'Received', 'X-Mailer', 'X-Priority', 'X-Scanned', etc. |
| 89 |
|
| 90 |
If you don't know how to fix or avoid the problem, please report it |
| 91 |
to _your_ postmaster or system manager. |
| 92 |
# |
| 93 |
[~[:useragent]|^X-Mailer:\\s*Microsoft Outlook Express 6\\.00|[" |
| 94 |
If using Microsoft Outlook Express as your MUA, make sure its |
| 95 |
settings under: |
| 96 |
Tools -> Options -> Send -> Mail Sending Format -> Plain & HTML |
| 97 |
are: "MIME format" MUST BE selected, |
| 98 |
and "Allow 8-bit characters in headers" MUST NOT be enabled! |
| 99 |
"]]# |
| 100 |
|# 3: NUL/CR |
| 101 |
IMPROPER USE OF CONTROL CHARACTER IN A MESSAGE HEADER SECTION |
| 102 |
|
| 103 |
The RFC 5322 document specifies rules for forming internet messages. |
| 104 |
It does not allow the use of control characters NUL and bare CR |
| 105 |
to be used directly in a mail header section. |
| 106 |
|# 4: empty |
| 107 |
IMPROPERLY FOLDED HEADER FIELD LINE MADE UP ENTIRELY OF WHITESPACE |
| 108 |
|
| 109 |
The RFC 5322 document specifies rules for forming internet messages. |
| 110 |
In section '3.2.2. Folding white space and comments' it explicitly |
| 111 |
prohibits folding of header fields in such a way that any line of a |
| 112 |
folded header field is made up entirely of white-space characters |
| 113 |
(control characters SP and HTAB) and nothing else. |
| 114 |
|# 5: long |
| 115 |
HEADER LINE LONGER THAN RFC 5322 LIMIT OF 998 CHARACTERS |
| 116 |
|
| 117 |
The RFC 5322 document specifies rules for forming internet messages. |
| 118 |
Section '2.1.1. Line Length Limits' prohibits each line of a header |
| 119 |
section to be more than 998 characters in length (excluding the CRLF). |
| 120 |
|# 6: syntax |
| 121 |
|# 7: missing |
| 122 |
MISSING REQUIRED HEADER FIELD |
| 123 |
|
| 124 |
The RFC 5322 document specifies rules for forming internet messages. |
| 125 |
Section '3.6. Field Definitions' specifies that certain header fields |
| 126 |
are required (origination date field and the "From:" originator field). |
| 127 |
|# 8: multiple |
| 128 |
DUPLICATE HEADER FIELD |
| 129 |
|
| 130 |
The RFC 5322 document specifies rules for forming internet messages. |
| 131 |
Section '3.6. Field Definitions' specifies that certain header fields |
| 132 |
must not occur more than once in a message header section. |
| 133 |
|# other |
| 134 |
]]# |