The recipient's e-mail address was not found in the recipient's e-mail system

Hello experts,

After a lot of searching for an answer, I'll ask here.
We just went from SBS 2003/exchange 6.5.7638.1 to SBS 2008/exchange 2007 and now when we try to "one-off" an email FAX with our GFI FAXmaker 12 server we get the following response:
Delivery has failed to these recipients or distribution lists:
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: eserver.snart.local
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Original message headers:
Received: from eserver.snart.local ([fe80::112d:e043:6bda:xxxx]) by
 eserver.snart.local ([fe80::11k1:e042:6bda:xxxxx]) with mapi; Sun, 6 Mar 2011 10:18:21 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: user <>
To: "" <>
Date: Sun, 6 Mar 2011 10:06:40 -0500
Subject: Test
Thread-Topic: Test
Thread-Index: AQHL3BAYSuMq9+OT6UustbV5yua4eg==
Message-ID: <29C33810ECEE0141B5FEAD2083CACA690200ED45D2@eserver.snart.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-TNEF-Correlator: <29C33810ECEE0141B5FEAD2083CACA690200ED45D2@eserver.snart.local>
MIME-Version: 1.0


I believe it has something to do with the anti-spam filtering but I don't exactly know how to restore this lost functionality. For common fax numbers we use with the sender/user having the emaill address as a contact in their address book does not trigger this error.

The one-off addressing is used quite frequently for infrequent contacts and they are numerous.  I don't want to tell all the users they need to create a contact for every faxnumber they send to.

I did have to create my own send and receive connectors for Exchange. GFI site (KB & Forums) have no real clues that I can find.

BASICALLY, my need is simply to allow all addresses with "* " addresses to forward the mailFAX to an internal IPadd

Hope you can help me!
Who is Participating?
PhosphorConnect With a Mentor Author Commented:
I eventually figured it out. I had to re-create the both send and receive connectors using exchange shell.
i don't quite understand the flow here.
 your users send an email to from their Outlook client with their From address being, and then they receive this bounce message?

and if i follow, if they just type in ###@faxmaker they get this bounce, but if they've got an Outlook contact created for ###@faxmaker it goes through?
PhosphorAuthor Commented:
Yes. that is correct.

There is both a send and recieve connector for *
When we get a successful inbound fax the address is from

If we send from our address book it comes back as successful to ContactName
When we used to send to a one-off it would be 1areacodeNumber@faxmaker
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

so is it the outbound fax that's failing or is it the returned confirmations?
PhosphorAuthor Commented:
So far only the outbound. It's obviously not a bare relay issue as we can send and receive with legal contacts (legal meaning no special chars in the contact name in their personal address books with the fax number formatted by pushing the Business Fax button to format it as +1(710) 555-1212

I would imagine the reply would be sent ok as inbound faxes have no problems. It's mostly a usability issue, but that's what we were used to and I just know it has to be some filter setting somewhere but naturally I know just enough to ask...
PhosphorAuthor Commented:
So far only the outbound fax. We get all successful confirmations...
PhosphorAuthor Commented:
I believe I found a workaround that is not very elegant.

This below mentions using IMCEAFAX- as a prefix. This was further reinforced when I clicked on the returned failure messages' phone number hyperlink it was formatted as IMCEAFAX-7105551212@snart.local
Further searching the term "IMCEAFAX" eventually led me to this item below.;en-us;323351

So maybe this is actually a FAXmaker issue after all?
What all this seems to suggest is that the translation from the allegedly supported address string [FAX:1234567890] to is not taking place...

Though If it's as simple as IMCEAFAX- as a prefix, I can live with that.
That's what it would sound like, although I still don't follow why it would have changed between Exchange versions, at least not to the degree that it would no longer work the way you'd been doing it. There are a ton of differences otherwise between the two.

unfortunatly i'm not that in the weeds on Exchange, i've never used that particular functionality.
sorry i don't think i'll be any help
PhosphorAuthor Commented:
Well, I found another MS KB article where it makes a note that

 "You cannot share an SMTP address space for which Exchange is authoritative."

I checked the faxmaker listing in Organization>Accepted Domains and it was selected as authoritative. I changed that setting to "Internal Relay Domain" and tested the string which failed.
I then tried the same string WITHOUT the "1"  and sent it as ""

It used to always fail without the country code before...
PhosphorAuthor Commented:
Self resolved issue. No actionable replies
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.