==== Required information ====
- iRedMail version (check /etc/iredmail-release):  v0.9.5-1
- Linux/BSD distribution name and version: CentOS release 6.7 (Final)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):    v2.6.0 (LDAP)
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? : Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
my iRed installation hosted my organisation email domain and clients email domain on same server
now client moved to other email service provider. whenever moved client send mail to my organisation mail id, it is rejecting.

Please find below log and kindly help

Your message to krishna@myorganisation.com couldn't be delivered.

Security or policy settings at myorganisation.com have rejected your message.
network.support     Office 365     myorganisation.com
Sender         Action Required
                   

        Security or policy violation

How to Fix It
The recipient's email server won't accept your message because it appears to violate their security or policy settings. Check the Reported error below to see if you can determine why it was blocked. Then try one or more of the following:
•    If the error mentions SPF, DKIM, or DMARC issues, forward this message to your email admin for assistance.
•    The recipient's email server might suspect that your message is spam. Follow the guidance in this article: E-mailing Best Practices for Senders. Then resend your message.
•    If the error suggests your message is too large, try to reduce the size of your attachment. If that isn't possible, place the file on a publicly accessible cloud storage location, like OneDrive. Then add a link to the file in your message, and resend the message.
•    Contact the recipient (by phone, for example) and tell them to ask their email admin to add you or your email domain to their allowed senders list.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.

Was this helpful? Send feedback to Microsoft.

________________________________________

More Info for Email Admins
Status code: 550 5.7.1

This error occurs when the recipient's domain has security or policy settings that reject the sender's message. However, we were unable to determine the specific setting that's causing this rejection. Usually the error is reported by an email server outside of Office 365. Common issues include the following: the receiving server suspects the message is malicious or spam; the Sender Policy Framework (SPF) record for clientdomain.com is incorrectly configured or doesn't exist; or the message includes an attachment larger than the receiving server will accept. Try one or more of the following:

Review the reported error - Check the Reported error shown below to help determine what the issue might be. For example, if the issue is related to an SPF failure, the reported error will usually include the acronym "SPF" or the phrase "Sender Policy Framework."

Correctly configure your SPF records - If you're the sender's email admin, make sure your domain's SPF records at your domain registrar are properly configured. Office 365 supports only one SPF record (a TXT record that defines SPF) for your domain. Include the following domain name: spf.protection.outlook.com. If you have a hybrid configuration (some mailboxes in the cloud and some mailboxes on premises) or if you're an Exchange Online Protection standalone customer, add the outbound IP address of your on-premises servers to the TXT record. To learn how, see Customize an SPF record to validate outbound email sent from your domain and External Domain Name System records for Office 365.

Unable to relay - If the Reported error indicates a problem with relaying (e.g. "unable to relay"), then the email server that reported the error likely isn't set up correctly to receive and relay messages from the sender's domain. This server will usually be one of your on-premises servers in a hybrid environment, a smart host email service that you're trying to route messages through, or possibly even an email hosting service you used in the past yet still have mail flow settings pointing to (e.g. your MX record at your domain registrar still points to your previous email service provider). Check Error reported by shown below to determine what domain, service, or server is reporting the error. The email server needs to be configured to either accept messages from anonymous users or to include the sending domain or IP in its list of authenticated senders. On an Exchange server, you can set this up in the server's receive connector. If it's a smart host managed by another service or partner, contact the service or partner to configure their servers to accept and relay messages from your senders. Also, work with your domain registrar to make sure your MX records are properly configured.

Contact the recipient's email admin - For some scenarios, you can fix the issue by contacting the email admin at the recipient domain to ask them to add the sender's email address or your domain to their allowed senders list, or to relax the setting that's causing the rejection.

For more information and tips for fixing this issue, see Fix email delivery issues for error code 5.7.1 in Office 365.

Original Message Details
Created Date:    9/19/2017 5:21:42 AM
Sender Address:    network.support@clientdomain.com

Recipient Address:    krishna@myorganisation.com

Subject:    TEST

Error Details
Reported error:    553 5.7.1 <network.support@clientdomain.com>: Sender address rejected: not logged in
DSN generated by:    BM1PR01MB0387.INDPRD01.PROD.OUTLOOK.COM
Remote server:    mailsrv.mailserver.com

Message Hops
HOP    TIME (UTC)    FROM    TO    WITH    RELAY TIME
1    9/19/2017
5:21:43 AM    BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM    BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM    mapi    1 sec
2    9/19/2017
5:21:43 AM    BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM    BM1PR01MB0387.INDPRD01.PROD.OUTLOOK.COM    Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256)    *
Original Message Headers
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clientdomain.com;
s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
bh=uDPJOfzjQy79Xzmlum9X/FAjcaI/nmTY/c6NubJNC4I=;
b=D50ZQkAkJlyAkSo1z7XHQ2oqEHh1IaXrbiiRRP7dzucYvY0+/uFs3dyWkVWp4k2bu7TgB4CmTVavzFJBzyMiQOgIZJPY4CRY46wcKx1rQMjYqiV8NkLn9gVHbXIeewUACF4AGJjBBIibTpkDxERwFixf3g6iA1wy7ZSrOrEuBng=
Received: from BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM (10.164.131.7) by
BM1PR01MB0387.INDPRD01.PROD.OUTLOOK.COM (10.164.131.8) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
15.20.56.11; Tue, 19 Sep 2017 05:21:43 +0000
Received: from BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM ([10.164.131.7]) by
BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM ([10.164.131.7]) with mapi id
15.20.0056.016; Tue, 19 Sep 2017 05:21:43 +0000
From: Corporate NW-Support <network.support@clientdomain.com>
To: "krishna@myorganisation.com" <krishna@myorganisation.com>
Subject: TEST
Thread-Topic: TEST
Thread-Index: AdMxBvH8YGILDnb1QsCW8suBMDrFkA==
Date: Tue, 19 Sep 2017 05:21:42 +0000
Message-ID: <BM1PR01MB038677BB7BC526423A8997CBE7600@BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
smtp.mailfrom=network.support@clientdomain.com;
x-originating-ip: [xxx.xxx.xxx.xxx]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1;BM1PR01MB0387;6:CY6GGt1V/8eDgYFx4NNx9E0lM1bIh/CVwmaHY4AAv5V+jlOZvJZnVHnpCTNY9ZXb6XWXtuM6aZkAf82zkOL4kWGY1KbGPmU/p/DTSa5z6tz4HFfN3tWEQ0oYErWIXxUkW/9vsRKK7Qyl/xJyE9vfBTc2DHv8wFG4U4hZRA1dRnsyRMEt8Z88rTt4bc/vwVwUQr1rZxsV+ua5B8oWZlJwdvcFqOBjiLzBg+uIvvz6AbkCmpqdXvngVWcjF6oDW0Unmh2fudTMar10XHA6zc88pBMghN272KnopPkxZHSMWwTI4YdtOrDnQjIo5Nc/jZ2TReAg7DFkBkAGFgumgMF4BA==;5:BjdQZe/7Xb/qj8urPTViyjmgIWhtpY84Q+38jS3PLN8bgV1+gE8RB7CTBhUq3xYUkv1Pq0U3SD5JdczCFIlj9Z8UkIPNXBTUaPdfjv6DkkbDWBJKFh7zkFBdOT3D6aERfQMN/8pFvUfTkHJPvYb6bg==;24:Enhhnc1SMaJFl4kVY0NMXswGPhfXbBHZQkdKQE7KgvVteo8UKxU2X51KFPyxXrsah8EDhCGE+t+R5IT8pdmQck22bla2JQUeMdHtLLbhSt8=;7:Rd8yYYaWMdn9kGHZYFKuubkeOkkkyfsmQOMD4wc8B6l8E5yVeZ6AvZBVpR6QSXrFsLpuJ8CSfYUGQhxSTtc9y+18RR/JaXaqaYQZ8dHyItSWd+r2qkrvXQ0G3jeOEYwMKeFECr9kpQMCl2ZWNMxFEO0YezOJrWzitFvweUInSXXexCsvhpxevYRfxz/lON74tNML+NAJysppn1qOWBsK9LYJGkDDNWp4HTeEglIybEg=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 49a812b4-930a-4bcf-46db-08d4ff1e5079
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254152)(2017082002075)(300000503095)(300135400095)(2017052603199)(49563074)(201703131423075)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095);SRVR:BM1PR01MB0387;
x-ms-traffictypediagnostic: BM1PR01MB0387:
x-exchange-antispam-report-test: UriScan:(126080769019788)(116415991822766)(81227570615382)(21748063052155);
x-microsoft-antispam-prvs: <BM1PR01MB03870B93F70D5984B9E3277FE7600@BM1PR01MB0387.INDPRD01.PROD.OUTLOOK.COM>
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(2401047)(8121501046)(5005006)(10201501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(6041248)(20161123555025)(20161123560025)(20161123564025)(20161123558100)(2016111802025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148)(6043046)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095);SRVR:BM1PR01MB0387;BCL:0;PCL:0;RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);SRVR:BM1PR01MB0387;
x-forefront-prvs: 04359FAD81
x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(346002)(376002)(199003)(189002)(66066001)(14454004)(6506006)(77096006)(5890100001)(7116003)(102836003)(6116002)(3846002)(7696004)(221733001)(5660300001)(33656002)(2906002)(2501003)(2900100001)(5640700003)(6436002)(236005)(478600001)(9686003)(6916009)(733005)(6306002)(54896002)(54556002)(53936002)(606006)(55016002)(8676002)(3480700004)(1730700003)(8936002)(81166006)(81156014)(105586002)(106356001)(7736002)(189998001)(74316002)(861006)(101416001)(99936001)(86362001)(50986999)(25786009)(54356999)(68736007)(2351001)(316002)(3660700001)(79362002)(569044001)(97736004)(3280700002)(215093002)(16866105001);DIR:OUT;SFP:1102;SCL:1;SRVR:BM1PR01MB0387;H:BM1PR01MB0386.INDPRD01.PROD.OUTLOOK.COM;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en;
received-spf: None (protection.outlook.com: clientdomain.com does not designate
permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/related;
        boundary="_009_BM1PR01MB038677BB7BC526423A8997CBE7600BM1PR01MB0386INDP_";
        type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: clientdomain.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2017 05:21:42.9215
(UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 070340cc-c8c5-4e10-bedb-73d22991c7ba
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BM1PR01MB0387