Special Education & Assistive Technologies
Special Interest Group
Assistive Technology SIG is very motivated to increase the knowledge and use of assistive technology for special populations.
Chair:
SITE Conference. Assistive Technology Co-Chair Position
Hello to all! The SITE Conference is quickly approaching. With this in mind, we will need to elect a new co-chair for the AT SIG. The election will take place at the conference. However, I would like to recruit individuals who would be interested in this leadership position. If you are interested, please send me a quick email and a short statement about your interest in being a Co-Chair.
Hope to see many of you at the conference.
Debra Bauder, AT SIG Co-Chair
debra.bauder@louisville.edu
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: edalton@techaccess-ri.org
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to inglej@easternct.edu couldn't be delivered.
inglej wasn't found at easternct.edu.
010001692b113ba6-8c0. . . Office 365 inglej 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 6:29:03 PM Sender Address: 010001692b113ba6-8c0d515f-a906-4ded-8210-b34e43ca5011-00000= 0@bounces.academicexperts.org Recipient Address: inglej@easternct.edu Subject: Assistive Technologies & Special Education: SITE Conference= . Assistive Technology Co-Chair Position
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= BN3NAM04FT014.eop-NAM04.prod.protection.outlook.com] DSN generated by: CY1PR0201MB1833.namprd02.prod.outlook.com Remote server: BN3NAM04FT014.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 2/26/2019 6:29:04 PM a8-40.smtp-out.amazonses.com SN1NAM04FT038.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 6:29:04 PM SN1NAM04FT038.eop-NAM04.prod.protection.outlook.com DM6= PR02CA0038.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 2/26/2019 6:29:04 PM DM6PR02CA0038.namprd02.prod.outlook.com BYAPR02MB5926.nampr= d02.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 2/26/2019 6:29:07 PM NAM04-CO1-obe.outbound.protection.outlook.com SN1NAM04FT0= 47.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 sec 5 2/26/2019 6:29:07 PM SN1NAM04FT047.eop-NAM04.prod.protection.outlook.com SN4= PR0201CA0072.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 6 2/26/2019 6:29:08 PM SN4PR0201CA0072.namprd02.prod.outlook.com DM6PR02MB59= 30.namprd02.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 2/26/2019 6:29:09 PM NAM02-CY1-obe.outbound.protection.outlook.com SN1NAM04FT0= 47.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 6:29:09 PM SN1NAM04FT047.eop-NAM04.prod.protection.outlook.com SN4= PR0201CA0072.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 9 2/26/2019 6:29:10 PM SN4PR0201CA0072.namprd02.prod.outlook.com CY1PR0201MB= 1833.namprd02.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 SN4PR0201CA0072.namprd02.prod.outlook.com (2603:10b6:803:20::34) by CY1PR0201MB1833.namprd02.prod.outlook.com (2a01:111:e400:527c::30) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.14; Tue, 26 = Feb 2019 18:29:10 +0000 Received: from SN1NAM04FT047.eop-NAM04.prod.protection.outlook.com (2a01:111:f400:7e4c::200) by SN4PR0201CA0072.outlook.office365.com (2603:10b6:803:20::34) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.16 via Front= end Transport; Tue, 26 Feb 2019 18:29:09 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.37.57) smtp.mailfrom=3Dbounces.academicexperts.org; myeasternct.mail.onmicrosoft.= com; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;myeasternct.mail.onmicrosoft.com; dmarc=3Dp= ass 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.57 as permitted sender) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (104.47.37.57)= by SN1NAM04FT047.mail.protection.outlook.com (10.152.89.225) 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 18:29:09 +0000 Received: from SN4PR0201CA0072.namprd02.prod.outlook.com (2603:10b6:803:20::34) by DM6PR02MB5930.namprd02.prod.outlook.com (2603:10b6:5:153::26) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.18; Tue, 26 = Feb 2019 18:29:08 +0000 Received: from SN1NAM04FT047.eop-NAM04.prod.protection.outlook.com (2a01:111:f400:7e4c::200) by SN4PR0201CA0072.outlook.office365.com (2603:10b6:803:20::34) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.16 via Front= end Transport; Tue, 26 Feb 2019 18:29:07 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.45.50) smtp.mailfrom=3Dbounces.academicexperts.org; myeasternct.mail.onmicrosoft.= com; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;myeasternct.mail.onmicrosoft.com; dmarc=3Dp= ass 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.45.50 as permitted sender) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.50)= by SN1NAM04FT047.mail.protection.outlook.com (10.152.89.225) 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 18:29:07 +0000 Received: from DM6PR02CA0038.namprd02.prod.outlook.com (2603:10b6:5:177::15= ) by BYAPR02MB5926.namprd02.prod.outlook.com (2603:10b6:a03:123::25) 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 18:29:04 +0000 Received: from SN1NAM04FT038.eop-NAM04.prod.protection.outlook.com (2a01:111:f400:7e4c::206) by DM6PR02CA0038.outlook.office365.com (2603:10b6:5:177::15) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1622.16 via Front= end Transport; Tue, 26 Feb 2019 18:29:04 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.40) smtp.mailfrom=3Dbounces.academicexperts.org; easternct.edu; dkim=3Dpass (signature was verified) header.d=3Dacademicexperts.org;easternct.edu; 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.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 SN1NAM04FT038.mail.protection.outlook.com (10.152.89.25) 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; Tue, 26 Feb 2019 18:29:04 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551205743; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DqXmP43JQSXzI5Uyt1pengc4PYw177THZK3SZK6ZkKxA=3D; b=3DHh2C0GgYVt9/mipEiXHCpy+0chbrth/OU4jX+ivaFietk8E+6WaNruZqIvmGp4H= a QmQLRMhPrExyRS/t0P8egY03mGK/sbUxzyIFIFXRwV7/99QBImp236c6VRnZZmdXmzV js3a7th95r83htb10ARC23kivstQhMrA0zSswKUQ=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155120= 5743; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DqXmP43JQSXzI5Uyt1pengc4PYw177THZK3SZK6ZkKxA=3D; b=3DTaAtvCPpFySVKXdu3i8iB5/rMecHg3jxTGCWK2thNLpks+BShvd3LNHkthZr2P8= x i3Indh+9OJX90aTUG5t3P3jIiaF6juzmSoqbottbXVa/Y7Ofzo1F8OQTxnuDKnuHQSu zyNeaDDBLXVVtrfMDwwnCrWpD3xMV/Evh1mVQVnw=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D47746443076497903= 20=3D=3D" MIME-Version: 1.0 Subject: Assistive Technologies & Special Education: SITE Conference. Assistive Technology Co-Chair Position
Posted
An error occurred while trying to deliver the mail to the following recipients: mgonzalez@marywood.edu
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.
010001692b1132e4-969. . . 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: 2/26/2019 6:29:01 PM Sender Address: 010001692b1132e4-9691b985-6f4e-40a1-950e-6aa31b4d096e-00000= 0@bounces.academicexperts.org Recipient Address: griffina@uncw.edu Subject: Assistive Technologies & Special Education: SITE Conference= . Assistive Technology Co-Chair Position
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= BY2NAM05FT029.eop-nam05.prod.protection.outlook.com] DSN generated by: MWHPR06MB2654.namprd06.prod.outlook.com Remote server: BY2NAM05FT029.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 2/26/2019 6:29:02 PM a8-44.smtp-out.amazonses.com BY2NAM05FT042.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 6:29:02 PM BY2NAM05FT042.eop-nam05.prod.protection.outlook.com MWH= PR06CA0030.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 2/26/2019 6:29:02 PM MWHPR06CA0030.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) 4 2/26/2019 6:29:04 PM NAM01-BY2-obe.outbound.protection.outlook.com BY2NAM05FT0= 27.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 6:29:04 PM BY2NAM05FT027.eop-nam05.prod.protection.outlook.com BN7= PR06CA0045.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 6 2/26/2019 6:29:04 PM BN7PR06CA0045.namprd06.prod.outlook.com BN8PR06MB5779.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 2/26/2019 6:29:07 PM NAM02-BL2-obe.outbound.protection.outlook.com BY2NAM05FT0= 35.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 3 sec 8 2/26/2019 6:29:07 PM BY2NAM05FT035.eop-nam05.prod.protection.outlook.com BN6= PR06CA0053.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) * 9 2/26/2019 6:29:08 PM BN6PR06CA0053.namprd06.prod.outlook.com MWHPR06MB2654.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 BN6PR06CA0053.namprd06.prod.outlook.com (2603:10b6:405:3a::4= 2) by MWHPR06MB2654.namprd06.prod.outlook.com (2603:10b6:300:4a::8) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.16; Tue, 26 = Feb 2019 18:29:08 +0000 Received: from BY2NAM05FT035.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::205) by BN6PR06CA0053.outlook.office365.com (2603:10b6:405:3a::42) 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 18:29:07 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.38.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.38.59 as permitted sender) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.59)= by BY2NAM05FT035.mail.protection.outlook.com (10.152.100.172) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1665.5 via Frontend Transport; Tue, 26 Feb 2019 18:29:07 +0000 Received: from BN7PR06CA0045.namprd06.prod.outlook.com (2603:10b6:408:34::2= 2) by BN8PR06MB5779.namprd06.prod.outlook.com (2603:10b6:408:c6::21) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.16; Tue, 26 = Feb 2019 18:29:04 +0000 Received: from BY2NAM05FT027.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::201) by BN7PR06CA0045.outlook.office365.com (2603:10b6:408:34::22) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1622.16 via Front= end Transport; Tue, 26 Feb 2019 18:29:04 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.34.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.34.59 as permitted sender) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (104.47.34.59)= by BY2NAM05FT027.mail.protection.outlook.com (10.152.100.164) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1665.5 via Frontend Transport; Tue, 26 Feb 2019 18:29:04 +0000 Received: from MWHPR06CA0030.namprd06.prod.outlook.com (2603:10b6:301:39::4= 3) 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.1643.14; Tue, 26 = Feb 2019 18:29:02 +0000 Received: from BY2NAM05FT042.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::206) by MWHPR06CA0030.outlook.office365.com (2603:10b6:301:39::43) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.16 via Front= end Transport; Tue, 26 Feb 2019 18:29:02 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.44) 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.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 BY2NAM05FT042.mail.protection.outlook.com (10.152.100.179) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA= 384) id 15.20.1665.5 via Frontend Transport; Tue, 26 Feb 2019 18:29:02 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551205741; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DH7Br7y/g93WY8MAxBNT8wFPaZuNRqK9k4k1FmzYVsvI=3D; b=3DALKhGQkQuf1moexLKXsK56mYDZ2KzIQzZN+0b9x/W4PSgvo+F4548rs0au3sMcH= Z sw4gun81BQFM3rVTbea2kpR6VySFhazzJNSK/C4wvwWghne61+IntOvYJ08AOGAUhQM ePHam3hmLo8GuW/AtAfXQ146S+ETiOTrpabWrfCk=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155120= 5741; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DH7Br7y/g93WY8MAxBNT8wFPaZuNRqK9k4k1FmzYVsvI=3D; b=3DcMe1DKFlVuYyWRy6tUfwHyalq8/75YuVBCsuDdBDxeW2mlxh7FJl0H7+LM0Kbgx= y RIEGzkwQw9xcAntirBb1gOgWK7Q/3hHU4msiSq7QkPs7IXiVQ2yjSjrhTL2kcaFMz0X QRsJo+f6XiqGetaMfrEyXE9LWwJtUNgz/H1liAZU=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D83830158627536761= 02=3D=3D" MIME-Version: 1.0 Subject: Assistive Technologies & Special Education: SITE Conference. Assistive Technology Co-Chair Position
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.
010001692b11cffd-d65. . . 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: 2/26/2019 6:29:41 PM Sender Address: 010001692b11cffd-d65ada5f-f743-4a03-baf6-3ec649092c8d-00000= 0@bounces.academicexperts.org Recipient Address: ajensdottir@rockyview.ab.ca Subject: Assistive Technologies & Special Education: SITE Conference= . Assistive Technology Co-Chair Position
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= TO1CAN01FT003.eop-CAN01.prod.protection.outlook.com] DSN generated by: YQXPR01MB3607.CANPRD01.PROD.OUTLOOK.COM Remote server: TO1CAN01FT003.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 2/26/2019 6:29:42 PM a8-40.smtp-out.amazonses.com QB1CAN01FT003.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 6:29:43 PM QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com YTX= PR0101CA0015.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 3 2/26/2019 6:29:43 PM YTXPR0101CA0015.CANPRD01.PROD.OUTLOOK.COM YTXPR0101MB= 0847.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 2/26/2019 6:29:43 PM CAN01-QB1-obe.outbound.protection.outlook.com QB1CAN01FT0= 06.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 5 2/26/2019 6:29:44 PM QB1CAN01FT006.eop-CAN01.prod.protection.outlook.com YTO= PR0101CA0049.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 6 2/26/2019 6:29:44 PM YTOPR0101CA0049.CANPRD01.PROD.OUTLOOK.COM YQXPR0101MB= 0837.CANPRD01.PROD.OUTLOOK.COM Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 2/26/2019 6:29:45 PM CAN01-QB1-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 2/26/2019 6:29:45 PM QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com YTX= PR0101CA0018.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 9 2/26/2019 6:29:45 PM YTXPR0101CA0018.CANPRD01.PROD.OUTLOOK.COM YQXPR01MB36= 07.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 YTXPR0101CA0018.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00::31= ) by YQXPR01MB3607.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:43::19) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.20; Tue, 26 = Feb 2019 18:29:45 +0000 Received: from QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5c::209) by YTXPR0101CA0018.outlook.office365.com (2603:10b6:b00::31) 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 18:29:45 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.60.61) 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.61 as permitted sender) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (104.47.60.61)= 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; Tue, 26 Feb 2019 18:29:45 +0000 Received: from YTOPR0101CA0049.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00:14::26) by YQXPR0101MB0837.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c00:18::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.14; Tue, 26 = Feb 2019 18:29:44 +0000 Received: from QB1CAN01FT006.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5c::204) by YTOPR0101CA0049.outlook.office365.com (2603:10b6:b00:14::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 18:29:44 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.60.89) 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.89 as permitted sender) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (104.47.60.89)= 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; Tue, 26 Feb 2019 18:29:43 +0000 Received: from YTXPR0101CA0015.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00::28= ) by YTXPR0101MB0847.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b00:5::30) 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 18:29:43 +0000 Received: from QB1CAN01FT003.eop-CAN01.prod.protection.outlook.com (2a01:111:f400:7e5c::205) by YTXPR0101CA0015.outlook.office365.com (2603:10b6:b00::28) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1643.16 via Front= end Transport; Tue, 26 Feb 2019 18:29:43 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.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: 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 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; Tue, 26 Feb 2019 18:29:42 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551205781; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DhV3/fNeVlHy0vz4m0Lj9UEwXc3UUFUnlEue64vbNhzA=3D; b=3DZ8xQitvA24vZH6hDv9ozhLkzawySnrUZh47zxj2zB9dDOjB0nlNAo0oRkf6azK0= / kS9mohwaqE9FgQhmULj0jeuVz8KwBTOe2Gjo4TJG2AW6v2e4EawNthwvWucVlu2L0qU rhO1JT0etTk5WXhNaShe5f6NrBeR5/aWkb6OMgRo=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155120= 5781; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DhV3/fNeVlHy0vz4m0Lj9UEwXc3UUFUnlEue64vbNhzA=3D; b=3DOTDs87JnMzoewlJGBzGoOOWtyOgPdVq9OJHvP1QY2zzKTElYgYgFdMBvlSGDTua= f KxB5N8nQK4+FGYJ2Vu/cqiANw21asQeuUQwHP7jlgazpSCZzeKjjqRdX5UWZxmELadS JFIwyPLTNunYT4QVp515zrckXMK4jp+bv1OiVLKo=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D56417745460741265= 98=3D=3D" MIME-Version: 1.0 Subject: Assistive Technologies & Special Education: SITE Conference. Assistive Technology Co-Chair Position
Posted
An error occurred while trying to deliver the mail to the following recipients: tahameister53@marianuniversity.edu
Posted
Delivery has failed to these recipients or groups:
mcferrin@nsula.edumcferrin@nsula.edu Your message couldn't be delivered to the recipient because you don't have = permission to send to it.
Ask the recipient's email admin to add you to the accept list for the recip= ient.
For more information, see DSN 5.7.129 Errors in Exchange Online and Office = 365https://go.microsoft.com/fwlink/?LinkId=3D389365.
Diagnostic information for administrators:
Generating server: DM5PR05MB3659.namprd05.prod.outlook.com
mcferrin@nsula.edu Remote Server returned '550 5.7.129 RESOLVER.RST.RestrictedToRecipientsPerm= ission; not authorized to send to recipient because the sender isn't on the= recipient's list of senders to accept mail from'
Original message headers:
Received: from BN6PR05CA0014.namprd05.prod.outlook.com (2603:10b6:405:39::2= 7) by DM5PR05MB3659.namprd05.prod.outlook.com (2603:10b6:4:3d::28) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.12; Tue, 26 = Feb 2019 18:29:59 +0000 Received: from CO1NAM05FT064.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::207) by BN6PR05CA0014.outlook.office365.com (2603:10b6:405:39::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1622.12 via Front= end Transport; Tue, 26 Feb 2019 18:29:59 +0000 Authentication-Results: spf=3Dpass (sender IP is 54.240.8.80) smtp.mailfrom=3Dbounces.academicexperts.org; nsula.edu; dkim=3Dpass (signa= ture was verified) header.d=3Dacademicexperts.org;nsula.edu; dmarc=3Dpass actio= n=3Dnone header.from=3Dacademicexperts.org; 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 CO1NAM05FT064.mail.protection.outlook.com (10.152.96.182) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.1665.5 via Frontend Transport; Tue, 26 Feb 2019 18:29:58 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dwqomk344gvrm3muyxnm2d4uc3vtooytb; d=3Dacademicexperts.org; t=3D1551205798; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DoV1TA3SdKeSGymjZ9o/KJhvLloigoALim1oeTzLdFCk=3D; b=3DSJ4okfg9UQtTHpPIYq22LYYqAGZOJA0Ilch+CwhLFN/+Ay+quH5Ygh1PGm/DKNp= E gYTUUzJMGihskwKvZVDK/XBB+6B0uX4Y83KxR9PjmX2Mr+DM+htuLU5ndcwBu2nDgHb cshvSoANCN5cOaSJiDMcnLPa2itgnrFvMvJt0Too=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=3Damazonses.com; t=3D155120= 5798; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DoV1TA3SdKeSGymjZ9o/KJhvLloigoALim1oeTzLdFCk=3D; b=3DASp29UKABVh/wJ1KKJamFdgOF0KSE9NfdxJitO2iYP8R9jBIpMoyajfMzT8MkNm= Y /bKLl/vtw5+Fr/q4TbBqwnrQKxNNM03MrRDNWrjLGvRqarD/VxSN5v+RW7UQG1Hh92i Q4bGZHlITbn6Hs6Bs0mztTNHYcsUr9GVy3MfI12o=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D08727574391207137= 27=3D=3D" MIME-Version: 1.0 Subject: Assistive Technologies & Special Education: SITE Conference. Assistive Technology Co-Chair Position
Posted
Thanks Deb. I have my hands full with the UDL SIG for one more year, but I do look forward to seeing you at SITE. I'm staying at the Flamingo, next to the Planet Hollywood, FYI. See you there! Betsy
Elizabeth M. Dalton, PhD Adjunct Professor, Dept. of Communicative Disorders, University of Rhode Island Principal Consultant, Dalton Education Services International (DESI) Co-Chair, Universal Design for Learning SIG, Society for Information Technology and Teacher Education (SITE) Director Emeritus, Development and Research, TechACCESS of Rhode Island Chair, Communications Committee, Unitarian Universalist Congregation of South County (UUCSC) elizabethmdalton@gmail.com @ElizabethDalt19 (Twitter) https://www.linkedin.com/in/elizabethmdalton http://www.scoop.it/t/udl-mobile-learning-and-assistive-technology
Posted
Debra, I have retired. Please take me off the list and best of luck to this SIG! Betty
Betty Nelson, Ph.D. Associate Professor, Retired UAB School of Education Scientist, Retired UAB School of Medicine University of Alabama at Birmingham
Posted
An error occurred while trying to deliver the mail to the following recipients: ssilveri@silveriacademy.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