Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

sub.domain.com Exchange 2000 Server connection with domain.com SMTP

Posted on 2004-10-12
7
Medium Priority
?
565 Views
Last Modified: 2008-01-09
I have a somewhat ordinary, but apparently less common than I thought, problem involving the following:

  * Exchange 2000 Server for email.domain.com behind ISA firewall - IMAPS, POP3S, OWA and SMTP all work fine
  * LSMTP server for domain.com residing in DMZ just outside the ISA box (MX points to this box's IP)

We're in the middle of transitioning from LSMTP to Exchange (a good move, I think).  I've set up a few accounts in Exchange and have Outlook clients connecting properly, but still pull email from our POP3 server.  I'd like to forward specific user@domain.com accounts internally as user@email.domain.com, and have Exchange populate the mailboxes.  At the same time, I'd like to allow Exchange users to send mail to domain.com users that are not yet set up on Exchange.  To do this, I've created an SMTP Connector to the domain.com SMTP server for processing.  It works (ie. I can send mail from OWA to a user not on Exchange but within our domain).  However, when I send mail to user@email.domain.com, it is somehow forwarded to the LSMTP server.  Is this impossible?

- Jer
0
Comment
Question by:bigmanjer
  • 4
5 Comments
 
LVL 22

Accepted Solution

by:
ATIG earned 200 total points
ID: 12289117
The first question that I have to ask is your RUS stampting @email.domain.com on the Exchange mailboxes? If so all local user on the Exchange server when sending a message will never leave the Exchange organization for those server will see that as a local mailbox.  
0
 
LVL 2

Author Comment

by:bigmanjer
ID: 12291061
My recipient policy has the following:

        SMTP: @domain.com (DEFAULT)
        SMTP: @sub.domain.com
        X400: [standard OU stuff]

Switching the default SMTP policy to @sub.domain.com and un-checking @domain.com still allows email out, but when someone sends to @sub.domain.com, it gets rejected by the server.  Is there a need for an MX record for sub.domain.com in my DNS provider?

- Jer
0
 
LVL 2

Author Comment

by:bigmanjer
ID: 12291338
Update: sending email to testalias@sub.domain.com (Contact in AD set up as an alias for mail forwarding) forwards to the appropraite email account properly!  Something with Recipient Policies and the external SMTP connector must be causing the confusion, I think...

- Jer
0
 
LVL 2

Author Comment

by:bigmanjer
ID: 12297872
Well folks, I did some switcheroos to solve one problem: I made @sub.domain.com the default SMTP policy (keeping @domain.com in there) and I can now receive forwards from @domain.com to @sub.domain.com in Exchange.

HOWEVER, now I cannot send using my Exchange account to @domain.com accounts, which (if they do not reside in Exchange) have to be forwarded to the @domain.com SMTP server.  In fact, I could forward all @domain.com mail to the @domain.com SMTP server, it would be redirected through forwards back to the @sub.domain.com server, so really I just need ALL @domain.com email to go there.  I assume this is done with a connector, which I do have set up, but I suppose it's not complete, or isn't set up properly.

ALSO, I need to mention that the ultimate plan is to make the sub.domain.com mail server the main domain.com mail server, which I think can be accomplished fairly easily by switching the default SMTP policy to @domain.com once we make the switch.  Ideas?

- Jer
0
 
LVL 2

Author Comment

by:bigmanjer
ID: 12298570
Okay, here's the thing - I made it work.  Here's how:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;321721

It explains how to share address spaces (@domain.com) with other SMTP servers.  I will still award points to the answer I got, since it is closely related to Recipient Policies (the primary change I had to make to get it to work), but not the full 500 points.  Thanks!

- Jer
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes Top 9 Exchange troubleshooting utilities that every Exchange Administrator should know. Most of the utilities are available free of cost. List of tools that I am going to explain in this article are:   Microsoft Remote Con…
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

580 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