From: duplex@mail.danbbs.dk
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Order
Date: Wed, 5 May 2004 01:17:44 -0400 [thread overview]
Message-ID: <20040505051747.9DEA01B54@neuromancer.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 58 bytes --]
Thank you for your request, your details are attached!
[-- Attachment #2.1: Type: text/plain, Size: 373 bytes --]
from postmaster@ethel:
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="details05_9fans.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="details05_9fans.zip"
[-- Attachment #2.2: details05_9fans.zip.suspect --]
[-- Type: application/octet-stream, Size: 29840 bytes --]
reply other threads:[~2004-05-05 5:17 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=20040505051747.9DEA01B54@neuromancer.cse.psu.edu \
--to=duplex@mail.danbbs.dk \
--cc=9fans@cse.psu.edu \
/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).