From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,561ac97c34d8f8ef X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-22 05:06:33 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!uninett.no!ntnu.no!not-for-mail From: Preben Randhol Newsgroups: comp.lang.ada Subject: Re: OT-spam detection, was Re: WM, and lindens rustled Date: Thu, 22 Jan 2004 13:06:32 +0000 (UTC) Organization: PVV Message-ID: References: <100tknotk84nfe0@corp.supernews.com> NNTP-Posting-Host: k-083152.nt.ntnu.no X-Trace: tyfon.itea.ntnu.no 1074776792 1273 129.241.83.152 (22 Jan 2004 13:06:32 GMT) X-Complaints-To: usenet@itea.ntnu.no NNTP-Posting-Date: Thu, 22 Jan 2004 13:06:32 +0000 (UTC) User-Agent: slrn/0.9.8.0 (Linux) Xref: archiver1.google.com comp.lang.ada:4638 Date: 2004-01-22T13:06:32+00:00 List-Id: On 2004-01-22, Larry Kilgallen wrote: > > For improvement of the Internet, it is better to reject such connections > at the SMTP level, or best of all engage in teergrubing/tarpitting. Such > are typically done based on DNSbls of the email administrator's choice. Well, since it isn't done I would suspect this approach isn't working. Besides by the time one find out which DNS that sendt the SPAM they probably moved to another. Or they broke into a persons machine and used it. Another solution would be SPAM-viruses etc... -- "Saving keystrokes is the job of the text editor, not the programming language."