Re: [gnus git] branch master updated: =4= message-goto-body: Really return point ; message-in-body-p: message-goto-body return points ; message: use called-interactively-p ; Revert "message: skip <#secure"

Re: [gnus git] branch master updated: =4= message-goto-body: Really return point ; message-in-body-p: message-goto-body return points ; message: use called-interactively-p ; Revert "message: skip <#secure"

[Lars Magne Ingebrigtsen]

Julien Danjou <julien@danjou.info> writes:

> +  (while (looking-at "^<#secure") (forward-line 1))
> +  (point))

I don't think this belongs here at all.  The user may have inserted all
kinds of MML tags and other stuff, but it still doesn't change the idea
that the body starts where the body starts.  So I think this should be
removed. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: [gnus git] branch master updated: =4= message-goto-body: Really return point ; message-in-body-p: message-goto-body return points ; message: use called-interactively-p ; Revert "message: skip <#secure"

[Julien Danjou]

<#secure method=pgpmime mode=sign>
On Wed, Nov 24 2010, Lars Magne Ingebrigtsen wrote:

> I don't think this belongs here at all.  The user may have inserted all
> kinds of MML tags and other stuff, but it still doesn't change the idea
> that the body starts where the body starts.  So I think this should be
> removed. 

Yep, just saw you were removing it while I was trying to fix it better.

You're the boss here. I just reverted it. :)

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

Re: [gnus git] branch master updated: =4= message-goto-body: Really return point ; message-in-body-p: message-goto-body return points ; message: use called-interactively-p ; Revert "message: skip <#secure"

[Lars Magne Ingebrigtsen]

Julien Danjou <julien@danjou.info> writes:

> You're the boss here. I just reverted it. :)

Thanks.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: [gnus git] branch master updated: =4= message-goto-body: Really return point ; message-in-body-p: message-goto-body return points ; message: use called-interactively-p ; Revert "message: skip <#secure"

[Greg Troxel]

[-- Attachment #1: Type: text/plain, Size: 573 bytes --]


I'm just barely following the "skip <#secure" discussion.  There really
should be some easy way for people to put in a hook to get signed mail,
and it should play well with forwarding, replying with quoting, etc.

I currently have:

      (if (boundp 'conf-gnus-epg)
	  (add-hook
	   'message-setup-hook
	   (lambda ()
	     (message-goto-body)
	     (mml-secure-message-sign-pgpmime))))

which works for 'r' but not 'R' and not 'C-c C-f'.


Also, replying to a message which has been decrypted should force
mml-secure to encrypt, and this should be the default behavior.

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [gnus git] branch master updated: =4= message-goto-body: Really return point ; message-in-body-p: message-goto-body return points ; message: use called-interactively-p ; Revert "message: skip <#secure"

[Dave Goldberg]

> I'm just barely following the "skip <#secure" discussion.  There really
> should be some easy way for people to put in a hook to get signed mail,
> and it should play well with forwarding, replying with quoting, etc.

> I currently have:

>       (if (boundp 'conf-gnus-epg)
> 	  (add-hook
> 	   'message-setup-hook
> 	   (lambda ()
> 	     (message-goto-body)
> 	     (mml-secure-message-sign-pgpmime))))

> which works for 'r' but not 'R' and not 'C-c C-f'.


> Also, replying to a message which has been decrypted should force
> mml-secure to encrypt, and this should be the default behavior.

This addition to gnus-message-setup-hook works (mostly) for me.  It's possibly not portable as is.  I use a custom function in mml-encrypt-alist for smime that maintains a local cache of certs that might affect the condition-case differently than the default.  This ensures that any sort of reply to an encrypted message is also encrypted.  It doesn't work for forwards.  Didn't occur to me to do that.

(add-hook 'gnus-message-setup-hook
	      (lambda ()
		(cond ((and gnus-article-reply
			    (message-with-reply-buffer
			      (re-search-forward
			       "^Content-Type.*application/\\(x-\\)?pkcs7-mime"
			       nil t)))
		       (condition-case nil
			   (mml-secure-message-encrypt-smime)
			 (error
			  (message "One or more recipients do not have certs"))))
		      ((and gnus-article-reply
			    (message-with-reply-buffer
			      (re-search-forward
			       "^Content-Type.*multipart/signed" nil t)))
		       (mml-secure-message-sign-smime)))))

-- 
Dave Goldberg
david.goldberg6@verizon.net