| 1 |
# |
| 2 |
# ============================================================================= |
| 3 |
# This is a template for VIRUS/BANNED SENDER NOTIFICATIONS. |
| 4 |
# For syntax and customization instructions see README.customize. |
| 5 |
# The From, To and Date header fields will be provided automatically. |
| 6 |
# Long header fields will be automatically wrapped by the program. |
| 7 |
# |
| 8 |
Subject: [? [:ccat|major] |
| 9 |
|Clean message from you\ |
| 10 |
|Clean message from you\ |
| 11 |
|Clean message from you (MTA blocked)\ |
| 12 |
|OVERSIZED message from you\ |
| 13 |
|BAD-HEADER in message from you\ |
| 14 |
|Spam claiming to be from you\ |
| 15 |
|Spam claiming to be from you\ |
| 16 |
|A message with UNCHECKED contents from you\ |
| 17 |
|BANNED contents from you (%F)\ |
| 18 |
|VIRUS in message apparently from you (%V)\ |
| 19 |
] |
| 20 |
[? %m |#|In-Reply-To: %m] |
| 21 |
Message-ID: <VS%i@%h> |
| 22 |
|
| 23 |
[? [:ccat|major] |Clean|Clean|MTA-BLOCKED|OVERSIZED|INVALID HEADER|\ |
| 24 |
Spammy|Spam|UNCHECKED contents|BANNED CONTENTS ALERT|VIRUS ALERT] |
| 25 |
|
| 26 |
Our content checker found |
| 27 |
[? %#V |#|[:wrap|78| | |[? %#V |viruses|virus|viruses]: %V]] |
| 28 |
[? %#F |#|[:wrap|78| | |banned [? %#F |names|name|names]: %F]] |
| 29 |
[? %#X |#|[[:wrap|78| | |%X]\n]] |
| 30 |
|
| 31 |
in email presumably from you %s |
| 32 |
to the following [? %#R |recipients|recipient|recipients]:[ |
| 33 |
-> %R] |
| 34 |
|
| 35 |
Our internal reference code for your message is %n/%i |
| 36 |
|
| 37 |
[? %a |#|[:wrap|78|| |First upstream SMTP client IP address: \[%a\] %g]] |
| 38 |
[? %e |#|[:wrap|78|| |According to a 'Received:' trace,\ |
| 39 |
the message apparently originated at: \[%e\], %t]] |
| 40 |
|
| 41 |
[:wrap|78|| |Return-Path: %s[?[:dkim|envsender]|| (OK)]] |
| 42 |
[:wrap|78|| |From: [:header_field|From|100][?[:dkim|author]|| (dkim:AUTHOR)]] |
| 43 |
[? [:header_field|Sender]|#|\ |
| 44 |
[:wrap|78|| |Sender: [:header_field|Sender|100]\ |
| 45 |
[?[:dkim|sender]|| (dkim:SENDER)]]] |
| 46 |
[? %m |#|[:wrap|78|| |Message-ID: %m]] |
| 47 |
[? %r |#|[:wrap|78|| |Resent-Message-ID: %r]] |
| 48 |
[? %j |#|[:wrap|78|| |Subject: [:header_field|Subject|100]]] |
| 49 |
|
| 50 |
[? %#D |Delivery of the email was stopped! |
| 51 |
|
| 52 |
]# |
| 53 |
[? %#V ||Please check your system for viruses, |
| 54 |
or ask your system administrator to do so. |
| 55 |
|
| 56 |
]# |
| 57 |
[? %#V |[? %#F ||# |
| 58 |
The message [?%#D|has been blocked|triggered this warning] because it contains a component |
| 59 |
(as a MIME part or nested within) with declared name |
| 60 |
or MIME type or contents type violating our access policy. |
| 61 |
|
| 62 |
To transfer contents that may be considered risky or unwanted |
| 63 |
by site policies, or simply too large for mailing, please consider |
| 64 |
publishing your content on the web, and only sending an URL of the |
| 65 |
document to the recipient. |
| 66 |
|
| 67 |
Depending on the recipient and sender site policies, with a little |
| 68 |
effort it might still be possible to send any contents (including |
| 69 |
viruses) using one of the following methods: |
| 70 |
|
| 71 |
- encrypted using pgp, gpg or other encryption methods; |
| 72 |
|
| 73 |
- wrapped in a password-protected or scrambled container or archive |
| 74 |
(e.g.: zip -e, arj -g, arc g, rar -p, or other methods) |
| 75 |
|
| 76 |
Note that if the contents is not intended to be secret, the |
| 77 |
encryption key or password may be included in the same message |
| 78 |
for recipient's convenience. |
| 79 |
|
| 80 |
We are sorry for inconvenience if the contents was not malicious. |
| 81 |
|
| 82 |
The purpose of these restrictions is to cut the most common propagation |
| 83 |
methods used by viruses and other malware. These often exploit automatic |
| 84 |
mechanisms and security holes in more popular mail readers (Microsoft |
| 85 |
mail readers and browsers are a common target). By requiring an explicit |
| 86 |
and decisive action from the recipient to decode mail, the danger of |
| 87 |
automatic malware propagation is largely reduced. |
| 88 |
# |
| 89 |
# Details of our mail restrictions policy are available at ... |
| 90 |
|
| 91 |
]]# |