Phil, (01)
> "Blind carbon copies or other implicit destinations are
> not allowed. (02)
I am aware that that is disallowed (probably for good reasons).
We need to work within that constraint -- i.e. use "c.c." and not
"b.c.c." for the purpose. Or, if "b.c.c." needs to be used, go on
and approve the post right away. (03)
> Somehow, the system turns what is sent to the nls-archive
> list into a BCC or other implicit destination. (04)
I don't think that is the case ... my last message to you got
into [nls-archive] properly (I think), without administrator
intervention. Let's look at this one again, and see what happens.
-- try NOT to approve this, even if you got asked to, but let's
follow-up (maybe even via the phone) on it quickly. (05)
I'm including Jonathan in the conversation ... he probably knows
more than I do. (06)
Regards. =ppy
-- (07)
PhilipGust wrote Mon, 27 Feb 2006 12:41:37 -0800:
> The details page states the reason as:
>
> "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.". We often CC the nls-technical or nls-legal list,
> for example. Somehow, the system turns what is sent to the nls-archive
> list into a BCC or other implicit destination. Could you check on how
> this is being done to see if that's the case? (08)
> At 08:57 AM 2/27/2006, you wrote:
>> Phil,
>>
>> Can you tell (from the admin message) "why" you would need to approve
>> them?
>>
>> The [nls-archive] list should be configured with "the union of all
>> other list-memberships" (i.e. everyone from nls-restore,
>> nls-technical, and nls-legal ... etc.) being treated as "auto accept"
>> for posting. That configuration option can be found on the page:
>> http://chm.cim3.net/mailman/admin/nls-archive/privacy/sender
>>
>> When I started the list, I've already done that ... but if you are
>> adding new subscribers to anyone of the other lists, this
>> "auto-accept" lists needs to be similarly expanded. (see:
>> http://chm.cim3.net/forum/nls-archive/2005-11/msg00001.html#nid07)
>> Maybe, this is what's causing the problem.
>>
>> Let's see if this message gets archived ... if it doesn't
>> (automatically), then maybe the issue is caused by something else.
>> Please check and advise.
>>
>> Cheers. =ppy
>> -- (09)
>> Philip Gust wrote Mon, 27 Feb 2006 06:36:39 -0800:
>>> Peter,
>>> I find that I'm having to approve every entry into the nls-archive
>>> list. Is there some way to set it so that items from the
>>> nls-restore, nls-technical, and nls-legal go into the archive without
>>> requiring approval of every one?
>>>
>>> Philip Gust
>>> Nouveau Systems, Inc.
>>> phone: +1 650 961-7992
>>> fax: +1 520 843-7217
>>>
>>> mailto: gust@NouveauSystems.com (010)
|