Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS issues #6

Open
slavaaaaaaaaaa opened this issue Jun 10, 2015 · 2 comments
Open

TLS issues #6

slavaaaaaaaaaa opened this issue Jun 10, 2015 · 2 comments

Comments

@slavaaaaaaaaaa
Copy link

I'm trying to get this to work on Gentoo. When built with gnutls useflag, it throws an error: "The TLS connection was non-properly terminated," which really seems to be a gnutls issue (even though it hasn't been mentioned for the current version) I then tried rebuilding mutt with ssl and -gnutls, and now after fetching mail it just errors "Connection to outlook.office365.com closed," followed by "Mailbox closed." I should mention that mutt successfully fetches hearders right before these errors. What am I missing?

net-libs/gnutls
Installed versions: 3.3.15(06:29:38 PM 06/05/2015)(crywrap cxx nls openssl zlib -dane -doc -examples -guile -pkcs11 -static-libs -test)

mail-client/mutt
Installed versions: 1.5.23-r5(07:13:17 AM 06/10/2015)(berkdb crypt debug doc gdbm gpg idn imap kerberos mbox nls nntp pop qdbm sasl sidebar slang smime smtp ssl tokyocabinet -gnutls -selinux

dev-libs/cyrus-sasl
Installed versions: 2.1.26-r9(2)(12:54:25 AM 06/08/2015)(berkdb gdbm pam ssl -authdaemond -java -kerberos -ldapdb -mysql -openldap -postgres -sample -sqlite -srp -static-libs -urandom

@ork
Copy link
Owner

ork commented Jun 11, 2015

Can you run Mutt in debug mode with mutt -d 3 (or a stronger debug level if you don't fear being overwhelmed by logs), then look at ~/.muttdebug0 what can cause this?
Alternatively you can set the environment variable GNUTLS_DEBUG_LEVEL if you feel like gnutls could be a suspect.

I'm experiencing some “Mailbox closed” messages too since the last few weeks, but it only happened after about 20 minutes because of an unreliable connection.

Overall, I feel like Mutt's IMAP code is not ready for the prime time, and maybe integrating with offlineimap could be a solution.

@slavaaaaaaaaaa
Copy link
Author

ork,

Tried debugging both with no good results. Today, however, my coworker and I got it down to these two lines in muttrc:

set imap_check_subscribed="yes"
set imap_list_subscribed="yes"

I don't know about you, but I had quite a few folders I've moved around all over the place.. Looks like that somehow broke things, since I get lines like these in muttdebug:

[2015-06-15 14:55:13] 6< a0034 NO INBOX/Todo doesn't exist.

That folder was moved out of Inbox, so looks like there's still some trace of it. Might want to leave some comments by those two lines saying it breaks for some.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants