headers
Graham Murray | 1 Dec 2004 08:09
Picon

Re: Asynchronous hashcash.el

Magnus Henoch <mange <at> freemail.hu> writes:

> Recommended hooks:
>
> (add-hook 'message-setup-hook 'mail-add-payment-async)
> (add-hook 'message-send-hook 'hashcash-wait-or-cancel)

I have set these hooks, but when composing mail (like this one),
multiple X-Hashcash lines are added as I am composing the message. The
longer I leave the message buffer open the more lines it generates.
Permalink | Reply | 2 comments |
headers
Katsumi Yamaoka | 1 Dec 2004 09:19
X-Face
Favicon
Gravatar

Re: bug in message.el, message-forward-make-body-plain

>>>>> In <yccsm6r9k26.fsf <at> monkeypuzzle.wc.cray.com> Ted Stern wrote:

> message-forward ignores message-forward-ignored-headers when the prefix
> argument is non-nil.

> To demonstrate:  Change the value of message-forward-ignored-headers globally,

[...]

> Now enter any gnus group, and attempt to forward a message using
>     C-u C-c C-f
> Instead of removing all but 4 or 5 relevant headers, nothing is changed.
> The same error occurs with
>     M-4 C-c C-f

I wrote the code for it, and then, I found a note when I was
going to write the ChangeLog file.

2002-07-27  Simon Josefsson  <jas <at> extundo.com>

	* message.el (message-forward-make-body): Don't use
	`message-forward-ignored-headers' when doing a "raw" followup (it
	is important to preserve e.g. CTE).

To forbid removing any headers will be overkill, however
message-forward-ignored-headers contains CTE, such an important
header, even now by default.  I think excluding CTE from m-f-i-h
may not solve the problem.  It is because m-f-i-h is a user
option and users can include any headers in it.  Any ideas?
(Continue reading)

Permalink | Reply | 8 comments |
headers
Uwe Brauer | 1 Dec 2004 11:23
Picon
Favicon

Re: Asynchronous hashcash.el

>>>>> "Graham" == Graham Murray <graham <at> gmurray.org.uk> writes:

    Graham> Magnus Henoch <mange <at> freemail.hu> writes:
    >> Recommended hooks:
    >> 
    >> (add-hook 'message-setup-hook 'mail-add-payment-async)
    >> (add-hook 'message-send-hook 'hashcash-wait-or-cancel)

    Graham> I have set these hooks, but when composing mail (like this one),
    Graham> multiple X-Hashcash lines are added as I am composing the message. The
    Graham> longer I leave the message buffer open the more lines it generates.

I just use 
(add-hook 'message-setup-hook 'mail-add-payment-async)

and have not found any problems so far.

Uwe Brauer
Permalink | Reply | 1 comment |
headers
Simon Josefsson | 1 Dec 2004 14:13

Re: Asynchronous hashcash.el

Uwe Brauer <oub <at> mat.ucm.es> writes:

>>>>>> "Graham" == Graham Murray <graham <at> gmurray.org.uk> writes:
>
>     Graham> Magnus Henoch <mange <at> freemail.hu> writes:
>     >> Recommended hooks:
>     >> 
>     >> (add-hook 'message-setup-hook 'mail-add-payment-async)
>     >> (add-hook 'message-send-hook 'hashcash-wait-or-cancel)
>
>     Graham> I have set these hooks, but when composing mail (like this one),
>     Graham> multiple X-Hashcash lines are added as I am composing the message. The
>     Graham> longer I leave the message buffer open the more lines it generates.
>
>
> I just use 
> (add-hook 'message-setup-hook 'mail-add-payment-async)
>
> and have not found any problems so far.

The simplest setting would be:

(setq message-generate-hashcash t)

It would be nice if the code removed X-hashcash lines for To/CC
recipients that I remove manually.
Permalink | Reply | 0 comments |
headers
Ted Zlatanov | 1 Dec 2004 16:36
X-Face
Favicon
Gravatar

Re: Bug: spam articles not processed

On 30 Nov 2004, tzz <at> lifelogs.com wrote:

> gnus-summary-pop-limit throws an error if there are no limits on the
> stack.
> 
> I could have gone directly to the
> 
> (gnus-summary-limit nil 'pop)
> 
> call that gnus-summary-pop-limit does, but it seemed like a better
> idea to go through the higher-level API.  As I already mentioned, I
> don't know the summary limit functionality so if anyone else thinks
> there's a better way, they are welcome to correct me.

Well, popping the summary limit makes spam.el lose track of ham
messages for me (I have the tick-mark as a ham mark).  Until I figure
out what's happening, I'm disabling the summary limit pop.  Any
suggestions are most welcome.

Ted
Permalink | Reply | 0 comments |
headers
Ted Stern | 1 Dec 2004 20:15
Favicon

Re: bug in message.el, message-forward-make-body-plain

Thank you, Yamaoka-san, for your prompt response!  Comments below.

On 1 Dec 2004 at 00:19 PST, Katsumi Yamaoka wrote:
>>>>>> In <yccsm6r9k26.fsf <at> monkeypuzzle.wc.cray.com> Ted Stern wrote:
>
>> message-forward ignores message-forward-ignored-headers when the prefix
>> argument is non-nil.
>
>> To demonstrate: Change the value of message-forward-ignored-headers globally,
>
> [...]
>
>> Now enter any gnus group, and attempt to forward a message using
>>     C-u C-c C-f
>> Instead of removing all but 4 or 5 relevant headers, nothing is changed.
>> The same error occurs with
>>     M-4 C-c C-f
>
> I wrote the code for it, and then, I found a note when I was
> going to write the ChangeLog file.
>
> 2002-07-27  Simon Josefsson  <jas <at> extundo.com>
>
> 	* message.el (message-forward-make-body): Don't use
> 	`message-forward-ignored-headers' when doing a "raw" followup (it
> 	is important to preserve e.g. CTE).
>
> To forbid removing any headers will be overkill, however
> message-forward-ignored-headers contains CTE, such an important
> header, even now by default.  I think excluding CTE from m-f-i-h
(Continue reading)

