CFP: ACM special issue on computational thinking
Dear CT SIG members,
I hope you are doing well. I would like to share the call for proposal for a ACM special issue on computational thinking.
The ACM and Robin Hood are co-funding a special ACM publication dedicated entirely to research on integrating computational thinking across K-12 learning disciplines including math, ELA, science, and computer science. Although we encourage empirical research from all K-12 levels, most articles will focus on the elementary levels of K-5. This can include, but is not limited to in-service elementary professional development, elementary preservice teacher education, K-5 (in all subject areas). The issue will focus specifically on existing and potential efforts that provide empirically-based evidence of how to integrate CT into K-5 practices.
You can see the call for proposals and abstract submission by visiting this link
If you have any questions, please reach out to the co-editors Anne Leftwich (aleftwic@indiana.edu) and Aman Yadav (ayadav@msu.edu).
Thank you.
CT SIG co-chairs, Gerald and Jongpil
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 lamkinsj@bolles.org couldn't be delivered. lamkinsj wasn't found at bolles.org. 01000174f53d213a-d0d. . . 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: 10/4/2020 8:10:58 PM Sender Address: 01000174f53d213a-d0ddbc4b-b584-404a-84fd-0dc3bf7bd6ea-00000= 0@bounces.academicexperts.org Recipient Address: lamkinsj@bolles.org Subject: Computational Thinking: CFP: ACM special issue on computati= onal thinking
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= CY1NAM02FT040.eop-nam02.prod.protection.outlook.com] DSN generated by: BN6PR06MB2611.namprd06.prod.outlook.com Remote server: CY1NAM02FT040.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 10/4/2020 8:10:59 PM a48-132.smtp-out.amazonses.com SN1NAM02FT028.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 10/4/2020 8:10:59 PM SN1NAM02FT028.eop-nam02.prod.protection.outlook.com SN4= PR0501CA0005.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 10/4/2020 8:10:59 PM SN4PR0501CA0005.namprd05.prod.outlook.com BLAPR06MB69= 78.namprd06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 10/4/2020 8:11:00 PM NAM11-BN8-obe.outbound.protection.outlook.com BL2NAM02FT0= 56.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 10/4/2020 8:11:00 PM BL2NAM02FT056.eop-nam02.prod.protection.outlook.com MN2= PR22CA0013.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 6 10/4/2020 8:11:01 PM MN2PR22CA0013.namprd22.prod.outlook.com BYAPR06MB4773.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 10/4/2020 8:11:03 PM NAM02-BL2-obe.outbound.protection.outlook.com CY1NAM02FT0= 38.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec 8 10/4/2020 8:11:03 PM CY1NAM02FT038.eop-nam02.prod.protection.outlook.com CY4= PR21CA0024.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 9 10/4/2020 8:11:04 PM CY4PR21CA0024.namprd21.prod.outlook.com BN6PR06MB2611.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 CY4PR21CA0024.namprd21.prod.outlook.com (2603:10b6:903:dd::3= 4) by BN6PR06MB2611.namprd06.prod.outlook.com (2603:10b6:404:57::10) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.36; Sun, 4 O= ct 2020 20:11:04 +0000 Received: from CY1NAM02FT038.eop-nam02.prod.protection.outlook.com (2603:10b6:903:dd:cafe::13) by CY4PR21CA0024.outlook.office365.com (2603:10b6:903:dd::34) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.9 via Fronte= nd Transport; Sun, 4 Oct 2020 20:11:03 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.38.56) smtp.mailfrom=3Dbounces.academicexperts.org; bolles.org; dkim=3Dfail (body= hash did not verify) header.d=3Dacademicexperts.org;bolles.org; 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.38.56 as permitted sender) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.56)= by CY1NAM02FT038.mail.protection.outlook.com (10.152.74.217) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) = id 15.20.3433.39 via Frontend Transport; Sun, 4 Oct 2020 20:11:03 +0000 Received: from MN2PR22CA0013.namprd22.prod.outlook.com (2603:10b6:208:238::= 18) by BYAPR06MB4773.namprd06.prod.outlook.com (2603:10b6:a03:4e::25) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.38; Sun, 4 O= ct 2020 20:11:01 +0000 Received: from BL2NAM02FT056.eop-nam02.prod.protection.outlook.com (2603:10b6:208:238:cafe::8b) by MN2PR22CA0013.outlook.office365.com (2603:10b6:208:238::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.35 via Front= end Transport; Sun, 4 Oct 2020 20:11:00 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.58.169= ) smtp.mailfrom=3Dbounces.academicexperts.org; bolles.org; dkim=3Dfail (body= hash did not verify) header.d=3Dacademicexperts.org;bolles.org; 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.58.169 as permitted sender) Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.169= ) by BL2NAM02FT056.mail.protection.outlook.com (10.152.77.221) with Microsof= t SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3433.39 via Frontend Transport; Sun, 4 Oct 2020 20:11:00 +0000 Received: from SN4PR0501CA0005.namprd05.prod.outlook.com (2603:10b6:803:40::18) by BLAPR06MB6978.namprd06.prod.outlook.com (2603:10b6:208:295::12) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.35; Sun, 4 O= ct 2020 20:10:59 +0000 Received: from SN1NAM02FT028.eop-nam02.prod.protection.outlook.com (2603:10b6:803:40:cafe::a0) by SN4PR0501CA0005.outlook.office365.com (2603:10b6:803:40::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.13 via Front= end Transport; Sun, 4 Oct 2020 20:10:59 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.48.132) 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.48.132 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.48.132; helo=3Da48-132.smtp-out.amazonses.com; Received: from a48-132.smtp-out.amazonses.com (54.240.48.132) by SN1NAM02FT028.mail.protection.outlook.com (10.152.72.105) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.3433.39 via Frontend Transport; Sun, 4 Oct 2020 20:10:59 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1601842258; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3Dbk5YYfqgi/ZyjptFVB6UkH98T5Tsbxc2kuMkybD+zi4=3D; b=3Dn5DJQM/0rqUh6Nnl1K8/2gVnfIL9P6AT7ONMEmoc0iqxGYudvpPsR+k+wY5A+7I= x bb6gJrHIreME8xF0TaMrUnq1L0DFL8tfGknM8KLDmfpqv/m8OP4U/hJU2GlPOsAkmaj 6srZMHvnJGqfmvhYFcn6YNU6L+CrTPEyh6PeKpR8=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D160184= 2258; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3Dbk5YYfqgi/ZyjptFVB6UkH98T5Tsbxc2kuMkybD+zi4=3D; b=3DY7ex1k6o4VRK+slSX1Eco2EsiKlles161BAqDJ7roQ5o686sh69IrM7L5IDE7cU= N XF63itwEPUU2Fpjsu6tJlb7L8kAt4Cxk9wDV1jZDhK6coi86bdGBmAfV3SeswIaAw69 E0k7EqIltCsDbiIRok7terGaaNmDDeUmZ7E19IzI=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D53105904821071309= 75=3D=3D" MIME-Version: 1.0 Subject: Computational Thinking: CFP: ACM special issue on computational thinking
Posted
An error occurred while trying to deliver the mail to the following recipients: iva.moss-redman@fremont38.com
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to gordoncr@uncw.edu couldn't be delivered. gordoncr wasn't found at uncw.edu. 01000174f53d82f6-dc7. . . Office 365 gordoncr 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: 10/4/2020 8:11:23 PM Sender Address: 01000174f53d82f6-dc709026-934c-4dae-87e1-14fffd9bc6f8-00000= 0@bounces.academicexperts.org Recipient Address: gordoncr@uncw.edu Subject: Computational Thinking: CFP: ACM special issue on computati= onal thinking
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= DM3NAM05FT038.eop-nam05.prod.protection.outlook.com] DSN generated by: CY4PR06MB3287.namprd06.prod.outlook.com Remote server: DM3NAM05FT038.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 10/4/2020 8:11:24 PM a8-99.smtp-out.amazonses.com CO1NAM05FT058.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 10/4/2020 8:11:25 PM CO1NAM05FT058.eop-nam05.prod.protection.outlook.com MW2= PR16CA0035.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 3 10/4/2020 8:11:25 PM MW2PR16CA0035.namprd16.prod.outlook.com CY4PR06MB3429.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 10/4/2020 8:11:26 PM NAM12-BN8-obe.outbound.protection.outlook.com DM3NAM05FT0= 48.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 10/4/2020 8:11:26 PM DM3NAM05FT048.eop-nam05.prod.protection.outlook.com DM5= PR07CA0137.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 6 10/4/2020 8:11:26 PM DM5PR07CA0137.namprd07.prod.outlook.com MWHPR06MB3150.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 10/4/2020 8:11:28 PM NAM10-DM6-obe.outbound.protection.outlook.com DM3NAM05FT0= 51.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec 8 10/4/2020 8:11:28 PM DM3NAM05FT051.eop-nam05.prod.protection.outlook.com DM3= PR12CA0086.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 9 10/4/2020 8:11:28 PM DM3PR12CA0086.namprd12.prod.outlook.com CY4PR06MB3287.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 DM3PR12CA0086.namprd12.prod.outlook.com (2603:10b6:0:57::30)= by CY4PR06MB3287.namprd06.prod.outlook.com (2603:10b6:910:56::33) with Micros= oft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3433.32; Sun, 4 Oct 2020 20:11:28 +0000 Received: from DM3NAM05FT051.eop-nam05.prod.protection.outlook.com (2603:10b6:0:57:cafe::7d) by DM3PR12CA0086.outlook.office365.com (2603:10b6:0:57::30) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34 via Front= end Transport; Sun, 4 Oct 2020 20:11:28 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.58.106) 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.58.106 as permitted sender) Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.106= ) by DM3NAM05FT051.mail.protection.outlook.com (10.152.98.165) with Microsof= t SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3455.13 via Frontend Transport; Sun, 4 Oct 2020 20:11:28 +0000 Received: from DM5PR07CA0137.namprd07.prod.outlook.com (2603:10b6:3:13e::27= ) by MWHPR06MB3150.namprd06.prod.outlook.com (2603:10b6:301:3d::17) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Sun, 4 O= ct 2020 20:11:26 +0000 Received: from DM3NAM05FT048.eop-nam05.prod.protection.outlook.com (2603:10b6:3:13e:cafe::de) by DM5PR07CA0137.outlook.office365.com (2603:10b6:3:13e::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.37 via Front= end Transport; Sun, 4 Oct 2020 20:11:26 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.55.176= ) 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.55.176 as permitted sender) Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.176= ) by DM3NAM05FT048.mail.protection.outlook.com (10.152.98.162) with Microsof= t SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3455.13 via Frontend Transport; Sun, 4 Oct 2020 20:11:26 +0000 Received: from MW2PR16CA0035.namprd16.prod.outlook.com (2603:10b6:907::48) = by CY4PR06MB3429.namprd06.prod.outlook.com (2603:10b6:910:55::38) with Micros= oft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3433.42; Sun, 4 Oct 2020 20:11:25 +0000 Received: from CO1NAM05FT058.eop-nam05.prod.protection.outlook.com (2603:10b6:907:0:cafe::9c) by MW2PR16CA0035.outlook.office365.com (2603:10b6:907::48) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.20 via Front= end Transport; Sun, 4 Oct 2020 20:11:25 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.99) 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.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 CO1NAM05FT058.mail.protection.outlook.com (10.152.96.176) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.3455.13 via Frontend Transport; Sun, 4 Oct 2020 20:11:24 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1601842283; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DqS6UJ3Cfv6Q+UAs9P9nwpFw+B1IxKGhHrxdh3LKpefA=3D; b=3DLvJpHrNEz6HGnvrRHcKtTwlJqzVG60Khwu2r57hdAtP89trU/NCVeyDxcv0DUYC= 3 01VYf5fimLKxreWwOpnorAG5A25USlOOK2f9EU7QEFCxgRj7SLo/dHy6ZR8fdm9nuBP 6PgehIF6WzAVcGAhJqo242TYsuicDgoLuB7nx1q8=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D160184= 2283; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DqS6UJ3Cfv6Q+UAs9P9nwpFw+B1IxKGhHrxdh3LKpefA=3D; b=3DcXrYZUlreHX3y4isj++aFdyT7HapirgjGLFk2lD1a8pqw/iwhypv8jcCodPA8yc= i ZQtZBSb4h+I65FJi2qZXLlfzewQhcwgRbYC4T+6ebE41jYx5C681nt9/m82Crqo2r3a Fr3qvM4FlhQ/kxg7vp55jf9k1tMkLyv1LiQn0kBI=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D39652697187215921= 56=3D=3D" MIME-Version: 1.0 Subject: Computational Thinking: CFP: ACM special issue on computational thinking
Posted
An error occurred while trying to deliver the mail to the following recipients: mskolodz@pepperdine.edu
Posted
NOTICE: Delivery Failure.
This Delivery Status Notification is sent from MTA...
Your delivery to the following address has been failed. Please refer to the below for details.
Delivery failed: gosyhong@kaist.ac.kr 143.248.5.130 does not like recipient. Remote host said[Response Message]: 550 Account disabled gosyhong@kaist.ac.kr Giving up on 143.248.5.130. STEP: RCPT TO
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: aali@uwlax.edu
Posted
An error occurred while trying to deliver the mail to the following recipients: neohao@uga.edu
Posted
Your message about "Computational Thinking: CFP: ACM special issue on computational thinking" was waitlisted. Please add yourself to my Guest List so your messages will be delivered to my Inbox. Use the link below.
Follow this link to deliver your message https://www.boxbe.com/crs?tc_serial=53496348459&tc_rand=278917598&utm_source=stf&utm_medium=email&utm_campaign=CN_STDW_v6&utm_content=001
Thank you, nemati_mahboobeh@yahoo.com
Posted