Hi!

Consider the following headers:

Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 323 invoked by uid 615); 9 Nov 2003 00:28:19 -0000
Received: from [EMAIL PROTECTED] by worf.andebakken.dk by uid 81 with
qmail-scanner-1.20
 (clamscan: 20030806. uvscan: v4.1.60/v4302. f-prot: 4.1.2/3.13.4.
spamassassin: 2.60.  Clear:RC:0(66.159.202.147):SA:1(6.0/5.0):.
 Processed in 3.978622 secs); 09 Nov 2003 00:28:19 -0000
Received: from adsl-66-159-202-147.dslextreme.com (HELO andebakken.dk)
(66.159.202.147)
  by worf.andebakken.dk with SMTP; 9 Nov 2003 00:28:15 -0000
Received: from fuad [192.168.1.100] by andebakken.dk with eSMTP;
        Sat, 8 Nov 2003 16:30:23 -0800
Message-ID: <[EMAIL PROTECTED]>
From: "michael" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Shower your womans face with curn with these pills!
Date: Sat, 8 Nov 2003 16:30:23 -0800
MIME-Version: 1.0
Content-Type: text/html; charset="ISO-8859-1"
X-Priority: 3
X-Mailer: PHP
Return-Path: [EMAIL PROTECTED]
Bel-Tracking: <YnJpYW4uaXBzZW5AYW5kZWJha2tlbi5kaw==>

The spammer uses my own email address as sender to try to inject spam into
my system - in combination with TMDA this just causes the confirmation
request be bounced/ /dev/null'ed - and I won't the the message anyway...

Is there any way of avoiding this ?? Yes, I know I can bounce them in my
badmailfrom file in qmail... but is there another way (not that I often send
mail to myself, but I had hoped there was a more intelligent way to specify,
that mails from the outside couldn't be sent into my system, claiming to be
from my own domain)??

Regards

/Brian


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to