Cannot (a)ccept always ssl certificate

2013-03-16 Thread David Woodfall

When I connect to my IMAPS server on LAN which has a certificate for
FDQ I get the message that certificate doesn't match domain name,
since I'm connecting to 192.168.1.2

I keep pressing 'a' to accept always, and it says it saves it, but it
doesn't and I must keep accepting every time I log in.

Am I missing something?




Mutt sets adjacent messages to N when a new one arrives (or something does)

2013-03-16 Thread Chris Green
If I'm reading messages in a mailbox when a new one arrives then the one
I am reading always seems to get set back to N when I stop reading it
and go back to the list of messages.

This has only started happning recently.  I have been playing about with
some of the settings in my muttrc recently but I can't see anything
directly relevant. (I had changed mail_check_recent and mark_old but
they're back at the defaults now)

Does anyone have any idea what might be wrong?

-- 
Chris Green


Re: Cannot (a)ccept always ssl certificate

2013-03-16 Thread David Woodfall

On (16/03/13 10:20), David Woodfall  put forth the 
proposition:

When I connect to my IMAPS server on LAN which has a certificate for
FDQ I get the message that certificate doesn't match domain name,
since I'm connecting to 192.168.1.2

I keep pressing 'a' to accept always, and it says it saves it, but it
doesn't and I must keep accepting every time I log in.

Am I missing something?


Correction, it _does_ save it in .mutt_certificates _but_ it still
presents me with a prompt as if it hasn't.

Any way of turning off verify?



Re: Cannot (a)ccept always ssl certificate

2013-03-16 Thread David Woodfall

On (16/03/13 10:39), David Woodfall  put forth the 
proposition:

On (16/03/13 10:20), David Woodfall  put forth the 
proposition:

When I connect to my IMAPS server on LAN which has a certificate for
FDQ I get the message that certificate doesn't match domain name,
since I'm connecting to 192.168.1.2

I keep pressing 'a' to accept always, and it says it saves it, but it
doesn't and I must keep accepting every time I log in.

Am I missing something?


Correction, it _does_ save it in .mutt_certificates _but_ it still
presents me with a prompt as if it hasn't.

Any way of turning off verify?


Ok from
http://superuser.com/questions/387064/mutt-will-not-let-me-save-an-ssl-certificate

set ssl_verify_host = no
set ssl_verify_dates = no




Re: Cannot (a)ccept always ssl certificate

2013-03-16 Thread James Griffin
[- Sat 16.Mar'13 at 10:39:17 +  David Woodfall :-]

> On (16/03/13 10:20), David Woodfall  put forth the 
> proposition:
> >When I connect to my IMAPS server on LAN which has a certificate for
> >FDQ I get the message that certificate doesn't match domain name,
> >since I'm connecting to 192.168.1.2
> >
> >I keep pressing 'a' to accept always, and it says it saves it, but it
> >doesn't and I must keep accepting every time I log in.
> >
> >Am I missing something?
> 
> Correction, it _does_ save it in .mutt_certificates _but_ it still
> presents me with a prompt as if it hasn't.
> 
> Any way of turning off verify?

I remember having this issue. It's because when you created the
certificate for your server, you used the Common Name (CN) as the FQDN
of the server, e.g: hostname.domain.tld. So, when you specify the local
address as 192.168.1.2, or if you used localhost, as another example,
that doesn't match the CN that was used in the certificate. If you put
the fqdn in the url for $folder, then it will accept it.

There is a setting in the openssl.cf file you can use so this doesn't
happen but I forget what it is now.

-- 
James Griffin:  jmz at kontrol.kode5.net 
jmzgriffin at gmail.com

A4B9 E875 A18C 6E11 F46D  B788 BEE6 1251 1D31 DC38


Re: Why sign every message? (was Re: Sending attachments without crypt_autosign

2013-03-16 Thread Kevin J. McCarthy
Florian Lohoff wrote:
> I my wet dreams i' encrypting every single message. But mutt is not very
> helpful in this. Yes - it can encrypt but i'd like mutt to decide
> automatically when it's capable of encrypting the mail (remember
> multiple To:, Cc:, Bcc). It would be okay to encrypt a mail if i have a
> key for all recipients. 

I've just sent a (6 part) patch to mutt-dev that implements this.  If
you're up for it, I'd appreciate people trying it out and providing
feedback.

http://marc.info/?l=mutt-dev&m=136340705622283&w=2

-Kevin



signature.asc
Description: Digital signature