There's nothing that can be done until VM get their server unlisted.Does VM have a place to report this?
Go to Answer
I've escalated this to the email team. They should respond in thread shortly.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
Good afternoon Nelem,
Please could you provide a little more context? Is there server blocked on the web browser?
This is sent via SMTP. The full report is:
Reporting-MTA: dns; know-smtprelay-5-imp [126.96.36.199]Received-From-MTA: dns; mail.crm.direct [188.8.131.52]Arrival-Date: Fri, 28 Aug 2020 11:20:26 +0100
Final-recipient: rfc822; ****@fasttrack-fitcamp.co.ukDiagnostic-Code: smtp; 550 The sending IP (184.108.40.206) is listed on https://spamrl.com/. Please resolve this and retry.
Last-attempt-Date: Fri, 28 Aug 2020 11:20:30 +0100
Thank you @ravenstar68. Do you have a direct channel to the email team?
We VIP's aren't employed by Virgin Media.
We are able to escalate via the Forum only.
@Zak_M the user is sending a message using an email client.
The 80.0.253.xxx servers are Virgin media's outbound SMTP servers in the omc server range. These servers SHOULD NEVER be blacklisted if your outbound anti spam measures are working correctly.
This needs escalation to the email or security team. If you need advice speak to @Kev_B or @Lisa_CC
This has been passed onto the relevant team now.
Soon as we hear anything back we'll be in touch.
Thanks @ravenstar68 for bringing this to our attention.
I'm now geeting erroneous bounces:<****@dmsav.com>: host smtp.ntlworld.com[220.127.116.11] said: 550 5.1.2Recipient Domain Invalid (VM521) (in reply to RCPT TO command)The domain is valid and I can send from another service.
That's odd, I've just run a manual test using that domain:
220 know-smtprelay-6-imp cmsmtp ESMTP server readyehlo desktop250-know-smtprelay-6-imp hello [<redacted>], pleased to meet you250-HELP250-AUTH LOGIN PLAIN250-SIZE 52000000250-ENHANCEDSTATUSCODES250-PIPELINING250-8BITMIME250 OKauth plain334<redacted>235 2.7.0 ... authentication succeededmail from: <email@example.com>250 2.1.0 <firstname.lastname@example.org> sender okrcpt to: <email@example.com>250 2.1.5 <firstname.lastname@example.org> recipient okrset250 2.0.0 OKquit221 Closing connection. Good bye.
Note that the error would occur at the red line normally, acceptance means that there is either an A record or MX record for the domain.
Is this affecting every mail you send or is it intermittent?
Found this answer helpful? Share it!
I've just tried it again and it went through. It could have been a temporary DNS problem earlier this morning.