Swallow, Harold wrote: > The application for which I intend to use qpsmtpd will > reside post-queue. It is expected that anti-virus and > anti-spam filtering will take place prior to entering > the MTA, Postfix, as you have outlined as being the best > situation. Actions that will take place within the > filter act on allowed users email.
That's the part I don't understand. What do you hope to accomplish with qpsmtpd post-queue? The whole point of qpsmtpd is to be a fully compliant SMTP engine with a flexible plugin architecture. It's designed to be a replacement for whatever process handles the inbound SMTP transfer. qpsmtp can handle antivirus, RBL-style blocklists, validation of FROM: and TO:, etc. > "Failures" during the filter processing will require notifying the sender. This is a very bad idea. If you have already accepted the messages, you no longer have the ability to refuse them during the SMTP transaction and can only bounce them. The vast majority of spam is sent with forged FROM: and/or envelope sender, so it is not acceptable to notify the sender via a bounce, since you are simply annoying an innocent bystander. Perhaps you can describe what feature of qpsmtpd you hope to utilize and then we can better advise you. As it stands, I can see no use for qpsmtpd post queue. John
