Why is our email not getting through to this domain

[hayabusaukuk]

Final-Recipient: rfc822;andrew.terry@xxxxxxxx.co.uk
Action: failed
Status: 5.0.0 (permanent failure)
Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'Callback setup failed while verifying <MDHall@Pxxxxxxx.co.uk>\n(result of an earlier callout reused).\nThe initial connection, or a HELO or MAIL FROM:<> command was\nrejected. Refusing MAIL FROM:<> does not help fight spam, disregards\nRFC requirements, and stops you from receiving standard bounce\nmessages. This host does not accept mail from domains whose servers\nrefuse bounces.\nSender verification failed (Sending test bounce to MDHall@ParetoLaw.co.uk\nfailed).' (delivery attempts: 0)
Reporting-MTA: dns; mail1.xxxxxxxx.co.uk


What do i need to change to get these mails through?


Thanks

 

[Scotsdude]

OK, this is something I ran across recently, and I asked our ISP to look into it. This is the response I got:

I have been looking into this issue and can see an attempt to send email from xxx.xxx@xxx.xx.uk. I have looked at the logs and it appears that their server does not respond correctly to callout sender verification. We use Sender Callout Verification to check the validity of the sender's address for incoming mail. This means when a mail comes in from an address we have not heard of before we will check that address by going through some of the steps of sending a mail to the address:
- We will look up the MX record for the domain
- We will connect to this server
- We will try the standard 'HELO' or 'EHLO' greeting
- We will send a 'MAIL FROM: <>' command
- We will send a 'RCPT TO:<address>' command with the address we want to verify
- We will end the session
Any RFC compliant mail server should respond to the above commands without error unless the email address does not exist or the server is not responsible for that address.
RFC guidelines describe this as one of the possible methods that can be used to verify email addresses.
We are rejecting mails from the address in question because the mail server responsible from that address does not comply with RFC guidelines as specified above.
It is worth noting that 9 out of 10 of the servers that are not RFC compliant are so because they reject the 'MAIL FROM:<>' command because it is blank.
Many servers do this as a way to stop read receipts, bounce messages and postmaster messages from being delivered. This is against RFC guidelines. (See RFC 1123 5.2.9)

looks like something similar to what I had. Speak to your ISP about it.

------------------------------------------------------
Matt
Life is all shadows and dust.
Live it up with women and wine while you can

 

[hayabusaukuk]

Thanks, is there anything i can do on my smtp connection to get around this?

My isp are cowboys, frankly

 

[Scotsdude]

not really. check to see if you're own email server is RFC 1123 5.2.9 compliant. if it is, then its the other email server that is the issue.

also, checking out your error again, it does mention "unknown address error".

seriously, talk to your ISP. most of them are cowboys, but they should be able to help you narrow down the exact cause.

------------------------------------------------------
Matt
Life is all shadows and dust.
Live it up with women and wine while you can

 

[hayabusaukuk]

hmmm still no luck, but thanks for your help.

Below is an error we are getting, i cant make out what the problem is

anyone??

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
AMaxwell@Law.co.uk
SMTP error from remote mail server after initial connection:
host mail1.law.co.uk [212.85.229.xxx]: 554 mail1.law.co.uk
------ This is a copy of the message, including all the headers. ------
------ The body of the message is 20299 characters long; only the first
------ 16384 or so are included here.
Return-path: <chris@appletonwoods.co.uk>
Received: from host-212-18-240-xx.static.mailbox.co.uk ([212.18.240.xx] helo=woods.co.uk)
by neon.webfusion.co.uk with esmtpa (Exim 4.54)
id 1Iu9dQ-00005K-5r
for AMaxwell@Law.co.uk; Mon, 19 Nov 2007 16:38:11 +0000
Received: from AWPC006 ([192.168.1.206]) by awoods.co.uk ([192.168.1.2] running VPOP3) with ESMTP for <AMaxwell@Law.co.uk>; Mon, 19 Nov 2007 16:37:10 -0000
From: "Chris Brown" <chris@woods.co.uk>
To: "Anthony Maxwell" <AMaxwell@Law.co.uk>
Subject: RE: Phil Brindley
Date: Mon, 19 Nov 2007 16:37:10 -0000
Message-ID: <JEECIKAHMLOGKABBBACCCELGDCAA.chris@appletonwoods.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01C82ACA.6E619B30"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Importance: Normal
In-Reply-To: <B4B4E19F08CDEA4FA0B44E03A3A3D4F001AD1988@plex01.Pareto.int>
X-Authenticated-Sender: chris
X-Server: VPOP3 Enterprise V2.4.0 - Registered
This is a multi-part message in MIME format.
------=_NextPart_000_001B_01C82ACA.6E619B30