Solved

550-Callback setup failed while verifying

Posted on 2004-09-13
2
7,400 Views
Last Modified: 2012-08-13
Since this last week I have been noticing that several external mail-accounts (three in total) are reporting the following error as inclosed below when you try to send them a message :

Reporting-MTA: dns; mail.beers.nl
Received-From-MTA: dns; pccq662 (unverified [10.18.200.150])
Arrival-Date: Mon, 13 Sep 2004 14:37:15 +0200

Final-Recipient: rfc822; auto.luxe@12move.nl
Action: failed
Status: 5.0.0 (Permanent failure - no additional status information available)
Remote-MTA: dns; mail-mx-00.tiscali.nl
Diagnostic-Code: smtp; 550-Callback setup failed while verifying <jimmy.velzen@beers.nl>
    550-(result of an earlier callout reused). 550-The initial connection, or a HELO or MAIL FROM:<>
    command was 550-rejected. Refusing MAIL FROM:<> does not help fight spam, disregards 550-RFC
    requirements, and stops you from receiving standard bounce 550-messages. This host does not
    accept mail from domains whose servers 550-refuse bounces. 550 Sender verify failed

The accounts to which the email is sent are valid accounts and can actually be reached from other external accounts.  I have received this same error from two different MTA's/ISP's. Besides the three external accounts that actually log this specific error all other external accounts are functioning just fine.
 
0
Comment
Question by:ns8matrix
2 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 12047224
First - don't forget that while there appear to be many ISPs out there, it isn't unusual for them to be sharing the same infrustructure with one of the big providers. In this case it looks like your email is being rejected by tiscali.

Have you got your server setup to reject NDR - non delivery reports? This is what Tiscali is effectively saying. Could also be a confused message with your reverse DNS not setup correctly.

Short term fix? I think an SMTP Connector for any domains that cause problems should get you going while you attempt to work out what the problem is and a longer term fix.
http://www.amset.info/exchange/smtp-connector.asp

Go to dnsreport.com and enter your domain name and see if it reports any errors.

Simon.
0
 

Author Comment

by:ns8matrix
ID: 12053688
Thanx for pointing me to the http://dnsreport.com, after running the DNSreport test I noticed that my mailserver did not meet the RFC-requirement regarding "Acceptance of NULL <> sender". After making the neccessary changes to the mailserver all email is sent the way the doctor ordered!
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Read this checklist to learn more about the 15 things you should never include in an email signature.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question