| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Stephen Bowman wrote:
Second, the email address in each recipient's certificate must match<mailto:email@hidden> does not match email@hidden <mailto:email@hidden>,
the email address in the To:/CC:/BCC: line. In addition, the case
must match for the username portion (i.e., email@hidden
but email@hidden <mailto:email@hidden> *does* match email@hidden
<mailto:email@hidden>). The reason for this is buried deep in
RFC2822. It's annoying, but technically is correct behavior.
Third, *you* are always an unstated recipient of every mail you
send, so the second point applies to your own email address and
certificate as well.
Wouldn't be able to digitally sign if any of this were incorrect, right?
Address matching only applies to your own certificate when sending a signed message. If you can sign, your cert & mail config is fine.
If you can't encrypt, then it's one of the other recipients.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Fed-talk mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/fed-talk/email@hidden This email sent to email@hidden
| References: | |
| >Re: [Fed-Talk] CAC Patch 1.2 help requested (From: Gregory Adair <email@hidden>) | |
| >Re: [Fed-Talk] CAC Patch 1.2 help requested (From: "Timothy J. Miller" <email@hidden>) | |
| >Re: [Fed-Talk] CAC Patch 1.2 help requested (From: "Stephen Bowman" <email@hidden>) | |
| >Re: [Fed-Talk] CAC Patch 1.2 help requested (From: "Timothy J. Miller" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.