4 replies
by steved
I do not pretend to be a total expert on Exchange Server 5.5, but perhaps my experience with a similar situation may be helpful anyway. You be the judge.
As far as I know, Exchange Server will not do what you're suggesting when using a permanent Internet connection. There's a suggestion on the Dial-up Connections property page that it will log in to individual accounts when using RAS. Otherwise, the Internet Mail Transport is expecting that remote servers will initiate connections to the Exchange Server and deliver the mail addressed to the domain.
The ISP hosting our domain offers the standard type of email service that you're describing, where they act as the central depository for the mail for the domain and individual clients canretrieve it from individual mailboxes. They also offer a mail relay service. (It's actually easier for them since they don't have to store the mail on their servers.) They simply configured their server to relay all mail addressed to our domain directly to our Exchange Server. Then our server, of course, understands which mailbox to place it in.
If your client's ISP will make that change, from hosting the domain's mailboxes to relaying all the domain's mail, then in my opinion that's the wayto go. In that configuration, your client has control over what mailboxes are valid in the domain. They won't have to go to the ISP every time someone is added or subtracted from the organization and have them change the mailboxes. It becomes much easier to administer.
I hope this turns out to be helpful. More detail available on request.
Steve Diamond
by steved
Here's more detail.
The ISP's SMTP server will try to make a connection with your client's Exchange Server on port 25 using the SMTP protocol. It just has to know where to find the client's Exchange Server (by IP or URL). The Exchange Server willbe listening on port 25 for SMTP connections.
Other related issues you may run into:
1. The Exchange Server must be configured to allow a connection from the remote SMTP server. See the Connections tab in the Internet Mail Service properties dialog for details. The default setting to accept connections from any host is OK, but it may open the door to others (spammers or worse) using your client's server as a mail relay point. You can decide how likely that is.
2. If your client has a firewall and/or is using NAT for their routing, it too must be configured to allow this connection to happen.
3. Depending again on the routing setup, your client may also need to relay their outgoing Internet mail through the ISP's server. (In our case that did turn out to be true.) This is also handled on the Connections property tab, under Message Delivery. If the default setting (use DNS) works, then all is well. (Look under Queues to see if outgoing messages are "stuck" in the queue.) Ifnot, ask the ISP to provide a relay host for outgoing messages and enter that address under "Forward all messages to host." Then the ISP's server must be configured to accept a connection from your client's server (see point #1).
Good luck.
Steve Diamond
by cj_mcnix
Thanks for your help Steve! I'm currently dealing with the ISP to start the ball rolling. I also finally found a book that may be of help. Several excerpts were *very* helpful. If the excerpts were that helpful, I can only dream about the full text!It's a little elderly (1997), but still a good buy (used at Amazon.com for 15 bucks)
"The Microsoft Exchange Server Internet Mail Connector" By Spyros Sakellariadis
by cj_mcnix
This discussion is closed to new replies.
Trending Software posts
Sort by Trending