Folks,
As of now, all current podlings (as defined in http://incubator.apache.org/podlings.xml) have been listed in DNS as if they were already TLPs. i.e. groovy.apache.org now exists. This was done as a result of improving the internal mail handling with the ASF, it highlighted an issue that has been masked by the old setup for a number of years now. As some of you may know, for a a number of years now, infrastructure has been rewriting incoming emails for podlings. i.e. d...@groovy.incubator.apache.org -> d...@groovy.apache.org This was done so that at the time of graduation, there was very little change required to a podling's email setup (just changing the outgoing address actually). Now, with the improved internal setup the spam/av scanning stack MTAs were failing to deliver mails because 'groovy.apache.org' did not exist in DNS, and so it failed the dns checks. We do not expect any negative fallout from this change, but this is a heads up that going forward all new podlings will need to be added to DNS as a TLP, before their mailing lists will work. This does apply to all podlings, not just groovy (in case there was any doubt). Note this email is not /private/ but private@incubator is the best way I can reach all podling mentors, and those who request new podlings etc most easily. So do no worry about the mixed private and public lists in the to: line. Many thanks, -- Tony On behalf of the Apache Infrastructure Team
pgpetMp1OWKEY.pgp
Description: PGP signature
