Exchange Server 2007 - Receive inbound emails but sender gets NDR

Hi all,

I have a SBS2008 server and utilise Exchange 2007. We use a popcollector bit of software called PopCon (www.christensen-software.com). Until yesterday, this solution has worked well.

Now, when someone sends an email to us, they receive an NDR (below) but the message is still delivered.

'Delivery has failed to these recipients or distribution lists:
user=allmail@purplejelly.co.uk<mailto:user%3Dallmail@purplejelly.co.uk>
The recipient's e-mail address was not found in the recipient's e-mail system.
Microsoft Exchange will not try to redeliver this message for you. Please check the
e-mail address and try resending this message, or provide the following diagnostic
text to your system administrator.
________________________________
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: pj.local
user=allmail@purplejelly.co.uk
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##
Original message headers:
Received: from exchange-pop3-connector.com (192.168.0.2) by AJAX.pj.local
 (192.168.0.2) with Microsoft SMTP Server id 8.2.176.0; Wed, 7 Apr 2010
 09:31:57 +0100
Return-Path: <paul@qhfc.co.uk>
Received: from lmtpproxyd (mailin1.hostvue.com [195.26.90.111])
         (authenticated user=allmail@purplejelly.co.uk bits=0)   by ms1.hostvue.com
 (Cyrus v2.3.12p2) with LMTPA;   Wed, 07 Apr 2010 09:31:03 +0100
X-Sieve: CMU Sieve 2.3
Received: from mailin1.hostvue.com (localhost.localdomain [127.0.0.1])
         (authenticated user=allmail@purplejelly.co.uk bits=0)   by
 mailin1.hostvue.com (Cyrus v2.3.12p2) with LMTPSA       (version=TLSv1/SSLv3
 cipher=AES256-SHA bits=256/256 verify=YES);     Wed, 07 Apr 2010 09:31:03 +0100
X-Sieve: CMU Sieve 2.3
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on mailin1.hostvue.com
X-Spam-Level:
X-Spam-Status: No, score=0.4 required=40.0 tests=AWL,NO_REAL_NAME autolearn=no
        version=3.1.9
X-Spam-Report: *  0.6 NO_REAL_NAME From: does not include a real name
        * -0.2 AWL AWL: From: address is in the auto white-list
Received: from mailsub2.hostvue.com ([195.26.90.72])    by mailin1.hostvue.com
 with esmtps (TLSv1:AES256-SHA:256)     (Exim 4.63)     (envelope-from
 <paul@qhfc.co.uk>)     id 1NzQf9-0000dY-CG     for paul@purplejelly.co.uk; Wed, 07
 Apr 2010 09:31:03 +0100
Received: from apache by mailsub2.hostvue.com with local (Exim 4.63)
        (envelope-from <paul@qhfc.co.uk>)       id 1NzQf8-0000IS-Hj     for
 paul@purplejelly.co.uk; Wed, 07 Apr 2010 09:31:02 +0100
Received: from 135.196.212.250        (SquirrelMail authenticated user
 paul@qhfc.co.uk)        by webmail.powerpanel.co.uk with HTTP;        Wed, 7
 Apr 2010 09:31:02 +0100 (BST)
Message-ID: <28359.135.196.212.250.1270629062.squirrel@webmail.powerpanel.co.uk>
Date: Wed, 7 Apr 2010 09:31:02 +0100
Subject: test4
From: <paul@qhfc.co.uk>
To: <paul@purplejelly.co.uk>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal'

Can anyone shed any light on this? The Allmail address certainly does exist on this system.

Many thanks


PurpleJellyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hilal1924Commented:


Here is a link to this error code: http://www.microsoft.com/technet/prodtechnol/exchange/guides/ExMgmtGuide/fb7830cf-23c6-48a6-8759-526b7854ae39.mspx?mfr=true

This question has previously been addressed here :

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_22797640.html

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_25023516.html

Take a look at the solutions and see if that applies to your case. Although in your case it is simply a matter of Recipient Not Found. May be the final recipient is null or does not exist.

Peace,
Hilal
0
PurpleJellyAuthor Commented:
Thanks Hilal

All domains that are accepted are set as authoritive domains and the the email address that is specified as failing on the NDR definately does exist. As I said, until somepoint yesterday, this was working fine. As far as I can see we have not had any updates installed so I am kinda at a bit of a loss.

Paul
0
Hilal1924Commented:
What is this Server " Generating server: pj.local" . I think this is the one server that is not able to find the recipient.

Peace,
Hilal
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

PurpleJellyAuthor Commented:
pj.local is the SBS2008. All recipients reside here.

Thanks
0
Hilal1924Commented:
OK Do One thing; use this command to verify the mail flow to that user:

Test-Mailflow pj.local -TargetEmailAddress allmail@purplejelly.co.uk

Let me know what was the result.

Peace,
Hilal
0
PurpleJellyAuthor Commented:
Hi Hilal,

Thanks for your help.

I have resolved the issue.

My pop collector was misreading the email header info. This part...

'user=allmail@purplejelly.co.uk<mailto:user%3Dallmail@purplejelly.co.uk>'

was being read as the user name of 'user%3Dallmail@purplejelly.co.uk' insted of 'allmail@purplejelly.co.uk'. Luckily in PopCon there is a part where you can strip out characters from the from of the header info. I have done this and it works well!

Phew!

Thanks for your help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Hilal1924Commented:
So why not rate this question ? I am glad it worked out for you.

" Take a look at the solutions and see if that applies to your case. Although in your case it is simply a matter of Recipient Not Found. May be the final recipient is null or does not exist"

This is what it was all about.

Peace,
Hilal
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.