 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Clients / October 2004Outlook 2003 switching default email accounts when syncronising
Hello, We are running SBS2003 and Exchange2003 with clients running 2Kpro (all patches etc appllied) Each client has the Excahnage server account and two POP 3 accounts one of which is set to be the default. When the server syncronises the cached folders it changes the default account to be the exchange account. The users then "send" without thinking and hence use the exchange account rather than their "proper" default account. My searches have shed little light on this problem. I have tried various profile settings trying to ensure that the server does not change things but nothing has worked. Any ideas? Thanks Stuart > Hello, > [quoted text clipped - 9 lines] > various profile settings trying to ensure that the server does not > change things but nothing has worked. Any ideas? I've seen posts about this before in the Outlook groups, but have never seen a fix - I'm presuming you're not using OL2000 or earlier? However, you can avoid all this mess by not using POP in your client profiles at all. I'd strongly suggest centralizing your e-mail on the Exchange server entirely - host your domain/domain's Internet mail there, rather than relying on clients to pull it down via POP. This has many advantages - centralized admin, easier mailbox creation/address modification, centralized AV scanning for mail (presuming you're using good Exchange antivirus software as you should) and the ability for users to use OWA. It's also a lot faster and more efficient in general. Do you have registered Internet domain name(s)? > Thanks > > Stuart I kind of thought this would be the response. I think my ultimate goal is to get to where you suggest but I was hoping to do it little by little. At the moment we need to support two external domains eg fred@companyA.co.uk & fred@companyB.co.uk there is also fred@company.local for exchange. Our connection to the outside world is via an ADSL connection. The two "external" domains are handled by an ISP that is very reliable (probably more so than our ADSL or even the server!). There is also the need for a couple of "remote" workers who need to send/receive emails away from the office. I am concerned about the robustness of ADSL for this sort of thing and my "exposure" to the internet. My server sits behind a router firewall. Any guidance is greatly appreciated. But fundamentaly, Why does it behave like this? Thanks again Stuart > > Hello, > > [quoted text clipped - 25 lines] > > > > Stuart > I kind of thought this would be the response. I think my ultimate > goal is to get to where you suggest but I was hoping to do it little [quoted text clipped - 4 lines] > > fred@company.local for exchange. You don't need to use company.local for your default/reply address in Exchange at all - set up a recipient policy that specifies the "real" domain name/s and make one the default for all users (make sure the mailboxes inherit the changes properly & are stamped with the correct Note that you can send only as the default address specified in your mailbox - see www.ivasoft.biz for an add-in that will let users send as alternate addresses defined in their mailboxes. Our connection to the outside world > is via an ADSL connection. The two "external" domains are handled by > an ISP that is very reliable (probably more so than our ADSL or even > the server!). Well, of course you should make sure your server is reliable and working properly anyway, but as to the connectivity or downtime in general, have someone else (your ISP? third party service)? specified as your domain's secondary/higher-cost MX record for automatic collection/redelivery of your mail when your server is unavailable for any reason. If your ISP won't do this, see www.dyndns.org for their MailHop BackupMX service - it's about $20/yr USD. In fact, if you have a dynamic public IP, you'll need something like dyndns anyway. There is also the need for a couple of "remote" workers > who need to send/receive emails away from the office. OWA :-) > I am concerned about the robustness of ADSL for this sort of thing > and my "exposure" to the internet. My server sits behind a router > firewall. Any guidance is greatly appreciated. > > But fundamentaly, Why does it behave like this? As to Outlook changing the default client? I'm not sure; as I said I've heard of this before (many posts, but haven't seen a real answer myself). > Thanks again > [quoted text clipped - 30 lines] >>> >>> Stuart Stuart: I have the exact problem and my research has yet to come up wit an answer. Have tried many many things. Any luck yet??? This is killin me. I must keep my popmail and it must be the default; but i need m exchange running as well coastaleddie@yahoo.com > *Hello, > [quoted text clipped - 19 lines] > > Stuart - coastaleddi |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.