[mailop] Help - Anyone know a GitHub People

[陈俊平]

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 not send out these emails.


I'd tried posting a support request at page https://github.com/contact , 
sending emails to ab...@github.com,h...@github.com,supp...@github.com, and some 
other ways to reach out to GitHub team. Unluckily I get no reply so far.


Now I turned to this list for help, please help to forward this message if you 
knew someone in GitHub. Thank you very very much!




Best Wishes,




-Junping Chen


chenjunp...@corp.netease.com


Netease Inc.(NASDAQ: NTES)



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[ml+mailop]

Maybe they run into something like this?

220 126.com Anti-spam GT for Coremail System (126com[20140526])
EHLO 
Connection to 126mx02.mxmail.netease.com closed by foreign host.

It takes a long time to get any reply... and then your sever
simply closes the connection.


And from a different system:

220 126.com Anti-spam GT for Coremail System (126com[20140526])
EHLO 
250-mail
250-PIPELINING
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-coremail 
1Uxr2xKj7kG0xkI17xGrU7I0s8FY2U3Uj8Cz28x1U7Ic2I0Y2UFWs58gUCa0xDrj
250-STARTTLS
250-SIZE 73400320
250 8BITMIME
mail from:<>
250 Mail OK
rcpt to:
Connection closed by foreign host.

Hmm...

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[Rich Kulawiec]

On Thu, Feb 25, 2016 at 07:17:56PM +0800, ?? wrote:
> 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.

I can't speak for GitHub, but I've had most of those domains blacklisted
for over a decade because of (a) nonstop spam, phishing, and other forms
of email abuse (b) failure to respond to abuse reports (c) failure to
support RFC-2142 mandated role addresses.

---rsk

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[Ryan Harris via mailop]

Responded Off list

On Thu, Feb 25, 2016 at 5:25 AM, Rich Kulawiec  wrote:

> On Thu, Feb 25, 2016 at 07:17:56PM +0800, ?? wrote:
> > 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.
>
> I can't speak for GitHub, but I've had most of those domains blacklisted
> for over a decade because of (a) nonstop spam, phishing, and other forms
> of email abuse (b) failure to respond to abuse reports (c) failure to
> support RFC-2142 mandated role addresses.
>
> ---rsk
>
> ___
> 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

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

[Franck Martin via mailop]

Well,

This is not a friendly welcome...

Please you have an opportunity to engage and get things fixed, so don't
throw a ton of bricks on the first email.

Thanks.

On Thu, Feb 25, 2016 at 4:25 AM, Rich Kulawiec  wrote:

> On Thu, Feb 25, 2016 at 07:17:56PM +0800, ?? wrote:
> > 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.
>
> I can't speak for GitHub, but I've had most of those domains blacklisted
> for over a decade because of (a) nonstop spam, phishing, and other forms
> of email abuse (b) failure to respond to abuse reports (c) failure to
> support RFC-2142 mandated role addresses.
>
> ---rsk
>
> ___
> 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

[mailop] Very large spike in false positives with Microsoft domains

[Dickie LaFlamme]

I wanted to see if other followers have heard any chatter about Microsoft
incorrectly classifying hard bounces for other providers/customers. We've
been trying to get to the root cause of why they could be creating so many
false positives for our platform over the past few weeks.

Final-Recipient: rfc822; (*taken out for confidentially*)@hotmail.com
Action: failed
Status: 5.4.0

By the RFC they should be at least including a diagnostic code, but they
are not, this is from a full header to note as well.

Final-Recipient: rfc822;(*taken out for confidentially*)@hotmail.com
Action: failed
Status: 5.0.0 (undefined status)
Remote-MTA: dns;mx3.hotmail.com (65.55.33.135)
Diagnostic-Code: smtp;554 Transaction failed
X-PowerMTA-BounceCategory: other

Essentially all we got back from Microsoft was that "this should be
classified as a soft bounce in your system": No help since we knew that.
We've since reclassified that bounce as well as this bounce below:

Final-Recipient: rfc822; (*taken out for confidentially)*@hotmail.com
Action: failed
Status: 5.5.4
Diagnostic-Code: smtp;501 5.5.4 Invalid arguments


We've seen this occuring at Hotmail, Live.com  and
Outlook.com . I'm not looking for a golden ticket from
anyone, but I wanted to see if fellow Deliverability professionals are
seeing these kind of problems from Microsoft domains. We're just left
scratching our heads as we try to fight these fires for our customers both
the deliverability team and engineers.

Has anyone else been having these problematic issues with Microsoft
domains?

Thanks,

[image: Dyn logo, Dyn.com] 
[image: Dyn facebook
account] [image:
Dyn LinkedIn account] 

Dickie LaFlamme / Deliverability Specialist
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Very large spike in false positives with Microsoft domains

[Michael Wise]

You should have seen the last of, “Transaction Failed” at about 1pm last 
Thursday, Feb 18th.
If you’ve seen it since, we need to see the whole bounce.

As to the rest … I’d need to see some more explicit samples. “Redacted” is fine.
But we need to know the banner you got when you connected, and as much of the 
transaction as you can share.

Aloha,
Michael.
--
Michael J Wise | Microsoft | Spam Analysis | "Your Spam Specimen Has Been 
Processed." | Got the Junk Mail Reporting 
Tool ?

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Dickie LaFlamme
Sent: Thursday, February 25, 2016 11:32 AM
To: mailop@mailop.org
Subject: [mailop] Very large spike in false positives with Microsoft domains

I wanted to see if other followers have heard any chatter about Microsoft 
incorrectly classifying hard bounces for other providers/customers. We've been 
trying to get to the root cause of why they could be creating so many false 
positives for our platform over the past few weeks.

Final-Recipient: rfc822; (taken out for 
confidentially)@hotmail.com
Action: failed
Status: 5.4.0

By the RFC they should be at least including a diagnostic code, but they are 
not, this is from a full header to note as well.

Final-Recipient: rfc822;(taken out for 
confidentially)@hotmail.com
Action: failed
Status: 5.0.0 (undefined status)
Remote-MTA: 
dns;mx3.hotmail.com
 (65.55.33.135)
Diagnostic-Code: smtp;554 Transaction failed
X-PowerMTA-BounceCategory: other

Essentially all we got back from Microsoft was that "this should be classified 
as a soft bounce in your system": No help since we knew that. We've since 
reclassified that bounce as well as this bounce below:

Final-Recipient: rfc822; (taken out for 
confidentially)@hotmail.com
Action: failed
Status: 5.5.4
Diagnostic-Code: smtp;501 5.5.4 Invalid arguments


We've seen this occuring at Hotmail, 
Live.com
 and 
Outlook.com.
 I'm not looking for a golden ticket from anyone, but I wanted to see if fellow 
Deliverability professionals are seeing these kind of problems from Microsoft 
domains. We're just left scratching our heads as we try to fight these fires 
for our customers both the deliverability team and engineers.

Has anyone else been having these problematic issues with Microsoft domains?

Thanks,

[Dyn logo, 
Dyn.com]

