QlarasMay 16, 2025

Tried to sign up for #kick.com to watch a stream independent of #Twitch - they have a #DumbEmailAddressRule - similar to @dumbpasswordrules - limiting an email address to a *max of 35 characters* - I have a normal registration email using + addressing as allowed via #rfc5233 that it tells me to buzz off with.

Guess I'm *not* registering for kick.com.

dmstorkSep 22, 2023
Was writing a mail to my ISP; A few months back I changed my mailadres using + #subaddressing, but that broke the internal system as the logon name didn't support + addressing but did accept it for mail.
Now there was a mismatch [email protected] != [email protected], couldn't check my invoices etc…
Wanted get that fixed, wrote a whole mail explaining #RFC5233. But before sending decided to check it again. And now they do accept + in logon! Should've checked before typing this long mail 🤓
Dervishe the GreySep 1, 2023
Petite question: utilisez-vous la #RFC5233 ([email protected]) dans un contexte professionnel (je veux dire en terme d'utilisateur final pas d'admin de serveur mail) ?
Si oui, sur quel types de cas d'utilisation ?
Merci pour vos réponses :)
RT apprécié
erAckMar 5, 2023

I hate booking forms (and others, but specifically bookings) that don't accept subaddressing (plus-addressing) in email addresses and insist on "you must enter a valid email address". You stupid brain dead web developers! Read and understand that damn RFC 5233!
https://www.rfc-editor.org/rfc/rfc5233

Or if that's too sophisticated for you then at least Wikipedia
https://en.wikipedia.org/wiki/Email_address#Subaddressing

#SubAddressing #PlusAddressing #Email #Forms #stupid #brainDead #Web #Developers #RFC5233

RFC 5233: Sieve Email Filtering: Subaddress Extension