Re: Interest in SASL GSSAPI / Kerberos support?

---=Part.101.b2b590cdfe962348.19f69db5c59.3589b03bfe59f13b=-
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Accept-Language: fr-FR, en-US, vi-VN, ru-RU, ar-TN, it-IT, de-DE, mn-MN
Content-Language: en-US

Hello Quan,

Following the rule of thunb "it's a standard with a RFC" I thi=
nk it makes sense to lend this in James codebase=2E

My personal preference=
 would be as a guice extension jars, in `protocols/sasl-kerberos`
--=C2=A0
=


Best regards,

Benoit TELLIER

General manager of Linagora VIETNAM=2E
Pro=
duct owner for Twake-Mail product=2E
Chairman of the Apache James project=
=2E

Mail: btellier@linagora=2Ecom
Tel: (0033) 6 77 26 04 58 (WhatsApp, Sig=
nal)



On Jul 16, 2026 9:23 AM, from Quan Tran Hong <quan=2Etranhong1999@g=
mail=2Ecom>Hi James community,

For a customer use case, we are considering=
 extending Apache James SASL
support with the GSSAPI mechanism, enabling Ke=
rberos-based authentication
as specified by RFC 4752 <rfc-editor=2Eorg/rfc/=
rfc4752=2Ehtml>=2E

Related Jira ticket: issues=2Eapache=2Eorg/jira/browse/=
JAMES-4215=2E

The intention would be to integrate it with James=E2=80=99s =
existing SASL
infrastructure and make it available to applicable protocols=
=2E

Would the community be interested in receiving and maintaining this
co=
ntribution upstream? If not, we may instead implement and maintain it in
TM=
ail Backend=2E

Regards,
Quan

---=Part.101.b2b590cdfe962348.19f69db5c59.3589b03bfe59f13b=---