incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: Bugzilla e-mail is bouncing and other e-mail issues
Date Fri, 09 Sep 2011 14:10:38 GMT
It sounds like there was general agreement to make all notifications
go to ooo-issues@i.a.o.  But did anyone follow through (or is anyone
intending to follow through) with a JIRA issue, as Mark requested?

I'm happy to do this myself, but I think it would be better for
someone with more background in how BZ was working before to engage
with Infra@ on this.


On Mon, Sep 5, 2011 at 3:51 AM, Mark Thomas <> wrote:
> Over the weekend, the ASF infra team noticed some e-mail from the ooo BZ
> instance was bouncing. Specifically, e-mail to
> There also are 142 other
> accounts.
> The delivery failure may be a temporary issue but it highlights a two
> tasks for the ooo podling.
> 1. These accounts need to be switched to ASF mailing lists. Please
> identify the required changes and open a Jira ticket with the
> infrastructure team to implement the changes.
> Note: These accounts were enabled. ASF Infra security policy requires
> that BZ accounts representing mailing lists are disabled. All 143
> accounts have been disabled. This does not stop update notifications
> being sent but it does stop people requesting password resets for these
> accounts or logging on using these accounts.
> 3. The assigned to field is set to just about anything other than
> ooo-dev@incubator.a.o. In the main ASF Bugzilla instance, this field is
> hard-coded to the relevant project's dev list and is read-only. This
> ensures that any updates to any issue are sent to the dev list. ASF
> policy requires that all issue tracker updates are sent to a project
> mailing list (usually dev@ or issues@) so that the community is aware of
> updates to the issues. Please decide how you want to handle this and
> then open a Jira ticket with the infrastructure team to make the changes.
> Please note I am not subscribed to this list and will not be monitoring
> it for replies. If you need to contact the infrastructure team please
> use the usual channels.
> Mark

View raw message