From: <MMEX_SA_DESPERADO@ateng.com>
To: <gdb-patches@sources.redhat.com>
Subject: MailMonitor for Exchange has processed a suspicious mail
Date: Thu, 18 Jul 2002 13:55:00 -0000 [thread overview]
Message-ID: <000501c22e9d$81baee90$7a01a8c0@ateng.com> (raw)
Message-ID: <20020718135500.ccQelJRGneuycM0IMSSm5hsCSt6hVLvICwoWSrYHFmE@z> (raw)
A mail addressed to you has been identified as suspicious by MailMonitor for Exchange.
Event: infection
Action: Message quarantined
Message ID: < 200207182055.g6IKt1Ug036462@sithdroid.ns1.com.br >
Message subject: NGapShowElement(elmID)
Sender: "porna" <porna@email.si>
=============================================================
Attachment information:
Event: infection
Action: Unable to disinfect
Filename: src.bat
Virus: W32/Klez-G
=============================================================
next reply other threads:[~2002-07-18 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 14:16 MMEX_SA_DESPERADO [this message]
2002-07-18 13:55 ` MMEX_SA_DESPERADO
2004-06-28 3:57 MailMonitor
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='000501c22e9d$81baee90$7a01a8c0@ateng.com' \
--to=mmex_sa_desperado@ateng.com \
--cc=gdb-patches@sources.redhat.com \
/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