Yes, you have a point. However, running logcheck I am notified every hour of each message that gets bounced, and if the sender or subject line bears scrutiny, I can check it and whitelist_to or whitelist_from in local.cf as appropriate. The bounces are copied and archived for seven days.
This wouldn't be workable for as ISP, but we're a small shop here, less than 250 accounts, and our users aren't paying for email service. It's less trouble for me than fielding complaints from our users about offensive porn spam. We did get a few false positives the first few days, but they are pretty rare now. This is still pretty new for us, and if it doesn't work out we can always stop bouncing on the "spam" subject and go around a show a couple of hundred people how to setup filters with their email client. Daniel Pittman wrote: > > On Wed, 13 Mar 2002, Michael Grau wrote: > > [...] > > > I don't see much point in tagging spam and then delivering > > it anyway. The spammers still got their message through. > > So what if it's in a special little folder all its own? > > The problem with this approach is that SpamAssassin is a heuristic > system. I have had a number of false positives on this list, for > example, over the last week. > > With your system, not only would I not know about this, I would probably > have lost my subscription when the number of bounced messages got too > high... > > False positives are the reason to put SPAM in a special folder and > review it every now and then. :) > > Daniel > > -- > How alike are the groans of love, to those of the dying. > -- Malcolm Lowry, _Under the Volcano_, (1947) > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
