<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi,</p>
<p>As Seun said, there is a default privacy setting in GNU Mailman
software (that facilitates the mailing list) that flags Blind
Carbon Copy (BCC) mails to mailing lists in the manner that you
experienced.</p>
<p>For alternative behaviour, the administrator or moderator has to
explicitly make a change:<br>
</p>
<blockquote>
<p>To accept all BCCs to the list and get rid of this message
entirely:</p>
<ul>
<li>Go to Privacy Options / Recipient Filters and set the
require_explicit_destination option to be "No". This should be
the first option on the page, and by default, Mailman will set
this option to be "Yes"<br>
</li>
</ul>
</blockquote>
However, the main reason behind this setting appears to be for the
protection of you and your mailing list colleagues from what was
recognised at some point to be a spammer characteristics. The
setting could be inconvenient though. <br>
<br>
By way of example, as I was composing this, I received a spam
message as a BCC'd message from a former client with what looks like
a malicious attachment. That message probably went to all of the
entries in his address book. If he was on the At-Large mailing list,
then we <u>would not have received it</u> due to the very setting
at issue. The spam engine is likely sending one message to a
significant number of recipients in the BCC field. The more
convincing spam tends have a person as a single recipient, or rather
than a huge list of unknown recipients.<br>
<br>
From a pedantic viewpoint, whilst you may need to BCC to a <i>distribution
list</i> (an identifier that conveniently points to and expands
into multiple email addresses), one would more conduct a broadcast
or discussion with an <i>electronic mailing list</i> / <i>listserv
</i>(an email client independent announce or discussion based,
automated membership facility allowing all members to be reached via
a single email address). One should not need <i>to hide</i> the
action of messaging a mailing list as <u>per its original purpose</u>.<br>
<br>
I do utilize <i>groups</i> (in Google) and <i>mailing lists</i>
(in Mailman) sometimes for the convenience of being better than <i>distribution
lists</i> especially with respect to being email client and device
independent. Sometimes, I don't wish for one group to be aware that
I emailed the other group the same thing, for whatever reason.
However, with Mailman, unless I'm administrating it, I have to toe
the line.<br>
<p>Moderation for technical reasons or in line with an acceptable
use policy is quite different to any concern about it being an
"open list".</p>
<p>Good discussion. Have a great day!<br>
</p>
<p>Regards,</p>
<p>Jason Hynds</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 5/23/2016 4:50 PM, Judith
Hellerstein wrote:<br>
</div>
<blockquote
cite="mid:cc4734f4-6d1e-d67b-b37b-46c37eb9a554@jhellerstein.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p>Hi Seun and Carlton,</p>
<p>I think this has to do more with the List Serve Providers than
with any other rules. It seems the List serves also do not like
HTML text and prefer text only at least that is what IT has told
me was the answer to why my emails to the ALAC list serve were
coming out blank</p>
<p>best,</p>
<p>Judith<br>
</p>
<pre class="moz-signature" cols="80">_________________________________________________________________________
Judith Hellerstein, Founder & CEO
Hellerstein & Associates
3001 Veazey Terrace NW, Washington DC 20008
Phone: (202) 362-5139 Skype ID: judithhellerstein
E-mail: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Judith@jhellerstein.com">Judith@jhellerstein.com</a> Website: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.jhellerstein.com">www.jhellerstein.com</a>
Linked In: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/jhellerstein/">www.linkedin.com/in/jhellerstein/</a>
Opening Telecom & Technology Opportunities Worldwide
</pre>
<div class="moz-cite-prefix">On 5/23/2016 4:57 PM, Seun Ojedeji
wrote:<br>
</div>
<blockquote
cite="mid:CAD_dc6gzAjj_oJbYQ6o=JS+i7QC5H5rxcOB-Ls5HfkVOxLWZeg@mail.gmail.com"
type="cite">
<p dir="ltr">Sent from my LG G4<br>
Kindly excuse brevity and typos<br>
On 23 May 2016 20:25, "Carlton Samuels" <<a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:carlton.samuels@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:carlton.samuels@gmail.com">carlton.samuels@gmail.com</a></a>>
wrote:<br>
><br>
> Here's a rule that defies reason...and evidence of this
propensity to major in minor matters! <br>
><br>
> So, pray tell, in context, what [is]/are [an] "implicit
destination[s]"?<br>
><br>
SO: In the case of blind copy, it is more of [they]/[you].....</p>
<p dir="ltr">><br>
And, again in context, might I ask why we are concerned
about how you address to send rather than about what and who
sends? <br>
><br>
SO: ... And that somewhat implies suspicious mails as it's
believed to be normally used by scammers. Unfortunately, when
the wicked is being moderated, the saints also partake in it
as well ;-)</p>
<p dir="ltr">> Or, is this rule purely a politically correct
surrogate for managing what is supposed to be an open list?<br>
><br>
SO: Don't know how many recipients exist in that particular
mail you sent but it's just a technical precaution. I believe
the settings can be further adjusted to not moderate up to
certain level of blind copied recipient.</p>
<p dir="ltr">Regards</p>
<p dir="ltr">> -Carlton<br>
><br>
><br>
> ==============================<br>
> Carlton A Samuels<br>
> Mobile: 876-818-1799<br>
> Strategy, Planning, Governance, Assessment &
Turnaround<br>
> =============================<br>
><br>
> ---------- Forwarded message ----------<br>
> From: <<a moz-do-not-send="true"
href="mailto:at-large-owner@atlarge-lists.icann.org">at-large-owner@atlarge-lists.icann.org</a>><br>
> Date: Mon, May 23, 2016 at 11:28 AM<br>
> Subject: Request to mailing list At-Large rejected<br>
> To: <a moz-do-not-send="true"
href="mailto:carlton.samuels@gmail.com">carlton.samuels@gmail.com</a><br>
><br>
><br>
> Your request to the At-Large mailing list<br>
><br>
> Posting of your message titled "WB Abandoning the<br>
> Developed/Developing Country Paradigm from World<br>
> Development Indicators"<br>
><br>
> has been rejected by the list moderator. The moderator
gave the<br>
> following reason for rejecting your request:<br>
><br>
> "Blind carbon copies or other implicit destinations are
not allowed.<br>
> Try reposting your message by explicitly including the
list address in<br>
> the To: or Cc: fields."<br>
><br>
> Any questions or comments should be directed to the list
administrator<br>
> at:<br>
><br>
> <a moz-do-not-send="true"
href="mailto:at-large-owner@atlarge-lists.icann.org">at-large-owner@atlarge-lists.icann.org</a><br>
><br>
><br>
> _______________________________________________<br>
> ttf mailing list<br>
> <a moz-do-not-send="true"
href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a><br>
> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/ttf">https://mm.icann.org/mailman/listinfo/ttf</a><br>
><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ttf mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/ttf">https://mm.icann.org/mailman/listinfo/ttf</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ttf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/ttf">https://mm.icann.org/mailman/listinfo/ttf</a>
</pre>
</blockquote>
</body>
</html>