On Fr, 09 Okt 15:23, Brendan Cully wrote: > On Friday, 09 October 2009 at 23:42, J. Prendick wrote: > > On Fri, 09 Oct 12:07, Brendan Cully wrote: > > > On Friday, 09 October 2009 at 20:36, J. Prendick wrote: > > > > Hello all, > > > > > > > > Since a few days I've got a problem with my Arcor mail-account. I can't > > > > connect anymore and mutt keeps telling me "A TLS packet with unexpected > > > > length was received.". I didn't change my mutt-setup nor the > > > > mutt-version > > > > (which by the way is "Mutt 1.5.18 (2008-05-17)"). > > > > > > > > A 'mutt -d 5' delivers: > > > > > > I'm assuming the word wrap was added later. > > > > > > > Thats true, sorry. > > > > > > (...) > > > > mutt_index_menu[633]: Got op 99 > > > > Connected to imap.arcor.de:993 on fd=4 > > > > imap_cmd_step: grew buffer to 512 bytes > > > > 4< * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE > > > > THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION > > > > STARTTLS] Courier-IMAP ready. Copyright 1998-2008 Double Precision, > > > > Inc. See COPYING for distribution information. > > > > > > Ok, STARTTLS is available. > > > > > > > Handling CAPABILITY > > > > IMAP queue drained > > > > imap_authenticate: Using any available method. > > > > > > But mutt hasn't tried to use it. Either it misparsed the capability > > > string or an option is unset. Have you double-checked that > > > ssl_starttls is NOT "no"? Make sure your setting isn't being clobbered > > > by a folder or account hook either. > > > > > > > I use the exact same account-~ and folder-hook for all my mailboxes: > > > > account-hook 'imaps://imap.arcor.de/' 'set imap_user=xxx imap_pass=yyy' > > folder-hook 'imaps://imap.arcor.de' 'set folder=imaps://imap.arcor.de > > record=imaps://imap.arcor.de/inbox/SentMail from="aaa <b...@arcor.de>" > > ssl_starttls=yes smtp_url="smtps://b...@mail.arcor.de" smtp_pass="yyy" > > pgp_sign_as="ABCDEFG" spoolfile=imaps://imap.arcor.de/inbox > > postponed=+INBOX.Drafts copy=yes' > > > > Shouldn't be a problem, should it? Every mailbox except for the one at > > Arcor works fine. > > That looks fine. I'd move ssl_starttls into account-hook though. It's > probably worth setting it once outside of the hook, too. >
Actually I've set ssl_starttls=yes additionally outside the hooks already. > > > > SASL local ip: 192.168.42.3;48768, remote ip:151.189.21.114;993 > > > > External SSF: 192 > > > > External authentication name: HTp > > > > SASL: No worthy mechs found > > > > imap_auth_sasl: IMAP4rev1 UIDPLUS CHILDREN NAMESPACE > > > > THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION > > > > STARTTLS unavailable > > > > > > This confusing message isn't actually saying mutt thinks STARTTLS is > > > unavailable, it's a debug message from the auth layer saying it can't > > > find any AUTH methods in the capability string. > > > > > > > 4> a0000 LOGIN "xxx" "yyy" > > > > tls_socket_read (A TLS packet with unexpected length was received.) > > > > imap_cmd_step: Error reading server response. > > > > mutt_socket_close: Attempt to close closed connection. > > > > > > The server hung up on you after mutt issued the LOGIN command, > > > presumably because it only allows LOGIN after TLS. > > > > Furthermore, I use the same mutt-configuration on my working-notebook > > (Debian stable) and my desktop at home (Debian testing) - on both I > > experience the same behavior of mutt since a few days. > > Probably you've never used TLS at all, but recently your server was > changed to not allow LOGIN without TLS. Just to be sure - could you have a look at another debug-output of another mailbox of mine: (...) mutt_index_menu[633]: Got op 99 Connected to mx.freenet.de:993 on fd=4 imap_cmd_step: grew buffer to 512 bytes 4< * OK IMAP ready. IMAP queue drained 4> a0000 CAPABILITY 4< * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 QUOTA STARTTLS Handling CAPABILITY 4< a0000 OK CAPABILITY completed IMAP queue drained imap_authenticate: Using any available method. SASL local ip: 192.168.42.3;54636, remote ip:195.4.92.9;993 External SSF: 128 External authentication name: 4> a0001 AUTHENTICATE CRAM-MD5 4< + PEY3MzIxQTNDQjk3N0Q5OTlBNkQ4Qzg2MjQxMThENEIyQG14LmZyZWVuZXQuZGU+ mutt_sasl_cb_authname: getting authname for mx.freenet.de:993 mutt_sasl_cb_pass: getting password for x...@mx.freenet.de:993 4> sifejiaslief8asfjsefafejsef9asfjase9fsjfasfjase9fajsefNhMQ== 4< a0001 OK AUTHENTICATE Ok. IMAP queue drained SASL protection strength: 0 SASL protection buffer size: 65536 Communication encrypted at 128 bits 4> a0002 CAPABILITY a0003 LIST "" "" 4< * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 QUOTA Handling CAPABILITY 4< a0002 OK CAPABILITY completed. 4< * LIST (\Noselect) "." "" Root delimiter: . 4< a0003 OK LIST completed IMAP queue drained 4> a0004 STATUS "INBOX.INBOX.drafts" (MESSAGES) (...) That doesn't say anything about using starttls, too - though while logging in mutt tells me, it's using STARTTLSv1. At least it seems to be encrypted in some way ;) (think I have to have a closer look at this whole encryption-thing at opportunity...). Best regards, J. Prendick
