From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: Hashcash-generation/check for IDN-domains
Date: Tue, 27 Sep 2005 17:54:49 +0200 [thread overview]
Message-ID: <87slvqfquu.fsf@koldfront.dk> (raw)
In-Reply-To: <iluy85ilf7m.fsf@latte.josefsson.org>
On Tue, 27 Sep 2005 17:09:49 +0200, Simon wrote:
> The X-hashcash header sent appeared to contain the non-ASCII
> characters, which I believe is wrong. So it is the generation that is
> faulty. Since, if I recall correctly, it copy the content from
> To/From/Cc, it probably should do its own IDN-processing. I'm not
> sure how that would interfact with answering 'n' at the query you
> refer to though. Perhaps that query is simply wrong? It doesn't make
> sense to send mail to non-ASCII domains ever, does it?
That depends on whether the MTA that Gnus talks to understands IDN and
can convert itself, right?
But I guess IDN is meant to be handled at the MUA level, and not by
the MTAs?
If that is correct, I don't know why the user is even asked. Perhaps
the author of that piece of code can explain?
> So Gnus should attempt to translate non-ASCII to xn--* via libidn,
> or refuse to send the message. Then the hashcash code could also
> unconditionally perform idn-encoding. Not sure what should happen if
> idn-encoding inside the hashcash cookie generation fail though.
> Leave the X-hashcash as-is, with non-ASCII characters? Or remove the
> header?
If the user really shouldn't be asked (above), it's easy (always
idn-encode in hashcash.el).
I think it sounds reasonable that if hashcash.el fails to generate a
payment, the header should not be added?
The checking does seem a little too fragile though, in that spam-split
breaks just because hashcash.el can't understand a Hashcash-header
(i.e. the mail-check-payment should just return false when the header
is not understandable, right? Instead of the error that makes nnmail
think that my fancy-split configuration is invalid).
> When we knew some more answers to these questions, I can try to
> implement them...
Great O:-)
Best regards,
--
"Mr. Cotton's... parrot. Same question." Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2005-09-27 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 13:23 Adam Sjøgren
2005-09-27 14:29 ` Other IDN-fixes (was: Hashcash-generation/check for IDN-domains) Arne Jørgensen
2005-09-27 15:14 ` Other IDN-fixes Simon Josefsson
2005-09-27 15:09 ` Hashcash-generation/check for IDN-domains Simon Josefsson
2005-09-27 15:31 ` Arne Jørgensen
2005-09-27 15:54 ` Adam Sjøgren [this message]
2005-09-28 9:40 ` Simon Josefsson
2005-09-28 9:57 ` Adam Sjøgren
2005-09-29 13:36 ` Simon Josefsson
2005-09-29 14:35 ` Adam Sjøgren
2005-09-30 0:19 ` Simon Josefsson
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=87slvqfquu.fsf@koldfront.dk \
--to=asjo@koldfront.dk \
/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).