subject:"ATT RBL f\-\-\-wits"

Re: ATT RBL f---wits

2023-11-29 Thread Matus UHLAR - fantomas


On 29/11/2023 00:51, Tracy Greggs via users wrote:

Cableone is SOA on this zone, so they are the issue.

You can ask them to create a PTR for your static IP and hope for the 
best.  Most I have dealt with will do it as long as it's a 
commercial account.


On 29.11.23 07:24, Noel Butler wrote:
As I pointed out - but failed to copy/paste a couple extra lines - 
cableone have issues, earlier they were reporting SERVFAIL then it was 
unreachables.


I have tried now.

116.24.in-addr.arpa.  is only delegated to two DNS servers and both of them 
have problems


Name:   116.24.in-addr.arpa.
Updated:2004-08-10
NameServer: NS2.CABLEONE.NET
NameServer: NS1.CABLEONE.NET
Ref:https://rdap.arin.net/registry/domain/116.24.in-addr.arpa.

While reverse zone on those servers has 4 NS records, it won't help before 
either of those servers can be reached to provide cacheable response.


The fact OP showed google knowing his PTR. says he should not have to 
have them add it manually, they need to fix what they already have - 
or they need to pay their bill :)


It's also why we dont accept reports here that " oh google says its 
there" because google have a history of not honouring TTL's, and it 
always pays to use a DNS server that you don't think would have your 
zone cached, to get a fresh perspective.


correct.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Spam is for losers who can't get business any other way.

Re: ATT RBL f---wits

2023-11-28 Thread Curtis Maurand





On 11/27/23 16:31, Philip Prindeville wrote:

We're being blacklisted by att.net with the following message:

(reason: 550 5.7.1 Connections not accepted from servers without a valid 
sender domain.flph840 Fix reverse DNS for 24.116.100.90)

I don't know what the hell is up with these pinheads:

philipp@ubuntu22:~$ dig -tmx redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -tmx redfish-solutions.com. 
@8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58379
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;redfish-solutions.com. IN MX

;; ANSWER SECTION:
redfish-solutions.com. 21600 IN MX 10 mail.redfish-solutions.com.

;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:29 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -ta mail.redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -ta mail.redfish-solutions.com. 
@8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19570
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mail.redfish-solutions.com. IN A

;; ANSWER SECTION:
mail.redfish-solutions.com. 21600 IN A 24.116.100.90

;; Query time: 72 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:39 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -x 24.116.100.90 @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -x 24.116.100.90 @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2371
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;90.100.116.24.in-addr.arpa. IN PTR

;; ANSWER SECTION:
90.100.116.24.in-addr.arpa. 21600 IN PTR mail.redfish-solutions.com.

;; Query time: 68 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:55 MST 2023
;; MSG SIZE  rcvd: 95

philipp@ubuntu22:~$

So that's not the problem.  You're supposed to be able to get the blacklisting fixed 
if you email abuse_...@abuse-att.net  but I've 
emailed them from 3 different addresses and have yet to get a response much less a 
resolution.

Has anyone else had to deal with this bullocks and gotten it resolved?


That has never worked for me.  I've only been met with radio silence.

Re: ATT RBL f---wits

2023-11-28 Thread Noel Butler


On 29/11/2023 00:51, Tracy Greggs via users wrote:


Cableone is SOA on this zone, so they are the issue.

You can ask them to create a PTR for your static IP and hope for the 
best.  Most I have dealt with will do it as long as it's a commercial 
account.


As I pointed out - but failed to copy/paste a couple extra lines - 
cableone have issues, earlier they were reporting SERVFAIL then it was 
unreachables.


The fact OP showed google knowing his PTR. says he should not have to 
have them add it manually, they need to fix what they already have - or 
they need to pay their bill :)


It's also why we dont accept reports here that " oh google says its 
there" because google have a history of not honouring TTL's, and it 
always pays to use a DNS server that you don't think would have your 
zone cached, to get a fresh perspective.


--
Regards,
Noel Butler

Re: ATT RBL f---wits

2023-11-28 Thread Tracy Greggs via users


NO PTR for the IP.

Cableone is SOA on this zone, so they are the issue.

