Solved

How to POP to Exchange clients e-mail another external POP user?

Posted on 2006-06-15
10
292 Views
Last Modified: 2010-03-06
Hi all,

I have an SBS server using POP to Exchange services (GFI to be exact) to collect and distribute all mail internally, works with no issues.  The issue is when internal users e-mail a person on the outside with the same domain name (This is also a POP account) the following occurs

The following recipient(s) could not be reached:

      'name@domainname.com' on 15/06/2006 11:35 AM
            The e-mail account does not exist at the organization this message was sent to.  Check the e-mail address, or contact the recipient directly to find out the correct address.
            <someserver.server.local #5.1.1>

Now these external users only use POP accounts to recieve their e-mail and do not need to be part of the server or a user.  

I have had this working in the past but for the life of me cannot figure it out.  Anyone have any ideas?

Your time appreciated.
0
Comment
Question by:servicad
10 Comments
 
LVL 4

Expert Comment

by:g127404
ID: 16912922
I've had this problem as well and ended up adding those external users as a local user.  Even if they don't use the exchange mailbox the server needs to see they are valid users in the domain.  There may be a way to set up aliases for those users and skip the actual creation of a mailbox, so we can wait and see if someone else has a better option.
0
 

Author Comment

by:servicad
ID: 16913035
YEs If you add them as local users then the e-mail gest stuck in Exchnage internally.
0
 
LVL 95

Expert Comment

by:Lee W, MVP
ID: 16913142
It sounds like you named your domain the same as your internet domain.  Not a good idea.  Should have been named "yourdomain.local".  Then you wouldn't have this problem.  The only solution is pretty much what g127404 suggests.
0
 

Author Comment

by:servicad
ID: 16913170
no it is called server.local  
0
Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

 

Author Comment

by:servicad
ID: 16913185
As per error message in original post
0
 
LVL 95

Expert Comment

by:Lee W, MVP
ID: 16913234
Sorry, I initially thought this was similar to a setup I have, but upon further reflection, it's not.  I have a setup where the the domain is .local and I had problems like this.  I suspect you have a recipient policy defined so, among other things, you have e-mail go out correctly.  BUT, in my setup, I only use Exchange for a mail store (WANT it to handle mail entirely, but owners are too paranoid)

Why not use the server as it was meant to be and make it your primary mail server?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 16913300
This is a classic problem. Wouldn't matter what your internal domain was called - whether it was a .local or a .com - you would get the same problem.

The basic issue is that Exchange thinks it is responsible for all email for that domain.
Ideally you should have all email delivered to the Exchange server. If you are on any kind of permanent connection then you can easily switch over to SMTP delivery. That will give you a better user experience.

You could look at recipient policy for the domain and deselect the option that says that Exchange is responsible for all email delivery for the domain. That might work.
Otherwise take a look at this page at Microsoft which gives you more options: http://support.microsoft.com/default.aspx?kbid=321721

Simon.
0
 

Author Comment

by:servicad
ID: 16920376
Thanks Sembee,

Thought that would do the trick but it prevented anyone from e-mail outside the office.  Bummer.
0
 
LVL 1

Accepted Solution

by:
DarthMod earned 0 total points
ID: 17232177
PAQed with points refunded (500)

DarthMod
Community Support Moderator
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
In this video we show how to create a User Mailbox 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 >> Mailb…
In this video we show how to create a mailbox database 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 Servers >> Data…

705 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now