Chris Knight

-UseWebLogin needs an additional parameter to allow the use of explicit credentials, rather than using the stored credentials associated with the logged on user account. The workaround is to run...

@erik0686 I'm a sysadmin pressed for time, mostly because of poorly implemented, poorly documented Microsoft systems :-) I read the Synopsis, Syntax and Examples - Description rarely has anything useful,...

Howdy, The problem with this configuration is that DKIM signing is done before any of the other Transport Agents get to look at the message and potentially modify it, which...

Good to hear. I'd suggest comparing your Transport Agent priority with a clean install of Exchange Server 2016 CU13 without any third party software installed to see what the order...

Howdy, Might be worth installing the App Compatibility FOD and see if that works for you. More info here - https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19 If it doesn't work I can confirm that installing...

What canonicalization is in use: relaxed or simple? My guess is that simple is configured and you're getting failures due to a mail server in the delivery path modifying the...

Howdy, Just checked my Exchange Server 2019 CU11 install running DKIM 3.4.0. Exchange DkimSigner transport agent has the lowest priority with no other transport agents installed other than the default...

Hello, I provided a fix for the Open and Save dialogs to work on Windows Server Core installs, but this won't be available until the next pre-release is available. The...

You install + configure dkim-exchange on the servers you have configured as Source Servers for the Send Connector(s) you're using for outbound mail and want DKIM signed. To find the...

Howdy, Might be worth checking the TNEF conversion settings on the Exchange Server. https://learn.microsoft.com/en-us/exchange/mail-flow/content-conversion/tnef-conversion?view=exchserver-2019#tnef-conversion-options-for-remote-domains On Tue, 6 Dec 2022 at 08:54, Jacob Dixon ***@***.***> wrote: > @stryqx @johnjore > @Alagbalive4eva...