amavisd-milter(8) | System Manager's Manual | amavisd-milter(8) |
amavisd-milter
—
sendmail milter for amavisd-new
amavisd-milter |
[-fhv ] [-d
debug-level] [-D
delivery-care-of] [-m
max-conns] [-M
max-wait] [-p
pidfile] [-P ]
[-q backlog]
[-s socket]
[-t timeout]
[-S socket]
[-T timeout]
[-w directory] |
The amavisd-milter
is a sendmail milter
(mail filter) for amavisd-new 2.4.3 and above and
sendmail 8.13 and above (limited support for 8.12 is
provided).
Instead of older amavis-milter helper program, full amavisd-new functionality is available, including adding spam and virus information header fields, modifying Subject, adding address extensions and removing certain recipients from delivery while delivering the same message to the rest.
For more information you can visit amavisd-milter website:
http://amavisd-milter.sourceforge.net/
and SourceForge project:
http://sourceforge.net/projects/amavisd-milter
The options are as follows:
-d
debug-level-D
delivery-care-ofWhen server method is used then amavisd-new is responsible to forward the message to recipients and can provide personalized header and body modification. $forward_method in amavisd.conf must point to some place willing to accept mail without further checking in amavisd-new.
-f
amavisd-milter
in the foreground (i.e. do not
daemonize). Print debug messages to the terminal.-h
-m
max-conns-M
max-wait-p
pidfile-P
-q
backlog-s
socketamavisd-milter
(default
/var/lib/amavis/amavisd-milter.sock). The protocol spoken over this socket
is
MILTER
(Mail FILTER). It must agree with the INPUT_MAIL_FILTER entry in
sendmail.mc
The socket should be in "proto:address" format:
-S
socketamavisd-milter
and
amavisd-new (default /var/lib/amavis/amavisd.sock). The
protocol spoken over this socket is
AM.PDP
(AMavis Policy Delegation Protocol). It must agree with the
$unix_socketname entry in amavisd.conf.
The socket should be in "proto:address" format:
-t
timeout-T
timeout-v
-w
directorysmfi_addheader
()
is used instead of
smfi_insheader
()
for insheader
and
addheader
AM.PDP responses. This works well with
amavisd-new 2.4.3 or newer.smfi_progress
()
isn't called when amavisd-milter wait for
amavisd-new communication socket.quarantine
isn't implemented.When remote client is authenticated, amavisd-milter forward this information to amavisd-new through AM.PDP request attribute policy_bank:
In amavisd.conf file change protocol and socket settings to:
$protocol = "AM.PDP"; # Use AM.PDP protocol $unix_socketname = "$MYHOME/amavisd.sock"; # Listen on Unix socket ### $inet_socket_port = 10024; # Don't listen on TCP port
Then (re)start amavisd daemon.
To the sendmail.mc file add the following entries:
define(`confMILTER_MACROS_ENVFROM', confMILTER_MACROS_ENVFROM`, r, b') INPUT_MAIL_FILTER(`amavisd-milter', `S=local:/var/lib/amavis/amavisd-milter.sock, F=T, T=S:10m;R:10m;E:10m')
Then rebuild your sendmail.cf file, install it (usually to /etc/mail/sendmail.cf) and (re)start sendmail daemon.
amavisd-milter
This example assume that amavisd-new is running as user amavis. It must agree with the entry $daemon_user in amavisd.conf.
First create working directory:
mkdir /var/lib/amavis/tmp chmod 750 /var/lib/amavis/tmp chown amavis /var/lib/amavis/tmp
Then start amavisd-milter
as
non-priviledged user amavis:
su - amavis -c
"amavisd-milter
-w
/var/lib/amavis/tmp"
To limit concurrent connections to 4 and fail after 10 minutes
(10*60 secs) of waiting run amavisd-milter
with this
options:
su - amavis -c
"amavisd-milter
-w
/var/lib/amavis/tmp -m
4 -M
600"
For troubleshooting run amavisd-milter
on
the foreground and set debug level to appropriate level:
su - amavis -c
"amavisd-milter
-w
/var/lib/amavis/tmp -f
-d
level"
where debug levels are:
amavisd-milter
debug messages.http://amavisd-milter.sourceforge.net http://www.ijs.si/software/amavisd/ http://www.milter.org/developers http://www.sendmail.org
This manual page was written by Petr Rehor <rx@rx.cz> and is based on Jerzy Sakol <jerzy.sakol@commgraf.pl> initial work.
A community mailing lists are available at:
http://sourceforge.net/mail/?group_id=138169
Enhancements, requests and problem reports are welcome.
If you run into problems first check the users mailing list archive before asking questions on the list. It's highly likely somebody has already come across the same problem and it's been solved.
Januar 23, 2006 | Debian |