Computational Thinking SIG Co-Chair Election at SITE 2021
Good morning. I hope that this email finds you well.
As you know, SITE 2021 is fast approaching and will be virtual. I wanted to let you know that during the conference we will be electing a new co-chair as my term will be ending. Jongpil's co-chair term continues until the 2022 conference.
I encourage any of you who are interested in taking a leadership role in this SIG. If you are interested, or if you have any questions about the position, please let me know. I am still waiting on the details for how the election will work, and as soon as I know that I will let us all know.
Be well and stay safe. Best, 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: 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: helen.teague@pepperdine.edu
Posted
An error occurred while trying to deliver the mail to the following recipients: vsutton@emaginos.com
Posted
An error occurred while trying to deliver the mail to the following recipients: a.strijker@slo.nl
Posted
[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versi= on=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. 0100017796790a7a-634. . . 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: 2/12/2021 1:40:51 PM Sender Address: 0100017796790a7a-63422ab4-bf3b-4167-8351-de6730cf01c2-00000= 0@bounces.academicexperts.org Recipient Address: kmhowell@volusia.k12.fl.us Subject: Computational Thinking: Computational Thinking SIG Co-Chair= Election at SITE 2021
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= BN7NAM10FT025.eop-nam10.prod.protection.outlook.com] DSN generated by: BYAPR07MB4184.namprd07.prod.outlook.com Remote server: BN7NAM10FT025.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 2/12/2021 1:40:51 PM a8-44.smtp-out.amazonses.com DM6NAM10FT047.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 2/12/2021 1:40:52 PM DM6NAM10FT047.eop-nam10.prod.protection.outlook.com DM5= PR06CA0095.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 3 2/12/2021 1:40:52 PM DM5PR06CA0095.namprd06.prod.outlook.com BY5PR07MB6483.nampr= d07.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 4 2/12/2021 1:40:53 PM NAM12-MW2-obe.outbound.protection.outlook.com DM6NAM10FT0= 38.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 2/12/2021 1:40:53 PM DM6NAM10FT038.eop-nam10.prod.protection.outlook.com DS7= PR03CA0116.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 6 2/12/2021 1:40:54 PM DS7PR03CA0116.namprd03.prod.outlook.com BYAPR07MB6134.nampr= d07.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 2/12/2021 1:40:55 PM NAM02-BL2-obe.outbound.protection.outlook.com DM6NAM10FT0= 28.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 8 2/12/2021 1:40:55 PM DM6NAM10FT028.eop-nam10.prod.protection.outlook.com DM5= PR08CA0052.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 9 2/12/2021 1:40:56 PM DM5PR08CA0052.namprd08.prod.outlook.com BYAPR07MB4184.nampr= d07.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 DM5PR08CA0052.namprd08.prod.outlook.com (2603:10b6:4:60::41)= by BYAPR07MB4184.namprd07.prod.outlook.com (2603:10b6:a02:c7::23) with Micros= oft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3846.25; Fri, 12 Feb 2021 13:40:56 +0000 Received: from DM6NAM10FT028.eop-nam10.prod.protection.outlook.com (2603:10b6:4:60:cafe::bd) by DM5PR08CA0052.outlook.office365.com (2603:10b6:4:60::41) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25 via Front= end Transport; Fri, 12 Feb 2021 13:40:55 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.38.52) 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.38.52 as permitted sender) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.52)= by DM6NAM10FT028.mail.protection.outlook.com (10.13.152.240) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) = id 15.20.3846.25 via Frontend Transport; Fri, 12 Feb 2021 13:40:55 +0000 Received: from DS7PR03CA0116.namprd03.prod.outlook.com (2603:10b6:5:3b7::31= ) by BYAPR07MB6134.namprd07.prod.outlook.com (2603:10b6:a03:124::26) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25; Fri, 12 = Feb 2021 13:40:54 +0000 Received: from DM6NAM10FT038.eop-nam10.prod.protection.outlook.com (2603:10b6:5:3b7:cafe::6a) by DS7PR03CA0116.outlook.office365.com (2603:10b6:5:3b7::31) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25 via Front= end Transport; Fri, 12 Feb 2021 13:40:53 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.66.44) 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.66.44 as permitted sender) Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.44)= by DM6NAM10FT038.mail.protection.outlook.com (10.13.153.151) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) = id 15.20.3846.25 via Frontend Transport; Fri, 12 Feb 2021 13:40:53 +0000 Received: from DM5PR06CA0095.namprd06.prod.outlook.com (2603:10b6:3:4::33) = by BY5PR07MB6483.namprd07.prod.outlook.com (2603:10b6:a03:1a6::20) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3825.29; Fri, 12 = Feb 2021 13:40:52 +0000 Received: from DM6NAM10FT047.eop-nam10.prod.protection.outlook.com (2603:10b6:3:4:cafe::7d) by DM5PR06CA0095.outlook.office365.com (2603:10b6:3:4::33) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25 via Front= end Transport; Fri, 12 Feb 2021 13:40:52 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.8.44) 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.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 DM6NAM10FT047.mail.protection.outlook.com (10.13.152.192) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.3846.25 via Frontend Transport; Fri, 12 Feb 2021 13:40:51 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1613137251; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3Dq4wNe7p3+JL+emuaS8U8rJgjUDRBlNPGp2GSgqgtn5A=3D; b=3DQh+CUlAA8FRvVZS6BbhgToCQe9nJvYvD/H0WIbtcJTQW9/u867L9cTG708dLoi/= f 3xl7ykp+1NtJ7c07khKil9A/679oR7z4fTTKMDa5qtAbghqZC5P1ms0s4TU67s8WgH+ 9lgg0+kQoqekiNm7icwSYvLJXHJN2ZlczCOyTnHg=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D161313= 7251; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3Dq4wNe7p3+JL+emuaS8U8rJgjUDRBlNPGp2GSgqgtn5A=3D; b=3DZ0u7FEq76RI+T0xBCuB6+0m27/XpEOyhePQNfv4Hogy3ijYA2rIbgScO7K980Mi= K qYFSxlrgxxX7zkEDpgnR4G/wnX2phf+dzgirjYugPGmyydz8Nz7ofxuM4KriwI6gjbo A/mOUXRPwKma7marBqXeFI3M30iir0Q+6DqkOTMM=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D74958780796913658= 60=3D=3D" MIME-Version: 1.0 Subject: Computational Thinking: Computational Thinking SIG Co-Chair Electi= on at SITE 2021
Posted
An error occurred while trying to deliver the mail to the following recipients: p.fisser@slo.nl
Posted
An error occurred while trying to deliver the mail to the following recipients: rbaldizon@miskschools.edu.sa
Posted
An error occurred while trying to deliver the mail to the following recipients: aali@uwlax.edu
Posted
[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versi= on=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470] Your message to gordoncr@uncw.edu couldn't be delivered. gordoncr wasn't found at uncw.edu. 01000177967add7b-d0c. . . 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: 2/12/2021 1:42:50 PM Sender Address: 01000177967add7b-d0c6c066-6255-49c8-b9cb-6921a06e32c8-00000= 0@bounces.academicexperts.org Recipient Address: gordoncr@uncw.edu Subject: Computational Thinking: Computational Thinking SIG Co-Chair= Election at SITE 2021
Error Details Reported error: 554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [= DM6NAM12FT027.eop-nam12.prod.protection.outlook.com] DSN generated by: SN6PR06MB6351.namprd06.prod.outlook.com Remote server: DM6NAM12FT027.mail.protection.outlook.com
Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 2/12/2021 1:42:50 PM a48-131.smtp-out.amazonses.com BN8NAM12FT019.mail.protecti= on.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 2/12/2021 1:42:50 PM BN8NAM12FT019.eop-nam12.prod.protection.outlook.com BN0= PR04CA0196.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 3 2/12/2021 1:42:51 PM BN0PR04CA0196.namprd04.prod.outlook.com DM6PR06MB4154.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 4 2/12/2021 1:42:51 PM NAM10-MW2-obe.outbound.protection.outlook.com MW2NAM12FT0= 45.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 5 2/12/2021 1:42:52 PM MW2NAM12FT045.eop-nam12.prod.protection.outlook.com MW3= PR05CA0001.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 6 2/12/2021 1:42:52 PM MW3PR05CA0001.namprd05.prod.outlook.com DM6PR06MB4089.nampr= d06.prod.outlook.com Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_= ECDHE_RSA_WITH_AES_256_GCM_SHA384) 7 2/12/2021 1:42:53 PM NAM11-CO1-obe.outbound.protection.outlook.com BN8NAM12FT0= 14.mail.protection.outlook.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 8 2/12/2021 1:42:54 PM BN8NAM12FT014.eop-nam12.prod.protection.outlook.com BN9= PR03CA0090.outlook.office365.com Microsoft SMTP Server (version=3DTLS1_= 2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 9 2/12/2021 1:42:54 PM BN9PR03CA0090.namprd03.prod.outlook.com SN6PR06MB6351.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 BN9PR03CA0090.namprd03.prod.outlook.com (2603:10b6:408:fc::3= 5) by SN6PR06MB6351.namprd06.prod.outlook.com (2603:10b6:805:103::15) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.27; Fri, 12 = Feb 2021 13:42:54 +0000 Received: from BN8NAM12FT014.eop-nam12.prod.protection.outlook.com (2603:10b6:408:fc:cafe::9c) by BN9PR03CA0090.outlook.office365.com (2603:10b6:408:fc::35) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25 via Front= end Transport; Fri, 12 Feb 2021 13:42:54 +0000 Authentication-Results: spf=3Dsoftfail (sender IP is 104.47.56.170) 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.56.170 as permitted sender) Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.170= ) by BN8NAM12FT014.mail.protection.outlook.com (10.13.183.44) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3846.25 via Frontend Transport; Fri, 12 Feb 2021 13:42:53 +0000 Received: from MW3PR05CA0001.namprd05.prod.outlook.com (2603:10b6:303:2b::6= ) by DM6PR06MB4089.namprd06.prod.outlook.com (2603:10b6:5:8c::18) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.27; Fri, 12 = Feb 2021 13:42:52 +0000 Received: from MW2NAM12FT045.eop-nam12.prod.protection.outlook.com (2603:10b6:303:2b:cafe::8e) by MW3PR05CA0001.outlook.office365.com (2603:10b6:303:2b::6) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.12 via Front= end Transport; Fri, 12 Feb 2021 13:42:52 +0000 Authentication-Results-Original: spf=3Dsoftfail (sender IP is 104.47.55.102= ) 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.102 as permitted sender) Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.102= ) by MW2NAM12FT045.mail.protection.outlook.com (10.13.181.12) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA= 384) id 15.20.3846.25 via Frontend Transport; Fri, 12 Feb 2021 13:42:51 +0000 Received: from BN0PR04CA0196.namprd04.prod.outlook.com (2603:10b6:408:e9::2= 1) by DM6PR06MB4154.namprd06.prod.outlook.com (2603:10b6:5:91::21) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.27; Fri, 12 = Feb 2021 13:42:51 +0000 Received: from BN8NAM12FT019.eop-nam12.prod.protection.outlook.com (2603:10b6:408:e9:cafe::b4) by BN0PR04CA0196.outlook.office365.com (2603:10b6:408:e9::21) with Microsoft SMTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25 via Front= end Transport; Fri, 12 Feb 2021 13:42:50 +0000 Authentication-Results-Original: spf=3Dpass (sender IP is 54.240.48.131) 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.131 as permitted sender) receiver=3Dprotection.outlook.com; client-ip=3D54.240.48.131; helo=3Da48-131.smtp-out.amazonses.com; Received: from a48-131.smtp-out.amazonses.com (54.240.48.131) by BN8NAM12FT019.mail.protection.outlook.com (10.13.183.160) with Microsoft S= MTP Server (version=3DTLS1_2, cipher=3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) = id 15.20.3846.25 via Frontend Transport; Fri, 12 Feb 2021 13:42:50 +0000 DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3Dewfifkinnvnhipiq3p7takgrl63euj24; d=3Dacademicexperts.org; t=3D1613137370; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID; bh=3DETrGdhDXcSk87Q0qIQ0er1E3bbHUAvtxNfOUdgzb+r8=3D; b=3Deo8gzd2ADKpvhXRZDkUbOfVCVJzU/kxSTuNfGmC3CDfZdfH/WZeWCa69AT4ElVb= / 5dC3I4EwKe0uGlEf4xFS05fAIjKOuoBqSEEuX9bu6v+8c3Xlm2QuyQWpGHfyAGSexB7 RlM+Dq7L6dKS51gVhH+pNRQYHXBfn2qIzm0iXdBk=3D DKIM-Signature: v=3D1; a=3Drsa-sha256; q=3Ddns/txt; c=3Drelaxed/simple; s=3D224i4yxa5dv7c2xz3womw6peuasteono; d=3Damazonses.com; t=3D161313= 7370; h=3DContent-Type:MIME-Version:Subject:From:To:Date:Message-ID:Feedb= ack-ID; bh=3DETrGdhDXcSk87Q0qIQ0er1E3bbHUAvtxNfOUdgzb+r8=3D; b=3DQJ8DCHikt6rf7tXH8aWGfdYXB/lhWVCasVxPOa2rI7OWgCi5pZjxrdou5BqsuM2= P pZ3ftpNTyT4wgrD7Mr+wKK13X9PsxdwdzEwVjY7iqpt7SrtIEb4w+htfqCxPCep25ix IYUoPHRpCktnTxsYK1O7FtYbiNT0Hs4Jpwu+Yep0=3D Content-Type: multipart/alternative; boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D01156928060651656= 83=3D=3D" MIME-Version: 1.0 Subject: Computational Thinking: Computational Thinking SIG Co-Chair Electi= on at SITE 2021
Posted
Your message about "Computational Thinking: Computational Thinking SIG Co-Chair Election at SITE 2021" 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=54347020264&tc_rand=885871265&utm_source=stf&utm_medium=email&utm_campaign=CN_STDW_v6&utm_content=001
Thank you, nemati_mahboobeh@yahoo.com
Posted
Good Morning Gerald,
I am doing well I hope you are, too.
I would be interested in serving as co-chair of the Computational Thinking = SIG if there is an opening. My term as co-chair of the Information Literac= y Education SIG ends this year, and I am interested in taking on a new lead= ership role. I have been doing research on integrating CT into pre-service = teacher education so I would love to be more involved in this SIG.
Kind Regards,
Jillian Powers, Ph.D. Assistant Professor, Instructional Technology Department of Teaching and Learning Florida Atlantic University
Posted
Jillian, Thanks so much for your interest in serving as the next co-chair. I will let you know about next steps.
Best, Gerald
Posted
Hi Gerald,
Thank you for your note. I am not interested as I have my hands full now. B= ut, I am interested in attending the conference soon. I was sorry that the = 2020 conference was canceled.
Dan Robinson Associate Dean of Research K-16 Mind, Brain and Education Endowed Chair College of Education The University of Texas at Arlington 504 Hammond Hall Arlington, TX 76019 Phone: 817-272-0116 (leave a voicemail)
Pronouns: He/Him/His
https://orcid.org/0000-0003-1285-1155
Posted
Dan, Thanks for getting back to me. Hope to see you soon. Gerald
Posted in reply to Gerald Ardito