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: (...) 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. Handling CAPABILITY IMAP queue drained imap_authenticate: Using any available method. 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 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. Anmeldung gescheitert... mutt_num_postponed: using old IMAP postponed count. mutt_index_menu[633]: Got op -1 mutt_index_menu[633]: Got op -1 (...) I'm afraid it's a mutt-related problem, for e.g. Sylpheed works just fine (using STARTTLS as well). The line "STARTTLS unavailable" in the above output seems a bit strange to me, as Sylpheed works with STARTTLS and even setting "ssl_starttls=no" in mutt doesn't change anything. Best regards, J. Prendick
