• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 296
  • Last Modified:

Exchange server 2003 config issue with external POP3 accounts

We are running Exchange Server 2003 and have a "catch all" POP3 account for our domain.  We have recently introduced a couple of roaming POP3 accounts for travelling salesman (UserA@ourdomain.com and UserB@ourdomain.com).  These accounts work fine until a user on the LAN tries to send to one of the roaming accounts.  Exchange looks at the internal list of addresses on the server and reports that the user account is unknown.

What is the best workaround for this issue?  I have tried setting up an Exchange contact for each of the accounts but this fails to route the message externally.  I assume that we need to reconfigure the recipient policy to allow messages to be routed correctly.

Any advice gratefully received!

Steve
0
SteveZX
Asked:
SteveZX
  • 4
  • 2
2 Solutions
 
tigermattCommented:

The best method would be to have your Sales Reps use either OWA on the Exchange Server or RPC/HTTP in their Outlook clients to remote into the Exchange Server directly, and collect their mail from Exchange.

As for the POP3 connector, have you considered moving to direct SMTP delivery? You are losing a LOT of Exchange's main features by using a POP3 connector.

-tigermatt
0
 
pistolslapperCommented:
There is a way to achieve this i think.

Try this, In the ESM, under the properties of you default smtp server there is a tab called 'Messages'. Click it and and enter in the hostname of your internet mail server (the isp's) where it says - Forward all mail with unresolved reciepients to host:

Then click apply and go to the 'Delivery' tab and click outbound security. Enter in the credentials of your catch-all account under the basic authentication settings. This will send any unresolved recipients to your isp's mail server where it will be queued for local delivery.

Also, you may want to give exchange services a restart.

This may not be ideal but it should work.
0
 
tigermattCommented:

The approach mentioned by pistolslapper could potentially work but has a number of flaws which could prevent it working. Does the Exchange Server run from a static IP address (thus the need for the POP3 connector)? If so, I highly doubt this method will work since the ISP may reject traffic going into their mail server.

The best solution is RPC/HTTP in Outlook, or OWA, so you are then making use of Exchange's extensive features (and getting solid backups of their mailboxes), rather than having two disparate mail systems running side-by-side.

-tm
0
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.

 
pistolslapperCommented:
My way will most definately work. Its not an ideal solution though.
0
 
tigermattCommented:

I didn't mean to sound as though it wouldn't work, but the significant loss you will gain from using that approach is definitely a blow! RPC/HTTP is the best solution here - SteveZX, any update?
0
 
SteveZXAuthor Commented:
Many thanks for the solutions guys.  I appreciated that OWA/RCP/HTTP is the more complete solution, but I was after "the route of least administrative effort".  Pistolslapper's solution is in place and working well.  We'll no doubt consolidate this at a later date, probably with an OWA solution.

Cheers

Steve
0
 
tigermattCommented:

You're welcome. I didn't mean to keep going on about RPC/HTTP and OWA, but I feel it was crucial you were made aware of the potential implications and the best way to go about this!

-Matt
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now