xen-devel

[Top] [All Lists]

[Xen-devel] DSN: failed (Error)

from [Mailbot for etexusa . com]

[Permanent Link][Original]

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] DSN: failed (Error)
From:	Mailbot for etexusa.com <>
Date:	Sat, 18 Sep 2010 05:08:45 -0700
Delivery-date:	Thu, 23 Sep 2010 05:33:05 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

This is a Delivery Status Notification (DSN).

I was unable to deliver your message to
acaruba@xxxxxxxx

I said 
  (end of message)

And they gave me the error;
  550 5.2.0 W32/Mydoom.o@MM!zip

Reporting-MTA: dns; etexusa.com
Final-Recipient: RFC822; acaruba@aol.com
Action: failed
Status: 5.0.0

Received: from lists.xensource.com ([122.178.155.156]) by etexusa.com for 
<acaruba@xxxxxxx>; Sat, 18 Sep 2010 05:08:32 -0700
From: xen-devel@xxxxxxxxxxxxxxxxxxx
To: acaruba@xxxxxxx
Subject: Error
Date: Sat, 18 Sep 2010 17:37:23 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="----=_NextPart_000_0013_30A5646E.2ABAB947"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] DSN: failed (Error), Mailbot for etexusa . com <=

Previous by Date:	Re: [Xen-devel] Does Xen scheduler preserves 5% of its utilization to every VM?, walmart
Next by Date:	[Xen-devel] Re: [Qemu-devel] [PATCH RFC V3 04/12] xen: Add the Xen platform pci device, Anthony PERARD
Previous by Thread:	[Xen-devel] remus failure -xen 4.0.1: xc_restore failed only at some heavy workload, Kyungjin Yoo
Next by Thread:	[Xen-devel] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot, Paweł Zuzelski
Indexes:	[Date] [Thread] [Top] [All Lists]