[http://dyn.com/wp-content/uploads/2013/08/esignature-icon-dyn-twitter.png] 



 [Dyn facebook account] 

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

[Al Iverson]

Don't respond to the troll.

Others of us want to be able to send mail to Netease domains, so we're
appreciative that there's somebody here now joining us.

Cheers,
Al

--
Al Iverson
www.aliverson.com
(312)725-0130


On Thu, Feb 25, 2016 at 1:25 PM, Franck Martin via mailop
 wrote:
> Well,
>
> This is not a friendly welcome...
>
> Please you have an opportunity to engage and get things fixed, so don't
> throw a ton of bricks on the first email.
>
> Thanks.
>
> On Thu, Feb 25, 2016 at 4:25 AM, Rich Kulawiec  wrote:
>>
>> On Thu, Feb 25, 2016 at 07:17:56PM +0800, ?? wrote:
>> > 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.
>>
>> I can't speak for GitHub, but I've had most of those domains blacklisted
>> for over a decade because of (a) nonstop spam, phishing, and other forms
>> of email abuse (b) failure to respond to abuse reports (c) failure to
>> support RFC-2142 mandated role addresses.
>>
>> ---rsk
>>
>> ___
>> 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
>

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[Rich Kulawiec]

On Thu, Feb 25, 2016 at 11:25:57AM -0800, Franck Martin via mailop wrote:
> Please you have an opportunity to engage and get things fixed, so don't
> throw a ton of bricks on the first email.

I didn't throw *any* bricks.  I gave a candid assessment of the situation.

And while it would be nice to have an opportunity to get things fixed,
the ongoing traffic arriving in numerous spamtraps strongly indicates
that -- so far -- zero effort has been made in that direction by anyone
at 163.com et.al.  If they're actually sincere about putting a stop
to the massive abuse (and abuse support) that's been going on there
for many years, that'd be great.  But they'll have to prove it, and until
they do, it would be unwise to take their (or anyone else's) word for it.

---rsk


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[Geordie Guy]

If you're the postmaster for 163.com can you please look at 
your NDR policies? I get NDRs daily from people forging 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, 陈俊平 
mailto:chenjunp...@corp.netease.com>> wrote:



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 not send out these emails.

I'd tried posting a support request at page https://github.com/contact , 
sending emails to 
ab...@github.com,h...@github.com,supp...@github.com,
 and some other ways to reach out to GitHub team. Unluckily I get no reply so 
far.

Now I turned to this list for help, please help to forward this message if you 
knew someone in GitHub. Thank you very very much!


Best Wishes,


-Junping Chen

chenjunp...@corp.netease.com

Netease Inc.(NASDAQ: NTES)







___
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

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

[Geordie Guy]

Yeah I've just noticed this reply to the original. Blacklisting now too. 

Sent from my mobile. Please excuse any unusual brevity or typos while I'm on 
the go. 

> On 25 Feb 2016, at 11:29 PM, Rich Kulawiec  wrote:
> 
>> On Thu, Feb 25, 2016 at 07:17:56PM +0800, ?? wrote:
>> 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.
> 
> I can't speak for GitHub, but I've had most of those domains blacklisted
> for over a decade because of (a) nonstop spam, phishing, and other forms
> of email abuse (b) failure to respond to abuse reports (c) failure to
> support RFC-2142 mandated role addresses.
> 
> ---rsk
> 
> ___
> 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

[mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Adrian Neale (iComms)]

Hi there, not sure what the correct protocol for answering these things is, but 
here goes so at least you know it has been resolved.

After looking at the logs myself from the shell of the Sophos UTM, the UTM was 
in fact Greylisting.  

Why Sophos did not originally spot this when I raised the call with them I do 
not know.  Also, why is it only affecting Hotmail/Gmail/Outlok.com, I do not 
know.

Anyway, so the emails are following the right MX records in the right order. 

They are getting Greylisted and are arriving at the 3rd priority MX record 
queuing service (which does not Greylist) and are being delivered back up to 
the primary MX record.

So all behaving as expected, well, kind of, but at least I know why.

Thank you for all your suggestions, they helped me identify and understand the 
problem with a bit of digging on my part.

Kind Regards,

Adrian.
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Brandon Long via mailop]

I should point out that "typical" greylisting doesn't work well with Gmail,
since there is no guarantee that the retries will be performed from the
same IP address... in fact, the chances are really high that it's from a
different one.

By typical, I mean based on any tuple which includes IP.

We will try multiple hosts in preference order if we fail connections to
earlier hosts or if the hosts return a 4xx banner.  We do also "learn" down
hosts, and will skip them without trying for limited periods of time (given
the mechanism there, it probably is only really used for fairly high volume
domains).

I can only imagine how greylisting would actually lead to that, unless it
was causing increased load resulting in slow responses or connection
failures, or if the box has some sort of attack mode where it would start
blocking connections earlier.

Brandon

On Thu, Feb 25, 2016 at 3:04 PM, Adrian Neale (iComms) 
wrote:

> Hi there, not sure what the correct protocol for answering these things
> is, but here goes so at least you know it has been resolved.
>
> After looking at the logs myself from the shell of the Sophos UTM, the UTM
> was in fact Greylisting.
>
> Why Sophos did not originally spot this when I raised the call with them I
> do not know.  Also, why is it only affecting Hotmail/Gmail/Outlok.com, I do
> not know.
>
> Anyway, so the emails are following the right MX records in the right
> order.
>
> They are getting Greylisted and are arriving at the 3rd priority MX record
> queuing service (which does not Greylist) and are being delivered back up
> to the primary MX record.
>
> So all behaving as expected, well, kind of, but at least I know why.
>
> Thank you for all your suggestions, they helped me identify and understand
> the problem with a bit of digging on my part.
>
> Kind Regards,
>
> Adrian.
> ___
> 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

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Mike Reed]

