Solved

Exchange 2003: 451 Could not complete sender verify callout

Posted on 2007-04-02
10
1,985 Views
Last Modified: 2008-01-09
I am trying to track down meaningful info on the following error and MS Exchange 2003 server.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The following recipient(s) could not be reached:

      Cathleen (sales@domainredacted.com) on 3/17/2007 2:13 PM
            The e-mail system was unable to deliver the message, but did not report a specific reason.  Check the address and try again.  If it still fails, contact your system administrator.
            <smtp.mydomain.com #4.0.0 smtp;451 Could not complete sender verify callout>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

It's only happening when the user sends to one particular domain.  What I've found so far leads me to believe that the recipient's server is trying to probe my server to verify the originating email account, and my server is not responding.  Some other sites suggested that it might be my server's problem.  

Can anyone help?
0
Comment
Question by:maamis
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
10 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 18838305
The recipient is doing some kind of lookup.

Put your domain in to dnsreport.com and ensure that everything is correct in there.
If you have any firewalls etc, ensure that they are not scanning SMTP traffic.

Do you have recipient filtering enabled? If not, turn it and the tar pit on. However don't set the tar pit for longer than 5 seconds.

Simon.
0
 

Author Comment

by:maamis
ID: 18838349
Did the DNSReport thing.  Everything is good in there.

I don't think I have recipient filtering on, and I don't know what the "tar pit" is...  Can you `splain that a liitle?  Thanks!
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18838373
http://www.amset.info/exchange/filter-unknown.asp

It basically drops connections for users who are unknown.

Simon.
0
Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

 

Author Comment

by:maamis
ID: 18838476
Ok.  In the Message Delivery properties, "Filter recipients who are not in the directory" is checked.  I then went to the SMTP virtual server properties and checked the "Apply Recipient Filter" box.

Next, I did the tarpit.reg as outlined in your link.

But I'm not sure how this is going to help with mail we are sending out...
0
 
LVL 104

Accepted Solution

by:
Sembee earned 250 total points
ID: 18838695
The server is calling back to your server. It should now get something positive back immediately.

This isn't strictly an Exchange issue, it is standard SMTP things. It is a matter of trying to work out what the remote site is looking for.

Do you have anything else scanning SMTP traffic? AV, Anti spam, firewall, appliance etc? Those can trigger that message as well.

Simon.
0
 

Author Comment

by:maamis
ID: 18838763
We have GFI Mail Essentials for spam, but if I understand correctly, it's not looking at the port 25 traffic, it's looking at emails in the store.

Thanks for the help on this.  The user is trying her message again.
0
 

Author Comment

by:maamis
ID: 18851634
The problem still occurs.
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18852850
You will have to contact the other side and ask them what they are looking for.

Simon.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  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

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create a Contact 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 Recipients >> Contact ta…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

635 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