--
Hello,
I'm using mailscanner(debian package 3.13.2-2) with exim (Debian package, version 3.35) on 3 different servers since few times (2 weeks)
and on each of them after 2 days of production I got some errors about
the defer director.
Mailscanner have a very simple process :
one exim take mails and put them in queue (/var/spool/exim_incoming/) -> mailscanner scan them -> a
second exim handle the queue and process them normaly
Here is an example of my problem :
/var/log/exim/mainlog/
2002-06-13 07:40:01 17INKp-0004YI-00 == userx@???
D=defer_director defer (-1): forced defer: All deliveries are deferred
2002-06-13 07:40:01 17INKp-0004YI-00 ** userx@???:
retry timeout exceeded
2002-06-13 07:40:01 17INKz-0004cu-00 <= <> R=17INKp-0004YI-00 U=mail
P=local S=31327
2002-06-13 07:40:01 17INKp-0004YI-00 Error message sent to
alerte@???
or in the same file :
2002-06-13 11:50:01 17IREs-0006LI-00 == some_users@???
R=defer_router defer (-1): remote host address is the local host
2002-06-13 11:50:01 17IREs-0006LI-00 ** some_users@???:
retry timeout exceeded
2002-06-13 11:50:01 17IREv-0006LS-00 <= <> R=17IREs-0006LI-00 U=mail
P=local S=3108
2002-06-13 11:50:01 17IREs-0006LI-00 Error message sent to
yuser@???
I join at this mail my exim.conf and mailscanner.conf files.
Obviously, it's a problem with the exim's defer director handling.
Anyone have yet meet this problem or know how to solve it ?
Personnally, for the moment, I don't user Defer; Only queue_only=true.
Maybe you can help me to understand how the second exim handle the
queue put in /var/spool/exim_incoming/. How does exim_outgoing know
where is this queue ?
Another question about something strange that happen this night.
A lot of mail get this error :
2002-06-14 03:08:02 17IfZ5-000292-00 ** iuser@???:
unrouteable mail domain "duke-interactive.com"
2002-06-14 03:08:02 17IfZK-0002Aa-00 <= <> R=17IfZ5-000292-00 U=mail
P=local S=1718
2002-06-14 03:08:02 17IfZ5-000292-00 Error message sent to
intranet@???
2002-06-14 03:08:02 17IfZ5-000292-00 Completed
2002-06-14 03:08:02 17IfZ6-000293-00 failed to open database lock file
/var/spool/exim_incoming/db/retry.lockfile: Permission denied (euid=8
egid=8)
This file retry.lockfile, and other in the directory db, was owned by root.
I look at in my history and I've find this normal lines :
mkdir -p /var/spool/exim_incoming/{db,input,msglog}
chown -R mail.mail /var/spool/exim_incoming
and after nothing about a change in the db Directory. Something similar
appear in another server :
vincent@anotherserver:~$ l /var/spool/exim_incoming/db/
total 25
drwxr-x--- 2 mail mail 184 May 16 06:25 .
drwxr-x--- 5 mail mail 120 May 16 09:45 ..
-rw-r----- 1 mail mail 20480 Jun 14 06:25 retry
-rw-r----- 1 mail mail 0 May 15 21:53 retry.lockfile
-rw-r----- 1 root root 4096 May 16 06:25 wait-remote_smtp
-rw-r----- 1 root root 0 May 16 06:25
wait-remote_smtp.lockfil
Someone have any solutions for all this question :) ?
--
Vincent Meoc
Administrateur système et réseau
DUKE - Digital Age Agency
T : 01 53 44 19 00
F : 01 53 44 19 20
e-mail : vincent@???
www.duke-interactive.com
--
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system administrator.
# This file originally generated by eximconfig at Mon Dec 4 11:41:30 CET 2000
# See exim info section for details of the things that can be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
######################################################################
# MAIN CONFIGURATION SETTINGS #
######################################################################
primary_hostname = mail.duke-interactive.com
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = duke-interactive.com
# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not want
# to do any local deliveries, uncomment the following line, but do not supply
# any data for it. This sets local_domains to an empty string, which is not
# the same as not mentioning it at all. An empty string specifies that there
# are no local domains; not setting it at all causes the default value (the
# setting of qualify_recipient) to be used.
local_domains = duke-interactive.com:localhost
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
#relay_domains =
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
relay_domains_include_local_mx = true
# No local deliveries will ever be run under the uids of these users (a colon-
# separated list). An attempt to do so gets changed so that it runs under the
# uid of "nobody" instead. This is a paranoic safety catch. Note the default
# setting means you cannot deliver mail addressed to root as if it were a
# normal user. This isn't usually a problem, as most sites have an alias for
# root that redirects such mail to a human administrator.
never_users = root
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.
#host_lookup = *
# The setting below would, if uncommented, cause Exim to check the syntax of
# all the headers that are supposed to contain email addresses (To:, From:,
# etc). This reduces the level of bounced bounces considerably.
# headers_check_syntax
# Exim contains support for the Realtime Blocking List (RBL) that is being
# maintained as part of the DNS. See
http://maps.vix.com/rbl/ for
# background. Uncommenting the following line will make Exim reject mail
# from any host whose IP address is blacklisted in the RBL at maps.vix.com.
#rbl_domains = rbl.maps.vix.com
#rbl_reject_recipients = false
#rbl_warn_header = true
# The setting below allows your host to be used as a mail relay only by
# localhost: it locks out the use of your host as a mail relay by any
# other host. See the section of the manual entitled "Control of relaying"
# for more info.
host_accept_relay = localhost:192.168.0.0/24
# If you want Exim to support the "percent hack" for all your local domains,
# uncomment the following line. This is the feature by which mail addressed
# to x%y@z (where z is one of your local domains) is locally rerouted to
# x@y and sent on. Otherwise x%y is treated as an ordinary local part
# percent_hack_domains=*
# If this option is set, then any process that is running as one of the
# listed users may pass a message to Exim and specify the sender's
# address using the "-f" command line option, without Exim's adding a
# "Sender" header.
trusted_users = mail
#trusted_users = mail:amavis
# If this option is true, the SMTP command VRFY is supported on incoming
# SMTP connections; otherwise it is not.
smtp_verify = false
# Some operating systems use the "gecos" field in the system password file
# to hold other information in addition to users' real names. Exim looks up
# this field when it is creating "sender" and "from" headers. If these options
# are set, exim uses "gecos_pattern" to parse the gecos field, and then
# expands "gecos_name" as the user's name. $1 etc refer to sub-fields matched
# by the pattern.
gecos_pattern = ^([^,:]*)
gecos_name = $1
# This sets the maximum number of messages that will be accepted in one
# connection. The default is 10, which is probably enough for most purposes,
# but is too low on dialup SMTP systems, which often have many more mails
# queued for them when they connect.
smtp_accept_queue_per_connection = 100
# Send a mail to the postmaster when a message is frozen. There are many
# reasons this could happen; one is if exim cannot deliver a mail with no
# return address (normally a bounce) another that may be common on dialup
# systems is if a DNS lookup of a smarthost fails. Read the documentation
# for more details: you might like to look at the auto_thaw option
freeze_tell_mailmaster = true
auto_thaw = 0s
# This string defines the contents of the \`Received' message header that
# is added to each message, except for the timestamp, which is automatically
# added on at the end, preceded by a semicolon. The string is expanded each
# time it is used.
received_header_text = "Received: \
${if def:sender_rcvhost {from ${sender_rcvhost}\n\t}\
{${if def:sender_ident {from ${sender_ident} }}\
${if def:sender_helo_name {(helo=${sender_helo_name})\n\t}}}}\
by ${primary_hostname} \
${if def:received_protocol {with ${received_protocol}}} \
(Exim ${version_number} #${compile_number} (Debian))\n\t\
id ${message_id}\
${if def:received_for {\n\tfor <$received_for>}}"
#maiscanner config
spool_directory = /var/spool/exim_incoming
queue_only = true
#protection serveur
#message_size_limit = 5000000
#return_size_limit = 4000000
#deliver_load_max = 4.0
#queue_only = true
deliver_queue_load_max = 4.0
queue_only_load = 2.0
message_filter = /etc/exim/big_file_filter
######################################################################
# TRANSPORTS CONFIGURATION #
######################################################################
# ORDER DOES NOT MATTER #
# Only one appropriate transport is called for each delivery. #
######################################################################
# This transport is used for local delivery to user mailboxes. On debian
# systems group mail is used so we can write to the /var/spool/mail
# directory. (The alternative, which most other unixes use, is to deliver
# as the user's own group, into a sticky-bitted directory)
local_delivery:
driver = appendfile
group = mail
mode = 0660
mode_fail_narrower = false
envelope_to_add = true
file = /var/spool/mail/${local_part}
# This transport is used for handling pipe addresses generated by
# alias or .forward files. If the pipe generates any standard output,
# it is returned to the sender of the message as a delivery error. Set
# return_fail_output instead if you want this to happen only when the
# pipe fails to complete normally.
address_pipe:
driver = pipe
return_output
# This transport is used for handling file addresses generated by alias
# or .forward files.
address_file:
driver = appendfile
# This transport is used for handling file addresses generated by alias
# or .forward files if the path ends in "/", which causes it to be treated
# as a directory name rather than a file name. Each message is then delivered
# to a unique file in the directory. If instead you want all such deliveries to
# be in the "maildir" format that is used by some other mail software,
# uncomment the final option below. If this is done, the directory specified
# in the .forward or alias file is the base maildir directory.
#
# Should you want to be able to specify either maildir or non-maildir
# directory-style deliveries, then you must set up yet another transport,
# called address_directory2. This is used if the path ends in "//" so should
# be the one used for maildir, as the double slash suggests another level
# of directory. In the absence of address_directory2, paths ending in //
# are passed to address_directory.
address_directory:
driver = appendfile
no_from_hack
prefix = ""
suffix = ""
# maildir_format
# This transport is used for handling autoreplies generated by the filtering
# option of the forwardfile director.
address_reply:
driver = autoreply
# This transport is used for procmail
procmail_pipe:
driver = pipe
command = "/usr/bin/procmail -d ${local_part}"
return_path_add
delivery_date_add
envelope_to_add
check_string = "From "
escape_string = ">From "
user = $local_part
group = mail
# This transport is used for delivering messages over SMTP connections.
remote_smtp:
driver = smtp
# vacation program
#user_vacation:
#driver = autoreply
#user = ${local_part}
#to = "${sender_address}"
#from = "${local_part}@???"
#file = /var/local/exim/msg.txt
#subject = "${if def:h_Subject: {Autoreply: ${local_part}@???} {Notification}}"
#subject = "${if def:h_Subject: {Autoreply: $h_Subject:} {Notification}}"
######################################################################
# DIRECTORS CONFIGURATION #
# Specifies how local addresses are handled #
######################################################################
# ORDER DOES MATTER #
# A local address is passed to each in turn until it is accepted. #
######################################################################
#mailscanner config
defer_director:
driver = smartuser
new_address = :defer: All deliveries are deferred
# This allows local delivery to be forced, avoiding alias files and
# forwarding.
real_local:
prefix = real-
driver = localuser
transport = local_delivery
# This director handles aliasing using a traditional /etc/aliases file.
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary.
system_aliases:
driver = aliasfile
file_transport = address_file
pipe_transport = address_pipe
include_domain = true
file = /etc/aliases
search_type = lsearch
user = list
# Uncomment the above line if you are running smartlist
# This director runs procmail for users who have a .procmailrc file
procmail:
driver = localuser
transport = procmail_pipe
require_files = ${local_part}:+${home}:+${home}/.procmailrc:+/usr/bin/procmail
no_verify
# This director handles forwarding using traditional .forward files.
# It also allows mail filtering when a forward file starts with the
# string "# Exim filter": to disable filtering, uncomment the "filter"
# option. The check_ancestor option means that if the forward file
# generates an address that is an ancestor of the current one, the
# current one gets passed on instead. This covers the case where A is
# aliased to B and B has a .forward file pointing to A.
# For standard debian setup of one group per user, it is acceptable---normal
# even---for .forward to be group writable. If you have everyone in one
# group, you should comment out the "modemask" line. Without it, the exim
# default of 022 will apply, which is probably what you want.
userforward:
driver = forwardfile
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
no_verify
check_ancestor
file = .forward
modemask = 002
filter
# This director matches local user mailboxes.
localuser:
driver = localuser
transport = local_delivery
# For a satellite sytem, all mail sent to local users is re-directed to
# their accounts on duke-interactive.com
#smart:
# driver = smartuser
# new_address = ${local_part}@???
######################################################################
# ROUTERS CONFIGURATION #
# Specifies how remote addresses are handled #
######################################################################
# ORDER DOES MATTER #
# A remote address is passed to each in turn until it is accepted. #
######################################################################
#mailscanner config
defer_router:
driver = domainlist
self = defer
route_list = "* 127.0.0.1 byname"
lookuphost:
driver = lookuphost
transport = remote_smtp
# Remote addresses are those with a domain that does not match any item
# in the "local_domains" setting above.
# Send all mail to a smarthost
#
#smarthost:
# driver = domainlist
# transport = remote_smtp
# route_list = "* mail.duke-interactive.com bydns_a"
#
# This router routes to remote hosts over SMTP using a DNS lookup with
# default options.
# This router routes to remote hosts over SMTP by explicit IP address,
# given as a "domain literal" in the form [nnn.nnn.nnn.nnn]. The RFCs
# require this facility, which is why it is enabled by default in Exim.
# If you want to lock it out, set forbid_domain_literals in the main
# configuration section above.
literal:
driver = ipliteral
transport = remote_smtp
######################################################################
# RETRY CONFIGURATION #
######################################################################
# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 2 hours and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 8 hours until 4 days have passed since the first
# failed delivery.
# Domain Error Retries
# ------ ----- -------
* * F,2h,2m; G,16h,2h,1.5; F,4d,8h
######################################################################
# REWRITE CONFIGURATION #
######################################################################
# These rewriters make sure the mail messages appear to have originated
# from the real mail-reading host.
^(?i)(root|postmaster|mailer-daemon)@stimpy.duke ${1}@??? Ffr
*@stimpy.duke ${1}@??? Ffr
^(?i)(root|postmaster|mailer-daemon)@localhost ${1}@??? Ffr
*@localhost ${1}@??? Ffr
*@in.limbo vincent@??? Ffr
# This rewriting rule is particularly useful for dialup users who
# don't have their own domain, but could be useful for anyone.
# It looks up the real address of all local users in a file
*@stimpy.duke ${lookup{$1}lsearch{/etc/email-addresses}\
{$value}fail} bcfrF
# End of Exim configuration file
--
# Configuration file for MailScanner E-Mail Virus Scanner
# This file assumes everything is in the default locations provided
# by the MailScanner and RedHat 6.2 and upwards.
#
# Note: If your directories are symlinked (soft-linked) in any way,
# please put their *real* location in here, not a path that
# includes any links. You may get some very strange error
# messages from some of the virus scanners if you don't.
# User to run as (provided for Exim users)
Run As User = mail
# Group to run as (provided for Exim users)
Run As Group = mail
# In every batch of virus-scanning, limit the maximum
# a) number of text-only messages to deliver
# b) number of potentially infected messages to unpack and scan
# c) total size of text-only messages to deliver
# d) total size of potentially infected messages to unpack and scan
Max Safe Messages Per Scan = 500
Max Unsafe Messages Per Scan = 100
Max Safe Bytes Per Scan = 100000000
Max Unsafe Bytes Per Scan = 50000000
# To avoid resource leaks, re-start periodically.
Restart Every = 14400 # 4 hours
# Name of this host, or just "the MailScanner" if you want to hide this info.
# It can be placed in the Help Desk note contained in virus warnings sent to users.
Host name = Duke MailScanner
# Add this extra header to all mail as it is scanned.
# (this must *include* terminating colon).
Mail Header = X-MailScanner:
# Set the mail header to these values for clean/infected messages.
Clean Header = Found to be clean
Infected Header = Found to be infected
Disinfected Header = Disinfected
# Set where to unpack incoming messages before scanning them
Incoming Work Dir = /var/spool/mailscanner/incoming
# Set where to store infected message attachments (if they are kept)
Quarantine Dir = /var/spool/mailscanner/quarantine
# Set where to store the process id so you can easily stop the scanner
Pid File = /var/run/mailscanner/mailscanner.pid
# Set where to find the attachment filename ruleset.
# The structure of this file is explained elsewhere, but it is used to
# accept or reject file attachments based on their name, regardless of
# whether they are infected or not.
Filename Rules = /etc/mailscanner/filename.rules.conf
# Set where to find the message text sent to users when one of their
# attachments has been quarantined.
Stored Virus Message Report = /etc/mailscanner/stored.virus.message.txt
Stored Bad Filename Message Report = /etc/mailscanner/stored.filename.message.txt
# Set where to find the message text sent to users when one of their
# attachments has been deleted.
Deleted Virus Message Report = /etc/mailscanner/deleted.virus.message.txt
Deleted Bad Filename Message Report = /etc/mailscanner/deleted.filename.message.txt
# Set where to find the message text sent to users explaining about the
# attached disinfected documents.
Disinfected Report = /etc/mailscanner/disinfected.report.txt
# Set location of incoming mail queue
# and location of outgoing mail queue.
Incoming Queue Dir = /var/spool/exim_incoming/input
Outgoing Queue Dir = /var/spool/exim/input
# Set whether to use sendmail or exim (default is sendmail)
MTA = exim
# Set how to invoke MTA when sending created message
# (e.g. to sender/recipient saying "found a virus in your message")
Sendmail = /usr/sbin/exim
# Sendmail2 is provided for Exim users.
# It defaults to the value supplied for Sendmail.
# It is the command used to attempt delivery of outgoing
# (scanned/cleaned) messages.
# This is not usually required for sendmail.
Sendmail2 = /usr/sbin/exim -C /etc/exim/exim_outgoing.conf
# Do you want to scan email for viruses?
# A few people have wanted to disable the entire virus scanning.
Virus Scanning = yes
# Which Virus Scanning package to use:
# sophos from www.sophos.com, or
# mcafee from www.mcafee.com, or
# command from www.command.co.uk, or
# kaspersky from www.kaspersky.com, or
# inoculate from www.cai.com/products/inoculateit.htm, or
# f-secure from www.f-secure.com, or
# f-prot from www.f-prot.com (which is *free* for Linux as of 1/1/2002)
#
# Note: If you want to use multiple virus scanners, then this should be a
# comma-separated list of virus scanners. For example:
# Virus Scanner = sophos, f-prot
#
Virus Scanner = sophos
# Where the Virus scanner is installed. This is the command needed to run it.
#
# Note: If you want to use multiple virus scanners, then this should be a
# comma-separated list of commands, **in the same order** as they are listed
# in the "Virus Scanner" keyword just above. For example:
# Sweep = /etc/mailscanner/wrapper/sophoswrapper, /etc/mailscanner/wrapper/f-protwrapper
#
Sweep = /etc/mailscanner/wrapper/sophoswrapper
# The maximum length of time the commercial virus scanner is allowed to run
# for 1 batch of messages (in seconds).
Virus Scanner Timeout = 300
# Expand TNEF attachments using an external program?
# This should be "yes" except for Sophos (when it should be "no")
# as Sophos has the facility built-in.
Expand TNEF = yes
# Where the MS-TNEF expander is installed.
# The new --maxsize option limits the maximum size that any expanded attachment
# may be. It helps protect against Denial Of Service attacks in TNEF files.
TNEF Expander = /usr/bin/tnef --maxsize=100000000
# The maximum length of time the TNEF Expander is allowed to run for 1 message.
# (in seconds)
TNEF Timeout = 120
# What should the attachments be called that replace virus-infected files?
Attachment Warning Filename = VirusWarning.txt
# Should we scan all messages, including plain-text messages which are normally
# harmless? This should be "yes" since the MyParty message appeared.
Scan All Messages = yes
# Once we have removed viruses from an email message and replaced them with
# VirusWarning.txt attachments, should we deliver the clean result to the
# original recipients (or just delete them if "no")?
Deliver To Recipients = yes
# Deliver messages with viruses removed to their original recipients
# if they came from a local address, or just delete them so no-one knows
# we have a virus outbreak on our site?
Deliver From Local Domains = no
# Notify the senders of infected messages that they should check out
# their systems?
Notify Senders = yes
# Set where to find the message text sent to the senders of infected
# messages.
#Sender Report = /etc/mailscanner/sender.report.txt
Sender Virus Report = /etc/mailscanner/sender.virus.report.txt
Sender Bad Filename Report = /etc/mailscanner/sender.filename.report.txt
Sender Error Report = /etc/mailscanner/sender.error.report.txt
# Notify the local postmaster when any infections are found?
Notify Local Postmaster = yes
# Include the full headers of each message in the postmaster notification?
Postmaster Gets Full Headers = yes
# Set email address of who to notify about any infections found.
# Should put your full domain name here too,
# e.g. postmaster@???
Local Postmaster = postmaster
# Set what to do with infected attachments or messages.
# keep ==> Store under the "Quarantine Dir"
# delete ==> Just delete them
#Action = delete
Action = keep
# Should I attempt to disinfect infected attachments and then deliver
# the clean ones
Deliver Disinfected Files = yes
# Local domain name, or filename containing a list of local domain names
# The file supports blank entries, '#' and ';' comment characters and
# uses the first word off each line. This should be compatible with all
# such lines in a sendmail or Exim configuration file.
Local Domains = /etc/mailscanner/localdomains.conf
#Local Domains = put.your.domain.name.here
# Mark infected messages in the message body.
# There can now be more than 1 of these configuration lines here, so you can
# break the warning message over multiple lines.
Mark Infected Messages = yes
Inline Text Warning = Warning: This message has had one or more attachments removed.
Inline Text Warning = Warning: Please read the "VirusWarning.txt" attachment(s) for more information.
Inline HTML Warning = <P><B><FONT SIZE="+1" COLOR="red">Warning: </FONT>This message has had one or more attachments removed. Please read the "VirusWarning.txt" attachment(s) for more information.</B><BR></P>
# Sign clean messages in the message body.
# There can be more than 1 of these configuration lines here, so you can
# break the signature message over multiple lines.
# Note that enabling this option will add to the overall system load as some
# major optimisations will no longer be possible!
Sign Clean Messages = no
Inline Text Signature = --
Inline Text Signature = This message has been scanned for viruses and
Inline Text Signature = dangerous content by MailScanner, and is
Inline Text Signature = believed to be clean.
Inline HTML Signature = <BR>--
Inline HTML Signature = <BR>This message has been scanned for viruses and
Inline HTML Signature = <BR>dangerous content by
Inline HTML Signature = <A HREF="
http://www.mailscanner.info/"><B>MailScanner</B></A>,
Inline HTML Signature = and is<BR>believed to be clean.
# Do you want to archive all mail in a directory for later inspection?
# Be warned if you are in the UK: this may well be illegal due to RIPA
# and DPA restrictions!
Archive Mail = no
# Where to store the mail archive.
# Be warned: this is likely to get big very quickly.
Archive Mail Dir = /var/spool/mailscanner/archive
#
# Per-Domain Scanning and Spam Detection
#
# Do we want to only scan certain named domains for viruses and spam?
Scanning By Domain = no
# Filename listing all the domains we want to scan
Domains To Scan = /etc/mailscanner/domains.to.scan.conf
# Do we want to add a MailScanner header to messages we have not scanned
Sign Unscanned Messages = yes
# What do we want to put in the header
Unscanned Header = not scanned: please contact your email provider for details
#
# Spam Detection
#
# Should the anti-spam checks be done on all incoming messages?
Spam Checks = no
# Set the name of the extra header to add to all messages found to be
# likely spam.
Spam Header = X-MailScanner-SpamCheck:
# Do you want to put some text on the front of the subject line when
# we think it is spam?
Spam Modify Subject = yes
# What text do we want to put on the front (gets followed by a " ")
Spam Subject Text = {SPAM?}
# Do we have the SpamAssassin package installed?
# This is a very good, very clever heuristics-based spam checker.
# For more info and installation instructions, see
http://spamassassin.taint.org/
Use SpamAssassin = no
# Set the maximum size of message which we will check with SpamAssassin
# Don't set this too large as your system load will get very high processing
# huge messages.
Max SpamAssassin Size = 100000
# Set the maximum time to allow SpamAssassin to process 1 message
SpamAssassin Timeout = 10
# Set the list of database names and their corresponding DNS domains.
# All of these databases work in a similar way, allowing the simple use
# of multiple databases.
# See
www.ordb.org and
www.mail-abuse.org for more information.
Spam List = ORDB-RBL, relays.ordb.org.
# MAPS now charge for their services, so you'll have to buy a contract before
# attempting to use the next 3 lines.
#Spam List = MAPS-RBL, blackholes.mail-abuse.org.
#Spam List = MAPS-DUL, dialups.mail-abuse.org.
#Spam List = MAPS-RSS, relays.mail-abuse.org.
# This next line works for JANET UK Academic sites only
#Spam List = MAPS-RBL+, rbl-plus.mail-abuse.ja.net.
# Define local networks from whom you should always accept mail, and
# never mark it as spam. This is useful in case your own mail servers
# are ever in the ORBS or MAPS lists.
#Accept Spam From = 152.78.
#Accept Spam From = 139.166.
# Define a list of email addresses and email domains from whom you should
# always accept mail, and never mark it as spam. This is useful in case
# someone you correspond with a lot has their mail servers in the ORBS or
# MAPS lists.
Spam White List = /etc/mailscanner/spam.whitelist.conf
#
# Advanced Features
# =================
#
# Don't bother changing anything below this unless you really know what
# you are doing.
#
# Set Debug to 1 to stop it running as a daemon
# and produce more verbose output
Debug = 0
# Attempt immediate delivery of messages, or just place them in the outgoing
# queue for the MTA to deliver at a time of its own choosing?
# If attempting immediate delivery, do them one at a time,
# or do them in batches of 30 at a time?
Delivery Method = queue
# Delivery Method = individual
#Delivery Method = batch
# How to lock spool files.
# Don't set this unless you *know* you need to.
# For sendmail, it defaults to "flock".
# For Exim, it defaults to "posix".
# No other type is implemented.
#Lock Type = flock
# Where to put the virus scanning engine lock files.
# These lock files are used between MailScanner and the virus signature
# "autoupdate" scripts, to ensure that they aren't both working at the
# same time (which could cause MailScanner to let a virus through).
Lock File Dir = /tmp
# What to do when you get several MailScanner headers in one message,
# from multiple MailScanner servers. Values are
# "append" : Append the new data to the existing header
# "add" : Add a new header
# "replace" : Replace the old data with the new data
# Default is "append"
Multiple Headers = append
# Some versions of Microsoft Outlook generate unparsable Rich Text
# format attachments. Do we want to deliver these bad attachments anyway?
# Setting this to yes introduces the slight risk of a virus getting through,
# but if you have a lot of troubled Outlook users you might need to do this.
# We are working on a replacement for the TNEF decoder.
Deliver Unparsable TNEF = no
# When attempting delivery of outgoing messages, should we do it in the
# background or wait for it to complete? The danger of doing it in the
# background is that the machine load goes ever upwards while all the
# slow sendmail processes run to completion. However, running it in the
# foreground may cause the mail server to run too slowly.
Deliver In Background = no
# Minimum acceptable code stability status -- if we come across code
# that's not at least as stable as this, we barf.
# This is currently only used to check that you don't end up using untested
# virus scanner support code without realising it.
# Levels used are:
# none - there may not even be any code.
# unsupported - code may be completely untested, a contributed dirty hack,
# anything, really.
# alpha - code is pretty well untested. Don't assume it will work.
# beta - code is tested a bit. It should work.
# supported - code *should* be reliable.
#
# Don't even *think* about setting this to anything other than "beta" or
# "supported" on a system that receives real mail until you have tested it
# yourself and are happy that it is all working as you expect it to.
# Don't set it to anything other than "supported" on a system that could
# ever receive important mail.
Minimum Code Status = supported
--