You can ask them to create a PTR for your static IP and hope for the 
best.  Most I have dealt with will do it as long as it's a commercial 
account.



-- Original Message --

From "Philip Prindeville" 

To users@spamassassin.apache.org
Date 11/27/2023 3:31:52 PM
Subject ATT RBL f---wits

Re: ATT RBL f---wits

2023-11-27 Thread Noel Butler


On 28/11/2023 08:59, Noel Butler wrote:


~$ host 24.116.100.90
;; connection timed out; no servers could be reached

Seems like AT  *ARE* doing the correct thing and it is *YOU* with the 
problem. before you start calling others f'wits do better 
investigation, a dig trace indicates root servers dont know you.


Seems your IP provider is the onle with problems, now I get an answer of 
sorts


~$ dig +trace -x 24.116.100.90

< snip >

116.24.in-addr.arpa. 86400 IN NS ns2.cableone.net.
116.24.in-addr.arpa. 86400 IN NS ns1.cableone.net.
116.24.in-addr.arpa. 10800 IN NSEC 117.24.in-addr.arpa. NS RRSIG NSEC
116.24.in-addr.arpa. 10800 IN RRSIG NSEC 8 4 10800 20231211213247 
20231127203247 6558 24.in-addr.arpa. 
ChfIccQU9mphSoPwTZf6Og2pumL3BRTQBGm7ZyFb5R8ycVL/jyXD94O8 
XOLL48wgXFQPuW4bfoSlmB/nNJ4tfb1Vyeb3x5MmVQTL74tdotoGfFYS 
2+gjyFWYkWAtkzOAmC7Eeva7hotpQ9Qa3LbkFtfznKBFdPAHHQ1vXs0K Shg=

;; Received 366 bytes from 199.180.180.63#53(r.arin.net) in 194 ms

;; connection timed out; no servers could be reached


On 28/11/2023 07:31, Philip Prindeville wrote:


We're being blacklisted by att.net with the following message:

(reason: 550 5.7.1 Connections not accepted from servers without a 
valid sender domain.flph840 Fix reverse DNS for 24.116.100.90)


I don't know what the hell is up with these pinheads:


--
Regards,
Noel Butler

Re: ATT RBL f---wits

2023-11-27 Thread Noel Butler


~$ host 24.116.100.90
;; connection timed out; no servers could be reached

Seems like AT  *ARE* doing the correct thing and it is *YOU* with the 
problem. before you start calling others f'wits do better investigation, 
a dig trace indicates root servers dont know you.


On 28/11/2023 07:31, Philip Prindeville wrote:


We're being blacklisted by att.net with the following message:

(reason: 550 5.7.1 Connections not accepted from servers without a 
valid sender domain.flph840 Fix reverse DNS for 24.116.100.90)


I don't know what the hell is up with these pinheads:

philipp@ubuntu22:~$ dig -tmx redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -tmx 
redfish-solutions.com. @8.8.8.8

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58379
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;;~$ host 24.116.100.90
;; connection timed out; no servers could be reached
QUESTION SECTION:
;redfish-solutions.com. IN MX

;; ANSWER SECTION:
redfish-solutions.com. 21600 IN MX 10 mail.redfish-solutions.com.

;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:29 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -ta mail.redfish-solutions.com. @8.8.8.8

; <~$ host 24.116.100.90
;; connection timed out; no servers could be reached
<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -ta 
mail.redfish-solutions.com. @8.8.8.8

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19570
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mail.redfish-solutions.com. IN A

;; ANSWER SECTION:
mail.redfish-solutions.com. 21600 IN A 24.116.100.90

;; Qu~$ host 24.116.100.90
;; connection timed out; no servers could be reached
ery time: 72 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:39 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -x 24.116.100.90 @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -x 24.116.100.90 
@8.8.8.8

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2371
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;90.100.116.24.in-addr.arpa. IN PTR

;; ANSWER SECTION:
90.100.116.24.in-addr.arpa. 21600 IN PTR mail.redfish-solutions.com.

;; Query time: 68 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:55 MST 2023
;; MSG SIZE  rcvd: 95

philipp@ubuntu22:~$