Hi Brandon,

Does GMail publish a list of its outbound hosts/ranges some place to enable
us to whitelist?

Kind regards,
Mike

On 25 February 2016 at 23:30, Brandon Long via mailop 
wrote:

> I should point out that "typical" greylisting doesn't work well with
> Gmail, since there is no guarantee that the retries will be performed from
> the same IP address... in fact, the chances are really high that it's from
> a different one.
>
> By typical, I mean based on any tuple which includes IP.
>
> We will try multiple hosts in preference order if we fail connections to
> earlier hosts or if the hosts return a 4xx banner.  We do also "learn" down
> hosts, and will skip them without trying for limited periods of time (given
> the mechanism there, it probably is only really used for fairly high volume
> domains).
>
> I can only imagine how greylisting would actually lead to that, unless it
> was causing increased load resulting in slow responses or connection
> failures, or if the box has some sort of attack mode where it would start
> blocking connections earlier.
>
> Brandon
>
> On Thu, Feb 25, 2016 at 3:04 PM, Adrian Neale (iComms) 
> wrote:
>
>> Hi there, not sure what the correct protocol for answering these things
>> is, but here goes so at least you know it has been resolved.
>>
>> After looking at the logs myself from the shell of the Sophos UTM, the
>> UTM was in fact Greylisting.
>>
>> Why Sophos did not originally spot this when I raised the call with them
>> I do not know.  Also, why is it only affecting Hotmail/Gmail/Outlok.com, I
>> do not know.
>>
>> Anyway, so the emails are following the right MX records in the right
>> order.
>>
>> They are getting Greylisted and are arriving at the 3rd priority MX
>> record queuing service (which does not Greylist) and are being delivered
>> back up to the primary MX record.
>>
>> So all behaving as expected, well, kind of, but at least I know why.
>>
>> Thank you for all your suggestions, they helped me identify and
>> understand the problem with a bit of digging on my part.
>>
>> Kind Regards,
>>
>> Adrian.
>> ___
>> 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
>
>
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Al Iverson]

On Thu, Feb 25, 2016 at 5:53 PM, Mike Reed  wrote:
> Hi Brandon,
>
> Does GMail publish a list of its outbound hosts/ranges some place to enable
> us to whitelist?

https://support.google.com/a/answer/60764?hl=en

SPF records are actually pretty useful for that, you can extract the
outbound SMTP IP addresses for almost any largish ISP.

When I was running a blacklist and wanted to exempt legitimate ISP
outbounds, I tracked the IPs of the top providers by way of their SPF
records.

Cheers,
Al Iverson
--
Al Iverson
www.aliverson.com
(312)725-0130

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Dave Warren]

On 2016-02-25 15:30, Brandon Long via mailop wrote:
I should point out that "typical" greylisting doesn't work well with 
Gmail, since there is no guarantee that the retries will be performed 
from the same IP address... in fact, the chances are really high that 
it's from a different one.


By typical, I mean based on any tuple which includes IP.


I'd argue that greylisting is really mostly once you know a sender is a 
mail server and implements proper retries.


I don't greylist everything, but if anything is suspicious (missing or 
invalid rDNS, weird EHLO, etc) I trigger a greylisting, and I've had 
good luck replacing the IP in a greylist entry with "SPF:PASS" 
indicator, such that a retry from any other IP that passes SPF is 
considered the same -- This works for any large sending farm that has 
valid SPF records.


--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Dave Warren]

On 2016-02-25 15:53, Mike Reed wrote:

Hi Brandon,

Does GMail publish a list of its outbound hosts/ranges some place to 
enable us to whitelist?




_spf.google.com.300 IN  TXT "v=spf1 
include:_netblocks.google.com include:_netblocks2.google.com 
include:_netblocks3.google.com ~all"


It's a lot of ranges, and I'm not sure if Google uses them all for mail 
today, but they well might tomorrow -- I don't see much point in 
greylisting mail from Google, other than perhaps to allow for URIBLs to 
learn of new hosts.


--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Brandon Long via mailop]

On Feb 25, 2016 5:03 PM, "Dave Warren"  wrote:
>
> On 2016-02-25 15:53, Mike Reed wrote:
>>
>> Hi Brandon,
>>
>> Does GMail publish a list of its outbound hosts/ranges some place to
enable us to whitelist?
>>
>
> _spf.google.com.300 IN  TXT "v=spf1 include:_
netblocks.google.com include:_netblocks2.google.com include:_
netblocks3.google.com ~all"
>
> It's a lot of ranges, and I'm not sure if Google uses them all for mail
today, but they well might tomorrow -- I don't see much point in
greylisting mail from Google, other than perhaps to allow for URIBLs to
learn of new hosts.

Yeah, we point people to the SPF record.   It does include most of our IP
space, which is probably broader than it should be, so it's quite larger
than our actual sending IPS.

At some point we may need to fix that, but obviously the SPF record will
always include all senders for Gmail/google and Google apps domains.

Brandon
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[陈俊平]

Hi Geordie,


Please send me some NDR message samples and we will look into it.


To stop being forged, as we know, I‘d recommand again that you add SPF(with 
rejecting policy),DKIM or even DMARC. These DNS records would help our system 
to identify whether an email is forged or not. We discard forged emails without 
a NDR.


Or we can discuss and figure out a solution, thoughts?


With Best Regards,


-Junping Chen

At 2016-02-26 04:58:45, "Geordie Guy"  wrote:

If you're the postmaster for 163.com can you please look at your NDR policies? 
I get NDRs daily from people forging 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 
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 not send out these emails.


I'd tried posting a support request at page https://github.com/contact , 
sending emails to ab...@github.com,h...@github.com,supp...@github.com, and some 
other ways to reach out to GitHub team. Unluckily I get no reply so far.


Now I turned to this list for help, please help to forward this message if you 
knew someone in GitHub. Thank you very very much!




Best Wishes,




-Junping Chen


chenjunp...@corp.netease.com


Netease Inc.(NASDAQ: NTES)








 

___
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

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

[陈俊平]

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 are personal emails or 
normal emails sent by good users, while some(small amounts of) spams or 
unsolicited advertisements leaking out.


To fight spams/UBEs/spammers, we, Netease anti-spam team, do put lots of effort 
to filter and block them, and are open to receive abuse reports, you may send 
leaking spams to RFC-2142 reporting mailboxes(such as 
ab...@163.com,ab...@126.com,ab...@corp.netease.com) or some other mailboxes 
published in our DNS Whois infos(such as nsad...@corp.netease.com), or our 
Customer Services pages(such as http://help.163.com).


If you are blocking netease domains, your users may miss normal emails. If 
possible, please send me some spams/email records and remove our domains from 
your blockinglist. Our filters will learn to stop them. Thank you very much.




Regards,


-Junping Chen



At 2016-02-26 04:59:34, "Geordie Guy"  wrote:
>Yeah I've just noticed this reply to the original. Blacklisting now too. 
>
>Sent from my mobile. Please excuse any unusual brevity or typos while I'm on 
>the go. 
>
>> On 25 Feb 2016, at 11:29 PM, Rich Kulawiec  wrote:
>> 
>>> On Thu, Feb 25, 2016 at 07:17:56PM +0800, ?? wrote:
>>> 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.
>> 
>> I can't speak for GitHub, but I've had most of those domains blacklisted
>> for over a decade because of (a) nonstop spam, phishing, and other forms
>> of email abuse (b) failure to respond to abuse reports (c) failure to
>> support RFC-2142 mandated role addresses.
>> 
>> ---rsk
>> 
>> ___
>> 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
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Microsoft/GMail MX Priority Issues - mailop Digest, Vol 100, Issue 32

[Matthias Leisi]

> Does GMail publish a list of its outbound hosts/ranges some place to enable 
> us to whitelist?

We try to keep up to date on IPs from Google Mail (and of course others) at 
dnswl.org, and one important use case for this data is to skip greylisting for 
any of the IPs found there (regardless of trust level) — after all, they are 
supposed to be „real“ mailservers who would retry anyway, so greylisting them 
has little value to begin with. 

— Matthias


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[Suresh Ramasubramanian]

I've personally found junping responsive to abuse issues and highly clued

And he runs domains with a massive userbase plus that are heavily forged into 
spam as well

Rich, you date back from the Morris worm days and I know you from the old 
spam-l in the late 90s - you always did like filtering rather a lot of mail for 
your own domain. :). Well, keep at it, but there are better ways to block 
forged spam without a wholesale block on freemail providers.

