linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mail Delivery Subsystem <MAILER-DAEMON@lamx02.mgw.rr.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Returned mail: see transcript for details
Date: Fri, 25 Jun 2004 18:51:59 -0400 (EDT)	[thread overview]
Message-ID: <200406252251.i5PMpx7C007771@lamx02.mgw.rr.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

The original message was received at Fri, 25 Jun 2004 18:51:57 -0400 (EDT)
from adsl-64-171-193-148.dsl.lsan03.pacbell.net [64.171.193.148]

   ----- The following addresses had permanent fatal errors -----
<24d11941@mn.rr.com>
    (reason: 550 5.1.1 unknown or illegal alias: 24d11941@mn.rr.com)

   ----- Transcript of session follows -----
... while talking to ms-mta-02.rdc-kc.rr.com.:
>>> DATA
<<< 550 5.1.1 unknown or illegal alias: 24d11941@mn.rr.com
550 5.1.1 <24d11941@mn.rr.com>... User unknown
<<< 554 5.5.0 No recipients have been specified.

[-- Attachment #2: Type: message/delivery-status, Size: 407 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: Type: text/rfc822-headers, Size: 715 bytes --]

Received: from mn.rr.com (adsl-64-171-193-148.dsl.lsan03.pacbell.net [64.171.193.148])
	by lamx02.mgw.rr.com (8.12.10/8.12.8) with ESMTP id i5PMpu7C007633
	for <24d11941@mn.rr.com>; Fri, 25 Jun 2004 18:51:57 -0400 (EDT)
Message-Id: <200406252251.i5PMpu7C007633@lamx02.mgw.rr.com>
From: linux-fbdev-devel@lists.sourceforge.net
To: 24d11941@mn.rr.com
Subject: Mail Delivery (failure 24d11941@mn.rr.com)
Date: Fri, 25 Jun 2004 15:51:59 -0700
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Virus-Scan-Result: Repaired 36326 W32.Netsky.P@mm

             reply	other threads:[~2004-06-25 22:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 22:51 Mail Delivery Subsystem [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-16  6:51 Returned mail: see transcript for details Mail Delivery Subsystem
2004-08-14  0:13 Mail Delivery Subsystem
2004-08-12 17:51 Mail Delivery Subsystem
2004-08-11  6:25 Mail Delivery Subsystem
2004-07-22  1:20 Mail Delivery Subsystem
2004-07-20  4:24 Mail Delivery Subsystem
2004-07-06 23:26 Mail Delivery Subsystem
2004-07-04  8:59 Mail Delivery Subsystem
2004-07-02  0:43 Mail Delivery Subsystem
2004-06-28  4:53 Mail Delivery Subsystem
2004-06-26 20:23 Mail Delivery Subsystem
2004-06-20 11:41 Mail Delivery Subsystem
2004-05-31 13:32 Mail Delivery Subsystem
2004-05-25  6:31 Mail Delivery Subsystem
2004-05-15 20:01 Mail Delivery Subsystem
2004-05-14  6:46 Mail Delivery Subsystem
2004-04-27  7:32 Mail Delivery Subsystem
2004-04-20 17:13 Mail Delivery Subsystem
2004-04-11  5:24 Mail Delivery Subsystem
2004-04-09 13:22 Mail Delivery Subsystem
2004-03-31 11:30 Mail Delivery Subsystem
2004-03-27  7:24 Mail Delivery Subsystem
2004-03-24  9:39 Mail Delivery Subsystem
2004-03-04  8:19 Mail Delivery Subsystem

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406252251.i5PMpx7C007771@lamx02.mgw.rr.com \
    --to=mailer-daemon@lamx02.mgw.rr.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).