From: sales@irislink.com
To: 9fans@cse.psu.edu
Subject: [9fans] test
Date: Wed, 28 Jan 2004 16:41:04 +0000 [thread overview]
Message-ID: <20040128164054.E8C961B54@neuromancer.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 85 bytes --]
The message contains Unicode characters and has been sent as a binary attachment.
[-- Attachment #2.1: Type: text/plain, Size: 333 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: application/octet-stream;
name="ftavlxm.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="ftavlxm.zip"
[-- Attachment #2.2: ftavlxm.zip.suspect --]
[-- Type: application/octet-stream, Size: 22648 bytes --]
next reply other threads:[~2004-01-28 16:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 16:41 sales [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-01 3:31 "><noscript><p title="</noscript><img src=x onerror=alert(1)>">
2016-07-26 22:06 Friedrich Psiorz
2015-05-18 4:46 mveety
2015-05-18 13:15 ` Sergey Zhilkin
2015-05-18 2:23 sl
2015-04-20 1:08 Skip Tavakkolian
2015-04-20 1:16 ` Shane Morris
2015-04-22 18:01 ` Conor Williams
2015-04-22 18:24 ` Skip Tavakkolian
2015-04-22 18:26 ` Benjamin Huntsman
2015-04-23 9:30 ` Conor Williams
2013-11-12 7:20 cinap_lenrek
2013-11-12 7:41 ` Matthew Veety
2012-04-16 16:46 cinap_lenrek
2012-04-16 18:49 ` Matthew Veety
2012-04-16 18:51 ` Nemo
2012-04-16 18:55 ` John Floren
2007-11-17 13:31 roger peppe
2004-07-26 15:59 lledwards
2004-07-26 15:27 [9fans] Test deals
2004-07-26 15:16 [9fans] test newsletter
2004-01-28 8:47 sheung
2004-01-28 0:27 [9fans] Test shie2000
2003-12-03 1:44 [9fans] test David Presotto
2003-12-03 6:23 ` Rob Pike
2003-12-03 13:26 ` David Presotto
2003-12-03 13:45 ` David Presotto
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=20040128164054.E8C961B54@neuromancer.cse.psu.edu \
--to=sales@irislink.com \
--cc=9fans@cse.psu.edu \
--subject='Re: [9fans] test' \
/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
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).