spamd whitelist updating
spamlogd manipulates the
spamd(8) database in /var/db/spamd used for
spamlogd updates the
/var/db/spamd whitelist entries whenever a
connection to port 25 is logged to the
pflog(4) interface. The source addresses of inbound connections are
whitelisted when seen by
spamlogd to ensure that
their entries in /var/db/spamd do not expire if the
connecting host continues to send legitimate mail. The destination addresses
of outbound connections are whitelisted when seen by
spamlogd so that replies to outbound mail may be
received without initial greylisting delays. Greylisting is explained more
fully in spamd(8).
The options are as follows:
- Debugging mode.
spamlogddoes not disassociate from the controlling terminal.
- Specify that
spamlogdis only to whitelist inbound SMTP connections. By default
spamlogdwill whitelist the source of inbound SMTP connections, and the target of outbound SMTP connections.
- Specify a network interface on which packets must arrive. The default is to watch for connections logged from all interfaces.
- Specify a pflog(4) interface to listen for connection notifications. The default is to watch for connections logged on “pflog0”.
- Adjust the time for whiteexp in hours. The default is 864 hours (approximately 36 days); maximum is 2160 hours (approximately 90 days).
- Add a target to receive synchronisation messages; see SYNCHRONISATION below. This option can be specified multiple times.
It is important to log any connections to and from the real MTA in
spamlogd to update the whitelist entries.
See spamd(8) for an example ruleset for logging such connections.
spamlogd sends log messages to
syslogd(8) using facility
spamlogd will log each connection it sees at level
spamlogd supports realtime synchronisation
of whitelist states by sending the information it updates to a number of
spamd(8) daemons running on multiple machines. To enable
synchronisation, use the command line option
specify the machines to which
spamlogd will send
messages when it updates the state information. For more information, see
syslog(3), pflog(4), spamd.conf(5), pflogd(8), spamd(8), spamd-setup(8), spamdb(8), syslogd(8), tcpdump(8)
spamlogd command first appeared in