DKIM

Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#21
use the part before your domain name
the first screenshot is correct - the zone is @ the the spf record.
it's autodiscover CNAME then the microsoft server name


for the dkim, you'll use this much as the CNAME:
CNAME: selector1._domainkey
Points to: selector1-yourdomain-com._domainkey.tenantname.onmicrosoft.com


CNAME: selector2._domainkey
Points to: selector2-yourdomain-com._domainkey.tenantname.onmicrosoft.com
 

CWM030

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#22
use the part before your domain name
the first screenshot is correct - the zone is @ the the spf record.
it's autodiscover CNAME then the microsoft server name

===============================================
On the autodiscover part I am confused?
What did I do wrong?
 
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#24
On the autodiscover part I am confused?
What did I do wrong?
no, the autodiscover record is correct - both of those records are correct. I just wasn't speaking clearly. Not enough coffee in me at the time. :)
 
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#25
Ok - the two selector records look correct. Do the headers of test messages indicate it is correct?
 

CWM030

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#26
no, the autodiscover record is correct - both of those records are correct. I just wasn't speaking clearly. Not enough coffee in me at the time. :)
no, the autodiscover record is correct - both of those records are correct. I just wasn't speaking clearly. Not enough coffee in me at the time. :)


HAHAHAHA... I know that feeling!


I think so.....

Authentication-Results: spf=pass (sender IP is 104.47.33.137)
smtp.mailfrom=CWM030.COM; msn.com; dkim=pass (signature was verified)
header.d=CWM030COM.onmicrosoft.com;msn.com; dmarc=bestguesspass action=none
header.from=CWM030.COM;
Received-SPF: Pass (protection.outlook.com: domain of CWM030.COM designates
104.47.33.137 as permitted sender) receiver=protection.outlook.com;

client-ip=104.47.33.137; helo=NAM01-BN3-obe.outbound.protection.outlook.com;
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (104.47.33.137)
by BY2NAM03FT034.mail.protection.outlook.com (10.152.84.211) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.715.13 via
Frontend Transport; Sun, 29 Apr 2018 17:46:52 +0000
X-IncomingTopHeaderMarker: OriginalChecksum:C4E8A41C5C042BD5D93FD652EF1884DDAEFAC670B05A6BEAD1292961E59B64D8;UpperCasedChecksum:8552851D4E89CC2C5B78B1FF4A508460BFDF70A1215438454CDA7AF330B0BAB6;SizeAsReceived:5216;Count:39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 

CWM030

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#29
I've NEVER had so much problems setting up my email..... Than I have with OFFICE 365


Untitled.png
 

CWM030

Senior Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#30
I've set the key up ......... So why is OL365 not seeing them!?

I'll give it an hour and try it again

Untitled.png


untitled2.png
 

trillyuk

New Member
Outlook version
Outlook 2016 32 bit
Email Account
Office 365 Exchange
#33
We setup DKIM and DMARC a few months ago and found this tool very useful to setup and more importantly monitor DMARC/DKIM/SPF. Only cost a few dollars a month and a lot cheaper and I think better than MXToolBox who we started out with.
DMARC Analyzer - Trusted Email. Delivered.
 
Thread starter Similar threads Forum Replies Date
T Exchange Server Questions 7
L Exchange Server Questions 1

Similar threads

Top