I think I have solved the problem in a very simple way. I used to have my email address listed in the dist file as follows tlt@tltodd.com
I changed it to just, tlt without the @tltodd.com.
Now the types of spam that were faking being me are being rejected. Here's an example header from one of them.
From tlt@tltodd.com Mon Jun 14 20:09:45 2004 Received: from AM-XXK ([218.22.151.181]) by tltodd.com (8.9.3/8.9.3) with SMTP id UAA31512; Mon, 14 Jun 2004 20:09:42 -0500 (CDT) (envelope-from tlt@tltodd.com) X-Message-Info: 952DXU698SGl27mufALBrsLPN694MC5lSZGquO51 Received: from 49.232.72.60 by heublein21-or74.atom906.tlt@tltodd.com with DAV; Wed, 16 Jun 2004 02:13:23 +0100 Message-ID: <1977290425195.12559@tlt@tltodd.com> X-Originating-IP: [152.141.110.254] X-Originating-Email: [tlt@tltodd.com] X-Sender: tlt@tltodd.com Reply-To: "Freddie Paul" tlt@tltodd.com From: "Freddie Paul" tlt@tltodd.com To: "Tlt" tlt@tltodd.com Subject: hiTlt Date: Tue, 15 Jun 2004 18:10:23 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--6022717837479247247" X-Diagnostic: Not on the accept list X-Envelope-To: [my-mailing-list]
The spammers apparently haven't figured out how to match my email address with my real name. Notice how the Message-ID: field is also faked to be from my system.
I can now send messages to the list from my localhost without any problem and not get faked messages coming through.
Tell me if there are any flaws in this that you might think of.
Terry Todd
smartlist@lists.rwth-aachen.de