Maker
Special Interest Group
Chairs:
Second Call Please Submit
Greetings,
We hope everyone is having a renewing and wonderful holiday season. This is a friendly reminder that the final call for the 2019 SITE proposal submissions will close on January 4th.
The MAKER SIG is excited to review your proposals and include them in our already strong schedule of presentations. There are multiple proposal formats, including brief or full papers, best practices, workshops, and symposia. Please review criteria, and details found on the 2019 SITE Call for Proposals page:
We look forward to seeing you at the conference this spring.
Follow this discussion to receive e-mail notifications whenever it is updated. Follow
Log in to post a a comment in this discussion.
Address not found
Your message wasn't delivered to Ken.morrill@nexthighschool.org because the address couldn't be found, or is unable to receive mail.
Learn more here: https://support.google.com/mail/?p=NoSuchUser
The response from the remote server was: 550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser f13si1517111itf.2 - gsmtp
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to monica.trevathan@tietronix.com couldn't be delivered.
monica.trevathan wasn't found at tietronix.com.
msgs+1p8.0e3380b5fd Office 365 monica.trevathan 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:
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlin= k/?LinkId=3D618497.
More Info for Email Admins Status code 554 5.4.14
Typically this error occurs because the recipient email address is incorrec= t or doesn't exist at the destination domain. This can usually be fixed by = the sender. However, sometimes the issue needs to be fixed by the recipient= or the recipient's email admin. 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 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. A forwarding rule can be configured by an admin via mail flow ru= les or mailbox forwarding address settings, or by the recipient via the Inb= ox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow= settings or MX records can cause this error. Check your Office 365 mail fl= ow settings to make sure your domain and any mail flow connectors are set u= p correctly. Also, work with your domain registrar to make sure the MX reco= rds for your domain are configured correctly.
Mail loop detected - This error also indicates that the receiving organizat= ion's email settings are misconfigured, creating a mail loop when a message= is sent to an address that isn't found in their directory. This usually wo= n't disrupt mail flow for recipients that actually exist, but the recipient= 's email admin should fix the misconfiguration to reduce the chance of any = other mail flow issues. A common cause for this loop is that the recipient'= s domain is configured as "Internal Relay" when it should be "Authoritative= ." Another common cause for the loop is that both the sender and recipient = are part of the same organization, but the sender's mailbox is hosted by Of= fice 365, while the recipient's mailbox is hosted on-premises, and an outbo= und connector from Office 365 to the on-premises email servers is missing o= r misconfigured. To fix this, the recipient's email admin should create a c= orrectly configured outbound connector in Office 365 to route the message t= o the on-premises mailbox.
For more information and tips to fix this problem, see Fix email delivery i= ssues for error code 5.4.14 in Office 365https://go.microsoft.com/fwlink/?= LinkId=3D397497.
Original Message Details Created Date: 12/31/2018 6:19:48 PM Sender Address: msgs+1p8.0e3380b5fd@academicexperts.org Recipient Address: monica.trevathan@tietronix.com Subject: Maker: Second Call Please Submit
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= BL2NAM02FT011.eop-nam02.prod.protection.outlook.com] DSN generated by: CY4PR10MB1717.namprd10.prod.outlook.com Remote server: BL2NAM02FT011.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 12/31/2018 6:19:49 PM ip-172-31-30-52.ec2.internal ip-172-31-30-52.ec2.interna= l ESMTP 1 sec 2 12/31/2018 6:19:49 PM ip-172-31-30-52.ec2.internal CY1NAM02FT004.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 12/31/2018 6:19:50 PM CY1NAM02FT004.eop-nam02.prod.protection.outlook.com MWH= PR10CA0065.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 4 12/31/2018 6:19:51 PM MWHPR10CA0065.namprd10.prod.outlook.com BL0PR10MB3444.nampr= d10.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 12/31/2018 6:19:52 PM NAM04-BN3-obe.outbound.protection.outlook.com SN1NAM02FT0= 38.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 6 12/31/2018 6:19:52 PM SN1NAM02FT038.eop-nam02.prod.protection.outlook.com CY4= PR1001CA0014.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 12/31/2018 6:19:53 PM CY4PR1001CA0014.namprd10.prod.outlook.com BN6PR10MB20= 35.namprd10.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 8 12/31/2018 6:19:55 PM NAM01-BN3-obe.outbound.protection.outlook.com CY1NAM02FT0= 38.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 sec 9 12/31/2018 6:19:55 PM CY1NAM02FT038.eop-nam02.prod.protection.outlook.com MWH= PR10CA0062.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) * 10 12/31/2018 6:19:55 PM MWHPR10CA0062.namprd10.prod.outlook.com CY4PR10MB1717.nampr= d10.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers
Received: from MWHPR10CA0062.namprd10.prod.outlook.com (2603:10b6:300:2c::2= 4) by CY4PR10MB1717.namprd10.prod.outlook.com (2603:10b6:910:9::16) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1471.20; Mon, 31 = Dec 2018 18:19:55 +0000 Received: from CY1NAM02FT038.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e45::203) by MWHPR10CA0062.outlook.office365.com (2603:10b6:300:2c::24) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1471.20 via Front= end Transport; Mon, 31 Dec 2018 18:19:55 +0000 Authentication-Results: spf=3Dnone (sender IP is 104.47.33.50) smtp.mailfrom=3Dacademicexperts.org; tietronixsoftware.onmicrosoft.com; dkim=3Dnone (message not signed) header.d=3Dnone;tietronixsoftware.onmicrosoft.com; dmarc=3Dfail action=3Dn= one header.from=3Dacademicexperts.org;compauth=3Dnone reason=3D405 Received-SPF: None (protection.outlook.com: academicexperts.org does not designate permitted sender hosts) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (104.47.33.50)= by CY1NAM02FT038.mail.protection.outlook.com (10.152.74.217) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1471.13 via Frontend Transport; Mon, 31 Dec 2018 18:19:55 +0000 Received: from CY4PR1001CA0014.namprd10.prod.outlook.com (2603:10b6:910:3d::27) by BN6PR10MB2035.namprd10.prod.outlook.com (2603:10b6:404:101::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1446.23; Mon, 31 = Dec 2018 18:19:53 +0000 Received: from SN1NAM02FT038.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e44::209) by CY4PR1001CA0014.outlook.office365.com (2603:10b6:910:3d::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1471.20 via Front= end Transport; Mon, 31 Dec 2018 18:19:52 +0000 Authentication-Results-Original: spf=3Dnone (sender IP is 104.47.46.53) smtp.mailfrom=3Dacademicexperts.org; tietronixsoftware.onmicrosoft.com; dkim=3Dnone (message not signed) header.d=3Dnone;tietronixsoftware.onmicrosoft.com; dmarc=3Dfail action=3Dn= one header.from=3Dacademicexperts.org;compauth=3Dnone reason=3D405 Received-SPF: None (protection.outlook.com: academicexperts.org does not designate permitted sender hosts) Received: from NAM04-BN3-obe.outbound.protection.outlook.com (104.47.46.53)= by SN1NAM02FT038.mail.protection.outlook.com (10.152.72.69) with Microsoft SM= TP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1446.11 via Frontend Transport; Mon, 31 Dec 2018 18:19:52 +0000 Received: from MWHPR10CA0065.namprd10.prod.outlook.com (2603:10b6:300:2c::2= 7) by BL0PR10MB3444.namprd10.prod.outlook.com (2603:10b6:208:7f::16) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1471.20; Mon, 31 = Dec 2018 18:19:51 +0000 Received: from CY1NAM02FT004.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e45::202) by MWHPR10CA0065.outlook.office365.com (2603:10b6:300:2c::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1471.20 via Front= end Transport; Mon, 31 Dec 2018 18:19:50 +0000 Authentication-Results-Original: spf=3Dnone (sender IP is 54.226.49.121) smtp.mailfrom=3Dacademicexperts.org; tietronix.com; dkim=3Dnone (message n= ot signed) header.d=3Dnone;tietronix.com; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D001 Received-SPF: None (protection.outlook.com: academicexperts.org does not designate permitted sender hosts) Received: from ip-172-31-30-52.ec2.internal (54.226.49.121) by CY1NAM02FT004.mail.protection.outlook.com (10.152.74.112) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1471.13 via Frontend Transport; Mon, 31 Dec 2018 18:19:49 +0000 Received: from ip-172-31-30-52.ec2.internal (localhost [127.0.0.1]) by ip-172-31-30-52.ec2.internal (8.14.4/8.14.4) with ESMTP id wBVIJ= mEd007791 for <monica.trevathan@tietronix.com>; Mon, 31 Dec 2018 18:19:49 GMT Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D6062642649= 980331157=3D=3D" MIME-Version: 1.0 Subject: Maker: Second Call Please Submit
Posted
B.
Get Outlook for iOShttps://aka.ms/o0ukef
Posted