From: Cor Gest <cor@clsnet.nl>
Subject: Re: add function to get time from message id's
Date: 10 Aug 2003 02:38:46 +0000 [thread overview]
Message-ID: <87ptjei6dl.fsf@cleopatra.clsnet.nl> (raw)
In-Reply-To: <4nu18qjnz6.fsf@lockgroove.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
> >> < Messages already have a "Date" header. How is this useful?
> >>
> >> Here at FBI Labs, all we have is the suspect's Message-ID.
> >
> >
> > hint,hint,nudge,nuge
> > google ?
> > It would safe the taxpayer some billions.....;-)
>
> Google doesn't archive personal mail... I thought of suggesting
> Google or something like it but Dan really just needs to archive
> messages of interest, not only the Message-IDs. Using the Message-ID
> for any parsing is unreliable at best.
Indeed, if I would be someone with really non-nice mails to sent I
would make sure all-ID's were the same on every mail, and all dates
rewritten to the same date, and ofcourse use 4096-strong-encryption
and anonymousely remailed through at least 5 anonymizing-remailers.
Even spammers use some of those tricks...
And then again, using packet-radio on an HF-frequency would do
the trick nicely too and also much simpler and really untraceable.
A nice side-effect is that the receiving-end nor the sender
have to be "at-any-home" at all ...;-)
cor
--
(setq reply-to (concatenate 'string "Cor Gest "" <cor"'(#\@)"clsnet.nl>"))
500 Years ago the Inca used strings to communicate, computers still do.
next prev parent reply other threads:[~2003-08-10 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 7:50 Dan Jacobson
[not found] ` <87smoaib9n.fsf@cleopatra.clsnet.nl>
2003-08-10 1:33 ` Ted Zlatanov
2003-08-10 2:38 ` Cor Gest [this message]
[not found] <878yq5yvgj.fsf@jidanni.org>
2003-08-08 17:12 ` Ted Zlatanov
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=87ptjei6dl.fsf@cleopatra.clsnet.nl \
--to=cor@clsnet.nl \
/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).