Character Type: Alphanumeric and special characters
Field Type: Text
Field Length Min : Max: 6 : 256
System Display
Display PDB emails as they are stored in PDB (no uppercasing or lowercasing).
Display edited/entered emails as edited/entered in CCR (no uppercasing or lowercasing).
Send emails as provided in transactions to states (no uppercasing or lowercasing).
For CCR to consider an email address valid it:
Must contain 6 to 256 characters (minimum A@B.CE)
Must have the @ sign
Must have a period in a position after the @ sign
Must have at least one character before and 4 characters after the @ sign
Must end with a top-level domain (“.com”, “.org”, “.net”, etc.) (See additional information at bottom of page)
Valid email examples:
jdough@ABC.com
janedough@gmail.com
Jdough12@Ernest.net
jane.dough@ABC.com
jsmith@company.info
P.Smith@JBA.net
john.smith1@somewhere.com
Notes:
The most common cause of failure is misspelling.
A valid format does not guarantee that the email is correct.
An invalid format ‘may’ be a legitimate email address. However, CCR will not be able to accept and transmit an email that does not meet the CCR requirements rendering it valid. In order to assure the greatest quality data, NIPR will follow the specification RFC2822.
CCR invalid email addresses:
Do not have @ sign. Example: jdoughABC.com
Have more than 1 @ sign. Example: jdough@testco@division.com.
Use angle brackets. Example: “Bob Smith” <bob.smith@example.com>, you should only enter bob.smith@example.com.
Use domain literals. Example: bob.smith@[192.168.1.100] will not be accepted. Use the domain name instead. (See additional information at bottom of page)
Have two or more consecutive periods. Example: bob..smith@example..com will not be accepted.
Contain double-quotes or spaces. Example: “Bob Smith”@example.com will not be accepted.
Email addresses that begin or end with period. Example, jdough@ABC.com.
Have more than 64 characters before the “@” symbol.
Contain comments to header fields by putting the comment inside normal parentheses:
jkorpeland@cc.hut.fi (Jukka Korpeland)
Additional information:
CCR generally supports specification RFC2822, with a few additional restrictions. (Internet Message Format http://tools.ietf.org/html/rfc2822)
Email segments. Every email address has three parts.
Local Mailbox Part (Before the '@') (Case sensitive)
Domain Name (What follows the '@') (not case sensitive)
The email address ReCipiENt@eXaMPle.cOm is different from recipient@example.com but it the same as ReCipiENt@example.com.
Domain Name The email domain (NIPR.com) must match the requirements of the host name.
Top Level Domain is a domain name in the Domain Name System that is a direct subdomain of the DNS root zone. The official list is maintained by the Internet Assigned Numbers Authority (IANA)
Domain Literal or “address literal” uses the destination system’s IP address enclosed by square brackets in the domain part, as an alternative to a domain name. This is often associated with spam messages.