--srs

> On 26-Feb-2016, at 8:37 AM, 陈俊平  wrote:
> 
> 
> Hi Geordie,
> 
> Please send me some NDR message samples and we will look into it.
> 
> To stop being forged, as we know, I‘d recommand again that you add SPF(with 
> rejecting policy),DKIM or even DMARC. These DNS records would help our system 
> to identify whether an email is forged or not. We discard forged emails 
> without a NDR.
> 
> Or we can discuss and figure out a solution, thoughts?
> 
> With Best Regards,
> 
> -Junping Chen
> 
> At 2016-02-26 04:58:45, "Geordie Guy"  wrote:
> If you're the postmaster for 163.com can you please look at your NDR 
> policies? I get NDRs daily from people forging 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 
>> 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 not send out these emails.
>> 
>> I'd tried posting a support request at page https://github.com/contact , 
>> sending emails to ab...@github.com,h...@github.com,supp...@github.com, and 
>> some other ways to reach out to GitHub team. Unluckily I get no reply so far.
>> 
>> Now I turned to this list for help, please help to forward this message if 
>> you knew someone in GitHub. Thank you very very much!
>> 
>> 
>> Best Wishes,
>> 
>> 
>> -Junping Chen
>> 
>> chenjunp...@corp.netease.com
>> 
>> Netease Inc.(NASDAQ: NTES)
>> ___
>> 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
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

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

[陈俊平]

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.135
220.181.14.136
220.181.14.137
220.181.14.138
220.181.14.139
220.181.14.140
220.181.14.141
220.181.14.142
$ dig +short 163mx01.mxmail.netease.com. @8.8.8.8
43.230.90.5
$ 


The networking is better when senders are delivering from oversea to China 
mainland. For all postmasters, you'd try these proxy servers if you have 
delivering problems.


But for the GitHub problem, we are seeing emails delivered normally into 
yeah.net/vip.163.com/vip.126.com/188.com and other sites. Only 163.com/126.com 
could miss their emails in a certain probability(yes not all of them), the 
logfiles tell that there're no inbound connections(or being closing 
unexpectedly before reaching our servers).


More and more 163.com/126.com users are complaining about missing their GitHub 
emails. For now, we really need a GitHub postmaster/engineer to help.




Anxiously,


-Junping Chen





At 2016-02-25 19:45:39, ml+mai...@esmtp.org wrote:
>Maybe they run into something like this?
>
>220 126.com Anti-spam GT for Coremail System (126com[20140526])
>EHLO 
>Connection to 126mx02.mxmail.netease.com closed by foreign host.
>
>It takes a long time to get any reply... and then your sever
>simply closes the connection.
>
>
>And from a different system:
>
>220 126.com Anti-spam GT for Coremail System (126com[20140526])
>EHLO 
>250-mail
>250-PIPELINING
>250-AUTH LOGIN PLAIN
>250-AUTH=LOGIN PLAIN
>250-coremail 
>1Uxr2xKj7kG0xkI17xGrU7I0s8FY2U3Uj8Cz28x1U7Ic2I0Y2UFWs58gUCa0xDrj
>250-STARTTLS
>250-SIZE 73400320
>250 8BITMIME
>mail from:<>
>250 Mail OK
>rcpt to:
>Connection closed by foreign host.
>
>Hmm...
>
>___
>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