<?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 Number of Recipients allowed in BCC in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/number-of-recipients-allowed-in-bcc/m-p/140054#M56960</link>
    <description>&lt;P&gt;I have used Thunderbird for email for may years. Primarily when communicating with the membershipo of a club I am chairman of. Recently I have become unable to send group emails i and get the following error message. There is no notice of which server. We are a small club with less than 50 members why has this suddenly started and how to I get round it. I tried breaking mailing list into two but get same message.&lt;/P&gt;&lt;P&gt;Sending that number of individual emails with identical content is time consuming and prone to missing someone out. Si if it cant be overcome I will have to move to a platform that does.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Sending of the message failed.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;The message was not sent due to exceeding the allowed number of recipients. The server responded: Policy-SC01 You’ve reached your sending limit. Don’t worry, you can&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;send again soon..&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2026 14:13:19 GMT</pubDate>
    <dc:creator>Duncan_McC</dc:creator>
    <dc:date>2026-09-30T14:13:19Z</dc:date>
    <item>
      <title>Number of Recipients allowed in BCC</title>
      <link>https://connect.mozilla.org/t5/discussions/number-of-recipients-allowed-in-bcc/m-p/140054#M56960</link>
      <description>&lt;P&gt;I have used Thunderbird for email for may years. Primarily when communicating with the membershipo of a club I am chairman of. Recently I have become unable to send group emails i and get the following error message. There is no notice of which server. We are a small club with less than 50 members why has this suddenly started and how to I get round it. I tried breaking mailing list into two but get same message.&lt;/P&gt;&lt;P&gt;Sending that number of individual emails with identical content is time consuming and prone to missing someone out. Si if it cant be overcome I will have to move to a platform that does.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;Sending of the message failed.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;The message was not sent due to exceeding the allowed number of recipients. The server responded: Policy-SC01 You’ve reached your sending limit. Don’t worry, you can&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;send again soon..&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2026 14:13:19 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/number-of-recipients-allowed-in-bcc/m-p/140054#M56960</guid>
      <dc:creator>Duncan_McC</dc:creator>
      <dc:date>2026-09-30T14:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: Number of Recipients allowed in BCC</title>
      <link>https://connect.mozilla.org/t5/discussions/number-of-recipients-allowed-in-bcc/m-p/140055#M56961</link>
      <description>&lt;P&gt;This limit will likely be imposed by the e-mail service (e.g. Outlook, Yahoo! Mail, GMail, ProtonMail, etc.) you're using.&amp;nbsp; It's unlikely Thunderbird itself would have suddenly enforced this.&lt;/P&gt;&lt;P&gt;What e-mail service does your club use?&amp;nbsp; Have you done a Google search for that service to see if they have a limit on the number of e-mail addresses that can be on one e-mail for free-accounts?&amp;nbsp; Having a limit is very common to reduce spam&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2026 14:16:52 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/number-of-recipients-allowed-in-bcc/m-p/140055#M56961</guid>
      <dc:creator>dftf</dc:creator>
      <dc:date>2026-09-30T14:16:52Z</dc:date>
    </item>
  </channel>
</rss>

