ports/93419: bug in ports/mail/mutt-devel 1.5.11

[Dieter Rauschenberger]

>Number:         93419
>Category:       ports
>Synopsis:       bug in ports/mail/mutt-devel 1.5.11
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 16 06:50:03 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Dieter Rauschenberger
>Release:        FreeBSD 6.0-RELEASE-p4 i386
>Organization:
>Environment:
System: FreeBSD a3.d-ra.net 6.0-RELEASE-p4 FreeBSD 6.0-RELEASE-p4 #8: Wed Jan 25 17:17:00 CET 2006 root at a3.d-ra.net:/usr/obj/usr/src/sys/A3 i386
>Description:
	If signing a mail with S/MIME and useing "sign as" the "0" from 
the certificate filename is not included. E.g. the certificates filename
is 37e51234.0 then mutt displays (and tries to open) 'sign as 37e51234.'.
This makes openssl to fail with:

7177:error:02001002:system library:fopen:No such file or directory:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bio/bss_file.c:278:fopen('/home/d-ra/.smime/certificates/37e51234.','r')

If useing the pure 'sign' everything is OK. Then the smime_default_key is correct used!
>How-To-Repeat:
	Every time when useing the 'sign as' feature with S/MIME. 
If this feature was once used, then even the pure 'sign' ist not working any more. One
has to leave mutt (postponeing the message), start mutt again and recall the postponed 
message. Then you can use 'sign' and will be successfull.
>Fix:
	None :-(
>Release-Note:
>Audit-Trail:
>Unformatted: