You can't generalize from a single sample. I see the pattern of email addresses with varying amounts of numbers in them, some of them also very long, every year with GSoC students.
Uli On Thu, August 20, 2015 00:32, sebb wrote: > The recent spammers have used quite unusual e-mail addresses, with > very long numbers in them. > > On 19 August 2015 at 23:18, Ulrich Stärk <u...@spielviel.de> wrote: >> So how would you distinguish a spammer's subscription request from that >> of a valid user? I certainly >> can't from looking at the email address alone. >> >> Uli >> >> On 17.08.15 14:46, sebb wrote: >>> On 17 August 2015 at 10:52, Gavin McDonald <ga...@16degrees.com.au> >>> wrote: >>>> So I checked the config for dev@community and it is set up as a normal >>>> dev@ list operates. >>>> >>>> Therefore anyone can subscribe to the list and post. >>>> >>>> The only thing we can do here is change it to subscription moderation >>>> - that is an on|off switch so therefore >>>> ALL subscription requests will have to be approved by a moderator. >>>> >>>> If you are ok with that I can make the change . >>> >>> +1 from me. >>> >>> >>>> I checked the logs and it looks like a mod has removed the >>>> subscription for the user in this thread. >>> >>> That was me, sorry forgot to let the list know. >>> >>>> Let me know, >>>> >>>> Gav… >>>> >>>>> On 17 Aug 2015, at 9:48 am, Ross Gardler <ross.gard...@microsoft.com> >>>>> wrote: >>>>> >>>>> Not sure if it's possible (you reply made me think I may be mixing up >>>>> Google Groups features with our lists) >>>>> >>>>> Sent from my Windows Phone >>>>> From: jan i <mailto:j...@apache.org> >>>>> Sent: 8/17/2015 1:44 AM >>>>> To: dev@community.apache.org <mailto:dev@community.apache.org> >>>>> Cc: Roman Shaposhnik <mailto:ro...@shaposhnik.org>; Apache >>>>> Infrastructure <mailto:infrastruct...@apache.org> >>>>> Subject: Re: What is the legal basis for enforcing release policies >>>>> at ASF? >>>>> >>>>> On 17 August 2015 at 10:24, Ross Gardler <ross.gard...@microsoft.com >>>>> <mailto:ross.gard...@microsoft.com>> wrote: >>>>> >>>>>> Moderating first posts would be better. >>>>>> >>>>> +1 to that solution (did not know that was possible), that way the >>>>> moderators to not get overloaded with work. >>>>> >>>>> Alternative would be to allow apache ID, and moderate others. >>>>> >>>>> rgds >>>>> jan i. >>>>> >>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: sebb [mailto:seb...@gmail.com <mailto:seb...@gmail.com>] >>>>>> Sent: Monday, August 17, 2015 1:22 AM >>>>>> To: Roman Shaposhnik <ro...@shaposhnik.org >>>>>> <mailto:ro...@shaposhnik.org>> >>>>>> Cc: ComDev <dev@community.apache.org >>>>>> <mailto:dev@community.apache.org>>; Apache Infrastructure < >>>>>> infrastruct...@apache.org <mailto:infrastruct...@apache.org>> >>>>>> Subject: Re: What is the legal basis for enforcing release policies >>>>>> at ASF? >>>>>> >>>>>> This is a new subscription (send an e-mail to dev-log@community.a.o >>>>>> <mailto:dev-log@community.a.o> for >>>>>> details) >>>>>> >>>>>> Perhaps we need to consider moderated subscriptions for this list. >>>>>> >>>>>> On 16 August 2015 at 21:33, Roman Shaposhnik <ro...@shaposhnik.org >>>>>> <mailto:ro...@shaposhnik.org>> wrote: >>>>>>> This email echoing keeps happening. I thought we've dealt with it, >>>>>>> no? >>>>>>> >>>>>>> >>>>>>> ---------- Forwarded message ---------- >>>>>>> From: 田義忠 <name0905189...@icloud.com >>>>>>> <mailto:name0905189...@icloud.com>> >>>>>>> Date: Sun, Aug 16, 2015 at 1:27 PM >>>>>>> Subject: Re: What is the legal basis for enforcing release policies >>>>>>> at >>>>>> ASF? >>>>>>> To: "dev@community.apache.org <mailto:dev@community.apache.org>" >>>>>>> <dev@community.apache.org <mailto:dev@community.apache.org>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 從我的 iPhone 傳送 >>>>>>> >>>>>>>> Roman Shaposhnik <ro...@shaposhnik.org >>>>>>>> <mailto:ro...@shaposhnik.org>> 於 2015年8月17日 04:25 寫道： >>>>>>>> >>>>>>>>> On Fri, Aug 14, 2015 at 3:59 PM, Shane Curcuru >>>>>>>>> <a...@shanecurcuru.org <mailto:a...@shanecurcuru.org>> >>>>>> wrote: >>>>>>>>>> On 8/7/15 7:53 AM, Niclas Hedhman wrote: >>>>>>>>>> Bill, >>>>>>>>>> So I can release "Niclas Hadoop platform, based on Apache >>>>>>>>>> Hadoop" >>>>>>>>>> ?? I thought the discussion a few years ago was that this was >>>>>> misleading... >>>>>>>>> >>>>>>>>> No, you cannot. See our actual trademark policy: >>>>>>>>> >>>>>>>>> >>>>>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww >>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww> >>>>>>>>> .apache.org >>>>>>>>> <http://apache.org/>%2ffoundation%2fmarks%2ffaq%2f%23products&data=01%7c01%7c >>>>>>>>> ross.gardler%40microsoft.com >>>>>>>>> <http://40microsoft.com/>%7c53be77cdd3ef4dca285308d2a6dced17%7c72 >>>>>>>>> f988bf86f141af91ab2d7cd011db47%7c1&sdata=DdcuJh%2bbhphaiy7yoW%2f2caG >>>>>>>>> y15TIxfrsXg1V%2fHh9Jsg%3d >>>>>>>>> >>>>>>>>> Our release policy, as Roman originally asked about, applies only >>>>>>>>> to >>>>>>>>> ASF projects, and has no bearing on third parties. However our >>>>>>>>> trademark policy, and trademark law, prevents third parties from >>>>>>>>> publicly providing software using our trademarks. >>>>>>>>> >>>>>>>>> Our operational policies only apply to our projects, just like >>>>>>>>> any >>>>>>>>> other corporation. Some policies, like our license itself and >>>>>>>>> our >>>>>>>>> formal trademark policy, inform the rest of the world how they >>>>>>>>> are >>>>>>>>> allowed to use our websites, software code, and brands. >>>>>>>>> >>>>>>>>> Make sense? >>>>>>>> >>>>>>>> It does, but our relationships with downstream Linux vendors (just >>>>>>>> to >>>>>>>> take the most obvious example) set a very confusing precedent. >>>>>>>> >>>>>>>> Shane, if would be super helpful if you took a look at: >>>>>>>> >>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpkgs.org%2fsearch%2fhadoop&data=01%7c01%7cross.gardler%40microsoft.com%7c53be77cdd3ef4dca285308d2a6dced17%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZXiKGbcB8ekfCts3JOcHVPYpX35xcqfr87Adbmf77%2f8%3d >>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpkgs.org%2fsearch%2fhadoop&data=01%7c01%7cross.gardler%40microsoft.com%7c53be77cdd3ef4dca285308d2a6dced17%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZXiKGbcB8ekfCts3JOcHVPYpX35xcqfr87Adbmf77%2f8%3d> >>>>>>>> >>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpkgs.org%2fsearch%2fmaven&data=01%7c01%7cross.gardler%40microsoft.com%7c53be77cdd3ef4dca285308d2a6dced17%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=bbku3kk8GRT8rNXWo5gwhRfpWIOoouH%2buNNzmrCpI0I%3d >>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpkgs.org%2fsearch%2fmaven&data=01%7c01%7cross.gardler%40microsoft.com%7c53be77cdd3ef4dca285308d2a6dced17%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=bbku3kk8GRT8rNXWo5gwhRfpWIOoouH%2buNNzmrCpI0I%3d> >>>>>>>> >>>>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpkgs >>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpkgs>. >>>>>>>> org%2fsearch%2fsubversion&data=01%7c01%7cross.gardler%40microsoft.com >>>>>>>> <http://40microsoft.com/> >>>>>>>> %7c53be77cdd3ef4dca285308d2a6dced17%7c72f988bf86f141af91ab2d7cd011db4 >>>>>>>> 7%7c1&sdata=BEHyTF%2b6dOsaARgvSX3%2bp1gWPkiVjbg7wODXVv2tzA8%3d >>>>>>>> and pubished your narrative of how the ASF branding policies apply >>>>>>>> in >>>>>>>> both cases. >>>>>>>> >>>>>>>> The 3 projects I'm picking represent a pretty diverse set of cases >>>>>>>> of >>>>>>>> how PMCs are conducting themselves. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Roman. >>>>>> >>>> >>>> Gav... >>>> >>>> ( ( ( >>>> ( )\ ) )\ ) )\ ) ( ) >>>> ) >>>> )\ (()/((()/( (()/( )\ ) ( ) ( /( ( ( >>>> ( /( ( ( ( >>>> ((((_)( /(_))/(_)) /(_)) ( (()/( )( ( /( ( )\()))( ))\ >>>> ( )\()) ))\ )( ))\ >>>> )\ _ )\ (_)) (_))_| (_)) )\ ) /(_))(()\ )(_)) )\ (_))/(()\ /((_) >>>> )\ (_))/ /((_)(()\ /((_) >>>> (_)_\(_)/ __|| |_ |_ _| _(_/((_) _| ((_)((_)_ ((_)| |_ ((_)(_))( >>>> ((_)| |_ (_))( ((_)(_)) >>>> / _ \ \__ \| __| | | | ' \))| _|| '_|/ _` |(_-<| _|| '_|| || |/ >>>> _| | _|| || || '_|/ -_) >>>> /_/ \_\ |___/|_| |___||_||_| |_| |_| \__,_|/__/ \__||_| >>>> \_,_|\__| \__| \_,_||_| \___| >>>> >>>> >>>> >>>> >>>> >
