<?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 Email Protection in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/email-protection/m-p/94576#M36930</link>
    <description>&lt;P&gt;Emails in the inbox should have the following protection (in case you didn't develop this yet).&lt;/P&gt;&lt;P&gt;1. Check if the email address matches the sender person as it is expected to be. For example, a certain bank should always have a certain email address matching the bank domain. To do this, there should exist a database of main companies such citi.com etc. so that Thunderbolt system can verify if all messages coming from Citibank really come from someone with email address ending in citi.com.&lt;/P&gt;&lt;P&gt;2. Check if there is a link in the message leading to a website different from the website it supposed to be. For example, a message coming from a bank should lead only to the bank website which is in your database.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp;In case 1 or 2 happens, and any other, the message should be sent to a Box called Phishing or something, not Spam.&amp;nbsp;Thunderbold could also send automatically a copy of this email sent to this Box to a outside controller related or not to Thunderbolt (Interpol etc.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 27 Apr 2025 19:14:38 GMT</pubDate>
    <dc:creator>fabio1</dc:creator>
    <dc:date>2025-04-27T19:14:38Z</dc:date>
    <item>
      <title>Email Protection</title>
      <link>https://connect.mozilla.org/t5/discussions/email-protection/m-p/94576#M36930</link>
      <description>&lt;P&gt;Emails in the inbox should have the following protection (in case you didn't develop this yet).&lt;/P&gt;&lt;P&gt;1. Check if the email address matches the sender person as it is expected to be. For example, a certain bank should always have a certain email address matching the bank domain. To do this, there should exist a database of main companies such citi.com etc. so that Thunderbolt system can verify if all messages coming from Citibank really come from someone with email address ending in citi.com.&lt;/P&gt;&lt;P&gt;2. Check if there is a link in the message leading to a website different from the website it supposed to be. For example, a message coming from a bank should lead only to the bank website which is in your database.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp;In case 1 or 2 happens, and any other, the message should be sent to a Box called Phishing or something, not Spam.&amp;nbsp;Thunderbold could also send automatically a copy of this email sent to this Box to a outside controller related or not to Thunderbolt (Interpol etc.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 27 Apr 2025 19:14:38 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/email-protection/m-p/94576#M36930</guid>
      <dc:creator>fabio1</dc:creator>
      <dc:date>2025-04-27T19:14:38Z</dc:date>
    </item>
  </channel>
</rss>