So that's not the problem.  You're supposed to be able to get the 
blacklisting fixed if you email abuse_...@abuse-att.net 
 but I've emailed them from 3 different 
addresses and have yet to get a response much less a resolution.


Has anyone else had to deal with this bullocks and gotten it resolved?

Thanks


--
Regards,
Noel Butler

Re: ATT RBL f---wits

2023-11-27 Thread Bill Cole


On 2023-11-27 at 16:31:52 UTC-0500 (Mon, 27 Nov 2023 14:31:52 -0700)
Philip Prindeville 
is rumored to have said:


We're being blacklisted by att.net with the following message:

   (reason: 550 5.7.1 Connections not accepted from servers without a 
valid sender domain.flph840 Fix reverse DNS for 24.116.100.90)


I don't know what the hell is up with these pinheads:

philipp@ubuntu22:~$ dig -tmx redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -tmx 
redfish-solutions.com. @8.8.8.8

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58379
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;redfish-solutions.com. IN MX

;; ANSWER SECTION:
redfish-solutions.com. 21600 IN MX 10 mail.redfish-solutions.com.

;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:29 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -ta mail.redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -ta 
mail.redfish-solutions.com. @8.8.8.8

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19570
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mail.redfish-solutions.com. IN A

;; ANSWER SECTION:
mail.redfish-solutions.com. 21600 IN A 24.116.100.90

;; Query time: 72 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:39 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -x 24.116.100.90 @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -x 24.116.100.90 
@8.8.8.8

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2371
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;90.100.116.24.in-addr.arpa. IN PTR

;; ANSWER SECTION:
90.100.116.24.in-addr.arpa. 21600 IN PTR mail.redfish-solutions.com.

;; Query time: 68 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:55 MST 2023
;; MSG SIZE  rcvd: 95

philipp@ubuntu22:~$

So that's not the problem.  You're supposed to be able to get the 
blacklisting fixed if you email abuse_...@abuse-att.net 
 but I've emailed them from 3 
different addresses and have yet to get a response much less a 
resolution.


Has anyone else had to deal with this bullocks and gotten it resolved?



Yes. Twice.

Time is your friend. AT still operates like it's 1970...



--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

ATT RBL f---wits

2023-11-27 Thread Philip Prindeville

We're being blacklisted by att.net with the following message:

   (reason: 550 5.7.1 Connections not accepted from servers without a valid 
sender domain.flph840 Fix reverse DNS for 24.116.100.90)

I don't know what the hell is up with these pinheads:

philipp@ubuntu22:~$ dig -tmx redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -tmx redfish-solutions.com. 
@8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58379
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;redfish-solutions.com. IN MX

;; ANSWER SECTION:
redfish-solutions.com. 21600 IN MX 10 mail.redfish-solutions.com.

;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:29 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -ta mail.redfish-solutions.com. @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -ta mail.redfish-solutions.com. 
@8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19570
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mail.redfish-solutions.com. IN A

;; ANSWER SECTION:
mail.redfish-solutions.com. 21600 IN A 24.116.100.90

;; Query time: 72 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:39 MST 2023
;; MSG SIZE  rcvd: 71

philipp@ubuntu22:~$ dig -x 24.116.100.90 @8.8.8.8

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -x 24.116.100.90 @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2371
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;90.100.116.24.in-addr.arpa. IN PTR

;; ANSWER SECTION:
90.100.116.24.in-addr.arpa. 21600 IN PTR mail.redfish-solutions.com.

;; Query time: 68 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Nov 19 15:08:55 MST 2023
;; MSG SIZE  rcvd: 95

philipp@ubuntu22:~$

So that's not the problem.  You're supposed to be able to get the blacklisting 
fixed if you email abuse_...@abuse-att.net  but 
I've emailed them from 3 different addresses and have yet to get a response 
much less a resolution.

Has anyone else had to deal with this bullocks and gotten it resolved?

Thanks

Re: ATT RBL f---wits

Re: ATT RBL f---wits

Re: ATT RBL f---wits

Re: ATT RBL f---wits

Re: ATT RBL f---wits

Re: ATT RBL f---wits

Re: ATT RBL f---wits

ATT RBL f---wits

8 matches

Site Navigation

Mail list logo

Footer information