Return-Path: Delivered-To: apmail-spamassassin-users-archive@www.apache.org Received: (qmail 87911 invoked from network); 4 Jun 2008 14:46:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jun 2008 14:46:03 -0000 Received: (qmail 48947 invoked by uid 500); 4 Jun 2008 14:45:56 -0000 Delivered-To: apmail-spamassassin-users-archive@spamassassin.apache.org Received: (qmail 48698 invoked by uid 500); 4 Jun 2008 14:45:55 -0000 Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 48687 invoked by uid 99); 4 Jun 2008 14:45:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jun 2008 07:45:55 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dbarker@visioncomm.net designates 74.254.46.133 as permitted sender) Received: from [74.254.46.133] (HELO mail.visioncomm.net) (74.254.46.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jun 2008 14:44:59 +0000 Received: from dan [172.30.0.203] by mail.visioncomm.net with ESMTP (SMTPD32-8.15) id AA7FFBF00A0; Wed, 04 Jun 2008 10:45:19 -0400 From: "Dan Barker" To: "'Jack Gostl'" , "'spam'" References: <01b101c8c64b$f473dd60$b401a50a@JackDell> Subject: RE: Undeliverable mails Date: Wed, 4 Jun 2008 10:45:20 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F9_01C8C630.1571AB80" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <01b101c8c64b$f473dd60$b401a50a@JackDell> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Thread-Index: AcjGTA+B6jsgnAUwRUqtzYAoJfIC6QABN/4A X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------=_NextPart_000_00F9_01C8C630.1571AB80 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit That's exactly what VBounce is for. If a bounce message does not contain your MTA, it's either backscatter (safe to delete) or useless (from AOHell, for example). If you can't track the source, you don't need to see it. I get about 10 legitimate bounces a day, and VBounce takes care of about 200 backscatter. I can read 10 messages, I can't read 200. The bounces I see are usually due to messages sent by my webserver (password request) by folks who type their email address incorrectly. The Backscatter was a big problem until I started using the VBounce rules. Trying to educate the sysadmins producing the backscatter is a hopeless cause (imo). Dan _____ From: Jack Gostl [mailto:gostl@argoscomp.com] Sent: Wednesday, June 04, 2008 10:05 AM To: spam Subject: Undeliverable mails I'm not sure if this can even be handled, but I thought I'd put it out there. Someone is using our email address to originate spam. We are getting bombed with "Mail undeliverable" etc. messages from failed spam delivery attempts. This morning I check my inbox and found almost 100 of these since last night. I'm not sure what can be done about this. I'm a bit squeamish about just knocking this stuff out in procmail. Does anyone have any suggestions? ------=_NextPart_000_00F9_01C8C630.1571AB80 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

That's exactly what VBounce is for. If a bounce = message=20 does not contain your MTA, it's either backscatter (safe to delete) or = useless=20 (from AOHell, for example). If you can't track the source, you don't = need to see=20 it. I get about 10 legitimate bounces a day, and VBounce takes care of=20 about 200 backscatter.

I can read 10 messages, I can't read 200. The = bounces I=20 see are usually due to messages sent by my webserver (password = request) by=20 folks who type their email address incorrectly. The Backscatter was a = big=20 problem until I started using the VBounce rules.

Trying to educate the sysadmins producing the = backscatter=20 is a hopeless cause (imo).

Dan

From: Jack Gostl = [mailto:gostl@argoscomp.com]=20
Sent: Wednesday, June 04, 2008 10:05 AM
To:=20 spam
Subject: Undeliverable mails

I'm not sure if this can even be handled, but I = thought I'd=20 put it out there.

Someone is using our email address to originate = spam. We are=20 getting bombed with "Mail undeliverable" etc. messages from failed spam = delivery=20 attempts. This morning I check my inbox and found almost 100 of these = since last=20 night.

I'm not sure what can be done about this. I'm a bit = squeamish=20 about just knocking this stuff out in procmail.

Does anyone have any suggestions?

------=_NextPart_000_00F9_01C8C630.1571AB80--