- 14/09/2017 at 04:33 #7377
When I use external device send standard TTL 3.3 V signals, the signal is send by every 500ms, and I get json data is such this :
but ,between two json data ,they ts is not 500ms, why????
and tobii pro glass developer support email is devsupport <[email protected]>, why I send to the address which reply
devsupport wasn’t found at tobii.com.
837530554 Office 365 devsupport
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 following:
•Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link “To send this message 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 address exists and is correct.
•The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they’ve set up is working correctly.
•Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, 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.
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn’t exist at the destination domain. The error is reported by the recipient domain’s email server, but most often it must be fixed by the person who sent the message. If the 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 address exists, is correct, and is accepting messages.
Synchronize your directories – If you have a hybrid environment and are using directory synchronization make sure the recipient’s email address is synced 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 mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Recipient has a valid license – Make sure the recipient has an Office 365 license assigned to them. The recipient’s email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > 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 flow 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 records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
DSN generated by: DB3PR03MB330.eurprd03.prod.outlook.com
HOP TIME (UTC) FROM TO WITH RELAY TIME
2:23:27 AM qq.com smtp.qq.com SMTP *
2:23:32 AM smtpbg65.qq.com VE1EUR03FT045.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) 5 sec
2:23:34 AM VE1EUR03FT045.eop-EUR03.prod.protection.outlook.com DB5PR0301CA0026.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) 2 sec
2:23:35 AM DB5PR0301CA0026.eurprd03.prod.outlook.com DB3PR03MB330.eurprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) 1 sec
Original Message Headers
Received: from DB5PR0301CA0026.eurprd03.prod.outlook.com (2603:10a6:0:2c::36)
by DB3PR03MB330.eurprd03.prod.outlook.com (2a01:111:e400:980f::28) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 18.104.22.168; Thu, 14
Sep 2017 02:23:35 +0000
Received: from VE1EUR03FT045.eop-EUR03.prod.protection.outlook.com
(2a01:111:f400:7e09::204) by DB5PR0301CA0026.outlook.office365.com
(2603:10a6:0:2c::36) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 22.214.171.124 via
Frontend Transport; Thu, 14 Sep 2017 02:23:34 +0000
Authentication-Results: spf=pass (sender IP is 126.96.36.199)
smtp.mailfrom=qq.com; tobii.com; dkim=pass (signature was verified)
header.d=qq.com;tobii.com; dmarc=pass action=none header.from=qq.com;
Received-SPF: Pass (protection.outlook.com: domain of qq.com designates
188.8.131.52 as permitted sender) receiver=protection.outlook.com;
Received: from smtpbg65.qq.com (184.108.40.206) by
VE1EUR03FT045.mail.protection.outlook.com (10.152.19.51) with Microsoft SMTP
Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 220.127.116.11
via Frontend Transport; Thu, 14 Sep 2017 02:23:32 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s201512;
From: “=?gb18030?B?zvfO9w==?=” <[email protected]>
To: “=?gb18030?B?ZGV2c3VwcG9ydA==?=” <[email protected]>
Subject: tobii pro glass TTL 3.3 V sync signal
Date: Thu, 14 Sep 2017 10:23:27 +0800
Message-ID: <[email protected]>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
Received: from qq.com (unknown [10.133.7.30])
by smtp.qq.com (ESMTP) with SMTP
id ; Thu, 14 Sep 2017 10:23:27 +0800 (CST)
Return-Path: [email protected]
X-MS-TrafficTypeDiagnostic: DB3PR03MB330:14/09/2017 at 12:56 #7379
Hi @yangxi, The Tobii Glasses are part of the Tobii Pro business department.
This forum is intended for support with the Tobii EyeX and C4 Eye Tracker and associated SDK’s.
Please get in touch with Tobii Pro Support department directly @ http://www.tobiipro.com/contact/contact-support/ for an
answer to your query.
Apologies for the inconvenience.15/09/2017 at 02:33 #7383
hi Grant I already touch by @ http://www.tobiipro.com/contact/contact-support/ but hava any response15/09/2017 at 02:34 #7384
hi Grant I already touch by @ http://www.tobiipro.com/contact/contact-support/ but have any response15/09/2017 at 11:07 #7385
Hi @yangxi, sorry to hear that.. please PM your ticket number and I will be sure to escalate the issue to the Tobii Pro Support department for resolution. Apologies for the inconvenience.15/09/2017 at 11:29 #738718/09/2017 at 03:29 #7390
Hello Grant, I wait some day, but have any response, do you have other method can get the Tobii Pro Support department Contact information？？18/09/2017 at 11:13 #7392
Hi @yangxi, thank you for your patience. I have spoken with Tobii Pro Support directly and they inform me they emailed you response on the 14th of September regarding this issue.. perhaps your SPAM filter picked this up instead?
In any event, they will resend their original message today, so please let them know if not received.
You can get in touch directly with them [email protected]
Best of luck.
- You must be logged in to reply to this topic.