[technology taskforce] Fwd: Request to mailing list At-Large rejected

Jason Hynds jason.hynds at partsinc.biz
Wed May 25 10:29:42 UTC 2016


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.

For alternative behaviour, the administrator or moderator has to 
explicitly make a change:

    To accept all BCCs to the list and get rid of this message entirely:

      * 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"

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.

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 _would not 
have received it_ 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.

 From a pedantic viewpoint, whilst you may need to BCC to a 
/distribution list/ (an identifier that conveniently points to and 
expands into multiple email addresses), one would more conduct a 
broadcast or discussion with an /electronic mailing list/ / /listserv 
/(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 /to hide/ the action of messaging a 
mailing list as _per its original purpose_.

I do utilize /groups/ (in Google) and /mailing lists/ (in Mailman) 
sometimes for the convenience of being better than /distribution lists/ 
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.

Moderation for technical reasons or in line with an acceptable use 
policy is quite different to any concern about it being an "open list".

Good discussion. Have a great day!


Jason Hynds

On 5/23/2016 4:50 PM, Judith Hellerstein wrote:
> Hi Seun and Carlton,
> 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
> best,
> Judith
> _________________________________________________________________________
> Judith Hellerstein, Founder & CEO
> Hellerstein & Associates
> 3001 Veazey Terrace NW, Washington DC 20008
> Phone: (202) 362-5139  Skype ID: judithhellerstein
> E-mail:Judith at jhellerstein.com    Website:www.jhellerstein.com
> Linked In:www.linkedin.com/in/jhellerstein/
> Opening Telecom & Technology Opportunities Worldwide
> On 5/23/2016 4:57 PM, Seun Ojedeji wrote:
>> Sent from my LG G4
>> Kindly excuse brevity and typos
>> On 23 May 2016 20:25, "Carlton Samuels" <carlton.samuels at gmail.com> 
>> wrote:
>> >
>> > Here's a rule that defies reason...and evidence of this propensity 
>> to major in minor matters!
>> >
>> > So, pray tell, in context, what [is]/are [an] "implicit 
>> destination[s]"?
>> >
>> SO: In the case of blind copy, it is more of [they]/[you].....
>> >
>> And, again in context, might I ask why we are concerned about how you 
>> address to send rather than about what and who sends?
>> >
>> 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 ;-)
>> > Or, is this rule purely a politically correct surrogate for 
>> managing what is supposed to be an open list?
>> >
>> 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.
>> Regards
>> > -Carlton
>> >
>> >
>> > ==============================
>> > Carlton A Samuels
>> > Mobile: 876-818-1799
>> > Strategy, Planning, Governance, Assessment & Turnaround
>> > =============================
>> >
>> > ---------- Forwarded message ----------
>> > From: <at-large-owner at atlarge-lists.icann.org 
>> <mailto:at-large-owner at atlarge-lists.icann.org>>
>> > Date: Mon, May 23, 2016 at 11:28 AM
>> > Subject: Request to mailing list At-Large rejected
>> > To: carlton.samuels at gmail.com <mailto:carlton.samuels at gmail.com>
>> >
>> >
>> > Your request to the At-Large mailing list
>> >
>> >     Posting of your message titled "WB Abandoning the
>> > Developed/Developing Country Paradigm from World
>> >  Development Indicators"
>> >
>> > has been rejected by the list moderator.  The moderator gave the
>> > following reason for rejecting your request:
>> >
>> > "Blind carbon copies or other implicit destinations are not allowed.
>> > Try reposting your message by explicitly including the list address in
>> > the To: or Cc: fields."
>> >
>> > Any questions or comments should be directed to the list administrator
>> > at:
>> >
>> > at-large-owner at atlarge-lists.icann.org 
>> <mailto:at-large-owner at atlarge-lists.icann.org>
>> >
>> >
>> > _______________________________________________
>> > ttf mailing list
>> > ttf at atlarge-lists.icann.org <mailto:ttf at atlarge-lists.icann.org>
>> > https://mm.icann.org/mailman/listinfo/ttf
>> >
>> _______________________________________________
>> ttf mailing list
>> ttf at atlarge-lists.icann.org
>> https://mm.icann.org/mailman/listinfo/ttf
> _______________________________________________
> ttf mailing list
> ttf at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/ttf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ttf/attachments/20160525/781a9232/attachment.html>

More information about the ttf mailing list