Re: smarthost authentication
From: Chris (chris.muller_at_mullermedia.com)
Date: 01/10/05
- Previous message: spiv007: "Re: w2k domain adding a exchange 2k or 2k3"
- Next in thread: Lanwench [MVP - Exchange]: "Re: smarthost authentication"
- Reply: Lanwench [MVP - Exchange]: "Re: smarthost authentication"
- Messages sorted by: [ date ] [ thread ]
Date: 10 Jan 2005 13:30:29 -0800
I posted this under another topic, but getting smarthost to work seems
to be a big part of our problem, so I hope you can help me. Please be
patient and read this through... thanks.
We have a small group (6) of users on an Exchange 2003 server.
(Previously, we had Exchange 5.5)
We want Exchange to handle *only* the internal email accounts, and our
clients (Outlook) to directly handle internet stuff. We mainly use
Exchange because of shared contacts and other public folders--which we
use extensively.
Here's what *used to* work for us:
Our Outlook clients are set up with 2 email accounts. The first is an
Internet email account which uses an external popmail server for
incoming. This is provided by the guys who host our domain/website.
(call it "popmail.abc.com")
Outgoing internet mail is handled by our DSL provider (smtp server =
outgoing.verizon.net; it also requires an id and
password--though we can all use the same one)
The second account is the Exchange Server account. Our clients by the
way are all set up to use local personal folders to receive incoming,
rather than use the exchange mail accounts.
If the Internet account is set as first choice for delivery, this
usually works, but sometimes the exchange server wants to send the
outgoing smtp traffic. I'd prefer it DID NOT do that, and for a while
did a "disable outgoing" on it. It would just keep complaining the
recipients couldn't be reached, etc.
Then I tried using smarthost, directing the outgoing to verizon's smtp.
That doesn't seem to work either.
In manager, I go to server\protocols\smtp\default smtp virtual
server\properties
Then, under Delivery tab, I click Advanced and insert
"outgoing.verizon.net" into smarthost. Since our exchange server and
domain are not registered, I set the masquerade domain to my external
email/web domain (happens to be mullermedia.com). The FQDN value, I set
to the one we use internally for the exchange server.
Then, since verizon smtp wants an id/password, I go back to
properties\delivery screen and click "outbound security". Then turn on
"basic authentication" and enter the Verizon id/password info. (I think
Verizon can tell whether we're on their DSL line, anway, because I
can't use this smtp server from home.)
This all still does not work. Exchange often grabs my outgoing messages
and tries to send them but can't. This happens most often, if I cc an
internal user when emailing an external person.
Can anyone tell me what I've done wrong?
If necessary, I'd be willing to turn off internal mail completely and
send to my coworkers through the net--as long as we could still use
outlook and get at our public folders.
Thanks for any help.
- Previous message: spiv007: "Re: w2k domain adding a exchange 2k or 2k3"
- Next in thread: Lanwench [MVP - Exchange]: "Re: smarthost authentication"
- Reply: Lanwench [MVP - Exchange]: "Re: smarthost authentication"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|