<?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 &amp;quot;distribution list&amp;quot;... in Tech Help - Software/Hardware etc</title>
    <link>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992228#M97086</link>
    <description>&lt;P&gt;Your thoughts please....&lt;/P&gt;
&lt;P&gt;------&lt;/P&gt;
&lt;P&gt;Scenario: Small church wishes to:&lt;/P&gt;
&lt;P&gt;-be able to send out emails to a list of people (less than 30),&lt;/P&gt;
&lt;P&gt;- without everyone knowing everyone else's email address.&lt;/P&gt;
&lt;P&gt;- Possibly want to have up to, say, 6 different lists.&lt;/P&gt;
&lt;P&gt;- Emails sending needs to be simple: for example, send emails to a dummy email address, which then forwards them.&lt;/P&gt;
&lt;P&gt;- Not "spammable", only limited people allowed to send the emails&lt;/P&gt;
&lt;P&gt;- Preferably be free&lt;/P&gt;
&lt;P&gt;- There will not be a lot of traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can think of several ways:&lt;/P&gt;
&lt;P&gt;Simplest is for individuals to just "BCC" the emails to a local, private, list of emails. Downsides: list of PersonA may not match list of PersonB; several people need to learn how to manage their own email distribution lists; fiddly to send emails&lt;/P&gt;
&lt;P&gt;Another way is to set up a "dummy email account", whose purpose in life is to accept emails, and forward them to a pre-defined list of emails. A technically savvy person can maintain the email list. Just send an email to that email address, and it gets forwarded. Downside: ANYONE can send an email to that distribution address. (Obvious spam CAN be filtered)&lt;/P&gt;
&lt;P&gt;Use someone like Mailchimp: centrally managed emails list. From what I read, (BICBW) only one person (for the free version) can send the emails; It seems that you have to use the MailChimp website to send the emails - so over-complicated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there something LIKE MailChimp, but rather than having to use the website to send the emails, can just reflect incoming emails from designated senders? So a relatively simple email forwarder, but with a level of simple "security" to limit who can originate the emails.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Paul&lt;/P&gt;</description>
    <pubDate>Sun, 01 Dec 2024 13:41:00 GMT</pubDate>
    <dc:creator>paul_blitz</dc:creator>
    <dc:date>2024-12-01T13:41:00Z</dc:date>
    <item>
      <title>Email "distribution list"...</title>
      <link>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992228#M97086</link>
      <description>&lt;P&gt;Your thoughts please....&lt;/P&gt;
&lt;P&gt;------&lt;/P&gt;
&lt;P&gt;Scenario: Small church wishes to:&lt;/P&gt;
&lt;P&gt;-be able to send out emails to a list of people (less than 30),&lt;/P&gt;
&lt;P&gt;- without everyone knowing everyone else's email address.&lt;/P&gt;
&lt;P&gt;- Possibly want to have up to, say, 6 different lists.&lt;/P&gt;
&lt;P&gt;- Emails sending needs to be simple: for example, send emails to a dummy email address, which then forwards them.&lt;/P&gt;
&lt;P&gt;- Not "spammable", only limited people allowed to send the emails&lt;/P&gt;
&lt;P&gt;- Preferably be free&lt;/P&gt;
&lt;P&gt;- There will not be a lot of traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can think of several ways:&lt;/P&gt;
&lt;P&gt;Simplest is for individuals to just "BCC" the emails to a local, private, list of emails. Downsides: list of PersonA may not match list of PersonB; several people need to learn how to manage their own email distribution lists; fiddly to send emails&lt;/P&gt;
&lt;P&gt;Another way is to set up a "dummy email account", whose purpose in life is to accept emails, and forward them to a pre-defined list of emails. A technically savvy person can maintain the email list. Just send an email to that email address, and it gets forwarded. Downside: ANYONE can send an email to that distribution address. (Obvious spam CAN be filtered)&lt;/P&gt;
&lt;P&gt;Use someone like Mailchimp: centrally managed emails list. From what I read, (BICBW) only one person (for the free version) can send the emails; It seems that you have to use the MailChimp website to send the emails - so over-complicated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there something LIKE MailChimp, but rather than having to use the website to send the emails, can just reflect incoming emails from designated senders? So a relatively simple email forwarder, but with a level of simple "security" to limit who can originate the emails.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Sun, 01 Dec 2024 13:41:00 GMT</pubDate>
      <guid>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992228#M97086</guid>
      <dc:creator>paul_blitz</dc:creator>
      <dc:date>2024-12-01T13:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Email "distribution list"...</title>
      <link>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992275#M97089</link>
      <description>&lt;P&gt;Hi Paul,&lt;/P&gt;
&lt;P&gt;Does the church have its own email domain?&lt;/P&gt;
&lt;P&gt;If yes, who administers it?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the church has its own email domain (for example&amp;nbsp;@daresburycofe.org.uk ) it should be possible for the system administrator to set up and manage forwarding lists, the ilk of ...&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;list1@daresburycofe.co.uk&lt;/LI&gt;
&lt;LI&gt;list2@daresburycofe.co.uk&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;That might not facilitate the restriction of who can send, except by knowledge that the addresses exists.&lt;/P&gt;
&lt;P&gt;The merits are...&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;It is all in-house&lt;/LI&gt;
&lt;LI&gt;There are no incremental costs&lt;/LI&gt;
&lt;LI&gt;It is an easy enough solution&lt;/LI&gt;
&lt;LI&gt;Sender's domains will not see this as bulk emailing&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;On thing to consider, whatever method you use is facilitation of a means for addressees to "unsubscribe".&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2024 13:18:17 GMT</pubDate>
      <guid>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992275#M97089</guid>
      <dc:creator>Townman</dc:creator>
      <dc:date>2024-12-02T13:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Email "distribution list"...</title>
      <link>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992280#M97090</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; Does the church have its own email domain?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It does, and 100% unsure who manages, but I can ask.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Indeed, we could set up some lists, the 2 issues I see are: (a) does the church email setup allow any form of 'auto-responders' to run the list?; (b) The fact that &lt;EM&gt;anyone&lt;/EM&gt; can still send emails could still be an issue.... But your plus-points are very valid, thank you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As far as 'unsubscribing', it's a small enough group, we can just tell people to "send an email to xxxx" if they want out.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2024 13:59:19 GMT</pubDate>
      <guid>https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/Email-quot-distribution-list-quot/m-p/1992280#M97090</guid>
      <dc:creator>paul_blitz</dc:creator>
      <dc:date>2024-12-02T13:59:19Z</dc:date>
    </item>
  </channel>
</rss>

