procmail
[Top] [All Lists]

Re: Spam bouncer

2000-01-05 08:25:01
* Mon 2000-01-03 Greg Waits <gtinternet(_at_)gtinternet(_dot_)com> list.procmail
* Message-Id: 
<NDBBIPCBKLAFOJCHPMFKGEMDCEAA(_dot_)gtinternet(_at_)gtinternet(_dot_)com>
| 
| do you know of a program that will BOUNCE SPAM? i tried to use a program
| called spam bouncer but it does not work at all.

That's odd, because hundreads/thousends of people are using it.
There is unwritten rule that 

    YOU SHOULD NOT BOUNCE BACK AUTOMATICALLY[1][2]

One day, you may bounce to a mailing list and you will be 
hung from your neck by the members.

There are lot of alternative resources to fight against spam, check
this and Era's pages at http://www.iki.fi/~era/procmail/

    http://www.procmail.org/jari/pm-tips.txt

        3.0 Anti-UBE pointers
            3.1 NoCEM, CAUCE and others
            3.2 General Filtering pages (more than procmail)
            3.3 Junk email and spam
            3.4 Comprehensive list of spammers
            3.5 Misc pointers
            3.6 Questionable UBE stop services
            3.7 UBE related newsgroups or mailing lists
            3.8 Software: the net abuse page
            3.9 Software: adcomplain -- Perl junk email rport
            3.10 Software: Ricochet -- Perl junk email rport
            3.11 Software: yell -- perl
            3.12 Software: ifile - Perl
            3.13 Software: RBL lookup tool -- C
            3.14 Software: mapSoN
            3.15 Software: spamgard
            3.16 Software: Spam Be Gone
            3.17 Software: ClearMail
            3.18 Software: TinyGnus - Emacs Gnus plug-in
        
 
jari




Footnotes: (Created with Emacs footnote.el)

[1] Do not use any "tool" that responds automatically. Instead
    It should delived to "suspectible spambox" from where you manaully
    select mails that are true spam. But there are exeptions,
    e.g. the blacklists bouncer (RBL).

[2] You can bounce spam, if you write the rule explicitedly yourself
    to the procmail. These are the "rapid spammers", that harrash you
    every day, so you can write explicit Received: header catch for them.


<Prev in Thread] Current Thread [Next in Thread>