From: Eric & Welsh Associates <bar.erics@info.org>, "X-EsetResult:clean"@nefty
To: insight@sources.redhat.com
Subject: Re: NOTIFICATION OF BEQUEST
Date: Tue, 29 Jun 2010 14:37:00 -0000 [thread overview]
Message-ID: <20100629143542.0D02C19CAE7@nefty.hu> (raw)
Reply-To: bar.erics@rediffmail.com
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: 8bit
Message-Id: <20100629143342.BDB3E19D63C@nefty.hu>
Date: Tue, 29 Jun 2010 16:33:25 +0200 (CEST)
<html>
<head>
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>New Page 1</title>
</head>
<body>
<p>Attention:<br>
On behalf of the Trustees and Executor of the estate of Late Mr.Edwin Gabriel.I
wish to notify you that late Mr.Edwin Gabriel made you a beneficiary to his
WILL.Do contact me for further details regarding your inheritance.<br>
Barr Eric Sipho.</p>
</body>
</html>
__________ Information from ESET Mail Security, version of virus signature database 5237 (20100629) __________
The message was checked by ESET Mail Security.
http://www.eset.com
reply other threads:[~2010-06-29 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100629143542.0D02C19CAE7@nefty.hu \
--to=bar.erics@info.org \
--cc="X-EsetResult:clean"@nefty \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).