From: SMART_Calgary_SMTP_Gateway@smarttech.com
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Content violation
Date: Wed, 5 May 2004 02:12:34 +0000 (UTC)
Date: Tue May 4 19:11:01 2004 [thread overview]
Message-ID: <E1BLBrG-0007e6-L9@sc8-sf-mx2.sourceforge.net> (raw)
Content violation found in email message.
From: linux-fbdev-devel@lists.sourceforge.net
To: gordpeters@smarttech.com
File(s): aboutyou.rtf.scr
Matching filename: *.scr
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next reply other threads:[~2004-05-05 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 2:12 SMART_Calgary_SMTP_Gateway [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 2:23 Content violation SMART_Calgary_SMTP_Gateway
2003-08-22 16:33 postmaster
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=E1BLBrG-0007e6-L9@sc8-sf-mx2.sourceforge.net \
--to=smart_calgary_smtp_gateway@smarttech.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 NNTP newsgroup(s).