Let's keep the two things separate: There's Pony Mail, and then there's
lists.apache.org which is a specific installation of it.
In the specific agreement we have about lists.apache.org, we wanted the
'.incubator' part of the mailing list IDs stripped, so we wouldn't have
to fix that every single time on graduation - it would just work when
projects became TLPs.
I realize this poses an issue with the subscribe button, but it's
something we (infra) are willing to live with for the time being, if it
means less overall work for an understaffed infra team.
We could, as I said on the JIRA ticket you raised, have
$podling.apache.org be a valid MX record from the beginning, but I'm
sure someone on this list will protest ;-)
So, in a way, we're caught between what's practical and what's proper.
With regards,
Daniel.
On 06/28/2016 04:02 PM, Stian Soiland-Reyes wrote:
Hi,
I'm helping the new Juneau podling, and some confusion came because
https://lists.apache.org/[email protected]
claims the address is [email protected]
and lists [email protected] as it's "Subscribe" address.
Reply-To on the list is however [email protected], as
you would expect.
Generally for podling both address styles work - and we just keep the
non-incubator address "secret". However in this case the DNS has not
been updated and sending to [email protected] fails.
The new lists.apache.org interface makes it a bit confusing for
committers and specially newcomers.
Are we moving to using the style dev@$project.apache.org straight away
for new podlings, or is this simply a bug in Ponymail? (We have
earlier discussed this as a possibility for website URLs)
I've raised the bug
https://github.com/apache/incubator-ponymail/issues/100 but wanted to
check here as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
