On 22/08/2012 18:47, Terry Barnum wrote: > > On Aug 21, 2012, at 2:22 PM, Daniele Nicolodi wrote: > >> On 21/08/2012 19:34, Mikkel Bang wrote: >>> Thanks a lot everyone! After thinking long and hard about all your >>> advice I finally ended up with: >>> >>> OpenBSD + postfix-anti-UCE.txt + undeadly's spamd setup (which >>> includes greylisting+greytrapping) + dspam: https://gist.github.com/3417519 >>> >>> Feedback would be much appreciated. >> >> Am I missing something or in this setup dspam is not used to reject spam >> but only to classify messages? I would like to give dspam a try, but in >> the the documentation no hints are given on how use dspam to reject >> spam, and this is an important requirement, IMHO. >> >> Cheers, >> Daniele > > Daniele, it's easy to configure dspam to classify/tag only. > > Preference "spamAction=tag" # { quarantine | tag | deliver } -> > default:quarantine > > http://dspam.git.sourceforge.net/git/gitweb.cgi?p=dspam/dspam;a=blob_plain;f=README;hb=HEAD
You didn't understand my comment. I want spam to be rejected at the SMTP transaction level. I don't want it to be stored anywhere, but of course I want the sender to be notified that the message didn't go through. Looks like this is not possible with dspam alone. Googling, the only proposed solution I found is to use a SMPT proxy which integrates dspam. Cheers, Daniele
