Date: Tue, 1 Jun 2021 19:01:52 -0400 From: grarpamp <grarpamp@gmail.com> To: clusteradm@freebsd.org Cc: freebsd-hubs@freebsd.org Subject: Re: MLMMJ Mail Archives to Update Coverage on bit0 rsync Message-ID: <CAD2Ti2-SBp5o2fbGKd1dBMLp%2Bssm4VnTxHmLeF4GUotiYrpLWQ@mail.gmail.com> In-Reply-To: <CAD2Ti29PtZmGUABnjkYf1Yd3f56Tq7r8hg1LM_CtcrEz6b38fQ@mail.gmail.com> References: <CAD2Ti29PtZmGUABnjkYf1Yd3f56Tq7r8hg1LM_CtcrEz6b38fQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
" Hi, this is the Mlmmj program managing the <list> mailing list. The message from <user> with subject <subject> was unable to be delivered to the list because the list address was not found in either the To: or CC: header. (The denied message is below.) " That was result of Bcc: to a MLMMJ list. Bcc: should probably be enabled on the lists to serve the function of "send a copy to a secondary lists (Bcc:) for interest and inclusion of parties, but don't expose such secondary lists to further replies by those in the primary lists (To: , Cc:) who blindly click 'reply all' thus continuing beyond initial fyi inclusion purpose". That could also help threads keep reference threading headers as lists come in and out of conversations, instead of breaking threads, originating new threads, etc. Various mailman lists out there do seem to have that capability enabled for that purpose, perhaps it is a config option or could be added to MLMMJ. questions@: > find 200 back issues
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2-SBp5o2fbGKd1dBMLp%2Bssm4VnTxHmLeF4GUotiYrpLWQ>