Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.
The following page has been changed by ScottLamb:
http://wiki.apache.org/spamassassin/IntegratedSpamdInPostfix
The comment on the change is:
There's nothing wrong with the first script.
------------------------------------------------------------------------------
A major problem with the above filter is that Postfix attempts to bounce messages flagged as spam. This is a waste of resources as most spams have fake return addresses. Furthermore, if they fake a return address that doesn't belong to them, you may end up bouncing the message to an innocent 3rd party. Enough of this can result in YOU being on an RBL.
+ '' '''Not true.''' (1) Postfix only bounces messages if you tell it to. I currently use the above filter, and I use a sieve rule to filter `X-Spam-Flag: YES` into a folder in the same account which I occasionally review. Many people sort mailing lists into separate folders, and this can typically be done with the same mechanism. It also makes it more practical to actually check it every now and then... all spam systems have false positives, so silently blackholing likely spam (potential ham) is far more rude than bouncing it. (2) If you use a proper bounce message (as opposed to those stupid virus filter notifications), there are ways for the innocent party to filter out bounces from messages they didn't send. When I get some time, I'll write one up and link to it. -Slamb''
+
Instead, we'd like to create a blackhole for spam.
To accomplish this while still using an after-queue filter, the spam may be redirected to another account on the system. Steps to do this are as follows:
You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.
The following page has been changed by ScottLamb:
http://wiki.apache.org/spamassassin/IntegratedSpamdInPostfix
The comment on the change is:
There's nothing wrong with the first script.
------------------------------------------------------------------------------
A major problem with the above filter is that Postfix attempts to bounce messages flagged as spam. This is a waste of resources as most spams have fake return addresses. Furthermore, if they fake a return address that doesn't belong to them, you may end up bouncing the message to an innocent 3rd party. Enough of this can result in YOU being on an RBL.
+ '' '''Not true.''' (1) Postfix only bounces messages if you tell it to. I currently use the above filter, and I use a sieve rule to filter `X-Spam-Flag: YES` into a folder in the same account which I occasionally review. Many people sort mailing lists into separate folders, and this can typically be done with the same mechanism. It also makes it more practical to actually check it every now and then... all spam systems have false positives, so silently blackholing likely spam (potential ham) is far more rude than bouncing it. (2) If you use a proper bounce message (as opposed to those stupid virus filter notifications), there are ways for the innocent party to filter out bounces from messages they didn't send. When I get some time, I'll write one up and link to it. -Slamb''
+
Instead, we'd like to create a blackhole for spam.
To accomplish this while still using an after-queue filter, the spam may be redirected to another account on the system. Steps to do this are as follows: