[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio=
n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to dossier@jds-associes.com couldn't be delivered.

dossier wasn't found at jds-associes.com.

jpjuan  Office 365      dossier
Action Required                 Recipient


Unknown To address


How to Fix It
The address may be misspelled or may not exist. Try one or more of the foll=
owing:

  *   Send the message again following these steps: In Outlook, open this n=
on-delivery report (NDR) and choose Send Again from the Report ribbon. In O=
utlook on the web, select this NDR, then select the link "To send this mess=
age again, click here." Then delete and retype the entire recipient address=
. If prompted with an Auto-Complete List suggestion don't select it. After =
typing the complete address, click Send.
  *   Contact the recipient (by phone, for example) to check that the addre=
ss exists and is correct.
  *   The recipient may have set up email forwarding to an incorrect addres=
s. Ask them to check that any forwarding they've set up is working correctl=
y.
  *   Clear the recipient Auto-Complete List in Outlook or Outlook on the w=
eb by following the steps in this article: Fix email delivery issues for er=
ror code 5.1.10 in Office 365<https://go.microsoft.com/fwlink/?LinkId=3D532=
972>, and then send the message again. Retype the entire recipient address =
before selecting Send.


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<https://go.microsoft.com/fwlin=
k/?LinkId=3D525921>.
________________________________


More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hos=
ted by Office 365 but the address is incorrect or doesn't exist at the dest=
ination domain. The error is reported by the recipient domain's email serve=
r, but most often it must be fixed by the person who sent the message. If t=
he steps in the How to Fix It section above don't fix the problem, and you'=
re the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient addres=
s exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are usi=
ng directory synchronization make sure the recipient's email address is syn=
ced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as=
 expected. Forwarding can be set up by an admin via mail flow rules or mail=
box forwarding address settings, or by the recipient via the Inbox Rules fe=
ature.

Recipient has a valid license - Make sure the recipient has an Office 365 l=
icense assigned to them. The recipient's email admin can use the Office 365=
 admin center to assign a license (Users > Active Users > select the recipi=
ent > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow=
 or MX record settings can cause this error. Check your Office 365 mail flo=
w settings to make sure your domain and any mail flow connectors are set up=
 correctly. Also, work with your domain registrar to make sure the MX recor=
ds for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email d=
elivery issues for error code 5.1.10 in Office 365<https://go.microsoft.com=
/fwlink/?LinkId=3D532972>.


Original Message Details
Created Date:   6/13/2018 9:54:00 AM
Sender Address: jpjuan@loxens.com
Recipient Address:      dossier@jds-associes.com
Subject:        Collaboratrice Comptable Autonome


Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient dossie=
r@jds-associes.com not found by SMTP address lookup
DSN generated by:       PR0P264MB0091.FRAP264.PROD.OUTLOOK.COM


Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       6/13/2018
9:54:00 AM              web12j.yandex.ru        HTTP    *
2       6/13/2018
9:54:01 AM      localhost       mxback16j.mail.yandex.net       ESMTP   1 s=
ec
3       6/13/2018
9:54:03 AM      mxback16j.mail.yandex.net       forward106p.mail.yandex.net=
     ESMTP   2 sec
4       6/13/2018
9:54:04 AM      forward106p.mail.yandex.net     VE1EUR01FT064.mail.protecti=
on.outlook.com       Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_=
ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384)       1 sec
5       6/13/2018
9:54:05 AM      VE1EUR01FT064.eop-EUR01.prod.protection.outlook.com     MR2=
P264CA0045.outlook.office365.com     Microsoft SMTP Server (version=3DTLS1_=
2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)    1 sec
6       6/13/2018
9:54:05 AM      MR2P264CA0045.FRAP264.PROD.OUTLOOK.COM  PR0P264MB0091.FRAP2=
64.PROD.OUTLOOK.COM  Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_=
ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *

Original Message Headers

Received: from MR2P264CA0045.FRAP264.PROD.OUTLOOK.COM (2603:10a6:500::33) b=
y
 PR0P264MB0091.FRAP264.PROD.OUTLOOK.COM (2603:10a6:100:3::19) with Microsof=
t
 SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA=
384) id
 15.20.841.15; Wed, 13 Jun 2018 09:54:05 +0000
Received: from VE1EUR01FT064.eop-EUR01.prod.protection.outlook.com
 (2a01:111:f400:7e01::207) by MR2P264CA0045.outlook.office365.com
 (2603:10a6:500::33) with Microsoft SMTP Server (version=3DTLS1_2,
 cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.863.16 via Fronte=
nd
 Transport; Wed, 13 Jun 2018 09:54:05 +0000
Authentication-Results: spf=3Dpass (sender IP is 77.88.28.109)
 smtp.mailfrom=3Dloxens.com; jds-associes.com; dkim=3Dpass (signature was
 verified) header.d=3Dloxens.com;jds-associes.com; dmarc=3Dbestguesspass
 action=3Dnone header.from=3Dloxens.com;
Received-SPF: Pass (protection.outlook.com: domain of loxens.com designates
 77.88.28.109 as permitted sender) receiver=3Dprotection.outlook.com;
 client-ip=3D77.88.28.109; helo=3Dforward106p.mail.yandex.net;
Received: from forward106p.mail.yandex.net (77.88.28.109) by
 VE1EUR01FT064.mail.protection.outlook.com (10.152.3.34) with Microsoft SMT=
P
 Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P=
384) id
 15.20.863.11 via Frontend Transport; Wed, 13 Jun 2018 09:54:04 +0000
Received: from mxback16j.mail.yandex.net (mxback16j.mail.yandex.net [IPv6:2=
a02:6b8:0:1619::92])
        by forward106p.mail.yandex.net (Yandex) with ESMTP id 013C72D869D3;
        Wed, 13 Jun 2018 12:54:03 +0300 (MSK)
Received: from localhost (localhost [::1])
        by mxback16j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id mtRURSlW=
mk-s0iWRxNg;
        Wed, 13 Jun 2018 12:54:01 +0300
DKIM-Signature: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=3Dloxens.com;=
 s=3Dmail; t=3D1528883641;
        bh=3Dbw1QYDRImiPyQ/ALoHgFKribQHGnX0l5Dq1l1TyoDSo=3D;
        h=3DFrom:To:Subject:Date:Message-Id;
        b=3DFebNx6yCeiY9vz6PloMcwQuUfrJoIUSR5/5lZ6FbBUjy3D4lBiFiHOcrAJFVn4x=
8z
         yxhzdDikTP69sXG5tA35j+m2zSk+Px/dAeLbimFJdYroPflTyFSr3obTC2+4dcc77V
         BHnxyaaBNvOXYYUC4OeuyPVdHLkpbiBQ7pznDnuU=3D
Authentication-Results-Original: mxback16j.mail.yandex.net; dkim=3Dpass
 header.i=3D@loxens.com
Received: by web12j.yandex.ru with HTTP;
        Wed, 13 Jun 2018 12:54:00 +0300
From: Jean-Pierre JUAN <jpjuan@loxens.com>
To: Jean-Pierre JUAN <jpjuan@loxens.com>
Subject: Collaboratrice Comptable Autonome
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Wed, 13 Jun 2018 11:54:00 +0200
Message-ID: <6958171528883640@web12j.yandex.ru>
Content-Type: multipart/mixed;
        boundary=3D"----=3D=3D--bound.695818.web12j.yandex.ru"
Return-Path: jpjuan@loxens.com
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 39930c1a-dbe7-4d81-9ea4-0750771e4495:0
X-Forefront-Antispam-Report: CIP:77.88.28.109;IPV:NLI;CTRY:RU;EFV:NLI;
X-Microsoft-Exchange-Diagnostics: 1;VE1EUR01FT064;1:X3EBGnqfslFa0SQiAZJju5E=
oshc0/nBqU/dZg3Rv56jdnZrHI3soZSjJJDJaLR3ZS5Q7gmM69qbJmZoOhHTMdkgPLTionq5yVn=
WnRg4XFOcf8fjumBwFPRXo0i1KJf90
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 4e9ac487-4ec8-46b5-eb95-08d5d11399=
7c
X-Microsoft-Antispam:
        UriScan:;BCL:0;PCL:0;RULEID:(7020095)(5600026)(711020)(4605076)(460=
8076)(49563074)(1401150)(8001031)(1414027)(71702078);SRVR:PR0P264MB0091;
X-Microsoft-Exchange-Diagnostics:
        1;PR0P264MB0091;3:hs9kBq0kM6CjHEmRinO/X8rAQwsQJX10fO7umrdbW3U4Y0Dfw=
pOf1hNSf3sEM1h2nAyDxTLv349fzS5X59ems9fPCvEUqyJj69UIe2mapCs0RkcV8t2VDWofSJ7M=
kOG7hYxzeJXfnq8fSO7yLyL1NcodBIAssuEcFEZRRL5pef3lpMaJMhrhbzr0qK9VMRfWBveMvDv=
E3ZROleXNAdJuuwOUmWwj8TEBzBA+5zLq/BiupAdx5JTJLH2LKWh5Z+P+JPWk4IwlsZIugtesZb=
nnxaGMmenk+8LkRKC6enBJxw5XFqZtcbh0LdHiTEWpdlDIFVZP/HaUSAuggzjptHYN2Q6+o2a8q=
aa8PCCksLMaqR4=3D;25:mUzKcKzZGQoi9YVN1bhHptS8GpRnsQ5PRmGvv8U+HLCBJCTnqmu2uN=
VexLLwMPUU+IgBtu0mWcWzgFZ4wba5TYufd6OiqKCvzyd+p9mDuHK52LorqKe6mc9bsdhIJ2BVm=
3sQhL5j5VDhREfHg6RbALKGL8z0wYF7Cm6pW4xXyQLcZ3BBrPEvNeNWdx3CIMOZCOdK0TeVJ9n+=
cKgZOLQpiXgOFH+tuf1p4IifrlfSovOVUCQ1mH1J7kmsqur4NJ8oZB6IpykL67XBChRl6Ti0b+S=
x1rvygaGXEKhsHpIwZJfkZ2ggWWK4/mpDeEVxWaTawdPSedEHCQS1tDXpQ55OxA=3D=3D
X-MS-TrafficTypeDiagnostic: PR0P264MB0091:

