Unable to reach relay.plus.net (ping)

[#1]

PING relay.plus.net (212.159.9.107): 56 data bytes

--- relay.plus.net ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

Not sure if it is just me?

Log line follows for a test email from earlier.

to=<richardpruen@gmail.com>, relay=none, delay=16968, delays=16968/0.01/0/0.01, dsn=4.0.0, status=deferred (delivery temporarily suspended: host relay.plus.net[212.159.8.107] refused to talk to me: 554 avasout-peh-004 smtp ESMTP server not available (blacklisted by local policy))

Where to go next? 

Thanks

Richard

[#2]

Are you on aPlusnet connection ? because it looks like the Cloudmark system has blacklisted your ip address

[#3]

A lookup gives 

84.92.82.212

Hostname: richardpruen.plus.com

ASN: 6871

ISP: British Telecommunications PLC

Services: None detected

Assignment: Likely Static IP

Country: United Kingdom of Great Britain and Northern Ireland

State/Region: England

City: Farnham

I Checked about 80 blacklists and seem to be clear on all of them.

[#4]

Email servers do not respond to pings by design. So that has no bearing on the real operational problem.

[#5]

Ok

Would any further info help? 

[#6]

Maybe try a telnet connection to relay.plus.net and see if you can login or at least get any response.

[#7]

@richardpruen 

Are we right in assuming that you are trying to ping this address because you can't access your emails? If so, more information as to the extent of the actual problem, such as how you are trying to access them would help focus responses as to your actual issue.

[#8]

@richardpruen looking at the error message you posted in your first post

554 avasout-peh-004 smtp ESMTP server not available (blacklisted by local policy)

Suggest you have a read of this thread 

HTH

[#9]

/home/rpruen # telnet relay.plus.net
Trying 212.159.9.107...
telnet: connect to address 212.159.9.107: Connection timed out
Trying 212.159.8.107...
telnet: connect to address 212.159.8.107: Connection timed out

No response at all

I am wondering if it's a DNS issue. I switched to using delegated DNS servers for my domain, and thus am not using plusnets DNS servers, if they are using internal/external zones or something to get customers to hit a different IP, I might be hitting the wrong IP?

That's the only major change I have made. If that is the case I can probably reconfigure things to use their DNS for anything plus.net related.

Just an idea, as it's the only thing that has changed in years of everything working fine.

[#10]

I use OpenDNS rather than the PN DNS servers and can use relay.plus.net just fine

when trying to telnet to relay.plus.net you need to use port 587

i.e telnet relay.plus.net 587

[#11]

@richardpruen 

you need to add the port you are trying to telnet

telnet relay.plus.net 587

:~$ telnet relay.plus.net 587
Trying 212.159.8.107...
Connected to relay.plus.net.
Escape character is '^]'.
220 avasout-peh-001 smtp relay.plus.net

HTH

[#12]

Sure, I have been forwarding mail from my domain for a number of years via relay.plus.net, as they request customers do. Just yesterday the server apparently stopped accepting connections at all. I can't ping or telnet to it, there is no response at all.

At the request of plusnet all mail from postfix is set to be forwarded to plusnet's mail server for delivery, rather than delivered direct. The exception to this would be if there is an IPV6 only mail server, but AFIAA none exists so far, so all mail will be via the relay. The reason for the mail server is running a wiki, email tokens are generated for those who sign up, as a valid email address is a requirement to edit pages 

All outgoing mail is signed (DKIM) and DMARC configured, it worked fine until yesterday and suddenly stopped. It doesn't seem to coincide with anything changing at this end, other than DNS server changes, and those happened not exactly in sync (maybe a week before the problem suddenly showed up).

I can post further log lines if that will help? What would you like to know, and I will try to get you the info.

[#13]

Oops I know that, my excuse is not enough coffee 

telnet relay.plus.net 587
Trying 212.159.8.107...
Connected to relay.plus.net.
Escape character is '^]'.
554 avasout-peh-004 smtp ESMTP server not available (blacklisted by local policy)
Connection closed by foreign host.

telnet relay.plus.net 25
Trying 212.159.9.107...
Connected to relay.plus.net.
Escape character is '^]'.
554 avasout-ptp-003 smtp ESMTP server not available (blacklisted by local policy)
Connection closed by foreign host.

Same on port 25, the server is definitely saying go away... 

[#14]

The problem appears identical. I have followed the steps in the thread, and the results of the telnet (port 25 and 587) are identical. I posted the transcripts above so won't repeat them here. 

Results from the what's my IP address page posted to that thread are:

Your Hostname:
richardpruen.plus.com

Your User Agent:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36

Postfix seems to be ok, see the Transcript below, and also open relay check (not an open relay): 

# postfix -v status
postfix: name_mask: host
postfix: inet_addr_local: configured 2 IPv4 addresses
postfix: inet_addr_local: configured 4 IPv6 addresses
postfix: been_here: 127.0.0.1/32: 0
postfix: been_here: 192.168.0.3/32: 0
postfix: been_here: [::1]/128: 0
postfix: been_here: [2001:470:18e4:0:91e6:d402:10ca:5ee7]/128: 0
postfix: been_here: [2001:470:18e4:0:dea6:32ff:fe06:757f]/128: 0
postfix: been_here: [fe80::2d21:b10e:7c87:1ae5]/128: 0
postfix: mynetworks_core: 127.0.0.1/32 192.168.0.3/32 [::1]/128 [2001:470:18e4:0:91e6:d402:10ca:5ee7]/128 [2001:470:18e4:0:dea6:32ff:fe06:757f]/128 [fe80::2d21:b10e:7c87:1ae5]/128
postfix/postfix-script: the Postfix mail system is running: PID: 7843

# telnet localhost 25
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 mail.pruen.co.uk ESMTP Postfix
quit
221 2.0.0 Bye
Connection closed by foreign host.

If blocked for supposed spam, then can I have some examples, please? If it has happened then I would like to verify the DKIM signatures and source. A quick check for compromised machines shows nothing out of the ordinary, and no tripwires have been triggered. I am in the process of verifying files against hashes to make sure nothing has been tampered with.

[#15]

@richardpruen - I've raised a ticket through to our engineers to take a look at why your IP appears to have been blacklisted (ref: INFOPS-88277).