Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Exchange/ISA
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
Exchange/ISA - 1.May2002 5:37:00 PM
|
|
|
angrav
Posts: 5
Joined: 25.Apr.2002
From: Arkansas
Status: offline
|
I'm utterly baffled by something and I hope it is simple. I recently upgraded from SBS 4.5 to SBS2000.
My clients use Outlook 2000 and were set up to use Exchange for internal email, but NOT for external email...for that they were directly accessing the ISP from the Outlook client. From what I could tell this was not going through Exchange at all. Our Exchange server has never been its own SMTP server.
After the upgrade, I am experiencing some issues that look like Exchange is trying to handle some of the external email as well. Users can send mail out, but it looks like it's coming from "user@mydomain.local" instead of "user@isp.com" like it used to. This can be fixed by moving the "internet mail" connector to the top of the list in the Outlook client.
However--after enabling packet filtering on ISA Server, including rules that allow ports 25 and 110, users cannot reply to messages without a long delay and an error. They can send and receive external mail just fine, but when they try to REPLY to an outside email, it hangs in the Outbox. A few cases showed Exchange had changed the reply-to address again.
I guess I am looking for what relationship Exchange has with ISA so that packet filtering would cause this behavior, and also how can I configure Exchange server so that it has nothing to do with our external email? I want the clients to just communicate directly with our ISP's mail server.
Thanks for any suggestions!
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|