From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Hashcash-generation/check for IDN-domains
Date: Thu, 29 Sep 2005 15:36:30 +0200 [thread overview]
Message-ID: <iluvf0kj8rl.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87y85hcy5s.fsf@koldfront.dk> (Adam =?iso-8859-1?Q?Sj=F8gren'?= =?iso-8859-1?Q?s?= message of "Wed, 28 Sep 2005 11:57:35 +0200")
asjo@koldfront.dk (Adam Sjøgren) writes:
>>> 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).
>
>> What error is that? Does it say "Unknown hashcash format version"?
>> Perhaps the call to hashcash.el should be made in a condition-case.
>
> That is where it failed, in hashcash-version, when I got the message
> about error in nnmail-split-methods.
>
> It's easy to recreate, just put the email in a buffer and run
> mail-check-payment: "Unknown hashcash format version".
Can you test this patch?
2005-09-29 Simon Josefsson <jas@extundo.com>
* spam.el: Load hashcash when compiling, to avoid warnings. Don't
autoload mail-check-payment.
(spam-check-hashcash): Define unconditionally, since hashcash.el
is part of Gnus now. Ignore errors from payment checking.
--- spam.el 27 Sep 2005 16:46:44 +0200 7.75
+++ spam.el 29 Sep 2005 15:34:25 +0200
@@ -42,6 +42,7 @@
(eval-when-compile (require 'cl))
(eval-when-compile (require 'spam-report))
+(eval-when-compile (require 'hashcash))
(require 'gnus-sum)
@@ -2023,18 +2024,10 @@
;;{{{ Hashcash.
-(eval-when-compile
- (autoload 'mail-check-payment "hashcash"))
-
-(condition-case nil
- (progn
- (require 'hashcash)
-
(defun spam-check-hashcash ()
"Check the headers for hashcash payments."
- (mail-check-payment))) ;mail-check-payment returns a boolean
+ (ignore-errors (mail-check-payment))) ;mail-check-payment returns a boolean
- (file-error))
;;}}}
;;{{{ BBDB
next prev parent reply other threads:[~2005-09-29 13:36 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
2005-09-28 9:40 ` Simon Josefsson
2005-09-28 9:57 ` Adam Sjøgren
2005-09-29 13:36 ` Simon Josefsson [this message]
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=iluvf0kj8rl.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).