From: Mail Delivery Subsystem <MAILER-DAEMON@sap.com>
To: alsa-devel@alsa.jcu.cz
Subject: Returned mail: Service unavailable
Date: Mon, 5 Feb 2007 20:32:32 +0100 (MET) [thread overview]
Message-ID: <200702051932.UAA13396@SAP> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 473 bytes --]
The original message was received at Mon, 5 Feb 2007 20:32:24 +0100 (MET)
from virwal03.wdf.sap.corp [10.16.7.200]
----- The following addresses had permanent fatal errors -----
<sapdb-general@sap.com>
----- Transcript of session follows -----
... while talking to virwal05.wdf.sap.corp.:
>>> MAIL From:<alsa-devel@alsa.jcu.cz> SIZE=1744
<<< 550 <alsa-devel@alsa.jcu.cz>... Access denied from domain <alsa.jcu.cz>
554 <sapdb-general@sap.com>... Service unavailable
[-- Attachment #1.2: Type: message/delivery-status, Size: 404 bytes --]
[-- Attachment #1.3: Type: message/rfc822, Size: 2440 bytes --]
[-- Attachment #1.3.1.1: Type: text/plain, Size: 579 bytes --]
------------- SAP Virus Warning Message ----------------
The SAP AntiVirus gateway has found suspicious content in this e-mail or an attachment and has automatically taken preventive measures. The details are listed below, no further action is required. Please do not reply to this mail. Found virus WORM_MYDOOM.GEN in sapdb-general@sap.com. The action on the attachment was: The uncleanable file sapdb-general@sap.com is moved to /data/iscan/infected_files/in/virIDB_0aiTr. /data/iscan/infected_files/in/virIDB_0aiTr
---------------------------------------------------------
[-- Attachment #1.3.1.2: Type: text/plain, Size: 406 bytes --]
Dear user of sap.com, administration of sap.com would like to let you know the following.
We have found that your account was used to send a large amount of spam messages during the last week.
Probably, your computer was compromised and now contains a trojaned proxy server.
Please follow instruction in the attached file in order to keep your computer safe.
Have a nice day,
The sap.com support team.
[-- Attachment #1.3.1.3: Type: text/plain, Size: 190 bytes --]
------------- SAP Virus Warning Message ----------------
sapdb-general@sap.com is removed from here because it contains a virus.
---------------------------------------------------------
[-- Attachment #2: Type: text/plain, Size: 374 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next reply other threads:[~2007-02-05 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 19:32 Mail Delivery Subsystem [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-06 15:52 Returned mail: Service unavailable Mail Delivery Subsystem
2006-08-09 19:34 Mail Delivery Subsystem
2006-04-19 14:02 Mail Delivery Subsystem
2006-03-21 8:00 Mail Delivery Subsystem
2004-04-30 3:33 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=200702051932.UAA13396@SAP \
--to=mailer-daemon@sap.com \
--cc=alsa-devel@alsa.jcu.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.