Hi Christoph,

Thanks for your reply. At least I know that it should be supported.

On Tue, 31 Aug 2010 20:52:27 +0200
Christoph Goehre <[email protected]> wrote:
> Type this two lines in a terminal:
> 
>   export NSPR_LOG_MODULES=negotiateauth:5
>   export NSPR_LOG_FILE=/tmp/negotiateauth.log
> 
There are only 6 lines logged:

-1319117968[a9826710]: entering nsAuthGSSAPI::nsAuthGSSAPI()
-1319117968[a9826710]: entering nsAuthGSSAPI::Init()
-1319117968[a9826710]: entering nsAuthGSSAPI::GetNextToken()
-1319117968[a9826710]: gss_init_sec_context() failed: An invalid name
was supplied
Hostname cannot be canonicalized
-1319117968[a9826710]:   leaving nsAuthGSSAPI::GetNextToken
[rv=80004005]


I don't understand why it is complaining about the hostname, and about
which hostname it is complaining. It's probably not the name of the IMAP
server, because I get the same error if I enter the server IP address
instead of the hostname.


Additional info:

aschur...@neminis:~$ hostname -f
neminis.loos.site
aschur...@neminis:~$ host gnome
gnome.loos.site has address 172.22.21.5
aschur...@neminis:~$ host genie
genie.loos.site has address 172.22.21.8
aschur...@neminis:~$ klist
Ticket cache: FILE:/tmp/krb5cc_10000_nwCqP7
Default principal: [email protected]

Valid starting     Expires            Service principal
09/08/10 12:01:49  09/08/10 22:01:49  krbtgt/[email protected]
        renew until 09/09/10 12:01:48
09/08/10 13:42:04  09/08/10 22:01:49  host/gnome.loos.site@
        renew until 09/09/10 12:01:48
09/08/10 13:42:04  09/08/10 22:01:49  host/[email protected]
        renew until 09/09/10 12:01:48



gnome is the IMAP server. /etc/krb5.conf contains:
[realms]
        LOOS.SITE = {
                kdc = genie.loos.site
                kdc = gnome.loos.site
                admin_server = genie.loos.site
        }


So, what's next? I have been trying other mail clients as well: Balsa
works, Claws fails in the same way as TB/ID.


Regards,
Arno




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to