Differences between version 10 and revision by previous author of MailScannerNotes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
Newer page: | version 10 | Last edited on Sunday, April 11, 2004 11:34:10 pm | by AristotlePagaltzis | Revert |
Older page: | version 1 | Last edited on Wednesday, July 31, 2002 11:53:30 pm | by DanielLawson | Revert |
@@ -1,13 +1,18 @@
-MailScanner is a [Virus] scanner for [MTA
]'s
. It can be set up with
at least [Sendmail|
http://www.sendmail
.org] and [Exim|http:
//www
.exim
.org]
+MailScanner 3.x
is deprecated, and not available in Woody. Unstable comes with
a newer v3; but to make
[ClamAV
] work (and the new
'freeish' F-Prot), you need MailScanner 4
. I have some packages for Debian
at http://www.wlug
.org.nz
/archive
/debian/ otherwise there are RPMs and
.tar
.gz's on MailScanner's website. -- CraigBox
-MailScanner can be found [here|http://
www.sng
.ecs
.soton
.ac
.uk/mailscanner/]
.
+There are more recent backports of
MailScanner 4. Check
www.apt-get
.org
. Currently (2004-02-03) the latest one is 4
.22
.5
. --Michael Bona
-It also tends to ship with SpamAssassin, which is a spam filter.
+-----
-----
+I noticed weird problems with MailScanner and [Exim]. It give odd errors when queueing an incoming mail
- say things like ''Remote host is local host'' or ''Retry timeout exceeded''. I'm still not sure what caused these, but I found out when they happen, which explains why no one else sees the problem:
-I noticed wierd problems with MailScanner and Exim
. It give odd errors when queueing an incoming mail - say things like
"Remote host is
local host" or "Retry timeout exceeded
".
I'm still not sure what caused these
, but I found out when they happen
, which explains why no one else sees
the problem:
+I use [PINE] on the same machine as the [MTA]
. [PINE] uses a
"local" transport (shows up in the logs as __local-esmtp__). This was the only transport causing problems
. If
I used [SMTP] from another machine
, or forced pine to use [SMTP] via setting its __smtp_server__ setting
, it was fine. If I sent mail from
the CommandLine via mail(1) it was fine. -- Daniel Lawson
-I use pine on the same machine as the MTA. Pine uses a "local" transport (shows up in the logs as local
-esmtp). This was the only transport causing problems. If I used SMTP from another machine, or forced pine to use smtp via setting its smtp_server setting, it was fine. If I sent mail from the cmdline via 'mail' it was fine.
+-----
-Wierd
. :
)
+I also have this weird problem (MailScanner 3
.13.2-4 and [Exim] 3.35-1
). Mails sent via [SMTP], mail(1) and /usr/lib/sendmail are delivered without errors. But mails generated from cron jobs are catched by the defer_director and immediatly produce a ''retry timeout exceeded'' error; with the resulting error messages it's the same. The retry settings in exim_incoming.conf are the same as set up by Debian, so retries should be done for four days.
+
+MailScanner doesn't seem to have anything to do with this behaviour, since it doesn't touch the mails before this error occurs; it seems, the required exim configuration is the only problem. -- Swen Kuehnlein
+
+----
+CategoryMailNotes