Advertisement

02.23.2008 at 08:07AM PST, ID: 23187123
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

Forcing Exchange to route internal emails through SMTP Connector

Tags: Microsoft, Exchange, SMTP connector
I have a client that has Exchange 2003 (SBS) running. Right now all their emails are coming through a 3rd party POP3 app. The reason for this is the 3rd party app allows emails to be left on the POP3 server. Two of the clients have Blackberrys from two different providers. The Blackberrys are configured to grab the emails from the POP3 servers (and that's why I'm not using Exchange's POP3 connector).

The problem I'm having is this, all incoming emails from outside sources eventually show up on the Blackberrys. When someone internally emails someone else internally, the email bypasses the SMTP Connector (routes it internally) and therefore bypasses the POP3 servers. This means that any emails sent internally are not being picked up by the Blackberrys.

When the clients are on the road, it is critical for them to receive their internal emails on the Blackberrys. The reason I don't put a rule to forward those emails is because the email address on the Blackberry is the same as their domain address and it would create a loop.
Start your free trial to view this solution
Question Stats
Zone: Software
Question Asked By: michaelfin
Solution Provided By: michaelfin
Participating Experts: 1
Solution Grade: A
Views: 206
Translate:
Loading Advertisement...
02.23.2008 at 08:23AM PST, ID: 20965432

Rank: Guru

All comments and solutions are available to Premium Service Members only.

Start your 7 day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
02.23.2008 at 09:01AM PST, ID: 20965623

All comments and solutions are available to Premium Service Members only.

Start your 7 day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
02.23.2008 at 09:03AM PST, ID: 20965632

All comments and solutions are available to Premium Service Members only.

Start your 7 day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
02.23.2008 at 09:20AM PST, ID: 20965685

Rank: Guru

All comments and solutions are available to Premium Service Members only.

Start your 7 day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
02.23.2008 at 02:30PM PST, ID: 20967064

All comments and solutions are available to Premium Service Members only.

Start your 7 day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
03.03.2008 at 07:43AM PST, ID: 21032528

All comments and solutions are available to Premium Service Members only.

Start your 7 day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
Microsoft
  • Internet Protocols
  • Applications
  • Development
  • OS
  • Hardware
  • Windows Security
Apple
  • Operating Systems
  • Hardware
  • Programming
  • Networking
  • Software
Internet
  • Search Engines
  • File Sharing
  • WebTrends / Stats
  • Spy / Ad Blockers
  • Web Browsers
  • New Net Users
  • Web Development
  • Chat / IM
  • Anti Spam
  • Web Servers
  • Anti-Virus
  • Email Clients
Gamers
  • Tips
  • Online / MMORPG
  • Puzzle
  • Emulators
  • Action / Adventure
  • Role Playing
  • Consoles
  • Game Programming
  • Strategy
  • Sports
  • Misc
  • Computer Games
Digital Living
  • Hardware
  • New Net Users
  • New Users
  • Software
  • Digital Music
  • Gaming World
  • Home Security
  • Apple
  • Networking Hardware
Virus & Spyware
  • Vulnerabilities
  • IDS
  • Encryption
  • Anti-Virus
  • Operating Systems Security
  • Software Firewalls
  • WebApplications
  • Cell Phones
  • Operating Systems
  • Internet
  • Hardware Firewalls
Hardware
  • Handhelds / PDAs
  • Displays / Monitors
  • Components
  • Networking Hardware
  • Peripherals
  • Laptops/Notebooks
  • Storage
  • Servers
  • Desktops
  • New Users
  • Misc
  • Apple
Software
  • System Utilities
  • Industry Specific
  • Network Management
  • Photos / Graphics
  • Page Layout
  • VMWare
  • Misc
  • Web Development
  • OS
  • CYGWIN
  • Voice Recognition
  • Message Queue
  • Quality Assurance
  • Security
  • Firewalls
  • MultiMedia Applications
  • Development
  • Database
  • Office / Productivity
  • Business Management
  • OS/2 Apps
  • Server Software
  • Internet / Email
ITPro
  • OS
  • Storage
  • Encryption
  • Operating Systems Security
  • Apple Hardware
  • Laptops & Notebooks
  • Servers
  • Networking Hardware
  • Peripherals
  • Devices
  • Displays / Monitors
  • WebTrends / Stats
  • Search Engines
  • Firewalls
  • WebApplications
  • IDS
  • Vulnerabilities
  • Email Clients
  • File Sharing
  • Spy / Ad Blockers
  • Web Browsers
  • Web Servers
  • Networking
  • Anti-Virus
  • Chat / IM
  • Anti Spam
Developer
  • Web Servers
  • Web Browsers
  • Game Programming
  • Dev Tools
  • Industry Specific
  • Office / Productivity
  • Database
  • CYGWIN
  • Web Development
  • Search Engines
  • File Sharing
  • WebTrends / Stats
  • Programming
  • Content Management
  • Application Servers
  • Protocols
Storage
  • Removable Backup Media
  • Storage Technology
  • Servers
  • Grid
  • Remote Access
  • Backup / Restore
  • Misc
  • Hard Drives
OS
  • Miscellaneous
  • Security
  • Development
  • Linux
  • VMWare
  • MainFrame OS
  • Unix
  • Apple
  • OS / 2
  • AS / 400
  • BeOS
  • Microsoft
  • VMS / OpenVMS
Database
  • Oracle
  • Miscellaneous
  • MySQL
  • Software
  • Sybase
  • Contact Management
  • PostgreSQL
  • Data Manipulation
  • Clarion
  • InterSystems Cache
  • Siebel
  • MUMPS
  • OLAP
  • SQLBase
  • SAS
  • GIS & GPS
  • 4GL
  • Berkeley DB
  • DB2
  • Informix
  • Interbase / Firebird
  • FoxPro
  • Reporting
  • LDAP
  • Filemaker Pro
  • MS SQL Server
  • dBase
  • MS Access
Security
  • Misc
  • Web Browsers
  • Software Firewalls
  • Operating Systems Security
  • File Sharing
  • Spy / Ad Blockers
  • Vulnerabilities
  • WebApplications
  • IDS
  • Anti-Virus
  • Encryption
  • Anti Spam
  • Email Clients
  • VPN
  • Chat / IM
Programming
  • Editors IDEs
  • Installation
  • Handhelds / PDAs
  • Multimedia Programming
  • System / Kernel
  • Algorithms
  • Game
  • Signal Processing
  • Project Management
  • Open Source
  • Database
  • Misc
  • Languages
  • Processor Platforms
  • Theory
Web Development
  • Scripting
  • Blogs
  • Web Servers
  • Software
  • Search Engines
  • Web Graphics
  • Images
  • Internet Marketing
  • Images and Photos
  • Components
  • Document Imaging
  • Web Languages/Standards
  • Illustration
  • WebApplications
  • Fonts
  • WebTrends / Stats
  • Authoring
  • Digital Camera Software
  • Miscellaneous
Networking
  • Protocols
  • Apple Networking
  • Network Management
  • Message Queue
  • Application Servers
  • Content Management
  • File Servers
  • Email Servers
  • Misc
  • Java Editors & IDEs
  • Wireless
  • Networking Hardware
  • Backup / Restore
  • System Utilities
  • ISPs & Hosting
  • Web Servers
  • Storage Technology
  • Removable Backup Media
  • Servers
  • Broadband
  • Grid
  • OS / 2
  • Novell Netware
  • Unix Networking
  • Windows Networking
  • Security
  • Telecommunications
  • Operating Systems
  • Linux Networking
Other
  • Community Advisor
  • Lounge
  • Community Support
  • New Net Users
  • Philosophy / Religion
  • Math / Science
  • Miscellaneous
  • URLs
  • Expert Lounge
  • Politics
  • Puzzles / Riddles
Community Support
  • Suggestions
  • New to EE
  • New Topics
  • Community Advisor
  • CleanUp
  • Announcements
  • General
  • Feedback
  • Input
  • EE Bugs
 
02.23.2008 at 08:23AM PST, ID: 20965432

Rank: Guru

I strongly recommend you to download and install the free version of blackberry enterprise server. Since you have two users only, you will receive one free license and you'll have to purchase a second one for 99$.
Another approach is forwarding the internal emails to external pop3 accounts, which in turn will forward everything to the blackberry addresses.
Forcing the internal delivery to change course is not an easy job, Cause local delivery depends on AD, when there is a message for the local domain, exchange will lookup AD to resolve the email address to a mailbox on the server, once it's resolved, will forward to the mailbox, plus i'm not even sure if you can do that. If there is anyone who knows how to, i will be glad to know it myself.
 
02.23.2008 at 09:01AM PST, ID: 20965623
Thanks isaman, I thought of those options myself but I fear that it'll get messy :(

Another approach I thought of, was creating a new email address on the Blackberrys (non domainish) and creating a rule to funnel only internal emails to those addresses.

The issue I have with Blackberry Exchange Server is that the 2 users are using different ISPs for their service. I think that that would complicate issues.  I'm also not familiar with the Blackberry Exchange Server software but doesn't it need a separate box? Or would it run on SBS?

Thanks
 
02.23.2008 at 09:03AM PST, ID: 20965632
One other thing that I though of, is to delete the local address from Recipient Policies and see if that forces the SMTP connector.
 
02.23.2008 at 09:20AM PST, ID: 20965685

Rank: Guru

Trust me, me too i had a similar situation, i knew nothing about BES, and i had three users (VPs) with three different carriers, once i decided to go, it was so easy and smooth, you won't have problems i promise, just make sure you follow the installation instructions and the prerequisits, there is not much and you'll be fine. Plus, you will gain a new experiance, which is priceless.
Grab any spare computer and install BES on it. I assure you, everyone, including yourself will adore the experiance.

Harout
 
02.23.2008 at 02:30PM PST, ID: 20967064
A quick update, I found a KB that apparently solves this problem, but in typical MS fashion, it's no longer there.

The kb is 319759
 
03.03.2008 at 07:43AM PST, ID: 21032528
I managed to find the kb:

How to Configure Exchange to Forward Messages to a Foreign Messaging System That Shares the Same SMTP Domain Name Space
View products that this article applies to.
This article was previously published under Q319759
SUMMARY
This article describes how to configure Microsoft Exchange to send messages to contacts whose user accounts exist in Active Directory, but whose e-mail addresses point to a foreign messaging system that shares the same SMTP domain name space as the Exchange server.

By default, if a group of e-mail recipients in an Exchange message handling system and a group of recipients in a foreign e-mail system (UNIX SendMail, for example) share the same Simple Mail Transfer Protocol (SMTP) domain, e-mail does not flow from Exchange to the foreign recipients. Exchange generates non-delivery reports (NDRs).
MORE INFORMATION
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
321721 XCON: Sharing SMTP Address Spaces in Exchange 2000
To configure Exchange to forward messages to a foreign messaging system that shares the same SMTP domain name space, follow these steps.

Note The domain name of Example.com is used throughout these steps as an example.
1.      Modify the Exchange default recipient policy to have a single primary SMTP address of @local that is authoritative. Create a secondary SMTP address that points to your domain name space. To do this, follow these steps:
1.      Start Exchange System Manager. To do this, click Start, point to Microsoft Exchange, and then click System Manager.
2.      Under Your Organization (Exchange), expand Recipients, click Recipient Policies, and then double-click Default Policy in the right pane of Exchange System Manager.
3.      Click the E-Mail Addresses tab, click the SMTP address (but do not click to clear the check box), and then click Edit.
4.      In the Address box, type @local.
5.      Click to select the This Exchange Organization is responsible for all mail delivery to this address check box (if it is not already selected), and then click OK.
6.      Click New, click SMTP Address, and then click OK.
7.      In the Address box, type @example.com (where example.com is the name of your SMTP domain name space).
8.      Click to clear the This Exchange Organization is responsible for all mail delivery to this address check box, and then click OK.
9.      Click the SMTP item that corresponds to the @local address space, and then click Set as Primary if the button is available (does not appear dimmed).
10.      Click OK, and then click Yes when you are prompted to update all corresponding recipient e-mail addresses.
2.      Create a second, higher-priority recipient policy with the Primary SMTP address that points to your domain name space and a secondary authoritative SMTP address of @local. To do this, follow these steps:
1.      In Exchange System Manager, right-click Recipient Policies, point to New, and then click Recipient Policy.
2.      Select the E-Mail Addresses check box, and then click OK.
3.      Type a friendly name for the policy in the Name box, and then click the Modify.
4.      In the Find list, click Exchange Recipients, and then click OK.
5.      Click OK, and then click the E-Mail Addresses (Policy) tab.
6.      Click the SMTP item that corresponds to your domain name space. For example, click @example.com, and then click Set as Primary.
7.      Click the SMTP item that corresponds to your domain name space (for example, click @example.com), and then click Edit.
8.      Click to clear the This Exchange Organization is responsible for all mail delivery to this address check box (if it is not already cleared), and then click OK.
9.      Click @local, and then click Edit.
10.      Click to select the This Exchange Organization is responsible for all mail delivery to this address check box (if it is not already selected), and then click OK.
11.      Click Apply, click Yes to update all corresponding recipient e-mail addresses, click Yes to update all corresponding recipient e-mail addresses after the addresses of type [smtp] have been modified, and then click OK.

The new policy is displayed above Default Policy in the right pane of Exchange System Manager.
3.      Modify the default SMTP Virtual Server properties to remove message forwarding for unresolved recipients. To do this, follow these steps:
1.      In Exchange System Manager, expand Administrative Groups, expand First Administrative Group, expand Servers, expand ServerName, expand Protocols, expand SMTP, and then click Default SMTP Virtual Server.

NOTE: You may have to expand SMTP Virtual Servers before you can click Default SMTP Virtual Server item.
2.      Right-click Default SMTP Virtual Server, and then click Properties.
3.      Click the Messages tab.
4.      Remove any entries that are displayed in the Forward all mail with unresolved recipients to host box, and then click OK.
4.      Create an SMTP connector that forwards all messages to the foreign messaging system. To do this, follow these steps:
1.      In Exchange System Manager, expand Administrative Groups, expand First Administrative Group, right-click Connectors, point to New, and then click SMTP Connector.
2.      In the Name box, type a descriptive name for this connector.
3.      Click Forward all mail through this connector to the following smart hosts, and then type the IP address of the remote messaging system inside square brackets ([]). For example, type:
[192.168.1.100]
4.      Click Add, click Default SMTP Virtual Server in the SMTP virtual server instances list, and then click OK.
5.      Click the Address Space tab, and then click Add.
6.      Click SMTP, and then click OK.
7.      In the E-mail domain box, type your e-mail domain. Do not precede the e-mail domain with the at sign (@). For example, type example.com.
8.      Click OK.
9.      Click to select the Allow messages to be relayed to these domains check box, and then click OK.
5.      Restart the Routing and SMTP services. To do this, follow these steps:
1.      Click Start, click Run, type services.msc, and then click OK.
2.      Right-click Microsoft Exchange Routing Engine, and then click Stop.
3.      Right-click Microsoft Exchange Routing Engine, and then click Start.
4.      Right-click Simple Mail Transport Protocol (SMTP), and then click Stop.
5.      Right-click Simple Mail Transport Protocol (SMTP), and then click Start.
6.      Quit the Services snap-in.
6.      Rebuild the Recipient Update Service (RUS). To do this, follow these steps:
1.      In Exchange System Manager, expand Recipients, and then click Recipient Update Services.
2.      In the right pane of Exchange System Manager, right-click the Recipient Update Service item (not the Enterprise Configuration item), and then click Rebuild.
3.      Click Yes to confirm the rebuilding of the client addresses.
4.      Quit Exchange System Manager.
7.      Create a new contact with an e-mail address, and then test the Exchange configuration.
The information in this article applies to:
"      Microsoft Exchange Server 2003 Enterprise Edition
"      Microsoft Exchange Server 2003 Standard Edition
"      Microsoft Exchange 2000 Server
"      Microsoft Windows Small Business Server 2003, Premium Edition
"      Microsoft Windows Small Business Server 2003, Standard Edition
Last Reviewed:      10/9/2003 (4.0)
Keywords:      kbinfo KB319759
Accepted Solution
 
 
20080236-EE-VQP-29 / EE_QW_2_20070628