Re: [mailop] New Google DNS Servers? 192.178.65.0/28 NO PTR records.. anyone? Brandon?

2023-12-04 Thread Tony Maszeroski via mailop 

Hello,

I believe you can enumerate cloudflare IPs via :

https://www.cloudflare.com/ips-v4
https://www.cloudflare.com/ips-v6

It's likely an overfit situation (not just resolvers), but it's something.

-tony

On 12/2/23 21:57, Arne Jensen via mailop wrote:

Always happy to help! And wauh, times flies by these days...

First of all - I completely agree with you, that several things could be 
better here ;-).


Taking the four major ones, the top list, from best to worst, might be 
like:


1. OpenDNS
2. Google
3. Quad 9/PCH
4. Cloudflare

Given your mention of "internal documentation", maybe there could be 
something more for you to document, if you haven't already:


Google does, as mentioned previously, document their resolver 
infrastructure on the Web, contrary to many others, but also with a JSON:


-> API/JSON: https://www.gstatic.com/ipranges/publicdns.json

OpenDNS is also documenting theirs, and also have PTR on the outgoing 
resolver IP, but unfortunately, the PTR **doesn't always** point to one 
of their OpenDNS.* domain names, which could be confusing:


Reaching OpenDNS Copenhagen:
- 146.112.135.70 (r7.compute.cph1.edc.strln.net)
- 2a04:e4c0:17::73 (r10.compute.cph1.edc.strln.net)

Reaching OpenDNS London:
- 208.69.34.73 (m53.lon.opendns.com)
- 2a04:e4c0:10::91 (r3.compute.lon1.edc.strln.net)

It is however consistent with their locations as retrieved from here:

-> Web: https://www.opendns.com/data-center-locations/
-> JSON: 
https://umbrella-dns-requests.marketops.umbrella.com/api/data-center-locations


Currently, it seems very much a hit and miss, mostly miss, when reaching 
any IP address with PTR records, through Quad 9. I haven't ever seen 
Quad 9 document it like OpenDNS or Google.


With Cloudflare, I've never see any of their outbound resolver IP 
addresses have any PTR records. I haven't ever seen Cloudflare document 
it like OpenDNS or Google.


With the above possible ways to retrieve the OpenDNS and Google data, 
you have the option to automate e.g. a weekly update of their resolver 
addresses, if you feel for something like that in any way. ;)




___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Seeing connection issues again with Microsoft mail servers

2018-02-08 Thread Tony Maszeroski via mailop 
Hello Michael,

Craigslist is seeing connection errors / timeouts while trying to
deliver messages to Microsoft domains again (see attached).

Nothing is hitting critical limits yet, but just FYI something is amiss.

Cheers!
-tony
Mail stuck in deferred grouped by domain:

 DOMAIN T 510204080   160   320   640  1280 
1280+
 
=
  TOTAL 82309  3200  3145  6567 13605 27808 24903   374   357   516  
1834
hotmail.com 53222  2124  2123  4405  9169 18732 16669 0 0 0 0
outlook.com 12161   462   466  1019  2082  4226  3906 0 0 0 0
   live.com  5909   243   230   481  1028  2124  1803 0 0 0 0
msn.com  5177   233   202   452   878  1805  1607 0 0 0 0

Top Backpressure IPS :

104.47.1.33 7860
104.47.2.33 6408
104.47.32.33 6027
104.47.46.33 5863
104.47.0.33 5567
104.47.5.33 4887
104.47.44.33 4632
104.47.41.33 4472
104.47.42.33 3752
104.47.40.33 3299
104.47.6.33 3233
104.47.45.33 3210
104.47.34.33 3091
104.47.4.33 2850
104.47.33.33 2496
104.47.36.33 2489
104.47.37.33 1639
104.47.38.33 1624
64.233.186.27 1064


Backpressure Reasons :

