Gary Kline <[EMAIL PROTECTED]> writes: > If your user login is "smith", you could have all mailing > list mail sent to "smitty" and keep an open mutt or other reader > a click away. Spam could be easily flagged ... .
Yes, there are several things you could filter on. However the traplist activities are really about identifying spam sending hosts. If a machine we have not exchanged mail with in recent times tries to deliver mail to something bizarre like <[EMAIL PROTECTED]> (which looks like it was actually based on a GNUS message-ID), the message is either spam or in some very rare cases a bounce message triggered by an attempt to deliver spam. > I'm bcc'ing this to my account with evolution to check out your > blog info. I've run into problems with spamd and other suites. I would be interested in hearing what the problems were. It's worth noting that spamd from OpenBSD 4.1 onwards differs in several important ways from earlier versions. And also, it's important not to confuse this spamd with the program with the same name out of spamassassin. Cheers, -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
