Re: Request: How to PGP/MIME sign by default?

[ShengHuo ZHU <zsh@cs.rochester.edu>]

Jorge Godoy <godoy@conectiva.com> writes:

> Oops! I think I've hit a bug!
> 
> On 14 Nov 2000, godoy@conectiva.com wrote:
> 
> (SNIP)
> 
> > BTW, with the hack you've made to sign messages by default, you you
> > type in the key wrong and want to send the message again ('C-c C-c',
> > by default) you'll get a "multipart sign=pgpmime" before the "part
> > sign=pgpmime" you've just added. Is there any way to prevent that?
> > Maybe changing this part of the function
> > 
> > 	(re-search-forward 
> > 	 "<#\\(/\\)?\\(multipart\\|part\\|external\\|mml\\)." nil t))
> >       (insert "
> > \n")
> >     (insert "
> > \n")))
> > 
> > 
> > to not add a "
> > " if it finds a "<#part
> > sign=pgpmime>" indication... 
> 
> As you could see, the message was signed whenever the "part" or
> "multipart" string was found. Isn't it in any RFC or other place a
> definition that it should be on the beginning of the line, with no
> spaces, or chars before it? If it isn't I'm proposing that this mime
> signing stuff only be used with <multipart> (no # to not trigger
> anything) and <part> in the beginning of the line.

It is MML, not RFC. To send <#part, you should type <#!part; to send
<#!part, type <#!!part.

ShengHuo