31.x pop account gets mail on startup, and then stops getting new mail. Fails with authentication via Kerberos, plain text auth works
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
People
(Reporter: actapenko, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted, Whiteboard: [regression:TB38?])
Updated•10 years ago
|
Updated•10 years ago
|
Comment 1•10 years ago
|
||
Comment 3•10 years ago
|
||
Updated•10 years ago
|
Comment 10•10 years ago
|
||
Comment 11•9 years ago
|
||
| Reporter | ||
Comment 12•9 years ago
|
||
Comment 13•9 years ago
|
||
| Reporter | ||
Comment 14•9 years ago
|
||
Updated•8 years ago
|
Comment 15•6 years ago
|
||
Other issues - https://mzl.la/2UTVeGl
Comment 16•5 years ago
|
||
Максим, do you still encounter this issue when using newer versions ?
| Reporter | ||
Comment 17•5 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #16)
Максим, do you still encounter this issue when using newer versions ?
Hello,
Still not working. Testing on version 68.0.1.7177.
Comment 19•5 years ago
|
||
I posted this over on bug 1383635 too:
I have no accounts that use Kerberos / GSSAPI so don't have a way to try this. Can anyone suggest a free email account that uses this or maybe provide me with a temporary test account using Kerberos/GSSAPI?
Comment 21•5 years ago
|
||
Gene, IIRC you have dovecot set up for testing? It looks like it's fairly easy to set up Kerberos too for it: https://wiki.dovecot.org/Authentication/Kerberos
Comment 22•5 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #21)
Gene, IIRC you have dovecot set up for testing? It looks like it's fairly easy to set up Kerberos too for it: https://wiki.dovecot.org/Authentication/Kerberos
Well hoping for a lazy/easy way to to test this but just doing it locally is probably the only way with Kerberos. Have kerberos daemons set up and now trying to get dovecot to authenticate via it.
Just realized this bug is for pop. I don't have dovecot setup to do POP, just imap. :(
Comment 23•5 years ago
|
||
Kerberos is operational and tried to run tb daily trunk with Security: None, Auth: Kerberos/GSSAPI and tb crashes (MOZ_ASSERT) at obj-x86_64-pc-linux-gnu/dist/include/mozilla/ServoUtils.h:33. Don't know why. No attempt to send authentication to dovecot even occurs since it crashes immediately after the imap greeting is received.
But when I run 68.7 release it doesn't crash. I see tb send a "ticket" to dovecot to attempt an authentication but dovecot says AUTHENTICATION FAILED in the response so no luck yet. I probably don't have something setup right on the dovecot server.
| Reporter | ||
Comment 24•5 years ago
|
||
Hi,
Tested on Thunderbird 68.7.0 32 and 64 bits and everything works great. Bug fixed!
Thank you!
Comment 25•5 years ago
|
||
After a lot of trial and error, I finally got kerberos/gssapi to work with tb imap and dovecot. I was planning on next trying it with pop3 but haven't got to it yet. Now you say it works ok with 68.7.0 with pop3? But it didn't work with 68.0.1.7177. Looking at Wayne's search in comment 15 and modification on it to include gssapi, I don't see anything mentioned that would affect this bug. So no idea how this could have got fixed...?
| Reporter | ||
Comment 26•5 years ago
|
||
Hi,
I do not understand too. But I tried on Windows 10 and Windows 7 client Thunderbird 68.7.0 32bit and 64bit fresh install in domain and while everything works. I’ll observe a couple of weeks. But it starts to work if you do a clean installation.
Comment 27•5 years ago
|
||
(In reply to Максим from comment #26)
Hi,
I do not understand too. But I tried on Windows 10 and Windows 7 client Thunderbird 68.7.0 32bit and 64bit fresh install in domain and while everything works. I’ll observe a couple of weeks. But it starts to work if you do a clean installation.
By "clean install" I assume you mean you also are using a new profile and not reusing the old profile?
| Reporter | ||
Comment 28•5 years ago
|
||
(In reply to gene smith from comment #27)
(In reply to Максим from comment #26)
Hi,
I do not understand too. But I tried on Windows 10 and Windows 7 client Thunderbird 68.7.0 32bit and 64bit fresh install in domain and while everything works. I’ll observe a couple of weeks. But it starts to work if you do a clean installation.By "clean install" I assume you mean you also are using a new profile and not reusing the old profile?
"Сlean install" implies uninstall old version, before delete safe mail box user, delete folder Thunderbird en route:
c:\Users"user"\AppData\Local\Thunderbird
c:\Users"user"\AppData\Roaming\Thunderbird
After that install latest version and everything works as it should.
If you update an already installed version, then nothing works as it did not work before. I don’t know why, but only "clean install" works.
Comment 29•5 years ago
|
||
Unfortunately i don't doesn't have Kerberos/GSSAPI anymore, so can't share test account.
Comment 31•4 years ago
•
|
||
Wayne found a POP3/STARTTLS/Kerberos-GSSAPI server at aegee.org. Testing this on that server, I see no problem. New messages are fetched on a timed interval (a.k.a., biff) properly. So I'm closing this bug as a duplicate of Bug 511832 which is marked "Works for me". I'm not sure if that bug was ever actually tested as WFM, but I have now so it's OK to say that.
Note: As pointed out in comment 26 to comment 28 above, it may be necessary to do a clean install to fix the problem. I'm not clear as to what the reporter is saying to do in comment 28, but I tested with a self-built daily with a recently created default profile and just added the aegee.org POP3 account in the usual way (although I did have to manually configure the non-standard POP3 port in account manager and specify Kerberos/gssapi authentication).
One other issue probably requiring a separate bug report: I still had the same problem with some MOZ_ASSERTS as mentioned in comment 23 above and further described in duplicate bug 1383635 comment 12.
Comment 32•4 years ago
|
||
The problem is maybe that the ticket has expired during pop3 refresh (e.g. because it was not renewable).
Comment 33•4 years ago
|
||
If for IMAP-refresh a persistent connection is used, that does not re-authenticate (on refresh), but for POP3 on refresh a new connection is used, and the Kerberos ticket is destroyed just before the refresh, the IMAP will work (as no reauthentication over the existing TCP connection is performed), while POP3 will fail (as it tries to reauthenticate).
Comment 34•4 years ago
|
||
(In reply to Дилян Палаузов from comment #33)
If for IMAP-refresh a persistent connection is used, that does not re-authenticate (on refresh), but for POP3 on refresh a new connection is used, and the Kerberos ticket is destroyed just before the refresh, the IMAP will work (as no reauthentication over the existing TCP connection is performed), while POP3 will fail (as it tries to reauthenticate).
I tested it with your POP3 server and it seemed to work for me. Are you saying it doesn't? Or maybe you are saying there is only a problem with POP3 after the kbr ticket expires?
Comment 35•4 years ago
|
||
Or maybe you are saying there is only a problem with POP3 after the kbr ticket expires?
Exactly, this might be the reason why the problem appears only under POP3 but not on IMAP4. (IMAP4 uses persistent connection, while POP3 does not - this is a guess, not a statement).
Description
•