Okay that would help to confirm if this is a dovecot problem or gsasl problem. You could try increasing the dovecot debug logging during the gsasl test, the generic error in dovecot must be caused by something and understanding what could explain things a bit. Maybe some file ownership/permissions problem or additional GSSAPI flag check that dovecot didn’t do before.
Alas I am traveling without laptop for the next few days so will have no ability to debug anything. /Simon > 29 apr. 2025 kl. 22:33 skrev Noah Meyerhans <no...@debian.org>: > > On Tue, Apr 29, 2025 at 10:22:21PM +0200, Simon Josefsson wrote: >> Thanks for report! Did you confirm that your new dovecot version has >> working GSSAPI support, with some other client? Or is this gsasl >> autopkgtest the only one that test that functionality? > > Gsasl (and libgssglue) tests are the only end-to-end tests currently > exercising the krb5/GSSAPI authentication mechanism, so I haven't > validated GSSAPI functionality at all yet. So that's probably the next > step. I haven't seen any reports of broken GSSAPI on the dovecot > mailing lіsts yet, but that doesn't mean much. > > I'll work on setting up a krb5 environment and will let you know how > things go... > > noah >
