[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The combination of spamd and pf is really working wonders for me. Kudos
to the development team. Currently, I don't use the greylist option, but
my own little algorithm for watching the mail log and adding IPs to the
tarpit as needed. I went from nearly 1000 delivery attempts per minute
(mostly dictionary attacks) to fewer than 30.
re: spamd version 3.5
Anyway, I'm running this on FreeBSD 5.2.1R, and everything works as
documented, except for the logging. 2 issues: -v doesn't log anything
extra to LOG_INFO. SMTP dialogue does go to LOG_DEBUG, tho only briefly.
The second issue is that all logging dies, usually in under 10 minutes:
May 5 13:30:02 d1 spamd: 22.214.171.124: connected (101/0)
May 5 13:30:02 d1 spamd: 126.96.36.199: disconnected after 54 seconds.
May 5 13:30:02 d1 spamd: 188.8.131.52: disconnected after 4 seconds.
May 5 13:30:02 d1 spamd: 184.108.40.206: disconnected after 54 seconds.
May 5 13:30:02 d1 spamd: 220.127.116.11: connected (99/0)
Yesterday at 13:30 was the last time I heard from spamd. The daemon is
still running and doing its job. If I use the '-d' flag so the terminal
stays attached, I continue to see the 'ip.add.re.ss connected for xx
seconds' messages even after logging has died. Killing the spamd daemon
and restarting it will cause the logs to work again, but again only
briefly. Any other FreeBSD users out there with similar issues?
Suggestions on tracking it down?
One other quickie: the output from using the -d flag for debugging often
shows something like this even though I don't have greylisting active:
(GREY) 18.104.22.168: <[email protected]> -> <[email protected]>
Any concern here? I assume it's a harmless notice from the greylisting
code, but just verifying. :-)
 - pf has got me hooked. Not sure how I ever lived with ipfw. Woohoo!
And the performance is awesome. 23,000 IPs in my spamd table currently.
IPFW would completely fall over under that load IME.