[mailop] Help - Anyone know a GitHub People

2016-02-25 Thread
Hello team, I am a postmaster of Netease Inc.(NASDAQ: NTES), we are a professional email service provider in China with domains 163.com, 126.com, yeah.net and etc. Recently we seems to miss a lot of GitHub emails(such as GitHub Reigister Verify Emails), as our logfiles tell, Github dose no

Re: [mailop] Help - Anyone know a GitHub People

2016-02-25 Thread
ging from on my domain to 163.com users that don't exist. Sent from my mobile. Please excuse any unusual brevity or typos while I'm on the go. On 25 Feb 2016, at 10:23 PM, 陈俊平 wrote: Hello team, I am a postmaster of Netease Inc.(NASDAQ: NTES), we are a professional email

Re: [mailop] Help - Anyone know a GitHub People

2016-02-25 Thread
Greetings team, For Github contact issue - Thank you Franck et al very much for all your helps, if you have a contact at GitHub, please help to introduce:) For Netease spamming issue - Netease are having nearly 700 million users now, users send out all kinds of emails, a majority of them ar

Re: [mailop] Help - Anyone know a GitHub People

2016-02-25 Thread
The closing of connections are strange, it could be due to the GFW or some networking problem. We published some MX-proxy servers oversea for domains 163.com,126.com,yeah.net,vip.163.com,vip.126.com,188.com,etc, such as: $ dig +short 163mx01.mxmail.netease.com. 220.181.14.143 220.181.14.

[mailop] why "not comply with best practices" on SpamRats?

2016-06-14 Thread
Hello All, One of my IP address 123.58.177.172 got blacklisted on SpamRats' RBL, when tried removing it from the blacklist I got a rejection as below: >> Does IP Address comply with reverse hostname naming convention... Failed! >> RATS-Dyna - On the list. To be removed go here >> >> The IP a

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-14 Thread
Thanks guys, as Suresh mentioned, Netease has a large number of users and a lot of IP addresses, each one has been put a reverse DNS record and its reverse DNS has a A record pointing back to the same IP. As the one hitting SpamRats' RBL, its PTR and the A of the reverse DNS looks fine, rig

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-14 Thread
Here're some reverse dns of big senders, they also use the format "x-x.xx.domain". $ dig +short -x 98.136.219.65 ng5-vm13.bullet.mail.gq1.yahoo.com. $ dig +short -x 209.85.218.44 mail-oi0-f44.google.com. $ dig +short -x 17.171.37.67 mdn-txn-msbadger0502.apple.com. Things are strange that

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-14 Thread
.177.172, for example: dig +short -x 123.58.177.172 m172-177.vip.163.com.<== present mail-wmsvr2.vip.163.com.<== new Regards, -Junping 在 2016-06-14 20:47:41,"Steve Freegard" 写道: On 14/06/16 13:16, "陈俊平 via mailop.org" wrote: Here're some re

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-14 Thread
liuxi...@126.com is a hacked account and abused to send out spams, it's disabled yesterday after our system recognizes. Netease operates email service on several domains including 163.com,126.com,yeah.net,vip.163.com,vip.126.com,188.com,etc. We try all means to stop spam but as we all know

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-14 Thread
Correct, in fact the number "163" is the very first dial-up line phone number on 1990s in China, at that time the first thing/icon that Chinese cyber citizen knows and remembers is the number "163" - they dialed this number everytime before they start surfing the Internet. That's also why

Re: [mailop] why "not comply with best practices" on SpamRats?

2016-06-20 Thread
Hi all, Today I got reply from SpamRats, they delisted our IP from blacklist. Recently part of people on this list suggest Netease changing our PTR to match "the best practise", some suggest SpamRats should change its rules, some suggest take no move or others. To make a easy world, we wi

[mailop] FacebookMail Contact?

2016-11-22 Thread
Hello Team, Is there any one from Facebook or got their contacts? The domain facebookmail.com is making a lot of SMTP connections to my MX servers and doing "SMTP RCPT TO" to many sorted and invalid accounts, whose requests are so many that it results in a DDOS-like attack. I appreciate a