From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: [9fans] you couldn't make it up
Date: Thu, 26 Feb 2004 16:18:05 +0000 [thread overview]
Message-ID: <5c141d86573387434a99f82b813d1d8a@juice.thebigchoice.com> (raw)
Microsoft has released a draft specification for Caller-ID for email, 'to addre
ss the widespread problem of domain spoofing' - the concept is similar to SPF, but is using XML.
http://www.microsoft.com/mscorp/twc/privacy/spam_callerid.mspx
hehe is this like calculating a hash to use CPU time !
m
reply other threads:[~2004-02-26 16:18 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=5c141d86573387434a99f82b813d1d8a@juice.thebigchoice.com \
--to=matt@proweb.co.uk \
--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).