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.
An error occurred while trying to deliver the mail to the following recipients: iva.moss-redman@fremont38.com
Posted
Delivery has failed to these recipients or groups:
cortiz29@hccfl.educortiz29@hccfl.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: CH2PR01MB6088.prod.exchangelabs.com
cortiz29@hccfl.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 BN6PR19CA0104.namprd19.prod.outlook.com (2603:10b6:404:a0::1= 8) by CH2PR01MB6088.prod.exchangelabs.com (2603:10b6:610:49::17) with Microso= ft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3433.35; Fri, 2 Oct 2020 20:35:32 +0000 Received: from BN3NAM04FT056.eop-NAM04.prod.protection.outlook.com (2603:10b6:404:a0:cafe::c9) by BN6PR19CA0104.outlook.office365.com (2603:10b6:404:a0::18) 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; Fri, 2 Oct 2020 20:35:31 +0000 Authentication-Results: spf=3Dpass (sender IP is 54.240.8.80) smtp.mailfrom=3Dbounces.academicexperts.org; hccfl.edu; dkim=3Dpass (signa= ture was verified) header.d=3Dacademicexperts.org;hccfl.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 BN3NAM04FT056.mail.protection.outlook.com (10.152.93.63) with Microsoft SM= TP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.3412.21 via Frontend Transport; Fri, 2 Oct 2020 20:35:31 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1601670931; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DEyMgXv8AK59CzlLAbx+v0az2air5ThwOCXmjhnIBsH8=3D; b=3DB4zNH+hw2TDirsmaASsR40ZyqCi7egvRY8RalLrGgN3JLzopd7HI94cq8iON4tc= m R2L5FYv5NjfU2MgMVK/L10hF11fL8DD96lEVdCRNEdCi5W3tQhgjmRkdzpxQN0uHZCg Ik5dzjZWCengjtfrN8l6/J5cr2PAhgRi11DR2jEo=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D160167= 0931; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DEyMgXv8AK59CzlLAbx+v0az2air5ThwOCXmjhnIBsH8=3D; b=3DLZlv2/e6hW3GsxuqkAi+LSH3R8l16NQjqhX4dJgptRkXQSewVHMBZ7hPyKQLDXy= F tZJP2m0bm25APRfBJWSKhstlWyKvd6W6mRT6iPBGHaf3YcawuFVwxfS9uQHBeBIocBn YWdmDqXRZwY/3GxY9eyAD+eHCSRVGP6oGzIl7x9k=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D20878319640511388= 48=3D=3D" MIME-Version: 1.0 Subject: Computational Thinking: CFP: ACM Special Issue on Computational Thinking
Posted
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio= n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to kmhowell@volusia.k12.fl.us couldn't be delivered. kmhowell wasn't found at volusia.k12.fl.us. 01000174eb071ca1-478. . . Office 365 kmhowell 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/2/2020 8:35:45 PM Sender Address: 01000174eb071ca1-4783e43e-af39-477a-a33a-ff92cd73b0f5-00000= 0@bounces.academicexperts.org Recipient Address: kmhowell@volusia.k12.fl.us 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 [= BN3NAM01FT030.eop-nam01.prod.protection.outlook.com] DSN generated by: MWHPR07MB3182.namprd07.prod.outlook.com Remote server: BN3NAM01FT030.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 10/2/2020 8:35:46 PM a8-91.smtp-out.amazonses.com BN3NAM01FT033.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 10/2/2020 8:35:46 PM BN3NAM01FT033.eop-nam01.prod.protection.outlook.com BN6= PR19CA0097.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 10/2/2020 8:35:46 PM BN6PR19CA0097.namprd19.prod.outlook.com CH2PR07MB8069.nampr= d07.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 10/2/2020 8:35:47 PM NAM11-DM6-obe.outbound.protection.outlook.com BN3NAM01FT0= 61.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 10/2/2020 8:35:48 PM BN3NAM01FT061.eop-nam01.prod.protection.outlook.com BN6= PR10CA0010.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 6 10/2/2020 8:35:48 PM BN6PR10CA0010.namprd10.prod.outlook.com DM6PR07MB5419.nampr= d07.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 10/2/2020 8:35:49 PM NAM10-BN7-obe.outbound.protection.outlook.com BN3NAM01FT0= 12.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 8 10/2/2020 8:35:49 PM BN3NAM01FT012.eop-nam01.prod.protection.outlook.com BN4= PR11CA0018.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 9 10/2/2020 8:35:49 PM BN4PR11CA0018.namprd11.prod.outlook.com MWHPR07MB3182.nampr= d07.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers
Received: from BN4PR11CA0018.namprd11.prod.outlook.com (2603:10b6:403:1::28= ) by MWHPR07MB3182.namprd07.prod.outlook.com (2603:10b6:300:eb::11) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.37; Fri, 2 O= ct 2020 20:35:49 +0000 Received: from BN3NAM01FT012.eop-nam01.prod.protection.outlook.com (2603:10b6:403:1:cafe::10) by BN4PR11CA0018.outlook.office365.com (2603:10b6:403:1::28) 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; Fri, 2 Oct 2020 20:35:49 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.70.106) smtp.mailfrom=3Dbounces.academicexperts.org; volusia.k12.fl.us; dkim=3Dfai= l (body hash did not verify) header.d=3Dacademicexperts.org;volusia.k12.fl.us; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfa= il reason=3D001 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.70.106 as permitted sender) Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.106= ) by BN3NAM01FT012.mail.protection.outlook.com (10.152.67.126) with Microsof= t SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3433.34 via Frontend Transport; Fri, 2 Oct 2020 20:35:49 +0000 Received: from BN6PR10CA0010.namprd10.prod.outlook.com (2603:10b6:405:1::20= ) by DM6PR07MB5419.namprd07.prod.outlook.com (2603:10b6:5:25::27) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.24; Fri, 2 O= ct 2020 20:35:48 +0000 Received: from BN3NAM01FT061.eop-nam01.prod.protection.outlook.com (2603:10b6:405:1:cafe::6b) by BN6PR10CA0010.outlook.office365.com (2603:10b6:405:1::20) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.36 via Front= end Transport; Fri, 2 Oct 2020 20:35:48 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.57.168= ) smtp.mailfrom=3Dbounces.academicexperts.org; volusia.k12.fl.us; dkim=3Dfai= l (body hash did not verify) header.d=3Dacademicexperts.org;volusia.k12.fl.us; dmarc=3Dfail action=3Dnone header.from=3Dacademicexperts.org;compauth=3Dfa= il reason=3D001 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning bounces.academicexperts.org discourages use of 104.47.57.168 as permitted sender) Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.168= ) by BN3NAM01FT061.mail.protection.outlook.com (10.152.66.252) with Microsof= t SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3433.34 via Frontend Transport; Fri, 2 Oct 2020 20:35:47 +0000 Received: from BN6PR19CA0097.namprd19.prod.outlook.com (2603:10b6:404:a0::1= 1) by CH2PR07MB8069.namprd07.prod.outlook.com (2603:10b6:610:12::23) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.36; Fri, 2 O= ct 2020 20:35:46 +0000 Received: from BN3NAM01FT033.eop-nam01.prod.protection.outlook.com (2603:10b6:404:a0:cafe::9f) by BN6PR19CA0097.outlook.office365.com (2603:10b6:404:a0::11) 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; Fri, 2 Oct 2020 20:35:46 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.91) smtp.mailfrom=3Dbounces.academicexperts.org; volusia.k12.fl.us; dkim=3Dpas= s (signature was verified) header.d=3Dacademicexperts.org;volusia.k12.fl.us; 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.91 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.8.91; helo=3Da8-91.smtp-out.amazonses.com; Received: from a8-91.smtp-out.amazonses.com (54.240.8.91) by BN3NAM01FT033.mail.protection.outlook.com (10.152.67.137) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.3433.34 via Frontend Transport; Fri, 2 Oct 2020 20:35:46 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1601670946; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3Df+AUMz5P9ZN3adNq9+i9d7eslfSW6TbMMstSaI+X+98=3D; b=3DBBp/IqdZRFhBG0qZvFE6K2EFAv7OmSzH1+t3sNv1P6BAe6d/7OWSf1Nfhun7SXN= F pqmy96Zs3s8h5OoVd+6kmV2C7NJADY/U+zhryg3ErzF8xuDpyS6E2pSb5vEvExB3LcT QE9EuBmeXAcLCJ4CDO/iUlcFUqDw/PMNYZ65riiA=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D160167= 0946; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3Df+AUMz5P9ZN3adNq9+i9d7eslfSW6TbMMstSaI+X+98=3D; b=3DfbDqUj0IAU3q+MpkAj0DqeiYwH8r2ts/ijjssE6EUMK+IbA5OAnTa+3gZF7xzJ6= U 8gg7cab0VNBTLAfvkRprtpMtTL9sL4jmr39jvh9TR34wqML97P8U5gcjanlWvzScgdV DDUSEPguDT7qjMjtHLBbaa4AwEzKLL669DgiHjMQ=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D39892645387135955= 15=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: neohao@uga.edu
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. 01000174eb07f513-49c. . . 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/2/2020 8:36:41 PM Sender Address: 01000174eb07f513-49cb2caa-2a24-439a-b229-ddd62aa6fdad-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 [= CO1NAM05FT004.eop-nam05.prod.protection.outlook.com] DSN generated by: DM6PR06MB6156.namprd06.prod.outlook.com Remote server: CO1NAM05FT004.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 10/2/2020 8:36:42 PM a48-130.smtp-out.amazonses.com CO1NAM05FT013.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec 2 10/2/2020 8:36:43 PM CO1NAM05FT013.eop-nam05.prod.protection.outlook.com MWH= PR1401CA0020.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 3 10/2/2020 8:36:43 PM MWHPR1401CA0020.namprd14.prod.outlook.com CH2PR06MB66= 47.namprd06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, ciphe= r=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 10/2/2020 8:36:44 PM NAM02-CY1-obe.outbound.protection.outlook.com CO1NAM05FT0= 25.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 10/2/2020 8:36:44 PM CO1NAM05FT025.eop-nam05.prod.protection.outlook.com MWH= PR11CA0031.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 6 10/2/2020 8:36:45 PM MWHPR11CA0031.namprd11.prod.outlook.com BYAPR06MB5830.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 10/2/2020 8:36:47 PM NAM04-BN8-obe.outbound.protection.outlook.com CO1NAM05FT0= 05.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec 8 10/2/2020 8:36:48 PM CO1NAM05FT005.eop-nam05.prod.protection.outlook.com CO2= PR05CA0065.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 9 10/2/2020 8:36:48 PM CO2PR05CA0065.namprd05.prod.outlook.com DM6PR06MB6156.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 CO2PR05CA0065.namprd05.prod.outlook.com (2603:10b6:102:2::33= ) by DM6PR06MB6156.namprd06.prod.outlook.com (2603:10b6:5:124::12) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.36; Fri, 2 O= ct 2020 20:36:48 +0000 Received: from CO1NAM05FT005.eop-nam05.prod.protection.outlook.com (2603:10b6:102:2:cafe::f6) by CO2PR05CA0065.outlook.office365.com (2603:10b6:102:2::33) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.7 via Fronte= nd Transport; Fri, 2 Oct 2020 20:36:48 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.74.42) 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.74.42 as permitted sender) Received: from NAM04-BN8-obe.outbound.protection.outlook.com (104.47.74.42)= by CO1NAM05FT005.mail.protection.outlook.com (10.152.96.110) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) = id 15.20.3455.13 via Frontend Transport; Fri, 2 Oct 2020 20:36:47 +0000 Received: from MWHPR11CA0031.namprd11.prod.outlook.com (2603:10b6:300:115::= 17) by BYAPR06MB5830.namprd06.prod.outlook.com (2603:10b6:a03:152::15) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.35; Fri, 2 O= ct 2020 20:36:45 +0000 Received: from CO1NAM05FT025.eop-nam05.prod.protection.outlook.com (2603:10b6:300:115:cafe::73) by MWHPR11CA0031.outlook.office365.com (2603:10b6:300:115::17) 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; Fri, 2 Oct 2020 20:36:44 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.37.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.37.55 as permitted sender) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (104.47.37.55)= by CO1NAM05FT025.mail.protection.outlook.com (10.152.96.133) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) = id 15.20.3455.13 via Frontend Transport; Fri, 2 Oct 2020 20:36:44 +0000 Received: from MWHPR1401CA0020.namprd14.prod.outlook.com (2603:10b6:301:4b::30) by CH2PR06MB6647.namprd06.prod.outlook.com (2603:10b6:610:8a::15) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.36; Fri, 2 O= ct 2020 20:36:43 +0000 Received: from CO1NAM05FT013.eop-nam05.prod.protection.outlook.com (2603:10b6:301:4b:cafe::17) by MWHPR1401CA0020.outlook.office365.com (2603:10b6:301:4b::30) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.14 via Front= end Transport; Fri, 2 Oct 2020 20:36:43 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.48.130) 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.48.130 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.48.130; helo=3Da48-130.smtp-out.amazonses.com; Received: from a48-130.smtp-out.amazonses.com (54.240.48.130) by CO1NAM05FT013.mail.protection.outlook.com (10.152.96.120) 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; Fri, 2 Oct 2020 20:36:42 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1601671001; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DvcAfzT5TclwBK+amPzP2rarrSDGKAQbDUQ87dklkWcc=3D; b=3DrGst6BoBPxS3p+Fu3p+X58r8FlrN6+PItDudoprsvfOAa4Xm+vou5IYjvCjkXjW= Z c9C9DxqDQrU2NzrT9uZ4rc5qo+t8Subz/p5jObkUxW5uPeD1qBlrYVrddGnPE557XHu 4IeAIJidX0w7xgoHWg0aJGv1LrfzFDWd7MmkS9UI=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D160167= 1001; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DvcAfzT5TclwBK+amPzP2rarrSDGKAQbDUQ87dklkWcc=3D; b=3DBpV6pcPFddWPMVSmtTPY+vyqhzBvS9gu6mFkKJOAwrFUEfY95y43a7GYWvUmnlo= B NS3Ig7imRdOVSzeORhyXtqEBEaMvCCeNZtOu9YT1y6bGWVr1DJk+48dmsHVdYw/3/F7 dKyFp1EtPQ4osHWLBebv6vq36yShZGTcxetUnmUI=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D77453714275822736= 62=3D=3D" MIME-Version: 1.0 Subject: Computational Thinking: CFP: ACM Special Issue on Computational Thinking
Posted
Hi Jongpil! Thanks for sharing! I saw that solicitation. I am currently working on a paper. I was deciding if I should send it to the ACM special issue or the SITE conference! Let's see how it will evolve! Thanks, Kaya
Posted