Issue 7129 - Messages to features@api.openoffice.org have to be moderated
Summary: Messages to features@api.openoffice.org have to be moderated
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-19 17:53 UTC by stx123
Modified: 2003-12-06 14:52 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
moderation message (5.56 KB, text/plain)
2002-08-19 17:54 UTC, stx123
no flags Details
another moderation message (3.17 KB, text/plain)
2002-08-20 12:36 UTC, stx123
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2002-08-19 17:53:20 UTC
The current configuration is that subscribers of the list 
ooposters@openoffice.org are allowed to send to any list without the need of 
moderation.
This doesn't work for features@api.openoffice.org. The most recent example is a 
message from thomas.lange@sun.com (who is subscribed to ooposters).
The moderation message is attached.
Comment 1 stx123 2002-08-19 17:54:17 UTC
Created attachment 2545 [details]
moderation message
Comment 2 stx123 2002-08-20 12:36:45 UTC
Created attachment 2555 [details]
another moderation message
Comment 3 Unknown 2002-08-21 22:45:53 UTC
accepting. initiating research.
Comment 4 Unknown 2002-08-30 17:54:38 UTC
Opened internal issue. 

As a short-term workaround, how about placing ooposters in the
"allowed posters" section of the features mailing list?
Comment 5 stx123 2002-08-30 18:03:51 UTC
Hi, thanks for the suggestion; I hesitate to duplicate data and
generate inconsistencies. My short term solution is to moderate :-(
Comment 6 Unknown 2002-10-30 06:05:48 UTC
Hi Stefan,

I am researching a moderation solution for you here & will update you
tomorrow.
Talk to ya soon,

Eric
Comment 7 Unknown 2002-10-30 06:11:11 UTC
I emailed the assigned engineer on what exactly needs to be done to
get the expected results. Will update this issue as soon as I get the
information.
Eric
Comment 8 Unknown 2002-10-30 16:49:51 UTC
Hi Stefan,
The engineer says he is a bit confused about duplicate data &
incosistencies.
He mentions the following.

The way it's supposed to work is that all mailing lists 
set to list type 'allowed-posters' should allow subscribers of ooposters 
to mail without moderation. That's a one-off for openoffice that was 
implemented a long time ago as I was told. I don't see any data 
redundancy in doing this? Maybe a misunderstanding in that 
he may have thought he had to copy subscribers from ooposters to 'Edit
allowed subscribers', 
which is not what they should do this.
Stefan, Can you let me know where we should go with this isue from here?
Thanks,

Eric
Comment 9 stx123 2002-10-30 19:14:57 UTC
Hi, my understanding of the configuration is a bit different.
Not only lists of type "allowed-posters" but also type "discuss" allow
posts from senders, who are not subscribed to the list itself - but
are subscribers to ooposters. A working example is
interface-discuss@ooo and features@sw.openoffice.org.
The goal is to have a domain wide allowed-posters list! We can't
maintain each list's allowed-posters entries, if we have a new trusted
community member.
This worked for all features@<project> list, but not for
features@api.openoffice.org. During my investigations today I found,
that 1 entry, which is in all other list's allowed-posters
subscribers, was missing for features@api. I added the needed entry
and will see, if this solved the problem.
Changing status to resolved/fixed.
Thanks, Stefan.
Comment 10 michael.bemmer 2003-03-24 08:23:47 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 11 michael.bemmer 2003-03-24 08:28:16 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.