Pro / dkim-exchange

DKIM Signing Agent for Microsoft Exchange Server
Other
408 stars 143 forks source link

Dkimsigner on 2 servers #370

Open erachoppe opened 2 years ago

erachoppe commented 2 years ago

Versions

Description

Hi,

If I have two mail servers that work in mirror, do I have to install the plugin on both?

Deckard99 commented 2 years ago

If you mean cluster/DAG by "mirror", than yes you have to install it on both of your servers. you can choose to use one certificate for each server (than you need two DNS entries - selectors) or you use the same certificate on both, than you need just one selector.

Deckard99 commented 2 years ago

BTW: you can't use v3.4 because it dropped Exchange 2010 support. https://github.com/Pro/dkim-exchange/releases/tag/v3.4.0

ePhoenixRNT commented 2 years ago

Hello Deckard99, I am currently setting up a DAG as well and I use the same SSL certificate in both Exchange servers. I copied the "keys" folder after install on the DAG but it fails to load (there is no entry in the Domains window. How could I just use the same keys on both servers? Thank you!

Deckard99 commented 2 years ago

You have to copy the settings file as well. not just the keys

ePhoenixRNT commented 2 years ago

Working now sorry. I had to restart the Transport service.

Great job!

Thank you!

Jose Dubois C : (587) 830-3361

From: Deckard99 @.> Sent: September 30, 2022 7:19 AM To: Pro/dkim-exchange @.> Cc: Jose Dubois @.>; Comment @.> Subject: Re: [Pro/dkim-exchange] Dkimsigner on 2 servers (Issue #370)

You have to copy the settings file as well. not just the keys

— Reply to this email directly, view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/370#issuecomment-1263566302, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3LDQ7D2N6CQG7VZ44RI5FDWA3SE3ANCNFSM53SKPICA. You are receiving this because you commented.Message ID: @.**@.>>

ePhoenixRNT commented 2 years ago

Hi! Thanks. I did, in fact t copied the entire directory content agter installation to be sure but still no domains on the DAG servers.

Sent from my Bell Samsung device over Canada's largest network.

-------- Original message -------- From: Deckard99 @.> Date: 2022-09-30 7:19 a.m. (GMT-07:00) To: Pro/dkim-exchange @.> Cc: Jose Dubois @.>, Comment @.> Subject: Re: [Pro/dkim-exchange] Dkimsigner on 2 servers (Issue #370)

You have to copy the settings file as well. not just the keys

— Reply to this email directly, view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/370#issuecomment-1263566302, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3LDQ7D2N6CQG7VZ44RI5FDWA3SE3ANCNFSM53SKPICA. You are receiving this because you commented.Message ID: @.***>

ericwpl commented 6 months ago

In my case, i got a Exchange CAS server (i.e. CAS01) and two mailbox database server (say it MDB01 and MDB02). I don't know which server i need to install the DKIM? I tried to install it on top of CAS01 and it seems that i stop at the step of "Restarting Exchange Transport Service". If i installed DKIM on both database server, then i need to have two TXT entries in the public DNS record ??

stryqx commented 6 months ago

Howdy,

You'll need to install it on both mailbox servers unless your Send Connector(s) for external mail has been scoped to a specific server. You can either share the same signing key between both mailbox servers or set up a signing key per mailbox server (different selectors for each) which will require two TXT records in public DNS for DKIM verification.

On Mon, 13 May 2024 at 13:23, ericwpl @.***> wrote:

In my case, i got a Exchange CAS server (i.e. CAS01) and two mailbox database server (say it MDB01 and MDB02). I don't know which server i need to install the DKIM? I tried to install it on top of CAS01 and it seems that i stop at the step of "Restarting Exchange Transport Service". If i installed DKIM on both database server, then i need to have two TXT entries in the public DNS record ??

— Reply to this email directly, view it on GitHub https://github.com/Pro/dkim-exchange/issues/370#issuecomment-2106563730, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEHYXKIDJ7K4NAXDVMDBE3ZCAW3DAVCNFSM53SKPICKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJQGY2TMMZXGMYA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Regards, Chris Knight

ericwpl commented 6 months ago

Hi Chris Knight

Thanks for your prompt reply. I had successfully installed it on both mail server and I worked without any problem. Million Thanks !

Regards/Eric

On Tue, May 14, 2024 at 2:23 PM Chris Knight @.***> wrote:

Howdy,

You'll need to install it on both mailbox servers unless your Send Connector(s) for external mail has been scoped to a specific server. You can either share the same signing key between both mailbox servers or set up a signing key per mailbox server (different selectors for each) which will require two TXT records in public DNS for DKIM verification.

On Mon, 13 May 2024 at 13:23, ericwpl @.***> wrote:

In my case, i got a Exchange CAS server (i.e. CAS01) and two mailbox database server (say it MDB01 and MDB02). I don't know which server i need to install the DKIM? I tried to install it on top of CAS01 and it seems that i stop at the step of "Restarting Exchange Transport Service". If i installed DKIM on both database server, then i need to have two TXT entries in the public DNS record ??

— Reply to this email directly, view it on GitHub https://github.com/Pro/dkim-exchange/issues/370#issuecomment-2106563730,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AEEHYXKIDJ7K4NAXDVMDBE3ZCAW3DAVCNFSM53SKPICKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJQGY2TMMZXGMYA>

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Regards, Chris Knight

— Reply to this email directly, view it on GitHub https://github.com/Pro/dkim-exchange/issues/370#issuecomment-2109377544, or unsubscribe https://github.com/notifications/unsubscribe-auth/A54IMZXLZ3VGYEURD6TJOVDZCGUUVAVCNFSM53SKPICKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJQHEZTONZVGQ2A . You are receiving this because you commented.Message ID: @.***>