Issue 102643 - security team/issue mailing lists broken
Summary: security team/issue mailing lists broken
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: Unknown All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@ooo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-10 13:37 UTC by malte_timmermann
Modified: 2012-04-13 05:37 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description malte_timmermann 2009-06-10 13:37:29 UTC
We just created a new project "security", and now the old mailing list
security-team@ooo doesn't work anymore, I guess same for security-alerts@OOo.

failure notice:
> <security-team@openoffice.org>:
> Unable to find address team in project security, domain openoffice.org
> Do you mean httpd-security-team@openoffice.org?

I can't work around this by creating "team" and "alerts" list in the security
project, because then all project members could subscribe, while the "team" list
is only for some dedicated people.

Since this list is used from external security companies to inform us about not
disclosed security issues, this is quite urgent.
Comment 1 floeff+ooo 2009-06-10 13:59:05 UTC
Adding myself in Cc
Comment 2 stx123 2009-06-10 14:04:59 UTC
reassigning to support...
Comment 3 Unknown 2009-06-10 18:16:11 UTC
mt

Can I post test-emails to the mentioned mailing lists to see if it works fine?
Let me re-confirm that you mentioned these two mailing lists weren't working:

security-alerts@openoffice.org
security-team@openoffice.org

Am I right?

Regards
N Deepak
Support Operations.
Comment 4 stx123 2009-06-10 20:20:57 UTC
As you see from Malte's failure notice we know that
security-team@openoffice.org
doesn't work. Feel free to send test-messages to security-team@openoffice.org.

We are not sure whether security-alerts@openoffice.org works.
But let's wait with testing this list with dozens of subscribers until we know
the status of security-team@openoffice.org.
Comment 5 Unknown 2009-06-12 23:59:03 UTC
Hi

We have filed an internal ticket to look in to this issue & will respond as soon
as possible.

Regards
N Deepak
Support Operations.
Comment 6 stx123 2009-06-16 12:37:02 UTC
Do you have an update for us on this P2 issue?
Comment 7 Unknown 2009-06-16 15:54:40 UTC
Hi

I have got some updates from our internal team & have asked them few questions
in return. I shall update you about the issue in a consolidated format once I
receive aswers from our team.

Regards
N Deepak
Support Operations.
Comment 8 stx123 2009-06-18 12:10:24 UTC
Do you have an update for us on this P2 issue after a week?
Comment 9 Unknown 2009-06-18 14:06:31 UTC
Hi

Our engineers have found that there does exist a bug in the following scenario.

1. Create new mailing list (test-new) in www project 
2. Create a new project (test)
3. Send a mail to test-new@domain. You will receive an error mail message saying
"Unable to find address new in project test, domain" 

So, the issue was only with the mailing threads xxx-yyy@domain and if a project with
name xxx exists. <With respect to this issue, the workaround is to change the
project name from security to something else.> This issue is fixed in CEE
versions 5.x & above.  Please let me know if you need more information.

Regards
N Deepak
Support Operations.
Comment 10 malte_timmermann 2009-06-18 14:49:10 UTC
Hello N Deepak,

of course renaming the project is not an option.
And waiting for the deployment a newer version of CEE is also not an option.

You said the bug only exists when the project was created after the mailing list.
Would it help to delete the mailing list, and create it again?

Thanks,
Malte.
Comment 11 Unknown 2009-06-19 14:16:07 UTC
Malte

Sounds like a good option, but you will have to make sure that this time you
name the mailing list to something else that does not coincide with a project's
name in the entire openoffice.org domain. Let me know if you need more
information from me to help you further or if I can go ahead & close this case
for now. :)

Thanks
N Deepak
Support Operations.
Comment 12 malte_timmermann 2009-06-19 14:39:00 UTC
Well, of course my suggestion was to recreate the list with exactly the _same_
name as before.

You stated that the issue would only exist when the project was created _after_
the list.

Shouldn't it work then?
Comment 13 Unknown 2009-06-22 17:09:34 UTC
Malte

The issue lies only with the mailing lists of the 'www' project alone. So, you
will have to create a new mailing list 'xxx@openoffice.org' where 'xxx' is not a
name of any existing project in the entire site openoffice.org.

If you still would insist on using the same mailing list, then you will have to
make sure all the posters post their respective emails to the mailing list
address in the following format:

<security-alerts@www.openoffice.org>
<security-team@www.openoffice.org>

I have tested sending emails to the above mentioned mailing address formats & it
does work. Please notice the '@www.openoffice.org' in the email address. If you
still have any doubts regarding this issue, please feel free to leave a phone
number where I can reach you.

Regards
N Deepak
Support Operations.
Comment 14 malte_timmermann 2009-06-22 18:12:30 UTC
Thanks for the update - I will clarify with the team if they want to use @www,
or a different list name...
Comment 15 Unknown 2009-06-23 20:39:28 UTC
Mt..

I removed my name from both the mailing lists. I would also suggest you to
verify the same. I think that cuts down the issue to your decision on how to
proceed further from here. So, could I go ahead & close this ticket for now?

Regards
N Deepak
Support Operations.
Comment 16 Unknown 2009-06-23 20:39:33 UTC
Mt..

I removed my name from both the mailing lists. I would also suggest you to
verify the same. I think that cuts down the issue to your decision on how to
proceed further from here. So, could I go ahead & close this ticket for now?

Regards
N Deepak
Support Operations.
Comment 17 malte_timmermann 2009-06-24 09:35:24 UTC
Since you wont fix this issue in our current environment, feel free to close it...
Comment 18 stx123 2011-03-23 16:21:22 UTC
Reset QA Contact to new default
Comment 19 Rob Weir 2012-04-12 18:07:19 UTC
legacy infrastructure issue, not pertinent to Apache