535 ...authentication rejected as source IP has a poor reputation

[#1]

Connecting to relay.plus.net from my Linux box.  Using AUTH LOGIN. Some of the time I'm getting rejected with the subject error message.  Other times it works.  It looks like of the SMPT servers (212.159.8.107, or 212.159.9.107) has got somehting against me.

User account name perdrix52.

Thanks

David

[#2]

DEBUG SMTP: connected to host "relay.plus.net", port: 587

EHLO Charon
250-avasout06 hello [196.52.84.53], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 104857600
250-PIPELINING
250-8BITMIME
250 OK
DEBUG SMTP: Found extension "HELP", arg ""
DEBUG SMTP: Found extension "AUTH", arg "LOGIN PLAIN"
DEBUG SMTP: Found extension "SIZE", arg "104857600"
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "8BITMIME", arg ""
DEBUG SMTP: Found extension "OK", arg ""
DEBUG SMTP: Attempt to authenticate
AUTH LOGIN
334 ...

: Redacted

334 ...
 : Redacted
535 ...authentication rejected as source IP has a poor reputation

[#3]

I connect to the internet at large using a VPN.   So the IP I use won't be a plus.net ip address.   I can bypass the problem by setting a routing exception in my VPN client so route stuff for the two IPs of relay.plus.net so it doens't travel via the encrypted tunnel, but directly to the servers using my plus.net IP.  I'd very much prefer not to do so however.

David

[#4]

Bump - I really prefer not to bypass my VPN for emails. Is there any way to resolve this?

Dave

[#5]

Hi Dave.

Sorry for the delayed response and that you're having issues sending mail.

I've raised this with our infrastructure operational engineers (INFOPS-5513) to investigate further.

We may need to know the source IP, if you can PM me it I'll pass it over.

[#6]

It was in  my second post but here it is again - 196.52.84.53 - though no guarantee it will be the same each time I connect to the VPN.

It belongs to PrivateInternetAccess.

David

[#7]

Hi @Perdrix,

I'm sorry that we missed that from your second post - thank you for confirming it again. I've added this information to the task that @Gandalf has raised to our infrastructure/operational engineers and we'll be in touch once we have an update on this.