Junping, I think many people don't know who netease is, at least your contribution to this list will help.
I think the point people on this list are making is that you need to setup specific PTR (that do not look like auto-generated) for the IPs that DO send emails. You need to make sure all your dynamic IPs (and other IPs) cannot send email directly and have to go through your mail servers. Ideally the PTR should match what is in the helo (and vice versa). Looking at your SPF, https://dmarcian.com/spf-survey/163.com, there are not many IPs listed as potentially sending emails (compared to other SPF), so you should be able to set some specific PTR for them. Also as Suresh mentioned, if this blocking list is not blocking many emails I would not worry much. On Tue, Jun 14, 2016 at 6:11 AM, 陈俊平 <chenjunp...@corp.netease.com> wrote: > > > Helpful thoughts Steve, many thanks again to you and to all :) > > Today Netease has 700+ million users and a lot of servers as well as IPs, > you can see all IPs and ranges from the SPF record of domain 163.com, > sothat we use the format "mxx-xx.domain" for reverse dns for balance. > > We keep reverse dns of our IPs to comply with standards and best > practises, well, SpamRats doesn't elaborate the saying "best practise" on > their page which'd create confusion. > > If I have no luck to receive SpamRats' reply then I will try changing the > reverse dns of 123.58.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" <steve.freeg...@fsl.com> 写道： > > > > On 14/06/16 13:16, "陈俊平 via mailop.org" <chenjunp...@corp.netease.com> > <chenjunp...@corp.netease.com> wrote: > > > 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 > <http://ng5-vm13.bullet.mail.gq1.yahoo.com>.* > > > Doesn't contain any octets of the IP address > > > *$ dig +short -x 209.85.218.44* > *mail-oi0-f44.google.com <http://mail-oi0-f44.google.com>.* > > > Has a single octet of the IP address but clearly shows mail- as the > function. My own heuristics would allow this, can't speak for others. > > *$ dig +short -x 17.171.37.67* > *mdn-txn-msbadger0502.apple.com <http://mdn-txn-msbadger0502.apple.com>.* > > > Again - no octets of the IP address appear within the name. > > Kind regards, > Steve. > > -- > Steve Freegard > Development Director > Fort Systems Ltd. > > > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
