I'm hoping someone can help me by answering a couple of questions regarding spamd. Ultimately, I'm wanting to know if the spamd setup I'm envisioning is possible. I'll explain the situation.
To begin, we attempted a typical setup of spamd in greylisting mode on our firewall in front of our MX. This worked great and was catching lots of spam, for around 48 hours. During this time, we (IT Dept.) got several complaints about delayed delivery of emails from our clients. This was mostly due to impatient recipients within our organization. However, as a result, we were told, by executive order, to shut down the greylisting. Apparently the greylisting, in doing what it's supposed to do, was "disrupting time-sensitive email". Nevermind that we were white-listing these senders as we were made aware of them. So, this brings me to my set-up inquiry. We do receive lots of delivery attempts to non-existent addresses in our domain and the greytrapping feature of spamd was especially handy for blocking sites attempting to deliver to these non-existent addresses. I would like to be able to take advantage of this feature of spamd, along with the "blacklist" features, while not delaying email to non spamtrapped addresses. >From my understanding of the interaction between spamd and pf, this either isn't possible or is non-trivial. However, I figured I would see if anyone has done a similar set-up or knows of a way to implement this. Thanks. [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]