Changes between Initial Version and Version 2 of Ticket #401


Ignore:
Timestamp:
10/05/09 07:25:40 (15 years ago)
Author:
broder
Comment:

I tried several times and was unable to reproduce the service ticket acquisition failure when I tried actually sitting in front of an office head, so I don't know what was going on.

I did find the necessary frob to enable SASL. I committed the change in r24049 and uploaded it to proposed. It seems to work, but more testing would be appreciated.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #401

    • Property Status changed from new to proposed
    • Property Component changed from -- to mail

  • Ticket #401 – Description

    initial v2  
    1 There are two issues with the thunderbird-config currently in -proposed. 
    2  
    3 First, we need to figure out what configuration option corresponds to the "Use SASL^WSecure Authentication" check mark. 
    4  
    5 The other one is more bizarre. When a user doesn't have an imap/poNN.mail.mit.edu service ticket, Thunderbird appears to not-quite-deterministically fail to acquire the service ticket, resulting in a mysterious error that the server "doesn't support" secure authentication. If you try again enough times, eventually Thunderbird will acquire the service ticket and connect successfully. 
    6  
    7 For what it's worth, running `kvno imap/poNN.mail.mit.edu` before starting Thunderbird eliminates that error. That is obviously not the way to fix the problem, though. 
     1We need to figure out what configuration option corresponds to the "Use SASL!^WSecure Authentication" check mark.