Maker
Special Interest Group
Chairs:
MAKER SIG Meeting
Good afternoon,
We hope this email greets you well. We are excited about celebrating SITE's 30th anniversary in Las Vegas in just a few weeks.
At the Maker SIG meeting, we will be voting to fill an open SIG Co-Chair position. If you are interested in serving as a co-chair, please send a note to Jason jtrumble@uca.edu or Monty joneswm2@vcu.edu.
We will also award our second paper award for the Maker SIG and share our successes for this year.
We are looking forward to seeing you.
All the best.
Follow this discussion to receive e-mail notifications whenever it is updated. Follow
Log in to post a a comment in this discussion.
An error occurred while trying to deliver the mail to the following recipients: mtearle3@gmail.com
Posted
An error occurred while trying to deliver the mail to the following recipients: myasar.ozden@bahcesehir.edu.tr
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.
010001692ba6609c-938. . . 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: 2/26/2019 9:11:57 PM Sender Address: 010001692ba6609c-938011c4-d44e-4a44-aa4d-6fc9b4475bb6-00000= 0@bounces.academicexperts.org Recipient Address: monica.trevathan@tietronix.com Subject: Maker: MAKER SIG Meeting
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= CY1NAM02FT031.eop-nam02.prod.protection.outlook.com] DSN generated by: CY4PR10MB1720.namprd10.prod.outlook.com Remote server: CY1NAM02FT031.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 2/26/2019 9:11:58 PM a8-80.smtp-out.amazonses.com BL2NAM02FT047.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 2/26/2019 9:11:58 PM BL2NAM02FT047.eop-nam02.prod.protection.outlook.com BN6= PR10CA0026.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 2/26/2019 9:11:58 PM BN6PR10CA0026.namprd10.prod.outlook.com BYAPR10MB3445.nampr= d10.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 2/26/2019 9:12:00 PM NAM02-CY1-obe.outbound.protection.outlook.com CY1NAM02FT0= 24.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 sec 5 2/26/2019 9:12:00 PM CY1NAM02FT024.eop-nam02.prod.protection.outlook.com BN6= PR10CA0040.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) * 6 2/26/2019 9:12:01 PM BN6PR10CA0040.namprd10.prod.outlook.com DM6PR10MB3449.nampr= d10.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 2/26/2019 9:12:02 PM NAM02-BL2-obe.outbound.protection.outlook.com CY1NAM02FT0= 13.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 8 2/26/2019 9:12:03 PM CY1NAM02FT013.eop-nam02.prod.protection.outlook.com DM5= PR10CA0016.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 9 2/26/2019 9:12:03 PM DM5PR10CA0016.namprd10.prod.outlook.com CY4PR10MB1720.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 DM5PR10CA0016.namprd10.prod.outlook.com (2603:10b6:4:2::26) = by CY4PR10MB1720.namprd10.prod.outlook.com (2603:10b6:910:a::7) with Microsof= t SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.1643.14; Tue, 26 Feb 2019 21:12:03 +0000 Received: from CY1NAM02FT013.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e45::207) by DM5PR10CA0016.outlook.office365.com (2603:10b6:4:2::26) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.15 via Front= end Transport; Tue, 26 Feb 2019 21:12:03 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.38.54) smtp.mailfrom=3Dbounces.academicexperts.org; tietronixsoftware.onmicrosoft= .com; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;tietronixsoftware.onmicrosoft.com; dmarc=3D= pass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D1= 00 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.38.54 as permitted sender) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.54)= by CY1NAM02FT013.mail.protection.outlook.com (10.152.75.162) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1643.11 via Frontend Transport; Tue, 26 Feb 2019 21:12:02 +0000 Received: from BN6PR10CA0040.namprd10.prod.outlook.com (2603:10b6:404:109::= 26) by DM6PR10MB3449.namprd10.prod.outlook.com (2603:10b6:5:71::30) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.15; Tue, 26 = Feb 2019 21:12:01 +0000 Received: from CY1NAM02FT024.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e45::209) by BN6PR10CA0040.outlook.office365.com (2603:10b6:404:109::26) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.15 via Front= end Transport; Tue, 26 Feb 2019 21:12:00 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.37.70) smtp.mailfrom=3Dbounces.academicexperts.org; tietronixsoftware.onmicrosoft= .com; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;tietronixsoftware.onmicrosoft.com; dmarc=3D= pass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D1= 00 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.37.70 as permitted sender) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (104.47.37.70)= by CY1NAM02FT024.mail.protection.outlook.com (10.152.74.210) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1643.11 via Frontend Transport; Tue, 26 Feb 2019 21:12:00 +0000 Received: from BN6PR10CA0026.namprd10.prod.outlook.com (2603:10b6:404:109::= 12) by BYAPR10MB3445.namprd10.prod.outlook.com (2603:10b6:a03:81::11) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.21; Tue, 26 = Feb 2019 21:11:58 +0000 Received: from BL2NAM02FT047.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e46::205) by BN6PR10CA0026.outlook.office365.com (2603:10b6:404:109::12) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.14 via Front= end Transport; Tue, 26 Feb 2019 21:11:58 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.80) smtp.mailfrom=3Dbounces.academicexperts.org; tietronix.com; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;tietronix.com; dmarc=3Dpass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpa= ss reason=3D100 Received-SPF: Pass (protection.outlook.com: domain of bounces.academicexperts.org designates 54.240.8.80 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.80; helo=3Da8-80.smtp-out.amazonses.com; Received: from a8-80.smtp-out.amazonses.com (54.240.8.80) by BL2NAM02FT047.mail.protection.outlook.com (10.152.77.9) with Microsoft SMT= P Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1643.11 via Frontend Transport; Tue, 26 Feb 2019 21:11:58 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551215518; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3D4lGo1lk85vnmPE4jF4DBY1m/hHifBnCV1K7WvLd07lY=3D; b=3DE89Czhq37nS5VgFB1RwzDWMxPGNTIf41LFJZrmBTAFeLt3tZwstn8yGm3CRE7L1= 2 1sXuJ0/te57KywfQHX8iorVcI6GNueogqyQuBm+QR2DYqrb6rz2eB4a2e6sDm7GuwR9 GWp0LuHmoxKJf1CNr9eASECKVEBDNCSZ3wSFpGgQ=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155121= 5518; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3D4lGo1lk85vnmPE4jF4DBY1m/hHifBnCV1K7WvLd07lY=3D; b=3DYZnMVureLnYU8G1tU1DkToX1yg6pLitvVPqNsTATj8e7WUxKgXK81s38bqJtDm+= H FTTvGbH4uUlt8R03oxjcxxUbElENBJ6B2kXrhwwFEfEXBNAcmxSJ2JciBXZAnClqAwo j/KY+jRKN/I+Iz1kaFybEerEu4B0EZk0ofOiX5yg=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D54711273138920778= 12=3D=3D" MIME-Version: 1.0 Subject: Maker: MAKER SIG Meeting
Posted
An error occurred while trying to deliver the mail to the following recipients: amothersele@swindsor.k12.ct.us
Posted
An error occurred while trying to deliver the mail to the following recipients: jinyi@iastate.edu
Posted
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 c12si461451pfc.2 - gsmtp
Posted