Bug#527190: mutt: Oh man this sucks.

2009-05-14 Thread Michelle Konzack
Am 2009-05-13 11:09:49, schrieb Robin Lee Powell:
 Warning: Couldn't save certificate
 
 The problem here is that it's already saved the certificate
 successfully, as far as I can tell.  It's somehow deciding that the
 cert it itself saved doesn't match what it's getting from the same
 server.
 
  What mutt version?
 
 Mutt 1.5.18 (2008-05-17)

This sound like a misconfiguration in a folder-hook or something similar
because I have (in the last 12 weeks) installed 14 Lenny Severs and  all
are with mutt.  There is not a singel problem with the  SMTP  engine  in
mutt and of course, I use SSL/TLS to, since otherwise I could not access
my Courier IMAP server.

Do yu use several accounts and use folder-hooks or something similar?
Could you check your config?

I had a similar error, because one time I use vserver1.tamay-dogan.net
and another mail.tamay-dogan.net or mail.private.tamay-dogan.net.

Greetings
Michelle


signature.pgp
Description: Digital signature


Bug#527190: mutt: Oh man this sucks.

2009-05-14 Thread Robin Lee Powell
On Thu, May 14, 2009 at 10:24:49PM +0200, Michelle Konzack wrote:
 Am 2009-05-13 11:09:49, schrieb Robin Lee Powell:
  Warning: Couldn't save certificate
  
  The problem here is that it's already saved the certificate
  successfully, as far as I can tell.  It's somehow deciding that the
  cert it itself saved doesn't match what it's getting from the same
  server.
  
   What mutt version?
  
  Mutt 1.5.18 (2008-05-17)
 
 This sound like a misconfiguration in a folder-hook or something similar
 because I have (in the last 12 weeks) installed 14 Lenny Severs and  all
 are with mutt.  There is not a singel problem with the  SMTP  engine  in
 mutt and of course, I use SSL/TLS to, since otherwise I could not access
 my Courier IMAP server.

For testing purposes, I stripped my .muttrc to only the following:

set folder=imaps://rpow...@engineyard.com@secure.emailsrvr.com/
set spoolfile=imaps://rpow...@engineyard.com@secure.emailsrvr.com/
set certificate_file=~/Mail-ey/certs

Then I deleted ~/Mail-ey/certs

The first time, I accept the cert, and it gets correctly saved to
~/Mail-ey/certs

Every subsequent time, it asks me to accept the cert again, and when
I do it complains that it can't save it.

It's not so much the complaining about not saving; it shouldn't even
be *asking*.  The cert is *right there*.

Did the first poster not include a patch to solve this?  I thought I
saw one.

-Robin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#527190: mutt: Oh man this sucks.

2009-05-14 Thread Y Giridhar Appaji Nag
On 09/05/14 13:51 -0700, Robin Lee Powell said ...
 Did the first poster not include a patch to solve this?  I thought I
 saw one.

No, but I think I'll try and submit one later today or tomorrow.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature


Bug#527190: mutt: Oh man this sucks.

2009-05-13 Thread Robin Lee Powell
Package: mutt
Severity: normal


This is really hard to deal with; I get asked to approve the cert on
every outbound mail, because I'm using the secure smtp stuff.

Any idea when this might be fixed?

-Robin


-- Package-specific info:
Mutt 1.5.18 (2008-05-17)
Copyright (C) 1996-2008 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.6.26.5-dk1 (x86_64)
ncurses: ncurses 5.7.20090404 (compiled with 5.7)
libidn: 1.14 (compiled with 1.14)
hcache backend: GDBM version 1.8.3. 10/15/2002 (built Aug 27 2008 08:41:43)
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
+USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  +USE_GSS  -USE_SSL_OPENSSL  +USE_SSL_GNUTLS  
+USE_SASL  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +COMPRESSED  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
 +HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE  
-ISPELL
SENDMAIL=/usr/sbin/sendmail
MAILPATH=/var/mail
PKGDATADIR=/usr/share/mutt
SYSCONFDIR=/etc
EXECSHELL=/bin/sh
MIXMASTER=mixmaster
To contact the developers, please mail to mutt-...@mutt.org.
To report a bug, please visit http://bugs.mutt.org/.

patch-1.5.13.cd.ifdef.2
patch-1.5.13.cd.purge_message.3.4
patch-1.5.13.nt+ab.xtitles.4
patch-1.5.4.vk.pgp_verbose_mime
patch-1.5.6.dw.maildir-mtime.1
patch-1.5.8.hr.sensible_browser_position.3

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26.5-dk1 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mutt depends on:
ii  libc62.9-4   GNU C Library: Shared libraries
ii  libcomerr2   1.41.3-1common error description library
ii  libgdbm3 1.8.3-4 GNU dbm database routines (runtime
ii  libgnutls26  2.6.4-2 the GNU TLS library - runtime libr
ii  libgssapi-krb5-2 1.6.dfsg.4~beta1-13 MIT Kerberos runtime libraries - k
ii  libidn11 1.14-3  GNU Libidn library, implementation
ii  libk5crypto3 1.6.dfsg.4~beta1-13 MIT Kerberos runtime libraries - C
ii  libkrb5-31.6.dfsg.4~beta1-13 MIT Kerberos runtime libraries
ii  libncursesw5 5.7+20090404-1  shared libraries for terminal hand
ii  libsasl2-2   2.1.22.dfsg1-23+b1  Cyrus SASL - authentication abstra

Versions of packages mutt recommends:
ii  exim4 4.69-9 metapackage to ease Exim MTA (v4) 
ii  exim4-daemon-heavy [mail-tran 4.69-9 Exim MTA (v4) daemon with extended
ii  locales   2.9-4  GNU C Library: National Language (
ii  mime-support  3.44-1 MIME files 'mime.types'  'mailcap

Versions of packages mutt suggests:
ii  aspell  0.60.6-1 GNU Aspell spell-checker
ii  ca-certificates 20081127 Common CA certificates
ii  gnupg   1.4.9-4  GNU privacy guard - a free PGP rep
ii  ispell  3.1.20.0-4.4 International Ispell (an interacti
ii  mixmaster   3.0.0-2  Anonymous remailer client and serv
ii  openssl 0.9.8g-16Secure Socket Layer (SSL) binary a
ii  urlview 0.9-18   Extracts URLs from text

Versions of packages mutt is related to:
ii  mutt 1.5.18-6+b1 text-based mailreader supporting M
pn  mutt-dbg none  (no description available)
pn  mutt-patched none  (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#527190: mutt: Oh man this sucks.

2009-05-13 Thread Justin T Pryzby
retitle 527190 mutt: user annoyance WRT certificate warning
thanks

On Wed, May 13, 2009 at 10:17:30AM -0700, Robin Lee Powell wrote:

 This is really hard to deal with; I get asked to approve the cert on
 every outbound mail, because I'm using the secure smtp stuff.
Do you have ca-certificates installed?  Is it a certificate that
shouldn't need extra help to be verified?  Or is it self-signed and,
if so, why don't you add it to .mutt_certificates?

What mutt version?

Justin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#527190: mutt: Oh man this sucks.

2009-05-13 Thread Robin Lee Powell
On Wed, May 13, 2009 at 10:54:34AM -0700, Justin T Pryzby wrote:
 retitle 527190 mutt: user annoyance WRT certificate warning
 thanks
 
 On Wed, May 13, 2009 at 10:17:30AM -0700, Robin Lee Powell wrote:
 
  This is really hard to deal with; I get asked to approve the cert on
  every outbound mail, because I'm using the secure smtp stuff.

 Do you have ca-certificates installed?  Is it a certificate that
 shouldn't need extra help to be verified?  Or is it self-signed and,
 if so, why don't you add it to .mutt_certificates?

I don't mean to be rude, but you need to read the bug report again.

What happens is:

Mutt says:

-- Mutt: TLS/SSL Certificate check
(r)eject, accept (o)nce, (a)ccept always

I type:

a

Mutt saves the cert into certificate_file 

I repeat: there *is* a cert saved to certificate_file

From then on, every time I do anything that needs a cert:

Mutt says:

-- Mutt: TLS/SSL Certificate check
(r)eject, accept (o)nce, (a)ccept always

I type:

a

Mutt says:

Warning: Couldn't save certificate

The problem here is that it's already saved the certificate
successfully, as far as I can tell.  It's somehow deciding that the
cert it itself saved doesn't match what it's getting from the same
server.

 What mutt version?

Mutt 1.5.18 (2008-05-17)

-Robin

-- 
They say:  The first AIs will be built by the military as weapons.
And I'm  thinking:  Does it even occur to you to try for something
other  than  the default  outcome?  See http://shrunklink.com/cdiz
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org