According to the RFC 5321 protocol, the local part can be sensitive to the scrap, depending on the messaging provider. However, the majority of them accept the use of capital letters. This means that if you write: contact@captainverify.com or CONtact@Captainverify.com, your message should, in most cases, arrive safely.
According to the RFC 5321 protocol, the local part can be sensitive to the scrap, depending on the messaging provider. However, the majority of them accept the use of capital letters. This means that if you write: contact@captainverify.com or CONtact@Captainverify.com, your message should, in most cases, arrive safely.
https://captainverify.com/blog/email-case-sensitive.html
https://datatracker.ietf.org/doc/html/rfc5321
https://stackoverflow.com/questions/9807909/are-email-addresses-case-sensitive
The part after the
@
aka the DOMAIN part should not be treated as different emailsaka, if
beniceyu@example.com
exist, i should not be able to add inberniceyu@EXAMPLE.COM
As a recruiter, this may mean candidates may try to apply multiple times under the same email.