| 3 | | Django already uses "recipient" to mean a complete email address, possibly including a friendly display name (e.g., django.core.mail.EmailMessage.all_recipients()). The official RFC 5322 term for the part before the @ is ''local-part'', but other common terms are ''user'' (e.g., existing EmailValidator code), ''username'' (e.g., Python's email.headerregistry.Address.username), or ''mailbox''. I'd maybe go with `validate_username()` and `validate_domain()` to align with Python's email package. |
| | 3 | Django already uses "recipient" to mean a complete email address, possibly including a friendly display name (e.g., django.core.mail.EmailMessage.all_recipients()). The official RFC 5322 term for the part before the @ is ''local-part'', but other common terms are ''user'' (e.g., existing EmailValidator code) or ''username'' (e.g., Python's email.headerregistry.Address.username). I'd maybe go with `validate_username()` and `validate_domain()` to align with Python's email package. |