Chris
Guest
|
 Posted:
Mon Jan 10, 2005 9:04 pm Post subject:
Simple Internet mail sending on Exch2003 |
|
|
Simple Internet mail sending on Exch2003.
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 at 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 out public folders.
Thanks for any help.
|
|
Fitz Crittle [MSFT]
Guest
|
| Posted:
Tue Jan 11, 2005 3:42 am Post subject:
Re: Simple Internet mail sending on Exch2003 |
|
|
For the Outlook configuration see the article below:
289467 Description of user profiles and information services in Outlook
http://support.microsoft.com/?id=289467
In terms of Exchange forwarding mail to Verizon, it's a much better option
to use the SMTP Connector and not the SMTP Virtual Server. Change the SMTP
Virtual Server settings back to the defaults accept for the Outbound
Security. Then install an SMTP Connector:
314961 How To Install and Configure SMTP Connectors in Exchange 2000/2003
Server
http://support.microsoft.com/?id=314961
Then on the General Tab of the SMTP Connector, enter the SMTP server,
outgoing.verizon.net.
Thanks,
Fitz Crittle
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Chris" <chris.muller@mullermedia.com> wrote in message
news:1105369441.512212.67240@c13g2000cwb.googlegroups.com...
| Quote: | Simple Internet mail sending on Exch2003.
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 at 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 out public folders.
Thanks for any help.
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in