Daniele Zelli
asked on
Not able to send mails from Office 365 (from a new domain)
Not able to send mails from Office 365 (from a new domain)
I have a hybrid environment, Exchange 2010 on-perm with Office 365. I have close to 10 domain with office 365, all of them can send mail perfectly, no problem
But from this new domain, When i am trying to send mail i am getting the below error
Error ------
Original Message Details
Created Date: 14/11/2018 11:23:27 PM
Sender Address: customer.care@payasyougo.c o.nz
Recipient Address: preethesh@gmail.com
Subject: TEST7
Error Details
Reported error: 550 5.7.1 Unable to relay
DSN generated by: SYXPR01MB0702.ausprd01.pro d.outlook. com
Remote server: webmail.punz.co.nz
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 14/11/2018
11:23:27 PM SYXPR01MB1469.ausprd01.pro d.outlook. com SYXPR01MB1469.ausprd01.pro d.outlook. com mapi *
2 14/11/2018
11:23:27 PM SYXPR01MB1469.ausprd01.pro d.outlook. com SYXPR01MB0702.ausprd01.pro d.outlook. com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_ AES_256_GC M_SHA384) *
Original Message Headers
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=PulseEnergyLtd.onmicroso ft.com; s=selector1-PulseEnergyLtd -onmicroso ft-com;
h=From:Date:Subject:Messag e-ID:Conte nt-Type:MI ME-Version :X-MS-Exch ange-Sende rADCheck;
bh=1pw2g1aWmb7qobaPmjAGFMb 5dAgx0f5J/ mZuLja1yQk =;
b=3D2xI9zgtIYehytYIZL7HMBf wC6TdeBC6a Mh7PyI/b75 d3AdCLB4/G L9/dcfTxjm SdzLBx+cRQ lkg8Ne8gZi j2YimHw9/8 g6qw7zKkH1 y0h+D3S7iv H70/LHfui4 qdqH8JxqAi 45yb3JPzar tioJPH5nZO bx/iBTfyzM x0NfVi0=
Received: from SYXPR01MB1469.ausprd01.pro d.outlook. com (10.171.38.11) by
SYXPR01MB0702.ausprd01.pro d.outlook. com (10.169.176.19) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_ AES_256_GC M_SHA384) id
15.20.1294.27; Wed, 14 Nov 2018 23:23:27 +0000
Received: from SYXPR01MB1469.ausprd01.pro d.outlook. com
([fe80::f0c8:d45a:3749:7b4 e]) by SYXPR01MB1469.ausprd01.pro d.outlook. com
([fe80::f0c8:d45a:3749:7b4 e%12]) with mapi id 15.20.1294.045; Wed, 14 Nov
2018 23:23:27 +0000
From: Customer Care PayAsYouGo <customer.care@payasyougo. co.nz>
To: "preethesh@gmail.com" <preethesh@gmail.com>
Subject: TEST7
Thread-Topic: TEST7
Thread-Index: AdR8cKohTuYPdCDXRICn5Ypb4v vHwA==
Date: Wed, 14 Nov 2018 23:23:27 +0000
Message-ID: <SYXPR01MB14699E858188F85E ABAED37CB0 C30@SYXPR0 1MB1469.au sprd01.pro d.outlook. com>
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=customer.car e@payasyou go.co.nz;
x-ms-exchange-messagesentr epresentin gtype: 1
x-originating-ip: [202.180.82.77]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagn ostics: 1;SYXPR01MB0702;20:KvGwJIB NKInEOckXr cAbcnkWpi1 CdOczM5fBP BCpWHkDhiJ ghNzyeLkF1 A1DLjpR33v tJYTTYiHB0 OBYuJZ5hYm 01XvMrfmP+ 0O2SGLarKb MQ9FPeBoH3 KD9d8PJ+au jniTDKlqDB ILV5mcdfpZ iomX/JMf6R +KJJ3aQd/M 5S18=
x-ms-office365-filtering-c orrelation -id: 6b3584cd-be21-4696-1c6c-08 d64a882e90
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(239009 8)(7020095 )(4652040) (8989299)( 4534185)(4 627221)(20 1703031133 081)(20170 2281549075 )(8990200) (5600074)( 711020)(20 1705260332 8)(7153060 )(7193020) ;SRVR:SYXP R01MB0702;
x-ms-traffictypediagnostic : SYXPR01MB0702:
x-microsoft-antispam-prvs: <SYXPR01MB070207325FA092BF E19D209ACC C30@SYXPR0 1MB0702.au sprd01.pro d.outlook. com>
x-exchange-antispam-report -test: UriScan:(21748063052155)(2 8532068793 085)(19050 1279198761 )(22761206 6756510);
x-ms-exchange-senderadchec k: 1
x-exchange-antispam-report -cfa-test: BCL:0;PCL:0;RULEID:(604052 2)(2401047 )(81215010 46)(500500 6)(1020150 1046)(3002 001)(32314 15)(944501 410)(52105 112)(93006 095)(93001 095)(14801 6)(149066) (150057)(6 041310)(20 1611235640 45)(201611 23560045)( 2016112355 8120)(2017 0313142309 5)(2017022 81528075)( 2016112355 5045)(2017 0306142107 5)(2017030 61406153)( 2016112356 2045)(2017 0807174201 1)(7699051 )(76991095 );SRVR:SYX PR01MB0702 ;BCL:0;PCL :0;RULEID: ;SRVR:SYXP R01MB0702;
x-forefront-prvs: 085634EFF4
x-forefront-antispam-repor t: SFV:NSPM;SFS:(10019020)(36 6004)(3460 02)(376002 )(396003)( 3985040000 4)(136003) (189003)(1 99004)(486 006)(25010 03)(316002 )(6116002) (790700001 )(3846002) (97736004) (711904000 01)(712004 00001)(136 1003)(1063 56001)(257 86009)(773 6002)(2906 002)(47600 3)(1445400 4)(1055860 02)(235100 1)(3906040 0002)(4270 600006)(18 6003)(1411 001)(66066 001)(86362 001)(74316 002)(74482 002)(55016 002)(55808 4003)(6916 009)(99286 004)(25600 4)(7696005 )(47860000 1)(5393600 2)(2900100 001)(17307 00003)(811 56014)(811 66006)(867 6002)(8936 002)(54896 002)(63060 02)(643600 2)(6506007 )(68736007 )(33656002 )(10283600 4)(5640700 003)(71160 03)(566030 0001)(2600 5)(9686003 );DIR:OUT; SFP:1102;S CL:1;SRVR: SYXPR01MB0 702;H:SYXP R01MB1469. ausprd01.p rod.outloo k.com;FPR: ;SPF:None; LANG:en;PT R:InfoNoRe cords;MX:3 ;A:1;
received-spf: None (protection.outlook.com: payasyougo.co.nz does not
designate permitted sender hosts)
x-microsoft-antispam-messa ge-info: 0Q4mC/kuiXfv93PAEivyR6L5AK dGluZNyRhz MwsNAfIYjA rD5YtXUB9A CMIDMOS+0m w6tKDTkIcx s8IB4jGISW ip/MMX4g3S MeZk4N0Fam WlEAwKzNrX +lcEBzmsdU TP6BC8qtqw ZQ+DUJNOK+ PwlsfjTit0 N1dsKFUdBP w0GWTd/lAD qmiMwv2FdT JdCTMX0dp+ xKtp37dgV6 0ucwwfMk9u y634dKfMS2 n79/1fZ0i5 dDJTafYSjE r2NtpBjY4h TftMyfMHf+ 9eTsuUiXdx ++t+oXCOZY on2qQ/1Wai GdpjbMNGvj h+hCu3Xds9 zHZSF6AUPY XdodVgTTCc n9nsu5gQbh gmDYzbNLA0 KjFI7rw=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary="_000_SYXPR01MB14 699E858188 F85EABAED3 7CB0C30SYX PR01MB1469 ausp_"
MIME-Version: 1.0
X-OriginatorOrg: payasyougo.co.nz
X-MS-Exchange-CrossTenant- Network-Me ssage-Id: 6b3584cd-be21-4696-1c6c-08 d64a882e90
X-MS-Exchange-CrossTenant- originalar rivaltime: 14 Nov 2018 23:23:27.5376
(UTC)
X-MS-Exchange-CrossTenant- fromentity header: Hosted
X-MS-Exchange-CrossTenant- id: 98125cad-14d9-4e5b-b948-05 14c26ef764
X-MS-Exchange-Transport-Cr ossTenantH eadersStam ped: SYXPR01MB0702
Have configured the SPF as per all other domain, need help to identify the issue, thanks in advance
I have a hybrid environment, Exchange 2010 on-perm with Office 365. I have close to 10 domain with office 365, all of them can send mail perfectly, no problem
But from this new domain, When i am trying to send mail i am getting the below error
Error ------
Original Message Details
Created Date: 14/11/2018 11:23:27 PM
Sender Address: customer.care@payasyougo.c
Recipient Address: preethesh@gmail.com
Subject: TEST7
Error Details
Reported error: 550 5.7.1 Unable to relay
DSN generated by: SYXPR01MB0702.ausprd01.pro
Remote server: webmail.punz.co.nz
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 14/11/2018
11:23:27 PM SYXPR01MB1469.ausprd01.pro
2 14/11/2018
11:23:27 PM SYXPR01MB1469.ausprd01.pro
Original Message Headers
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=PulseEnergyLtd.onmicroso
h=From:Date:Subject:Messag
bh=1pw2g1aWmb7qobaPmjAGFMb
b=3D2xI9zgtIYehytYIZL7HMBf
Received: from SYXPR01MB1469.ausprd01.pro
SYXPR01MB0702.ausprd01.pro
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
15.20.1294.27; Wed, 14 Nov 2018 23:23:27 +0000
Received: from SYXPR01MB1469.ausprd01.pro
([fe80::f0c8:d45a:3749:7b4
([fe80::f0c8:d45a:3749:7b4
2018 23:23:27 +0000
From: Customer Care PayAsYouGo <customer.care@payasyougo.
To: "preethesh@gmail.com" <preethesh@gmail.com>
Subject: TEST7
Thread-Topic: TEST7
Thread-Index: AdR8cKohTuYPdCDXRICn5Ypb4v
Date: Wed, 14 Nov 2018 23:23:27 +0000
Message-ID: <SYXPR01MB14699E858188F85E
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=customer.car
x-ms-exchange-messagesentr
x-originating-ip: [202.180.82.77]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagn
x-ms-office365-filtering-c
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(239009
x-ms-traffictypediagnostic
x-microsoft-antispam-prvs:
x-exchange-antispam-report
x-ms-exchange-senderadchec
x-exchange-antispam-report
x-forefront-prvs: 085634EFF4
x-forefront-antispam-repor
received-spf: None (protection.outlook.com: payasyougo.co.nz does not
designate permitted sender hosts)
x-microsoft-antispam-messa
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary="_000_SYXPR01MB14
MIME-Version: 1.0
X-OriginatorOrg: payasyougo.co.nz
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
(UTC)
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-Transport-Cr
Have configured the SPF as per all other domain, need help to identify the issue, thanks in advance
ASKER
yes i am sending from the email address from the new domain.
You are getting a relaying error. Can you ask your ISP Support why this error would occur if you are not relaying.
ASKER
as mentioned i have another 10 domain, configured the same way and all of them can send mail without any issues.
Is your domain name a problem in some way? There are many email send/receive issues, but relaying means that the email is seen to come from a source that is not native.
Is the new domain related to one of the other domains?
Have you asked your ISP?
Is the new domain related to one of the other domains?
Have you asked your ISP?
From: Customer Care PayAsYouGo <customer.care@payasyougo. co.nz>
To: "preethesh@gmail.com" <preethesh@gmail.com>
Remote server: webmail.punz.co.nz
Where does punz.co.nz email server come into play here?
To: "preethesh@gmail.com" <preethesh@gmail.com>
Remote server: webmail.punz.co.nz
Where does punz.co.nz email server come into play here?
make sure the domain is an accepted Authoritative domain I. your o365 environment.
ASKER
How can I make my domain as a authoritative domain on o365 ?
first you need to add the domain to o365 and verify it. Dee link below for help if you havent do e that yet.
https://docs.microsoft.com/en-us/office365/admin/setup/add-domain?view=o365-worldwide
once done you can now manage that domain as and accepted authoritative domain. see below link for assistance with that:
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/manage-accepted-domains/manage-accepted-domains
https://docs.microsoft.com/en-us/office365/admin/setup/add-domain?view=o365-worldwide
once done you can now manage that domain as and accepted authoritative domain. see below link for assistance with that:
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/manage-accepted-domains/manage-accepted-domains
ASKER
hi David, "webmail.punz.co.nz" is my on-perm exchange FQDN that will be provided for HELO.
ASKER
hi timgreen, the new domain is under Accepted domains and has a value "Authoritative Domain" both on-perm and o365.
Please review the information below: This explains the error, and let us know if this seems to be the issue:
5.7.1 Unable to relay The sending email system is not allowed to send a message to an email system where that email system is not the final destination of the message. This error occurs when the sending email system tries to send an anonymous message to a receiving email system, and the receiving email system does not accept messages for the domain or domains specified in one or more of the recipients. The following are the most common reasons for this error:
• A third party tries to use a receiving email system to send spam, and the receiving email system rejects the attempt. By the nature of spam, the sender's email address might have been forged, and the resulting NDR could have been sent to the unsuspecting sender's email address. It is difficult to avoid this situation.
• An MX record for a domain points to a receiving email system where that domain is not accepted. The administrator responsible for the specific domain name must correct the MX record or configure the receiving email system to accept messages sent to that domain, or both.
• A sending email system or client that should use the receiving email system to relay messages does not have the correct permissions to do this.
5.7.1 Unable to relay The sending email system is not allowed to send a message to an email system where that email system is not the final destination of the message. This error occurs when the sending email system tries to send an anonymous message to a receiving email system, and the receiving email system does not accept messages for the domain or domains specified in one or more of the recipients. The following are the most common reasons for this error:
• A third party tries to use a receiving email system to send spam, and the receiving email system rejects the attempt. By the nature of spam, the sender's email address might have been forged, and the resulting NDR could have been sent to the unsuspecting sender's email address. It is difficult to avoid this situation.
• An MX record for a domain points to a receiving email system where that domain is not accepted. The administrator responsible for the specific domain name must correct the MX record or configure the receiving email system to accept messages sent to that domain, or both.
• A sending email system or client that should use the receiving email system to relay messages does not have the correct permissions to do this.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Are you sending from a different email address than your native Outlook Address