Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net
 designates 76.96.30.56 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: [Discuss] ASF hosted openoffice.org email service  [Was: Re:
 [Discussion] dev@openoffice.org]
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <4E4FF44E.6000401@shanecurcuru.org>
Date: Sat, 20 Aug 2011 12:17:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <14D88004-C290-40B3-9A24-077CB0C5B5E5@comcast.net>
References: 
 <CAP-ksogaUSKq+6kChq7OYV-3utjLLYZr5xNV53vH+N6y7s9fzw@mail.gmail.com>
	<4E4E6144.6050503@wtnet.de>
 <CAP-ksoirVUW6dAasS8-KLSkmvWJmN3cFKyaWYFQqQ+iPbWMBww@mail.gmail.com>
 <4E4E9456.8090509@wtnet.de>
 <F0151780-62C6-47ED-860D-DEE6954902C7@comcast.net> <4E4E9DCA.1050400@gmx.net>
 <229D299C-7F8F-4D83-875F-07BDC6795A83@comcast.net>
 <4E4ECE82.7040007@cfl.rr.com> <4E4FF44E.6000401@shanecurcuru.org>
To: ooo-dev@incubator.apache.org

Changing the subject as requested by Daniel

On Aug 20, 2011, at 10:52 AM, Shane Curcuru wrote:

> On 8/19/2011 4:58 PM, TJ Frazier wrote:
>> Hi, Dave
>> On 8/19/2011 13:48, Dave Fisher wrote:
>>>=20
>>> On Aug 19, 2011, at 10:30 AM, Mathias Bauer wrote:
>>>=20
>> [snip]
>>>> The foobar@openoffice.org mail addresses OTOH should be preserved. =
They
>>>> are only forwarding addresses now and they can be kept that way,
>>>> can't they?
>>>=20
>>> Not sure about it. There are considerations.
>>>=20
>>> (1) How do we get the forwarding data from Oracle? Is it legal to
>>> transfer the list, or is it required?
>>>=20
>>> (2) Will the ASF host this forwarding on the normal apache.org mail
>>> servers
>>>=20
>>> (3) Who on the OOO PPMC will handle the daily administration of =
these
>>> forwarders as individual email addresses change?
>>>=20
>>> Regards,
>>> Dave
>>>=20
>> For (1) and (3): the addresses are part of the account with OO.o. The
>> forwarding address is the user's registered (verified) email address =
for
>> the account. Accordingly, the info will be transferred with the =
account
>> data, and is administered (for changes) by the user.
>>=20
>> (2) Can't really say if ASF can/will forward. Why not?
>=20
> Currently, ASF infra provides mail forwarding and sending capability =
for committers, but no-one else.  Committers are people who have shown =
clear merit (i.e. they've been voted in by one of our project =
communities) and also have signed an iCLA, so we have some sort of =
relationship with them.
>=20
> Personally, I would not envision allowing any new me@oo.o email =
addresses to be created, unless they're for committers (who should =
probably use an @apache.org id instead).  I don't quite know what to do =
with the many existing aliases, however.  Short term we certainly can =
keep them (seem useful to people) but long term we would indeed need to =
see how 1) infra would support it, and 2) how the future PMC would =
provide oversight and manage any account issues (oh, yeah, that's your =
(3) above.

How would Infra support email forwarding for the openoffice.org domain? =
Would there be a text or xml file with a forwarding map in svn =
somewhere? Would all the email automatically go through spamassassin =
before forwarding?

If we had a single mapping then we can include redirection for all of =
the 100s of current OOo MLs into the several AOOo MLs along with the =
many individual emails.

Regards,
Dave


>=20
> - Shane