public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: mark@mcselec.com
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Can you please verify#1fsAkl1apS8g50EZYBVUzpstVFiPpbGv
Date: Mon, 01 May 2006 05:25:00 -0000	[thread overview]
Message-ID: <E1FaQq7-0005uw-EA@vps.mcselec.com> (raw)

The message you sent requires that you verify that you 
are a real live human being and not a spam source.

I understand that it is not convenient but the large amount of spam we receive forced us to use this protection. Simple reply to this email and you are verfied. 

Leave the subject line intact.

The headers of the message sent from your address are show below:

From ecos-discuss@sources.redhat.com Mon May 01 01:20:55 2006
Received: from albertsm by vps.mcselec.com with local-bsmtp (Exim 4.52)
 id 1FaQq6-0005um-Oq
 for mark@mcselec.com; Mon, 01 May 2006 01:20:55 -0400
Received: from localhost by vps.mcselec.com
	with SpamAssassin (version 3.1.0);
	Mon, 01 May 2006 01:20:55 -0400
From: ecos-discuss@sources.redhat.com
To: mark@mcselec.com
Subject: Good day
Date: Mon, 1 May 2006 10:54:50 +0530
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on vps.mcselec.com
X-Spam-Level: **********
X-Spam-Status: Yes, score=10.6 required=5.0 tests=BAYES_50,MISSING_MIMEOLE,
	NO_REAL_NAME,PRIORITY_NO_NAME,RCVD_IN_SORBS_WEB,RCVD_IN_XBL 
	autolearn=no version=3.1.0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_44559AB7.E69DEBCF"
Message-Id: <E1FaQq6-0005um-Oq@vps.mcselec.com>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-05-01  5:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  5:25 mark [this message]
2006-05-01 23:06 ` Lars Poeschel

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=E1FaQq7-0005uw-EA@vps.mcselec.com \
    --to=mark@mcselec.com \
    --cc=ecos-discuss@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).