(delivery temporarily suspended: lost connection with 
hotmail-com.olc.protection.outlook.com[104.47.1.33] while sending RCPT TO) 5792
(delivery temporarily suspended: lost connection with 
outlook-com.olc.protection.outlook.com[104.47.1.33] while sending RCPT TO) 928
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.101]. (AS843) (in reply to RCPT 
TO command)) 36
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.100]. (AS843) (in reply to RCPT 
TO command)) 33
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.98]. (AS843) (in reply to 
RCPT TO command)) 31
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.102]. (AS843) (in reply to 
RCPT TO command)) 26
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.96]. (AS843) (in reply to 
RCPT TO command)) 22
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.97]. (AS843) (in reply to 
RCPT TO command)) 22
(host eur.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.105]. (AS843) (in reply to RCPT 
TO command)) 21
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.96]. (AS843) (in reply to RCPT TO 
command)) 20
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.101]. (AS843) (in reply to 
RCPT TO command)) 19
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.104]. (AS843) (in reply to RCPT 
TO command)) 18
(host outlook-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.102]. (AS843) (in reply to 
RCPT TO command)) 18
(host eur.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.100]. (AS843) (in reply to RCPT 
TO command)) 16
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.103]. (AS843) (in reply to RCPT 
TO command)) 14
(host outlook-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.96]. (AS843) (in reply to 
RCPT TO command)) 14
(host eur.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.103]. (AS843) (in reply to RCPT 
TO command)) 13
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.100]. (AS843) (in reply to 
RCPT TO command)) 13
(host hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 
Server busy. Please try again later from [208.82.237.105]. (AS843) (in reply to 
RCPT TO command)) 13
(host eur.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.101]. (AS843) (in reply to RCPT 
TO command)) 12
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.105]. (AS843) (in reply to RCPT 
TO command)) 12
(host live-com.olc.protection.outlook.com[104.47.1.33] said: 451 4.7.500 Server 
busy. Please try again later from [208.82.237.97]. (AS843) (in reply to

Re: [mailop] AOL backing up the queue

2017-11-28 Thread Tony Maszeroski via mailop 
Experienced significant SMTP connection timeout issues for AOL twice in
the past week :

2017-11-24 11:15 - 2017-11-25 03:00 UTC
2017-11-27 11:21 - 2017-11-28 04:10 UTC

In both instances deferred queues for aol.com grew by 6600% before draining.

-tony

On 11/27/17 14:34, Russell Clemings wrote:
> I've been getting timeouts on Earthlink for about four hours now. AOL
> seems OK from here though -- nothing in the queue.
> 
> On Mon, Nov 27, 2017 at 2:10 PM, Steve Atkins  > wrote:
> 
> 
> > On Nov 27, 2017, at 1:46 PM, Josiah Ritchie 
>  > wrote:
> >
> > It appears that AOL is having some problems right now in other areas 
> regarding mail, but I haven't seen any commentary from mail operators yet. 
> Anyone else having intermittent ability to send mail to AOL mail servers?
> >
> > I'm seeing a lot of this in our logs:
> > status=deferred (delivery temporarily suspended: conversation with 
> mailin-04.mx.aol.com [152.163.0.67]
> timed out while receiving the initial server greeting)
> 
> It's not just you.
> 
> Several large consumer ISPs, including AOL, are getting more Cyber
> Monday junk mail today than their systems were really engineered to
> handle.
> 
> Cheers,
>   Steve
> ___
> 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] Email delivery to Yahoo! and Frontier (who also uses Yahoo! email)

2017-07-13 Thread Tony Maszeroski via mailop 
+1 - Yahoo queues bloating here as well.

These appear to be our top three problematic destinations:

mta6.am0.yahoodns.net[98.136.216.25]
mta7.am0.yahoodns.net[98.136.217.203]
mta7.am0.yahoodns.net[98.138.112.33]

-tony

On 7/13/17 09:40, Tara Natanson wrote:
> Yes,  We have been seeing this as well and I have confirmed several
> other senders are seeing it too.  Same error.  
> 
> One person reported this error started appearing over the weekend. 
> 
> Tara Natanson 
> 
> On Thu, Jul 13, 2017 at 12:32 PM, Frank Bulk  > wrote:
> 
> We're seeing outbound email queue up for yahoo.com
>  and frontier.com  and
> frontiernet.net  since 7:50 am U.S.
> Central.  Our email server is logging
> "451 4.3.2 Internal error reading data"
> 
> Frank
> 
> 
> ___
> 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