🚀 go-pugleaf

The recent thread about Reply-[tT]o: got me thinking about another
email header.

VM-5.31 puts a Full-Name: header in outgoing messages.  It runs
"user-full-name" to get something useful to put there (see
vm-reply.el). 

Q1.  	Shouldn't users be able to set a variable to control whether a
	Full-Name: header is provided at all?

Q2.	Is user-full-name the right function to use, or should there
	be a similar but vm-specific function, or even better, a
        well-documented vm variable that a user may customize to
        present an appropriate Full-Name: header?  I can elisp my way
        around this, but I don't feel I should have to. :-)  

Q3.	Is Full-Name: really that useful?  Isn't much of what it
	provides doable through the name part of the From: header,
        like "From: user@host.xxx.com (anything I want here)"?
	I'd guess that in following the "be narrow in what you send"
        rule you'd let people write elisp to add Full-Name: themselves
        if they really want it.

Q4.  	(This last question might be better asked of the SuperCite
	mailing list, but I'll ask it here first anyway.)
	Why didn't adding the line about Full-Name: below remove this
        from my SuperCitations?  I had previously been successful in
        adding to mail-yank-ignored-headers to get rid of other rare
        headers from my citations, but Full-Name: still appears in the
        cited text.  

 	   (setq mail-yank-ignored-headers
		 (concat "^Content-Length:\\|"
			 "^Content-Type:\\|"
			 "^Email-Version:\\|"
			 "^End-of-Header:\\|"
			 "^End-of-Protocol:\\|"
			 "^Full-Name:\\|"
			 "^Message-Version:\\|"
			 "^Message-Service:\\|"
			 "^Reply-Path:\\|" 
			 "^Reply-To:\\|" 
			 "^>To:\\|"
			 "^UA-Content-ID:\\|"
			 "^UA-Message-ID:\\|"
			 "^X-at-.*:\\|" mail-yank-ignored-headers))

Finally, we've been at 5.31 for quite a while now.  Kyle, is there a
5.32-beta coming along soon?  
						Jay Borkenhagen