SIG Co-chair Nomination 2019
The SITE 2019 conference is only two weeks away! The Assessment/E-folio SIG is currently seeking nominees for the role of SIG co-chair. This is a two-year term (March 2019 - March 2021). Candidates for election must be members of SITE and the Assessment/E-folio SIG. Self-nominations are welcome. Duties of this position include:
- Coordinate reviews and decisions about proposals submitted to the SIG for SITE Annual Conference program
- Communicate with SIG members about SITE and SIG developments and events
- Encourage SIG members to participate in SITE Annual Conference, other events and/or projects
- Attend SITE Annual Conference for each year in office
- Conduct Assessment/E-folio SIG meetings at the SITE Annual Conferences
- Represent Assessment/E-folio SIG at Teacher Education Council meetings at SITE Annual Conference
- Solicit nominations and conduct elections of Assessment/E-folio SIG co-chairs
To nominate someone, or self-nominate, for the Assessment/E-folio SIG co-chair position, please send an email to lli@bgsu.edu with the candidate's name, email address, title, program/department/university or organization, and a short bio including the candidate’s interest in the position and their experience with SITE. Nominations will be due Sunday, March 10, 2018. Nominees will be contacted to confirm their nomination. Full CV’s may be requested. We will hold the election digitally before the SIG meeting and then will have the final vote at the SIG meeting (March 20th). Candidates running must be present at the SIG meeting.
Thank you for being a member of the Assessment/E-folio SIG! We look forward to seeing you in Las Vegas at the SITE Annual Conference!
Follow this discussion to receive e-mail notifications whenever it is updated. Follow
Log in to post a a comment in this discussion.
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to AZ.Bashet@unthsc.edu couldn't be delivered.
AZ.Bashet wasn't found at unthsc.edu.
010001695358fc89-ed3. . . Office 365 AZ.Bashet 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: 3/6/2019 2:12:14 PM Sender Address: 010001695358fc89-ed324583-c56c-4e97-98ed-ee70d5cf3fb0-00000= 0@bounces.academicexperts.org Recipient Address: AZ.Bashet@unthsc.edu Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= CO1NAM04FT051.eop-NAM04.prod.protection.outlook.com] DSN generated by: MWHPR01MB2494.prod.exchangelabs.com Remote server: CO1NAM04FT051.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/6/2019 2:12:15 PM a8-40.smtp-out.amazonses.com SN1NAM04FT043.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 3/6/2019 2:12:15 PM SN1NAM04FT043.eop-NAM04.prod.protection.outlook.com DM5= PR0101CA0034.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 3/6/2019 2:12:16 PM DM5PR0101CA0034.prod.exchangelabs.com BN6PR01MB2483.prod.= exchangelabs.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 4 3/6/2019 2:12:17 PM NAM04-CO1-obe.outbound.protection.outlook.com SN1NAM04FT0= 36.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 5 3/6/2019 2:12:17 PM SN1NAM04FT036.eop-NAM04.prod.protection.outlook.com BN6= PR0101CA0014.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 6 3/6/2019 2:12:17 PM BN6PR0101CA0014.prod.exchangelabs.com DM6PR01MB5225.prod.= exchangelabs.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 3/6/2019 2:12:19 PM NAM04-CO1-obe.outbound.protection.outlook.com CO1NAM04FT0= 61.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 sec 8 3/6/2019 2:12:19 PM CO1NAM04FT061.eop-NAM04.prod.protection.outlook.com MN2= PR01CA0003.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 9 3/6/2019 2:12:20 PM MN2PR01CA0003.prod.exchangelabs.com MWHPR01MB2494.prod.= exchangelabs.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
Original Message Headers
Received: from MN2PR01CA0003.prod.exchangelabs.com (2603:10b6:208:10c::16) = by MWHPR01MB2494.prod.exchangelabs.com (2603:10b6:300:3e::12) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.1665.18; Wed, 6 Mar 2019 14:12:20 +0000 Received: from CO1NAM04FT061.eop-NAM04.prod.protection.outlook.com (2a01:111:f400:7e4d::208) by MN2PR01CA0003.outlook.office365.com (2603:10b6:208:10c::16) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:12:19 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.45.84) smtp.mailfrom=3Dbounces.academicexperts.org; unthsc.edu; dkim=3Dfail (body= hash did not verify) header.d=3Dacademicexperts.org;unthsc.edu; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D0= 01 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.45.84 as permitted sender) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.84)= by CO1NAM04FT061.mail.protection.outlook.com (10.152.91.130) 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; Wed, 6 Mar 2019 14:12:19 +0000 Received: from BN6PR0101CA0014.prod.exchangelabs.com (2603:10b6:405:2a::27)= by DM6PR01MB5225.prod.exchangelabs.com (2603:10b6:5:6e::33) with Microsoft SM= TP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) = id 15.20.1665.19; Wed, 6 Mar 2019 14:12:17 +0000 Received: from SN1NAM04FT036.eop-NAM04.prod.protection.outlook.com (2a01:111:f400:7e4c::204) by BN6PR0101CA0014.outlook.office365.com (2603:10b6:405:2a::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.18 via Front= end Transport; Wed, 6 Mar 2019 14:12:17 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.45.55) smtp.mailfrom=3Dbounces.academicexperts.org; unthsc.edu; dkim=3Dfail (body= hash did not verify) header.d=3Dacademicexperts.org;unthsc.edu; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D0= 01 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.45.55 as permitted sender) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.55)= by SN1NAM04FT036.mail.protection.outlook.com (10.152.89.149) 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; Wed, 6 Mar 2019 14:12:17 +0000 Received: from DM5PR0101CA0034.prod.exchangelabs.com (2603:10b6:4:28::47) b= y BN6PR01MB2483.prod.exchangelabs.com (2603:10b6:404:51::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.1665.18; Wed, 6 Mar 2019 14:12:16 +0000 Received: from SN1NAM04FT043.eop-NAM04.prod.protection.outlook.com (2a01:111:f400:7e4c::206) by DM5PR0101CA0034.outlook.office365.com (2603:10b6:4:28::47) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:12:15 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.40) smtp.mailfrom=3Dbounces.academicexperts.org; unthsc.edu; dkim=3Dpass (sign= ature was verified) header.d=3Dacademicexperts.org;unthsc.edu; dmarc=3Dpass acti= on=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D100 Received-SPF: Pass (protection.outlook.com: domain of bounces.academicexperts.org designates 54.240.8.40 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.40; helo=3Da8-40.smtp-out.amazonses.com; Received: from a8-40.smtp-out.amazonses.com (54.240.8.40) by SN1NAM04FT043.mail.protection.outlook.com (10.152.89.45) with Microsoft SM= TP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1643.11 via Frontend Transport; Wed, 6 Mar 2019 14:12:15 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551881534; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DS3LMK1sXYHh/OQuU2Vy77Qz/o9QyCvhUM7PuGB6FTNw=3D; b=3DATIBbVMBD2vzLxnLhN46cYm2jLMUmTPys7UFyxPZp6Bqz39WkPv0qxoJys5ciRJ= d kJS6JnOj9Dp+4TzSwq04ccd5111ytVc8f6gcmfeXV0CYTt/Faolyq72J89B5VwXu/sb lur2vcYsyNOS0g2YzZOqUITfzEth2HqjnMd+jIQg=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155188= 1534; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DS3LMK1sXYHh/OQuU2Vy77Qz/o9QyCvhUM7PuGB6FTNw=3D; b=3DiB2FL8evf0TNCE/m65rDK4B9uDUSQnhuMWFJTCRI9qmJb3Ejqbkw18sz2YFDsku= 8 RnfrlUDoUBYT9kUEFwxiwXulj/IWKcwv3vL5xXHOpgL5wpSkJ9DfsCCyj9oFEg25Zhf GKZB4k8K3cbbWLe9dCKy50OZ+fmJgVW8PNHlQu+Y=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D67550418529089406= 78=3D=3D" MIME-Version: 1.0 Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to cwoolley@rockyview.ab.ca couldn't be delivered.
cwoolley wasn't found at rockyview.ab.ca.
0100016953590d3f-8e3. . . Office 365 cwoolley 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: 3/6/2019 2:12:18 PM Sender Address: 0100016953590d3f-8e3a6557-ae24-421d-9e24-92f873c70a16-00000= 0@bounces.academicexperts.org Recipient Address: cwoolley@rockyview.ab.ca Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= TO1CAN01FT004.eop-CAN01.prod.protection.outlook.com] DSN generated by: YTBPR01MB2445.CANPRD01.PROD.OUTLOOK.COM Remote server: TO1CAN01FT004.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/6/2019 2:12:19 PM a8-99.smtp-out.amazonses.com TO1CAN01FT003.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 3/6/2019 2:12:19 PM TO1CAN01FT003.eop-CAN01.prod.protection.outlook.com YQB= PR0101CA0041.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 3/6/2019 2:12:19 PM YQBPR0101CA0041.CANPRD01.PROD.OUTLOOK.COM YQXPR0101MB= 1814.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 3/6/2019 2:12:20 PM CAN01-QB1-obe.outbound.protection.outlook.com TO1CAN01FT0= 05.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 5 3/6/2019 2:12:21 PM TO1CAN01FT005.eop-CAN01.prod.protection.outlook.com YQX= PR01CA0020.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 6 3/6/2019 2:12:21 PM YQXPR01CA0020.CANPRD01.PROD.OUTLOOK.COM YT1PR01MB3705.CANPR= D01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 3/6/2019 2:12:22 PM CAN01-TO1-obe.outbound.protection.outlook.com TO1CAN01FT0= 10.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 8 3/6/2019 2:12:22 PM TO1CAN01FT010.eop-CAN01.prod.protection.outlook.com YQB= PR0101CA0035.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 9 3/6/2019 2:12:22 PM YQBPR0101CA0035.CANPRD01.PROD.OUTLOOK.COM YTBPR01MB24= 45.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers
Received: from YQBPR0101CA0035.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00::48= ) by YTBPR01MB2445.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:22::10) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.16; Wed, 6 M= ar 2019 14:12:22 +0000 Received: from TO1CAN01FT010.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5d::209) by YQBPR0101CA0035.outlook.office365.com (2603:10b6:c00::48) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:12:22 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.61.40) smtp.mailfrom=3Dbounces.academicexperts.org; rockyview.ab.ca; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;rockyview.ab.ca; dmarc=3Dpass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpa= ss reason=3D100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.61.40 as permitted sender) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (104.47.61.40)= by TO1CAN01FT010.mail.protection.outlook.com (10.152.122.137) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1643.11 via Frontend Transport; Wed, 6 Mar 2019 14:12:22 +0000 Received: from YQXPR01CA0020.CANPRD01.PROD.OUTLOOK.COM (2a01:111:e400:5b9e::30) by YT1PR01MB3705.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:c::29) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.18; Wed, 6 M= ar 2019 14:12:21 +0000 Received: from TO1CAN01FT005.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5d::204) by YQXPR01CA0020.outlook.office365.com (2a01:111:e400:5b9e::30) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.18 via Front= end Transport; Wed, 6 Mar 2019 14:12:21 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.60.51) smtp.mailfrom=3Dbounces.academicexperts.org; rockyview.ab.ca; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;rockyview.ab.ca; dmarc=3Dpass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpa= ss reason=3D100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.60.51 as permitted sender) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (104.47.60.51)= by TO1CAN01FT005.mail.protection.outlook.com (10.152.122.116) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1643.11 via Frontend Transport; Wed, 6 Mar 2019 14:12:20 +0000 Received: from YQBPR0101CA0041.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:1::= 18) by YQXPR0101MB1814.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:1c::15) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Wed, 6 M= ar 2019 14:12:19 +0000 Received: from TO1CAN01FT003.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5d::200) by YQBPR0101CA0041.outlook.office365.com (2603:10b6:c00:1::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:12:19 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.99) smtp.mailfrom=3Dbounces.academicexperts.org; rockyview.ab.ca; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;rockyview.ab.ca; 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.99 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.99; helo=3Da8-99.smtp-out.amazonses.com; Received: from a8-99.smtp-out.amazonses.com (54.240.8.99) by TO1CAN01FT003.mail.protection.outlook.com (10.152.122.114) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1643.11 via Frontend Transport; Wed, 6 Mar 2019 14:12:19 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551881539; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3D3xAe6dWefbc119Z63bx/kuV7lCxSZ3cBEUb8fseHSfI=3D; b=3DevJz97chl4oWK95OQHoJ+hc4DrKgupeNcgKj8R+YxatWPiwFfK7zx7N5NyGYt3M= n bAXYxfeZBq8JUlIj6gF3HSweoVAPTW+T3I2ZteCt8ctEiF/6Amd7inCY9qtCaI41NbO FgMOz52evuYvp/GZ7HWcYLHaX7n8HXY5XzJ2Ys+8=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155188= 1539; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3D3xAe6dWefbc119Z63bx/kuV7lCxSZ3cBEUb8fseHSfI=3D; b=3DBfnGc7wDb9Ww+URKBBIxuRE978YFsUpULm2Gaj8R+x1hXw1IlyIW2EKjxk6j3OJ= m OJvYYZHjYJIoKLxdo4kedPgogopaosfLjZqvcJiYanaBYfF1OGURK0Evy1Gubu7aa3b SDerOvTW6Wp8xp+0q9HNnLYNtt1+DgQ0nt3alfsM=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D57137538716075183= 11=3D=3D" MIME-Version: 1.0 Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Posted
An error occurred while trying to deliver the mail to the following recipients: tahameister53@marianuniversity.edu
Posted
An error occurred while trying to deliver the mail to the following recipients: ibaangun@usf.edu
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to lamkinsj@bolles.org couldn't be delivered.
lamkinsj wasn't found at bolles.org.
010001695359a193-6cb. . . Office 365 lamkinsj 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: 3/6/2019 2:12:56 PM Sender Address: 010001695359a193-6cb87641-8a66-4f83-acb8-bd29f411bb30-00000= 0@bounces.academicexperts.org Recipient Address: lamkinsj@bolles.org Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= SN1NAM02FT027.eop-nam02.prod.protection.outlook.com] DSN generated by: DM6PR06MB6201.namprd06.prod.outlook.com Remote server: SN1NAM02FT027.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/6/2019 2:12:57 PM a8-44.smtp-out.amazonses.com SN1NAM02FT030.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 3/6/2019 2:12:57 PM SN1NAM02FT030.eop-nam02.prod.protection.outlook.com DM6= PR06CA0001.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 3/6/2019 2:12:58 PM DM6PR06CA0001.namprd06.prod.outlook.com DM6PR06MB5884.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 4 3/6/2019 2:12:59 PM NAM03-CO1-obe.outbound.protection.outlook.com BL2NAM02FT0= 26.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 5 3/6/2019 2:12:59 PM BL2NAM02FT026.eop-nam02.prod.protection.outlook.com BN7= PR06CA0014.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 6 3/6/2019 2:13:00 PM BN7PR06CA0014.namprd06.prod.outlook.com BN7PR06MB5266.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 3/6/2019 2:13:03 PM NAM01-BY2-obe.outbound.protection.outlook.com SN1NAM02FT0= 22.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 sec 8 3/6/2019 2:13:03 PM SN1NAM02FT022.eop-nam02.prod.protection.outlook.com BN6= PR06CA0024.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) * 9 3/6/2019 2:13:04 PM BN6PR06CA0024.namprd06.prod.outlook.com DM6PR06MB6201.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
Original Message Headers
Received: from BN6PR06CA0024.namprd06.prod.outlook.com (2603:10b6:404:10b::= 34) by DM6PR06MB6201.namprd06.prod.outlook.com (2603:10b6:5:127::22) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.16; Wed, 6 M= ar 2019 14:13:04 +0000 Received: from SN1NAM02FT022.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e44::208) by BN6PR06CA0024.outlook.office365.com (2603:10b6:404:10b::34) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.17 via Front= end Transport; Wed, 6 Mar 2019 14:13:03 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.34.50) smtp.mailfrom=3Dbounces.academicexperts.org; bolles.org; dkim=3Dpass (sign= ature was verified) header.d=3Dacademicexperts.org;bolles.org; dmarc=3Dpass acti= on=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.34.50 as permitted sender) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (104.47.34.50)= by SN1NAM02FT022.mail.protection.outlook.com (10.152.72.148) 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; Wed, 6 Mar 2019 14:13:03 +0000 Received: from BN7PR06CA0014.namprd06.prod.outlook.com (2603:10b6:406:80::2= 7) by BN7PR06MB5266.namprd06.prod.outlook.com (2603:10b6:408:8::25) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.21; Wed, 6 M= ar 2019 14:13:00 +0000 Received: from BL2NAM02FT026.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e46::205) by BN7PR06CA0014.outlook.office365.com (2603:10b6:406:80::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.18 via Front= end Transport; Wed, 6 Mar 2019 14:12:59 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.40.51) smtp.mailfrom=3Dbounces.academicexperts.org; bolles.org; dkim=3Dpass (sign= ature was verified) header.d=3Dacademicexperts.org;bolles.org; dmarc=3Dpass acti= on=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.40.51 as permitted sender) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (104.47.40.51)= by BL2NAM02FT026.mail.protection.outlook.com (10.152.77.156) 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; Wed, 6 Mar 2019 14:12:59 +0000 Received: from DM6PR06CA0001.namprd06.prod.outlook.com (2603:10b6:5:120::14= ) by DM6PR06MB5884.namprd06.prod.outlook.com (2603:10b6:5:1aa::25) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.16; Wed, 6 M= ar 2019 14:12:58 +0000 Received: from SN1NAM02FT030.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e44::205) by DM6PR06CA0001.outlook.office365.com (2603:10b6:5:120::14) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:12:57 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.44) smtp.mailfrom=3Dbounces.academicexperts.org; bolles.org; dkim=3Dpass (sign= ature was verified) header.d=3Dacademicexperts.org;bolles.org; dmarc=3Dpass acti= on=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D100 Received-SPF: Pass (protection.outlook.com: domain of bounces.academicexperts.org designates 54.240.8.44 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.44; helo=3Da8-44.smtp-out.amazonses.com; Received: from a8-44.smtp-out.amazonses.com (54.240.8.44) by SN1NAM02FT030.mail.protection.outlook.com (10.152.72.114) 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; Wed, 6 Mar 2019 14:12:57 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551881576; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3D4pcrNOre61m89cFOYTW09heXIRAcD/BgBfiMiN4YhtA=3D; b=3DN6eCcnBbdpKUr3yE9/xOCxML/2CucDpolNUZeTFhkuSy7XV1jvorIH81wRPjQab= o OGMTnU1M5a2INoWrn6ifmJw4h/6TNKWGhm3rcl80YKdf/fBwnCU04fQZUXQNVNvLglW q4CqOmQ2J8OYKFYY0O/QA3PPOrIftIzSTZLC65eA=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155188= 1576; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3D4pcrNOre61m89cFOYTW09heXIRAcD/BgBfiMiN4YhtA=3D; b=3DPi2y4uKb4Blx5LauFQrg+lXwbaUL/hKpUFpDHJBpleJgbwhJZwIGm81u0Bleo0j= n 5Cza9fBt4Vb7pl3OfWJlKKgcjYpZECgdwsqbXo7XGNVZIBcWj1UvbQ8zMmS/Duk62Xv WptaHxzINcvQF4cOGxObt6hAgxx8iiyk9oUiIJ+s=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D51983924519922743= 52=3D=3D" MIME-Version: 1.0 Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Posted
An error occurred while trying to deliver the mail to the following recipients: acnode@tea.ntue.edu.w
Posted
An error occurred while trying to deliver the mail to the following recipients: david.gibson@curveshift.com
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to ajensdottir@rockyview.ab.ca couldn't be delivered.
ajensdottir wasn't found at rockyview.ab.ca.
010001695359fc61-74b. . . Office 365 ajensdottir 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: 3/6/2019 2:13:20 PM Sender Address: 010001695359fc61-74bbcb0c-5019-4acf-af7d-b4061165a5ce-00000= 0@bounces.academicexperts.org Recipient Address: ajensdottir@rockyview.ab.ca Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= TO1CAN01FT005.eop-CAN01.prod.protection.outlook.com] DSN generated by: YQXPR0101MB1816.CANPRD01.PROD.OUTLOOK.COM Remote server: TO1CAN01FT005.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/6/2019 2:13:20 PM a8-99.smtp-out.amazonses.com QB1CAN01FT006.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 3/6/2019 2:13:21 PM QB1CAN01FT006.eop-CAN01.prod.protection.outlook.com YTO= PR0101CA0065.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 3 3/6/2019 2:13:21 PM YTOPR0101CA0065.CANPRD01.PROD.OUTLOOK.COM YTXPR0101MB= 1824.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 3/6/2019 2:13:22 PM CAN01-QB1-obe.outbound.protection.outlook.com TO1CAN01FT0= 10.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 5 3/6/2019 2:13:22 PM TO1CAN01FT010.eop-CAN01.prod.protection.outlook.com YQB= PR0101CA0011.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 6 3/6/2019 2:13:22 PM YQBPR0101CA0011.CANPRD01.PROD.OUTLOOK.COM YT1PR01MB24= 43.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 3/6/2019 2:13:23 PM CAN01-TO1-obe.outbound.protection.outlook.com QB1CAN01FT0= 03.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 8 3/6/2019 2:13:23 PM QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com YTO= PR0101CA0053.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) * 9 3/6/2019 2:13:23 PM YTOPR0101CA0053.CANPRD01.PROD.OUTLOOK.COM YQXPR0101MB= 1816.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers
Received: from YTOPR0101CA0053.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00:14::30) by YQXPR0101MB1816.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:1d::33) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Wed, 6 M= ar 2019 14:13:23 +0000 Received: from QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5c::204) by YTOPR0101CA0053.outlook.office365.com (2603:10b6:b00:14::30) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:13:23 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.61.52) smtp.mailfrom=3Dbounces.academicexperts.org; rockyview.ab.ca; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;rockyview.ab.ca; dmarc=3Dpass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpa= ss reason=3D100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.61.52 as permitted sender) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (104.47.61.52)= by QB1CAN01FT003.mail.protection.outlook.com (10.152.120.124) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1643.11 via Frontend Transport; Wed, 6 Mar 2019 14:13:23 +0000 Received: from YQBPR0101CA0011.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00::24= ) by YT1PR01MB2443.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:2::33) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.17; Wed, 6 M= ar 2019 14:13:22 +0000 Received: from TO1CAN01FT010.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5d::204) by YQBPR0101CA0011.outlook.office365.com (2603:10b6:c00::24) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.17 via Front= end Transport; Wed, 6 Mar 2019 14:13:22 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.60.53) smtp.mailfrom=3Dbounces.academicexperts.org; rockyview.ab.ca; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;rockyview.ab.ca; dmarc=3Dpass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpa= ss reason=3D100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.60.53 as permitted sender) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (104.47.60.53)= by TO1CAN01FT010.mail.protection.outlook.com (10.152.122.137) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1643.11 via Frontend Transport; Wed, 6 Mar 2019 14:13:22 +0000 Received: from YTOPR0101CA0065.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00:14::42) by YTXPR0101MB1824.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00:4::14) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.16; Wed, 6 M= ar 2019 14:13:21 +0000 Received: from QB1CAN01FT006.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5c::200) by YTOPR0101CA0065.outlook.office365.com (2603:10b6:b00:14::42) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.18 via Front= end Transport; Wed, 6 Mar 2019 14:13:21 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.99) smtp.mailfrom=3Dbounces.academicexperts.org; rockyview.ab.ca; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;rockyview.ab.ca; 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.99 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.99; helo=3Da8-99.smtp-out.amazonses.com; Received: from a8-99.smtp-out.amazonses.com (54.240.8.99) by QB1CAN01FT006.mail.protection.outlook.com (10.152.120.66) 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; Wed, 6 Mar 2019 14:13:20 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551881600; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DZu+Itk1TkzxFjfy5uMG3EEzXGuVYkU1Ddxg/lYhi7DY=3D; b=3DMQrLYzwXRZOBPF1Y+7hpLZHA4vdLyWL4tlTMQeuuz8Qzk+ayyXm0aXTIDXpIAhc= m 6wsa39Y+uMoLoVU7tGW7qyZMuhYicbFb1s5mCq7ks0oq8Ek7kQWrJC9LrOB0FpPiJp7 aKfqcjWz1FGhMOmuxQFIvpSso40Z+sKa3ZJmVPSE=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155188= 1600; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DZu+Itk1TkzxFjfy5uMG3EEzXGuVYkU1Ddxg/lYhi7DY=3D; b=3DJeNvw3vcjdSlNubppivnNzJu3HtW4BlFTJA2EIa8NXk8NmmJOXsxCbHBiHNvu6o= Z XXrELnaTqekUhFfhcalPK0I6F3wFr+cit2TlurbNrysYK7txP5LF7tN3xc2KPXBYfG0 ZtTNNLFbxl2FOrLghQOVeOVKKU2GThF9FYAcPznU=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D33431734383041401= 50=3D=3D" MIME-Version: 1.0 Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to Kathy.Wood@ashford.edu couldn't be delivered.
Kathy.Wood wasn't found at ashford.edu.
01000169535a3f71-334. . . Office 365 Kathy.Wood 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: 3/6/2019 2:13:37 PM Sender Address: 01000169535a3f71-3342a936-e382-47e7-8ce8-dadc3c5b3822-00000= 0@bounces.academicexperts.org Recipient Address: Kathy.Wood@ashford.edu Subject: EXT - Assessment/E-Folios: SIG Co-chair Nomination 2019
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= SN1NAM02FT060.eop-nam02.prod.protection.outlook.com] DSN generated by: DM6PR08MB5500.namprd08.prod.outlook.com Remote server: SN1NAM02FT060.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/6/2019 2:13:37 PM a8-40.smtp-out.amazonses.com BL2NAM02FT030.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 3/6/2019 2:13:37 PM BL2NAM02FT030.eop-nam02.prod.protection.outlook.com DM6= PR08CA0033.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 3/6/2019 2:13:38 PM DM6PR08CA0033.namprd08.prod.outlook.com BYASPR01MB0029.namp= rd08.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 4 3/6/2019 2:13:42 PM NAM04-CO1-obe.outbound.protection.outlook.com BL2NAM02FT0= 39.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 4 sec 5 3/6/2019 2:13:42 PM BL2NAM02FT039.eop-nam02.prod.protection.outlook.com MWH= PR08CA0021.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 6 3/6/2019 2:13:43 PM MWHPR08CA0021.namprd08.prod.outlook.com DM6PR08MB5722.nampr= d08.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 3/6/2019 2:13:44 PM NAM04-SN1-obe.outbound.protection.outlook.com BL2NAM02FT0= 50.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 8 3/6/2019 2:13:44 PM BL2NAM02FT050.eop-nam02.prod.protection.outlook.com DM6= PR08CA0033.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 9 3/6/2019 2:13:44 PM DM6PR08CA0033.namprd08.prod.outlook.com DM6PR08MB5500.nampr= d08.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers
Received: from DM6PR08CA0033.namprd08.prod.outlook.com (2603:10b6:5:80::46)= by DM6PR08MB5500.namprd08.prod.outlook.com (2603:10b6:5:103::29) with Microso= ft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.1686.18; Wed, 6 Mar 2019 14:13:44 +0000 Received: from BL2NAM02FT050.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e46::209) by DM6PR08CA0033.outlook.office365.com (2603:10b6:5:80::46) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.17 via Front= end Transport; Wed, 6 Mar 2019 14:13:44 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.44.54) smtp.mailfrom=3Dbounces.academicexperts.org; ashford.edu; dkim=3Dfail (sig= nature did not verify) header.d=3Dacademicexperts.org;ashford.edu; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D0= 01 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.44.54 as permitted sender) Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.54)= by BL2NAM02FT050.mail.protection.outlook.com (10.152.77.101) 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; Wed, 6 Mar 2019 14:13:44 +0000 Received: from MWHPR08CA0021.namprd08.prod.outlook.com (2603:10b6:301:5f::3= 4) by DM6PR08MB5722.namprd08.prod.outlook.com (2603:10b6:5:179::22) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Wed, 6 M= ar 2019 14:13:43 +0000 Received: from BL2NAM02FT039.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e46::207) by MWHPR08CA0021.outlook.office365.com (2603:10b6:301:5f::34) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.18 via Front= end Transport; Wed, 6 Mar 2019 14:13:42 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.45.54) smtp.mailfrom=3Dbounces.academicexperts.org; ashford.edu; dkim=3Dfail (sig= nature did not verify) header.d=3Dacademicexperts.org;ashford.edu; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D0= 01 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.45.54 as permitted sender) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.54)= by BL2NAM02FT039.mail.protection.outlook.com (10.152.77.152) 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; Wed, 6 Mar 2019 14:13:42 +0000 Received: from DM6PR08CA0033.namprd08.prod.outlook.com (2603:10b6:5:80::46)= by BYASPR01MB0029.namprd08.prod.outlook.com (2603:10b6:a03:75::10) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Wed, 6 M= ar 2019 14:13:38 +0000 Received: from BL2NAM02FT030.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e46::205) by DM6PR08CA0033.outlook.office365.com (2603:10b6:5:80::46) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.17 via Front= end Transport; Wed, 6 Mar 2019 14:13:37 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.40) smtp.mailfrom=3Dbounces.academicexperts.org; ashford.edu; dkim=3Dpass (sig= nature was verified) header.d=3Dacademicexperts.org;ashford.edu; dmarc=3Dpass action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D1= 00 Received-SPF: Pass (protection.outlook.com: domain of bounces.academicexperts.org designates 54.240.8.40 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.40; helo=3Da8-40.smtp-out.amazonses.com; Received: from a8-40.smtp-out.amazonses.com (54.240.8.40) by BL2NAM02FT030.mail.protection.outlook.com (10.152.77.172) 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; Wed, 6 Mar 2019 14:13:37 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551881617; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3D7cTVmGq+8UtQ1XhhO0V3gdgXS/y79HtbUxsiJ+6dOtc=3D; b=3DaE4wW0DqivtV/fhBnsTeAW1N0nVOTKbX4tDx+Xv4gwgHUUT1UXSxEMqxBMGAu6G= P InvYUqQF43wAPl/QWu4lr2uqLNeemZPAkkVz6bqmyCFxrXJ/9/kbuvaa2kPzV8oMWvk 66Zw+XlxAKKBc9T2B25HK/JqwERtLTecj8u4kFn0=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155188= 1617; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3D7cTVmGq+8UtQ1XhhO0V3gdgXS/y79HtbUxsiJ+6dOtc=3D; b=3DAE71k97x0SuahKRcxbyFUpJTSF7nJGxKs/N1skb8YkFYTi7ImeRUtgZ/GNbEfCl= X JVG6WL2IW4RiQkMnjQm+GjHbWCdDxZ6nq8dMuXZI0u0QJTj40AGplxgvg6bjzwknYh9 Yc9WORhYA6wNldNUATLeAZitNDbl0iYKUOFqnLXA=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D62709109966748494= 72=3D=3D" MIME-Version: 1.0 Subject: EXT - Assessment/E-Folios: SIG Co-chair Nomination 2019
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to griffina@uncw.edu couldn't be delivered.
griffina wasn't found at uncw.edu.
01000169535a9064-4a5. . . Office 365 griffina 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: 3/6/2019 2:13:58 PM Sender Address: 01000169535a9064-4a5c1a2f-2310-4d67-8d27-4d8073f30b21-00000= 0@bounces.academicexperts.org Recipient Address: griffina@uncw.edu Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= BY2NAM05FT034.eop-nam05.prod.protection.outlook.com] DSN generated by: BYAPR06MB5781.namprd06.prod.outlook.com Remote server: BY2NAM05FT034.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/6/2019 2:13:58 PM a8-40.smtp-out.amazonses.com CO1NAM05FT052.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 3/6/2019 2:13:59 PM CO1NAM05FT052.eop-nam05.prod.protection.outlook.com CY4= PR06CA0045.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 3 3/6/2019 2:13:59 PM CY4PR06CA0045.namprd06.prod.outlook.com MN2PR06MB5789.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 3/6/2019 2:14:00 PM NAM04-SN1-obe.outbound.protection.outlook.com DM3NAM05FT0= 12.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 5 3/6/2019 2:14:01 PM DM3NAM05FT012.eop-nam05.prod.protection.outlook.com DM6= PR06CA0011.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 6 3/6/2019 2:14:01 PM DM6PR06CA0011.namprd06.prod.outlook.com MN2PR06MB5791.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) * 7 3/6/2019 2:14:02 PM NAM01-BN3-obe.outbound.protection.outlook.com CO1NAM05FT0= 40.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 8 3/6/2019 2:14:03 PM CO1NAM05FT040.eop-nam05.prod.protection.outlook.com DM6= PR06CA0005.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 9 3/6/2019 2:14:03 PM DM6PR06CA0005.namprd06.prod.outlook.com BYAPR06MB5781.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers
Received: from DM6PR06CA0005.namprd06.prod.outlook.com (2603:10b6:5:120::18= ) by BYAPR06MB5781.namprd06.prod.outlook.com (2603:10b6:a03:151::14) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.16; Wed, 6 M= ar 2019 14:14:03 +0000 Received: from CO1NAM05FT040.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::201) by DM6PR06CA0005.outlook.office365.com (2603:10b6:5:120::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:14:03 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.33.55) smtp.mailfrom=3Dbounces.academicexperts.org; uncw.edu; dkim=3Dfail (body h= ash did not verify) header.d=3Dacademicexperts.org;uncw.edu; dmarc=3Dfail action= =3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D001 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.33.55 as permitted sender) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (104.47.33.55)= by CO1NAM05FT040.mail.protection.outlook.com (10.152.96.153) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1686.5 via Frontend Transport; Wed, 6 Mar 2019 14:14:02 +0000 Received: from DM6PR06CA0011.namprd06.prod.outlook.com (2603:10b6:5:120::24= ) by MN2PR06MB5791.namprd06.prod.outlook.com (2603:10b6:208:126::20) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Wed, 6 M= ar 2019 14:14:01 +0000 Received: from DM3NAM05FT012.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::203) by DM6PR06CA0011.outlook.office365.com (2603:10b6:5:120::24) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:14:01 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.44.59) smtp.mailfrom=3Dbounces.academicexperts.org; uncw.edu; dkim=3Dfail (body h= ash did not verify) header.d=3Dacademicexperts.org;uncw.edu; dmarc=3Dfail action= =3Dnone header.from=3Dacademicexperts.org;compauth=3Dfail reason=3D001 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.44.59 as permitted sender) Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.59)= by DM3NAM05FT012.mail.protection.outlook.com (10.152.98.121) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1686.5 via Frontend Transport; Wed, 6 Mar 2019 14:14:00 +0000 Received: from CY4PR06CA0045.namprd06.prod.outlook.com (2603:10b6:903:77::3= 1) by MN2PR06MB5789.namprd06.prod.outlook.com (2603:10b6:208:12c::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Wed, 6 M= ar 2019 14:13:59 +0000 Received: from CO1NAM05FT052.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::205) by CY4PR06CA0045.outlook.office365.com (2603:10b6:903:77::31) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1686.16 via Front= end Transport; Wed, 6 Mar 2019 14:13:59 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.40) smtp.mailfrom=3Dbounces.academicexperts.org; uncw.edu; dkim=3Dpass (signat= ure was verified) header.d=3Dacademicexperts.org;uncw.edu; dmarc=3Dpass action=3Dn= one header.from=3Dacademicexperts.org;compauth=3Dpass reason=3D100 Received-SPF: Pass (protection.outlook.com: domain of bounces.academicexperts.org designates 54.240.8.40 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.40; helo=3Da8-40.smtp-out.amazonses.com; Received: from a8-40.smtp-out.amazonses.com (54.240.8.40) by CO1NAM05FT052.mail.protection.outlook.com (10.152.96.168) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1686.5 via Frontend Transport; Wed, 6 Mar 2019 14:13:58 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551881638; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3D4cJtMg8wyzOCVAkdTVwKmNpbV/qUD42Gu78FtsZM+C0=3D; b=3DMIWKpL0p/KL9TeBQ1GTq9HPlpFbDiLQuj8m28CuW990vigvoPBWjiID7xetT8pf= l UySVBkxIDI+LoC4b+8wuKtwlHfIX46T9RgjAhEKdAU7ooBRTLFfw+JM/PBCPchVxJ3L ZYtsdMzD3jUCi0qtXrI/0+5OheXC2QXE0W8fRohE=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155188= 1638; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3D4cJtMg8wyzOCVAkdTVwKmNpbV/qUD42Gu78FtsZM+C0=3D; b=3DMHshbdzN4gTQhSN9CXdChlRI4M7XNHnfegmu6jxiWNdJ7vaKc9akJJBMl+bmU/r= W jMfNe+08vlRbPlrO1gQ1YAwmKn91rtu/dQhKWPoiEf6mII2k80VPVkUX+tvXDte+3T9 1jxKUbRFD0RWul3qwWz4hhLgKBtx0A0XfI85nTNs=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D41895701590555536= 15=3D=3D" MIME-Version: 1.0 Subject: Assessment/E-Folios: SIG Co-chair Nomination 2019
Posted
An error occurred while trying to deliver the mail to the following recipients: d.mona2010aljohani@gamil.com
Posted
An error occurred while trying to deliver the mail to the following recipients: ssilveri@silveriacademy.org
Posted
An error occurred while trying to deliver the mail to the following recipients: James.Telese@utb.edu
Posted
An error occurred while trying to deliver the mail to the following recipients: dkanter@calvertsercvices.org
Posted
This is the mail system at host mail.palaumoe.net.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to
If you do so, please include this problem report. You can delete your own text from the attached returned message.
<marciainacio@palaumoe.net>: host mail.palaumoe.net[/var/lib/imap/socket/lmtp] said: 452 4.2.2 Over quota (in reply to RCPT TO command)
Posted