linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mail Delivery Subsystem <MAILER-DAEMON@iphase.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Returned mail: see transcript for details
Date: Tue, 20 Apr 2004 12:13:20 -0500 (CDT)	[thread overview]
Message-ID: <200404201713.i3KHDK905887@eclipse.iphase.com> (raw)

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

The original message was received at Tue, 20 Apr 2004 12:13:19 -0500 (CDT)
from uucp@localhost

   ----- The following addresses had permanent fatal errors -----
<pwang@iphase.com>
    (reason: 550 5.1.1 <pwang@iphase.com>... User unknown)

   ----- Transcript of session follows -----
... while talking to mailhub.iphase.com.:
>>> RCPT To:<pwang@iphase.com>
<<< 550 5.1.1 <pwang@iphase.com>... User unknown
550 5.1.1 <pwang@iphase.com>... User unknown

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

[-- Attachment #3: Type: message/rfc822, Size: 1806 bytes --]

[-- Attachment #3.1.1: Type: text/plain, Size: 43 bytes --]


For further details see the attachment.



[-- Attachment #3.1.2: data.zip.htm --]
[-- Type: Text/HTML, Size: 594 bytes --]

<html><head><meta HTTP-EQUIV="Content-Type" content="text/html; charset=">
<title>VIRUS INFECTION ALERT</title></head>
<body>
<h1><font color="#FF0000">VIRUS INFECTION ALERT</font></h1>
<p>The Gauntlet Firewall&reg discovered a virus in this file.
The file was not repaired and has therefore been removed.
See your system administrator for further information.
</p>
<p>Filename: data.zip<br>
Virus name: W32/Netsky.p@MM!zip</p>

<p>Copyright &copy; 1993-2001, Networks Associates Technology, Inc.All Rights Reserved.<br>
<a href="http://www.pgp.com">http://www.pgp.com</a></p>
 </body></html>


             reply	other threads:[~2004-04-20 17:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 17:13 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-25 22:51 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-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=200404201713.i3KHDK905887@eclipse.iphase.com \
    --to=mailer-daemon@iphase.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).