Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: hashcash
Date: 6 Oct 2004 11:17:12 -0400	[thread overview]
Message-ID: <4n4ql7c1vr.fsf@lifelogs.com> (raw)
In-Reply-To: <ilu8yamjmwp.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 04 Oct 2004 21:36:38 +0200")

On Mon, 04 Oct 2004, jas@extundo.com wrote:

> "Ted Zlatanov" <tzz@lifelogs.com> writes:
> 
>> After using hashcash on systems with and without the hashcash binary,
>> I think the sending error (when hashcash is missing) should be changed
>> to a warning and sit-for 1.
> 
> But why did you enable hashcash generation, if you don't have the
> binary?  If you are using the same .emacs on several systems, some
> with a hashcash binary, and some without, it seems the proper .emacs
> setting would be:
> 
> (setq message-generate-hashcash (executable-find "hashcash"))

How about:

(defcustom message-generate-hashcash (executable-find "hashcash")
  "*Whether to generate X-Hashcash: headers.
You must have the \"hashcash\" binary installed, see `hashcash-path'."
  :group 'message-headers
  :link '(custom-manual "(message)Mail Headers")
  :type 'boolean)

(it's nil by default now)

But then what if users don't want to generate it?  I'm not sure what's
the right way to proceed.  Maybe there should be these extra
possibilities: (shorter names will probably be needed)

- enable-when-hashcash-binary-in-path
- enable-when-hashcash-binary-in-path-and-fast-machine [but how do we
  know this?]
- ask-to-enable-when-hashcash-binary-in-path [default?]

It seems like we should encourage hashcash generation in order to make
Gnus mail less likely to be tagged as spam - I see this as a service
to the users.  On the other hand it will slow down an already slow
process (sending mail, which often does extra network I/O anyway).

>> The user can't override the error otherwise to send mail, and has to
>> manually set hashcash-path to nil.
> 
> I'm not sure I agree with this view.  It seems the user already
> overrode the default behavior when she request hashcash in the first
> place.  So she could revert to the default behavior by disabling it:
> 
> M-x set-variable RET message-generate-hashcash RET nil RET

My particular problem was that I was doing it the old way with a hook
so I had to remove-hook :) I think you are right, generally speaking,
I was just blinded by my experience.

Ted



  parent reply	other threads:[~2004-10-06 15:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 15:30 hashcash Adam Sjøgren
2004-09-26 17:36 ` hashcash Simon Josefsson
2004-09-26 20:59   ` hashcash Adam Sjøgren
2004-09-27  2:03     ` hashcash Paul Foley
2004-09-27 14:32       ` hashcash Simon Josefsson
2004-09-27 14:46         ` hashcash Adam Sjøgren
2004-09-29 14:37         ` hashcash Dan Christensen
2004-09-29 14:40           ` hashcash Ted Zlatanov
2004-09-29 19:11             ` hashcash Dan Christensen
2004-09-29 21:08               ` hashcash Magnus Henoch
2004-09-30 14:30                 ` hashcash Ted Zlatanov
2004-09-30 20:42                   ` hashcash Magnus Henoch
2004-09-27 14:45       ` hashcash Adam Sjøgren
2004-09-27 15:21         ` hashcash Simon Josefsson
2004-09-27 15:38           ` hashcash Adam Sjøgren
2004-09-27 17:13             ` hashcash Jesper Harder
2004-09-27 19:02               ` hashcash Adam Sjøgren
2004-09-27 19:38                 ` hashcash Simon Josefsson
2004-09-27 19:54                   ` hashcash Adam Sjøgren
2004-09-27 19:56                   ` hashcash Jesper Harder
2004-09-27 20:50                     ` hashcash Simon Josefsson
2004-09-28 14:08         ` hashcash Ted Zlatanov
2004-09-28 14:49           ` hashcash Simon Josefsson
2004-09-28 17:41             ` hashcash Ted Zlatanov
2004-09-30 20:50               ` hashcash Simon Josefsson
2004-10-04 17:06                 ` hashcash Ted Zlatanov
2004-10-04 19:36                   ` hashcash Simon Josefsson
2004-10-05  2:34                     ` hashcash Dan Christensen
2004-10-06 15:17                     ` Ted Zlatanov [this message]
2004-09-27 16:10 ` hashcash Ted Zlatanov
  -- strict thread matches above, loose matches on Subject: below --
2002-07-31 19:24 new spam functionality added Ted Zlatanov
2002-07-31 20:14 ` Simon Josefsson
2002-07-31 20:25   ` Josh Huber
2002-07-31 20:34     ` Scott A Crosby
2002-07-31 20:41       ` Josh Huber
2002-07-31 21:07         ` Scott A Crosby
2002-08-02  2:05           ` Jason R. Mastaler
2002-08-02  3:43             ` Russ Allbery
2002-08-02  4:29               ` Jason R. Mastaler
2002-08-02  4:34                 ` Russ Allbery
2002-08-02 16:17                   ` TMDA (was: new spam functionality added) Paul Jarc
2002-08-05 17:38                     ` Per Abrahamsen
2002-08-05 17:49                       ` Paul Jarc
2002-08-05 17:57                         ` Simon Josefsson
2002-08-05 20:18                           ` David Masterson
2002-08-05 20:46                             ` Stainless Steel Rat
2002-08-06  3:04                               ` David Masterson
2002-08-06 14:27                                 ` Stainless Steel Rat
2002-08-06 17:13                                   ` David Masterson
2002-08-06 17:26                                     ` David Masterson
2002-08-06 18:08                                       ` Stainless Steel Rat
2002-08-07 12:02                                         ` Lloyd Zusman
2002-12-30  0:22                                           ` Hashcash (was: TMDA) Lars Magne Ingebrigtsen
2003-01-02 18:33                                             ` Hashcash Simon Josefsson
2003-01-02 19:25                                               ` Hashcash Lars Magne Ingebrigtsen
2003-01-02 21:01                                                 ` Hashcash Simon Josefsson
2003-01-02 21:05                                                   ` Hashcash Lars Magne Ingebrigtsen

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=4n4ql7c1vr.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).