> Justin Mason wrote:
> >I've been thinking about this. It might be useful to offer a plugin
> >implementing this hashcash, since it'd offer a good way to come up
> >with an unforgeable FORGED_MUA_OUTLOOK rule.
> >However, we'd have to be sure that the CSRI algorithm really is
> >sufficiently open
Justin Mason wrote:
I've been thinking about this. It might be useful to offer a plugin
implementing this hashcash, since it'd offer a good way to come up
with an unforgeable FORGED_MUA_OUTLOOK rule.
However, we'd have to be sure that the CSRI algorithm really is
sufficiently open, and not paten
cumbered, since this *is* MS we're
talking about :(
--j.
Matt Kettler writes:
> mouss wrote:
> > - The x-cr-hashedpuzzle header contains the recipients. There is a
> > serious privacy issue.
> > - the algorithm isn't open. If every company starts adding proprietary
mouss wrote:
- The x-cr-hashedpuzzle header contains the recipients. There is a
serious privacy issue.
- the algorithm isn't open. If every company starts adding proprietary
headers, we will no more have a place for the body.
Followup: I've recently discovered that both of the
> >> http://www.openspf.org/caller-id/csri.pdf Chapter 11, pages 37 to 45
> >> inclusive
On 05.02.08 15:54, [EMAIL PROTECTED] wrote:
> interesting reading :) I believe that, in a time where zombie armies
> powered by quad-core cpus pour spam over the internet, compute-bound
> puzzles would not rea
>>
>> http://www.openspf.org/caller-id/csri.pdf Chapter 11, pages 37 to 45
>> inclusive
>>
interesting reading :)
I believe that, in a time where zombie armies powered by quad-core cpus pour
spam over the
internet, compute-bound puzzles would not really be a hurdle for the spammers
Wolfgang
http://www.openspf.org/caller-id/csri.pdf Chapter 11, pages 37 to 45 inclusive
More new features than ever. Check out the new AOL Mail ! -
http://webmail.aol.com
http://www.openspf.org/caller-id/csri.pdf Chapter 11, pages 37 to 45 inclusive
More new features than ever. Check out the new AOL Mail ! -
http://webmail.aol.com
Matt Kettler wrote:
mouss wrote:
if you can't validate the header, you can't trust it.
And the whole point of the Michael's original message was to find out
if you can validate it, therefore trust it.
A simple "I don't think you can validate that" would have been
appropriate, but suggestin
mouss wrote:
if you can't validate the header, you can't trust it.
And the whole point of the Michael's original message was to find out
if you can validate it, therefore trust it.
A simple "I don't think you can validate that" would have been
appropriate, but suggesting he use it as a bloc
http://www.openspf.org/caller-id/csri.pdf Chapter 11, pages 37 to 45
inclusive
--
View this message in context:
http://www.nabble.com/x-cr-hashedpuzzle-tp15235646p15252629.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
only spoke of the x-cr-mumble headers.
- The x-cr-hashedpuzzle header contains the recipients. There is a
serious privacy issue.
- the algorithm isn't open. If every company starts adding proprietary
headers, we will no more have a place for the body.
- ...
Anyone have any HELPful sugges
Thank you, as always, you have been !extremely helpful.
So, your proposal is to block all email from all modern outlook clients.
Brilliant plan. No, I don't worship MS, but I live in reality.
We should just block anything with the Thread header, X-Mailers with Outlook
in it, any outlook/ exchange
Michael Scheidell wrote:
anyone looked at x-cr-hashedpuzzle?
(its the strange, 'hash cash', 'postage stamp' that Outlook 11+ adds
to emails it thinks might be blocked as spam)
What about a plugin to decode, score, validate it?
What about calculating it on outbound emails?
anyone looked at x-cr-hashedpuzzle?
(its the strange, 'hash cash', 'postage stamp' that Outlook 11+ adds to
emails it thinks might be blocked as spam)
What about a plugin to decode, score, validate it?
What about calculating it on outbound emails?
Would that require a li
15 matches
Mail list logo
