[GH-ISSUE #65] Forwarded Email #51

Closed
opened 2026-02-26 10:35:25 +03:00 by kerem · 1 comment
Owner

Originally created by @Benjile on GitHub (Sep 19, 2014).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/65

Hello (french here so sorry for my english i'll do my best),

I'm trying your project on an 2010 Exchange Server.
I had an issue on an incoming mail (from AOL) automatically forwarded to an external contact in GMAIL. The agent correctly signed the email, but gmail tried to authenticate the mail with aol public DKIM key instead of my own public key which is normal.
So in fact the agent should not add a signature in case of a forwarding to preserve the original authentication. I know in DMARC implementation forwarded emails SHOULD be whitelisted and not authenticated but it appears that gmail and others try to do it.

Have you encountered this problem? Any idea on how to fix it?

Thanx

PS: i'm trying to do more researchs

Originally created by @Benjile on GitHub (Sep 19, 2014). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/65 Hello (french here so sorry for my english i'll do my best), I'm trying your project on an 2010 Exchange Server. I had an issue on an incoming mail (from AOL) automatically forwarded to an external contact in GMAIL. The agent correctly signed the email, but gmail tried to authenticate the mail with aol public DKIM key instead of my own public key which is normal. So in fact the agent should not add a signature in case of a forwarding to preserve the original authentication. I know in DMARC implementation forwarded emails SHOULD be whitelisted and not authenticated but it appears that gmail and others try to do it. Have you encountered this problem? Any idea on how to fix it? Thanx PS: i'm trying to do more researchs
kerem closed this issue 2026-02-26 10:35:25 +03:00
Author
Owner

@Benjile commented on GitHub (Sep 19, 2014):

OK you can close this issue. Reading the headers i realized that case of automatic forwarding your agent is not signing, the signature is the aol one, but the body hash did not verify. It seems it is an Exchange problem.

Sorry and thanks again for your project

<!-- gh-comment-id:56233058 --> @Benjile commented on GitHub (Sep 19, 2014): OK you can close this issue. Reading the headers i realized that case of automatic forwarding your agent is not signing, the signature is the aol one, but the body hash did not verify. It seems it is an Exchange problem. Sorry and thanks again for your project
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dkim-exchange-Pro#51
No description provided.