IMO nobody ever uses + in a username.
If somebody ends up being in this case, he could migrate user data into a new
username without the + prior to the upgrade using
https://james.apache.org/server/manage-webadmin.html#Change_a_username
--
Best regards,
Benoit TELLIER
General manager of
Enhancing MailAddress seems sensible.
I'm somewhat surprised that `+` was allowed previously (I understand that given it was valid address
it was allowed/accepted but still :) ). I'm wondering though, what would be the upgrade path in this
case and how to possibly handle it (and if anyone ever
breaking
> change.Regards,Envoyé depuis mon appareil Galaxy
> Message d'origine De : Wojtek Date :
> 10/10/2023 15:54 (GMT+07:00) À : James Users List
> Objet : Re: Subaddressing (RFC 5233) support
> in James Hi Benoit,thank you for confirming my observation. Ind
to forbid '+' usage
in user names, which should likely be documented in upgrade instructions as a
breaking change.Regards,Envoyé depuis mon appareil Galaxy
Message d'origine De : Wojtek Date : 10/10/2023 15:54 (GMT+07:00) À : James Users List Objet : Re: Subaddressing (RFC
'+' usage in user names, which should likely
be documented in upgrade instructions as a breaking change.Regards,Envoyé
depuis mon appareil Galaxy
Message d'origine De : Wojtek Date :
10/10/2023 15:54 (GMT+07:00) À : James Users List
Objet : Re: Subaddressing (RFC 5233
'+' usage in user names, which should likely
be documented in upgrade instructions as a breaking change.Regards,Envoyé
depuis mon appareil Galaxy
Message d'origine De : Wojtek Date :
10/10/2023 15:54 (GMT+07:00) À : James Users List
Objet : Re: Subaddressing (RFC 5233
Hi Benoit,
thank you for confirming my observation. Indeed, it seems quite extensive.
I was wondering if we shouldn't adjust org.apache.james.core.Username API and make a distinction
between localpart (so username+subaddress) and actuall username (i.e. `username` without subaddress
part. Or
Correct! I've been identifying it for a couple of time and even have ideas of
how to manage it ;-)
That's a bit of a complex story to work with!
As a starter :
- ValidRcptHandler needs to accept sub-addresses of an existing user
- IsLocalRecipient needs to accept sub-addresses of an existing
