Returned mail: see transcript for details (fwd)

Returned mail: see transcript for details (fwd)

[Joseph S. Myers]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1150 bytes --]

Could urkgqtncaius@spammotel.com be removed from gcc-patches, as an
address generating bounces to original senders of messages?

-- 
Joseph S. Myers
jsm@polyomino.org.uk

---------- Forwarded message ----------
Date: Mon, 28 Jun 2004 16:38:17 -0400
From: urkgqtncaius@spammotel.com
To: jsm@polyomino.org.uk
Subject: Returned mail: see transcript for details

The original message was received at Mon, 28 Jun 2004 16:38:13 -0400
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<urkgqtncaius@spammotel.com>
    (reason: 500 Your message appears to be spam and was rejected. Please send a blank message to allow@access.bpa.nu to be instantly added to the whitelist - mail then sent by you will not be rejected.)

   ----- Transcript of session follows -----
... while talking to mx.access.bpa.nu.:
>>> DATA
<<< 500 Your message appears to be spam and was rejected. Please send a blank message to allow@access.bpa.nu to be instantly added to the whitelist - mail then sent by you will not be rejected.
554 5.5.0 Remote protocol error
451 4.0.0 Cannot open hash database /etc/mail/aliases.db: Invalid argument

[-- Attachment #2: Type: MESSAGE/DELIVERY-STATUS, Size: 504 bytes --]

Reporting-MTA: dns; spammotel.spammotel.com
Received-From-MTA: DNS; localhost
Arrival-Date: Mon, 28 Jun 2004 16:38:13 -0400

Final-Recipient: RFC822; urkgqtncaius@spammotel.com
Action: failed
Status: 5.5.2
Remote-MTA: DNS; mx.access.bpa.nu
Diagnostic-Code: SMTP; 500 Your message appears to be spam and was rejected. Please send a blank message to allow@access.bpa.nu to be instantly added to the whitelist - mail then sent by you will not be rejected.
Last-Attempt-Date: Mon, 28 Jun 2004 16:38:17 -0400

[-- Attachment #3: Type: TEXT/RFC822-HEADERS, Size: 2309 bytes --]

Return-Path: <re.NX66HUZ4@spammotel.com>

Received: from spammotel.spammotel.com (localhost [127.0.0.1])

	by spammotel.spammotel.com (8.12.11/8.12.11) with ESMTP id i5SKcDFH014000

	for <urkgqtncaius@spammotel.com>; Mon, 28 Jun 2004 16:38:13 -0400

Received: (from root@localhost)

	by spammotel.spammotel.com (8.12.11/8.12.11/Submit) id i5SKcDHE013993

	for urkgqtncaius@spammotel.com; Mon, 28 Jun 2004 16:38:13 -0400

Old-Return-Path: <gcc-patches-return-120885-urkgqtncaius=spammotel.com@gcc.gnu.org>

Received: from sourceware.org (sourceware.org [12.107.209.250])

	by spammotel.spammotel.com (8.12.11/8.12.11) with SMTP id i5SKc564013495

	for <urkgqtncaius@spammotel.com>; Mon, 28 Jun 2004 16:38:05 -0400

Received: (qmail 6849 invoked by alias); 28 Jun 2004 20:39:32 -0000

Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm

Precedence: bulk

List-Unsubscribe: <mailto:gcc-patches-unsubscribe-urkgqtncaius=spammotel.com@gcc.gnu.org>

List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>

List-Post: <mailto:gcc-patches@gcc.gnu.org>

List-Help: <mailto:gcc-patches-help@gcc.gnu.org>

Sender: gcc-patches-owner@gcc.gnu.org

Delivered-To: mailing list gcc-patches@gcc.gnu.org

Received: (qmail 6842 invoked from network); 28 Jun 2004 20:39:31 -0000

Received: from unknown (HELO lon-mail-3.gradwell.net) (193.111.201.127)

  by sourceware.org with SMTP; 28 Jun 2004 20:39:31 -0000

Received: (qmail 66577 invoked from network); 28 Jun 2004 20:39:29 -0000

Received: from digraph.polyomino.org.uk (postmaster%pop3.polyomino.org.uk@81.187.227.50)

  by lon-mail-3.gradwell.net with SMTP; 28 Jun 2004 20:39:29 -0000

Received: from jsm28 (helo=localhost)

	by digraph.polyomino.org.uk with local-esmtp (Exim 4.34)

	id 1Bf2uW-00032u-TB

	for gcc-patches@gcc.gnu.org; Mon, 28 Jun 2004 20:39:28 +0000

Date: Mon, 28 Jun 2004 20:39:28 +0000 (UTC)

From: "Joseph S. Myers" <jsm@polyomino.org.uk>

X-X-Sender: jsm28@digraph.polyomino.org.uk

To: gcc-patches@gcc.gnu.org

Old-Subject: Patch to change built-in exec*, fork to DEF_EXT_LIB_BUILTIN

Message-ID: <Pine.LNX.4.58.0406282038280.23874@digraph.polyomino.org.uk>

MIME-Version: 1.0

Content-Type: TEXT/PLAIN; charset=US-ASCII

Subject: **Fwd: Patch to change built-in exec*, fork to DEF_EXT_LIB_BUILTIN

Reply-To: <re.NX66HUZ4@spammotel.com>

Re: Returned mail: see transcript for details (fwd)

[Christopher Faylor]

On Mon, Jun 28, 2004 at 09:00:15PM +0000, Joseph S. Myers wrote:
>Could urkgqtncaius@spammotel.com be removed from gcc-patches, as an
>address generating bounces to original senders of messages?

Sure could.  I removed another one of these from the gcc mailing list
last week, IIRC.

Should I be more draconian and block any attempts from anyone at
spammotel.com to subscribe to a mailing list?

cgf

Re: Returned mail: see transcript for details (fwd)

[Christopher Faylor]

On Wed, Jun 13, 2001 at 11:56:14AM -0400, Christopher Faylor wrote:
>On Wed, Jun 13, 2001 at 11:56:19AM +0100, Joseph S. Myers wrote:
>>Could someone remove this person from whatever gcc lists they are on?
>>
>>If you can work out what system is removing the envelope sender
>>information, or ignoring it and using the header From address instead, it
>>might be as well to complain to their postmaster about the broken system
>>as well.
>
>I've removed ceo@nbensacomputers.com from all gcc lists.

Hmm.  I've also removed him from all sources.redhat.com lists.  I was
getting bounce messages from the cygwin lists.  How annoying.

cgf

Re: Returned mail: see transcript for details (fwd)

[Christopher Faylor]

On Wed, Jun 13, 2001 at 11:56:19AM +0100, Joseph S. Myers wrote:
>Could someone remove this person from whatever gcc lists they are on?
>
>If you can work out what system is removing the envelope sender
>information, or ignoring it and using the header From address instead, it
>might be as well to complain to their postmaster about the broken system
>as well.

I've removed ceo@nbensacomputers.com from all gcc lists.

cgf

Returned mail: see transcript for details (fwd)

[Joseph S. Myers]

Could someone remove this person from whatever gcc lists they are on?

If you can work out what system is removing the envelope sender
information, or ignoring it and using the header From address instead, it
might be as well to complain to their postmaster about the broken system
as well.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

---------- Forwarded message ----------
Date: Wed, 13 Jun 2001 03:42:56 -0700 (PDT)
From: Mail Delivery Subsystem <MAILER-DAEMON@mail-in.namezero.com>
To: jsm28@cam.ac.uk
Subject: Returned mail: see transcript for details

The original message was received at Wed, 13 Jun 2001 03:42:55 -0700 (PDT)
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<nbensa@yahoo.com>
    (reason: 554 delivery error: dd Sorry, your message to nbensa@yahoo.com cannot be delivered.  This account is over quota. - mta311.mail.yahoo.com)

   ----- Transcript of session follows -----
... while talking to mx3.mail.yahoo.com.:
>>> DATA
<<< 554 delivery error: dd Sorry, your message to nbensa@yahoo.com cannot be delivered.  This account is over quota. - mta311.mail.yahoo.com
554 5.0.0 <nbensa@yahoo.com>... Service unavailable