<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Block student to student email for specific user in Peer-Peer Topics</title>
    <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/862#M571</link>
    <description>&lt;P&gt;Our Middle School Principal is wanting us to set up a sort of penalty Box where we can put students in, and they can not send to or receive from the student email domain, but can continue to send to and receive from the staff domain.&amp;nbsp; As an example, our staff uses&amp;nbsp; @ourdomain.org while the students use&amp;nbsp;@ourdomainfulllength.org&lt;/P&gt;&lt;P&gt;The preferable method would be to put the penalized student into a PenaltyBox group that is configured in a way that the student can not send or receive emails to&amp;nbsp;@ourdomainfulllength.org, but they can continue to receive/send emails from/to&amp;nbsp;@ourdomain.org.&amp;nbsp; If this is not possible to be done by putting them in a group, then perhaps an OU that has some specific settings to achieve the above?&amp;nbsp; It would just be way easier to do it by group, of course if I knew how to accomplish it, lol .&amp;nbsp; Open to ideas on this. Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Fri, 08 Sep 2023 00:02:34 GMT</pubDate>
    <dc:creator>ParatrooperJoe</dc:creator>
    <dc:date>2023-09-08T00:02:34Z</dc:date>
    <item>
      <title>Block student to student email for specific user</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/862#M571</link>
      <description>&lt;P&gt;Our Middle School Principal is wanting us to set up a sort of penalty Box where we can put students in, and they can not send to or receive from the student email domain, but can continue to send to and receive from the staff domain.&amp;nbsp; As an example, our staff uses&amp;nbsp; @ourdomain.org while the students use&amp;nbsp;@ourdomainfulllength.org&lt;/P&gt;&lt;P&gt;The preferable method would be to put the penalized student into a PenaltyBox group that is configured in a way that the student can not send or receive emails to&amp;nbsp;@ourdomainfulllength.org, but they can continue to receive/send emails from/to&amp;nbsp;@ourdomain.org.&amp;nbsp; If this is not possible to be done by putting them in a group, then perhaps an OU that has some specific settings to achieve the above?&amp;nbsp; It would just be way easier to do it by group, of course if I knew how to accomplish it, lol .&amp;nbsp; Open to ideas on this. Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 00:02:34 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/862#M571</guid>
      <dc:creator>ParatrooperJoe</dc:creator>
      <dc:date>2023-09-08T00:02:34Z</dc:date>
    </item>
    <item>
      <title>Re: Block student to student email for specific user</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/863#M572</link>
      <description>&lt;P&gt;ll, I actually figured out how to do it via setting up a sub OU, and setting email compliance rule to only allow send/receive for teacher/staff domain, and moved that student into that OU. Tested and it seems to work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the Penalized student account emails another student, the email seems to never get sent, (not even a trace of it in the Vault), and despite there being a reject message, the student does not get notified that their email did not go through. This does achieve the end goal (so it seems with my small testing) but it would be easier if could set up that same scenario with a group, as opposed to having to move the student into that penalty box.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 01:13:47 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/863#M572</guid>
      <dc:creator>ParatrooperJoe</dc:creator>
      <dc:date>2023-09-08T01:13:47Z</dc:date>
    </item>
    <item>
      <title>Re: Block student to student email for specific user</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/864#M573</link>
      <description>&lt;P&gt;a bit more testing has revealed that the reject message (for my particular setup) appears to be displayed to a student who tries to email a student who is in the email penalty box ou.&amp;nbsp; Good to know.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 01:18:35 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/864#M573</guid>
      <dc:creator>ParatrooperJoe</dc:creator>
      <dc:date>2023-09-08T01:18:35Z</dc:date>
    </item>
    <item>
      <title>Re: Block student to student email for specific user</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/865#M574</link>
      <description>&lt;P&gt;Not all things can be set by group. Routing and Content Compliance rules are such things.&lt;/P&gt;&lt;P&gt;The issue is that the group membership isn't checked when an email is sent/received.&lt;/P&gt;&lt;P&gt;But, it never hurts to give Google feedback on that, so it can perhaps be added in the future.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 06:32:02 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Block-student-to-student-email-for-specific-user/m-p/865#M574</guid>
      <dc:creator>Kim_Nilsson</dc:creator>
      <dc:date>2023-09-08T06:32:02Z</dc:date>
    </item>
  </channel>
</rss>

