<?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 Using 3rd party email gateway (mimecast/proofpoint) in Peer-Peer Topics</title>
    <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Using-3rd-party-email-gateway-mimecast-proofpoint/m-p/77575#M2907</link>
    <description>&lt;P&gt;For those that use a email gateway like mimecast or proofpoint, and are using google workspace, do you route internal google domain (same domain) emails internally, or do you just have google send the emails to the internet (mx) and then have it come back into the email gateway?&lt;/P&gt;&lt;P&gt;We're switching from proofpoint to mimecast and the engineer/specialist we're working with is suggesting for google (maybe just in general) that we route internal emails internally and setup journaling, and only use mimecast for externally-incoming emails based on mx records&lt;/P&gt;&lt;P&gt;How our setup is now with proofpoint is all email (internally sent, or externally received) is routed using the mx record and therefore an email from me to a coworker would go through the proofpoint system.&lt;/P&gt;&lt;P&gt;The mimecast specialist stated that if we went the route with all emails going through the mimecast system that it may cause spf/dkim/dmarc issues.&lt;/P&gt;&lt;P&gt;Has anyone in a similar situation had that? We don't have any issues with the spf/dkim/dmarc the way we do it...&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jul 2024 15:08:09 GMT</pubDate>
    <dc:creator>alexgrutza</dc:creator>
    <dc:date>2024-07-23T15:08:09Z</dc:date>
    <item>
      <title>Using 3rd party email gateway (mimecast/proofpoint)</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Using-3rd-party-email-gateway-mimecast-proofpoint/m-p/77575#M2907</link>
      <description>&lt;P&gt;For those that use a email gateway like mimecast or proofpoint, and are using google workspace, do you route internal google domain (same domain) emails internally, or do you just have google send the emails to the internet (mx) and then have it come back into the email gateway?&lt;/P&gt;&lt;P&gt;We're switching from proofpoint to mimecast and the engineer/specialist we're working with is suggesting for google (maybe just in general) that we route internal emails internally and setup journaling, and only use mimecast for externally-incoming emails based on mx records&lt;/P&gt;&lt;P&gt;How our setup is now with proofpoint is all email (internally sent, or externally received) is routed using the mx record and therefore an email from me to a coworker would go through the proofpoint system.&lt;/P&gt;&lt;P&gt;The mimecast specialist stated that if we went the route with all emails going through the mimecast system that it may cause spf/dkim/dmarc issues.&lt;/P&gt;&lt;P&gt;Has anyone in a similar situation had that? We don't have any issues with the spf/dkim/dmarc the way we do it...&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2024 15:08:09 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Using-3rd-party-email-gateway-mimecast-proofpoint/m-p/77575#M2907</guid>
      <dc:creator>alexgrutza</dc:creator>
      <dc:date>2024-07-23T15:08:09Z</dc:date>
    </item>
  </channel>
</rss>

