Hi Jonathan!
On Fri, Mar 16, 2012 at 10:25:38PM -0500, Jonathan Nieder wrote:
> Darshaka Pathirana wrote:
>
>> Reading imaps://$MYUSERNAME@imap.$MYIMAPSERVER.org/INBOX...
>> Looking up imap.$MYIMAPSERVER.org...
>> Connecting to imap.$MYIMAPSERVER.org...
>> SSL/TLS connection using TLS1.0 (DHE-RSA/AES-128-CBC/SHA1)
>> Connected to imap.$MYIMAPSERVER.org:993 on fd=4
>> 4< * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
>> AUTH=PLAIN] Dovecot ready.
>> imap_authenticate: Using any available method.
>> SASL local ip: 10.0.0.188;58868, remote ip:xxx.yyy.zzz.254;993
>> Error allocating SASL connection
>
> Thanks.
Thank You for your help!
> sasl_client_new() was called like so:
>
> rc = sasl_client_new("imap", "imap.$MYIMAPSERVER.org",
> "10.0.0.188;58868", "xxx.yyy.zzz.2554;993",
> mutt_sasl_get_callbacks(&conn->account), 0, saslconn);
>
> It didn't return SASL_OK. Maybe it returned SASL_NOMECH instead.
Very nice pointer to help debugging the problem:
> - does "ldd /usr/bin/mutt" show it pointing to the right sasl lib?
I already had checked that:
% ldd /usr/bin/mutt | grep sasl
libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007f5174d9e000)
Seemed ok.
> - based on tracing with "ltrace -o /tmp/log mutt", what does
> sasl_client_new actually return?
So this gave me the right track:
,----
| <... sasl_client_init resumed> ) = 0
| getsockname(3, 0x7fff0752dd20, 0x7fff0752de4c, 0, 64) = 0
| getnameinfo(0x7fff0752dd20, 16, "\305\336eO", 1025, "\001", 32, 3) = 0
| snprintf("\001\200\255\373\001", 4964065, "") = 16
| getpeername(3, 0x7fff0752dda0, 0x7fff0752de4c, 0x4bbee1, 0) = 0
| getnameinfo(0x7fff0752dda0, 16, "10.0.0.188", 1025, "", 32, 3) = 0
| snprintf("\001\200\255\373\001", 4964065, "") = 18
| sasl_client_new(0x4b7457, 0x25db690, 0x7fff0752d520, 0x7fff0752d920,
| 0x6dbe20) = 0xffffffff
`----
Although getnameinfo() seems to successfully return with 0. I tried
% hostname
intrepid
and
% hostname -f
hostname: Name or service not known
I then quickly added something like:
127.0.1.1 intrepid.lan intrepid
in my '/etc/hosts' file and tried again:
% hostname -f
intrepid.lan
Then I restarted mutt and was able to read my mails. *yeah* ;)
Just a quick note on my setup here: My machine is in a simple
home-network using a Thomson TG585 v7 as my router and DHCP-Server.
So a few things I am curious about (maybe a bit OT):
- why did fqdn-lookup fail on my setup? (read: what did I do wrong
when installing my system?)
- why does mutt fail so miserably without a fqdn? (read: shouldn't
it give me a better error message?)
- is my workaround ok? (This is a home-network. I can not and do not
want to setup a DNS-Server and also do not want set static IPs).
So thank you very much Jonathan!
But: I am still not sure if this is a bug in the code, the
documentation or a misleading error message. What do you think?
Regards,
- Darsha
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
