{rfc.822} This is an old name of rfc822-read-headers. This is kept for the backward compatibility. The new code should use rfc822-read-headers instead. Function: rfc822-header-ref header-list field-name :optional default {rfc.822} An utility procedure to get a specific field from the parsed header list, which is returned by rfc822-read-headers.

Mark is correct, this requirement is intended to indicate that in the EAS case, the user's email address must be in the Principal Name value or the RFC822 Name value of the SAN field of the certificate. In some cases, the UPN is the user's email address but this is not necessarily always the case. 18.11. rfc822 — Parse RFC 2822 mail headers — Python 2.7 A list of tuple string pairs, one per address. In each member, the first is the canonicalized name part, the second is the actual route-address ('@'-separated username-host.domain pair). Footnotes. 1. This module originally conformed to RFC 822, hence the name. Since then, RFC 2822 has been released as an update to RFC 822. RFC822 Problem on Exchange Solutions | Experts Exchange

would get IIS to look for RFC822 Name instead of otherName:Principal Name? BTW, what is "S4U"? Thanks!! Post by Krish Shenoy[MSFT] Is this a Windows Server 2003 domain. If so does the certificate subject name have the correct Distinguished name. If so then IIS will try to do. S4U.

I've been having no luck in generating a CSR with an RFC 822 entry in the SAN portion. From what I've read I should be able to use subjectAltName=RFC822:me@domain.com, others say subjectAltName=RFC822Name:me@domain.com, but neither have been functional. Using openssl with the command(s): MimePart (Java EE 6 ) - Oracle A Header line is a raw RFC822 header-line, containing both the "name" and "value" field. Throws: MessagingException. getMatchingHeaderLines java.util.Enumeration getMatchingHeaderLines(java.lang.String[] names) throws MessagingException Get matching header lines as an Enumeration of Strings.

Useful Background links: SSLHandshakeException: No subject alternative names present; How are SSL certificate server names resolved/Can I add alternative names using keytool?

I've been having no luck in generating a CSR with an RFC 822 entry in the SAN portion. From what I've read I should be able to use subjectAltName=RFC822:me@domain.com, others say subjectAltName=RFC822Name:me@domain.com, but neither have been functional. Using openssl with the command(s): MimePart (Java EE 6 ) - Oracle