Permalink | Reply | 0 comments |
headers
Romain Francoise | 1 Dec 2004 20:48
X-Face
Favicon
Gravatar

Re: bug in message.el, message-forward-make-body-plain

The fix looks simple enough; the problem appears to be in this change:

<URL: http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/lisp/message.el.diff?r1=6.377&r2=6.378>

With the following ChangeLog entry:

2003-10-29  Simon Josefsson  <jas <at> extundo.com>

	* message.el (message-forward-make-body-plain): Remove ignored
	headers.  Tiny patch from Andre Srinivasan <andre <at> e2open.com>.
	(message-forward-make-body-plain): Fix ARG=1.

The test is weird:

(when (and (not current-prefix-arg)
           message-forward-ignored-headers)

how can current-prefix-arg be nil since you call this function from C-u
C-c C-f?  Its value is '(4) here... unless I'm missing something.

Index: message.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/message.el,v
retrieving revision 7.63
diff -u -r7.63 message.el
--- message.el	26 Nov 2004 03:07:29 -0000	7.63
+++ message.el	1 Dec 2004 19:46:41 -0000
 <at>  <at>  -6257,8 +6263,7  <at>  <at> 
        (buffer-string)))
     (setq e (point))
(Continue reading)

Permalink | Reply | 6 comments |
headers
Ted Stern | 1 Dec 2004 22:39
Favicon

Re: bug in message.el, message-forward-make-body-plain

On 1 Dec 2004 at 11:48 PST, Romain Francoise wrote:
> The fix looks simple enough; the problem appears to be in this change:
>
> <URL: http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/lisp/message.el.diff?r1=6.377&r2=6.378>
>
> With the following ChangeLog entry:
>
> 2003-10-29  Simon Josefsson  <jas <at> extundo.com>
>
> 	* message.el (message-forward-make-body-plain): Remove ignored
> 	headers.  Tiny patch from Andre Srinivasan <andre <at> e2open.com>.
> 	(message-forward-make-body-plain): Fix ARG=1.
>
> The test is weird:
>
> (when (and (not current-prefix-arg)
>            message-forward-ignored-headers)
>
> how can current-prefix-arg be nil since you call this function from C-u
> C-c C-f?  Its value is '(4) here... unless I'm missing something.
>
> Index: message.el
> ===================================================================
> RCS file: /usr/local/cvsroot/gnus/lisp/message.el,v
> retrieving revision 7.63
> diff -u -r7.63 message.el
> --- message.el	26 Nov 2004 03:07:29 -0000	7.63
> +++ message.el	1 Dec 2004 19:46:41 -0000
>  <at>  <at>  -6257,8 +6263,7  <at>  <at> 
>         (buffer-string)))
(Continue reading)

Permalink | Reply | 3 comments |
headers
Romain Francoise | 1 Dec 2004 22:56
X-Face
Favicon
Gravatar

Re: bug in message.el, message-forward-make-body-plain

Ted Stern <stern+gnus <at> cray.com> writes:

> This patch works for me, but the offsets are wrong.

Sorry about this, I edited the patch since it mixed with other local
changes I have in message.el; glad to know it solves the problem for
you.  Katsumi, what do you think?

--

-- 
Romain Francoise <romain <at> orebokech.com> | They're nothing but cold
it's a miracle -- http://orebokech.com/ | little demons.
Permalink | Reply | 2 comments |
headers
Simon Josefsson | 1 Dec 2004 23:08

Re: Gnus and sieve

"Jochen Küpper <usenet" <at> jochen-kuepper.de writes:

> I had posted this on gnu.emacs.gnus before but did not get any
> response. If the question is unclear, please let me know what
> additional information might be useful.
>
>
> So far I wrote my sieve script by hand, but now I am trying to put my
> sieve-rules into group parameters. For groups where I have a single
> sender put in it works nicely:
> ,----
> | (sieve address "sender" "someone.somewhere.org")
> `----
>
> However, I could not figure out how to generate rules like the
> following:
> ,----
> | if address :contains "from" ["name <at> one.com", "else@..."] {
> |     fileinto "groupname";
> | }
> `----
> I've tried to put a list, a long string, multiple sieve parameters and
> other such constructs into gnus-parameters.
>
> How does one achieve such behavior?

Try:

(sieve address :contains "from" ("name <at> one.com" "else@..."))
(Continue reading)

Permalink | Reply | 4 comments |

Gmane