Discussion Locked

Out of Office Assistant - external email

0 helpful
119 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Problem: Out of Office Assistant will not automatically forward external email!

I am trying to setup the Out-of-Office Assistant to automatically forward all incoming internal and external email to an external account (AOL) for someone going on maternity leave. We are using Outlook 97 and Exchange Server (v5.5). I have already cleared the check boxes ?Disable Out of Office responses to the Internet? and ?Disable Automatic Replies to the Internet? on my Exchange server and restarted those services. The problem is that it will never forward external email to an external account. Internally generated email will successfully forward every time. Because it is successfully forwarding internally generated email to an external account, it leads me to believe that the Exchange portion of the situation is configured properly. However, in all the various ?how to?s? that I have read, it indicates that Outlook must be configured to ?Disconnect when finished sending and receiving?. However, I am using a LAN connection (Outlook-Tools-Services-Internet Mail-Properties-Connection) and the check box to ?disconnect?? is not available (grayed out) for this connection type. This leads me to suspect that it is not ?disconnecting? when it has finished receiving the external email and therefore can not ?connect? to send it out because our connection is constant. Any and all help will be greatly appreciated.

Thanks!

119 replies

by rlevesque

Here is what I would try.

If you want your emails forwarded to your AOL account, make a custom recipient, select internet email, and enter janedoe@aol.com. Save this custom recipient, which will show an icon of a globe and not a mailbox. If the mailbox of this person is Jane Doe, I would call this Jane Doe - AOL.

Then, open your Jane Doe's real mailbox properties, change to the Delivery Option page, and under Alternate recipients, enter the Custom recipient name you just created above. Save it, and from this point forward, anything sent to this email address regardless if its from the inside or outside world, will automatically be forwarded to the aol acount, in this example.

There is even an check box option to either keep a copy of all emails forwarded in her inbox as well.

Hope this helps!

Richard

by Member 35711908

The solution above is the best way to do this, as long as the user doesn't need to turn it on and off too frequently, since it can only be accessed from Exchange Admin, and therefore you have to be the one to do it, not the end user.

One other note: After you've followed all the steps above, you can go back into the properties of the custom recipient which you created and on the Advanced tab, choose to hide it from the Address Book so that no one else can send email to it.

by billc124

This is kind of a crazy idea, but it will probably work for you. I think that you can forward external mail to an internal address. If you forward the external mail back to the users internal account, then it will forward to the external account. You sort of have a looping situation and this will use more resources, but it is an easy fix if you are just looking for a workaround. Otherwise, I think the first solution will work as well.

by tony.colgrove

Althought the Rules Wizard and Out-of-Office Assistant work well, the most reliable solution is the Custom Recepient route, and as #2 stated make sure to go back and hide the CR from the address book, so your internal users dont her email twice (internal and the AOL account).

by kees.valkenswaard

Currently I have no connection to the combination Outlook 97 and Exchange Server. So I have to work from the top of my head. As far as I know it is possible in Tools, Options, Internet-e-mail, to set the time that the system should check for new mail. I think to remember that at the same moment also the outbox is emptied.
The server is a push system for new e-mail. By checking this box you have an additional push-pull system.
I have no experience with AOL. So I don?t know if this would give any additional problems.
Let us hear if this works.
Next week I may be at a site where they have such a configuration. So I could check this and other possibilities.
Good luck.

by cmoss

Richard & Kathryn are exactly correct in their responses. You had the right idea, but used the client side instead of the server side. Users may be confused by the custom recipient having the same name as the one they should be addressing in the GAL. I recommend naming the account with zzJane Doe or something of that nature to avoid confusion. Additionally, if you are interested in making the rules themselves work, it is helpful to know that in some cases your SERVER may also be confused bythe similar name and not forward the requests, but rather resolve her name internally so the message would never make it out. For a clearer explanation of the IMC circumventing the MTA, seeQ259616 at
http://support.microsoft.com/support/kb/articles/Q259/6/16.ASP

Hope this is helpful,
Chenoa Moss

by mark phelan

One thing i dont see mentioned here is outlook web.

A much simpler way of sorting the issue, with several side benefits.

Firstly you retain all company sensitive information, within company systems, Also you are reducing the number of times a mail message is bounced about, so reducing the number fo times it can be intercepted.

by greg

I agree, answers 1-6 are the way to go if you have occasionally have a user going away... don't know about no.7... but if you want the client to be able to sort the problem him/herself - always good news for a sys admin - (and as far as no.8 goes), it's always good practice to use windowsupdate.com to apply updates and security fixes to microsoft systems - it might just be that you're suffering from a bug (feature!) ala no.7.
What version of IE are you using? Later versions of IE (5.0 upwards I believe) improves your connection options for Outlook as well, so upgrading to IE5.5 (don't put 6.0 on essential machines as yet!) could give you more options along the lines of your original thinking.
just my pennies worth!

by jereg

I'll put in my 2 cents worth just as an alternative. I had the same situation at my company, and the fix was just to enable the outbound mail to the internet. While I tried to figure it out, I found a service on teh web, www.mail2web.com that et's my users access the pop server without having to forward mail to another account. It seems to make the users happy here.
Hope that helps.

by tonyd

What you need to do is create a custom recipient. And point that to AOL account. Then go in to the mailbox for the person who is on leave, and go to the tab for delivery option. Then go to alternate recipient the none option is checked by default. Change that you do this by clicking on bottom radio button then clicks on modify. That will bring you address book, select the new custom recipient you created. this will work do not check the deliver message to both because the mail box will getfull if you have limit set on mail boxes.
You could put the other change back the way they were. Those option are only for receipt created by SA.

by Member 35772270

Here is some food for thought. Why forward the mail?, there is no reason.

The mail belongs to the company and can be accessed and managed easily enough.

You said that you could forward internal messages so that means that you had a registeredserver with a register IP address.

The user has an AOL account, is the company going to reinburst the user for using ther personnel account?

If so then install the web access extentions for exchange and use web access. Then the user can access her mail by logging on through the internet using her normal passwords.

If she needs help on how to log on using web access I got written instructions that can guide her step by step.

Of course she will need some info from you such as the registered name of the server and your domain name.

by Former member

Get a book...since i know you won't rate this answer and time will expire it, I thought I'd just grab some points....Heh.

by nicholasp

Upgrade to Outlook 2000.
I woyld bet your problem goes away.

I used to have several problems with Outlook 97... thwy just dissapeared when I installed Outlook 2000.
Just be carefull when installing SP2, you may not want to installit!

by colemanp

I agree with Answer #14 -- do not apply sr2. The only easy way to completely get rid of is to format the computer.

by soekratis

I have to agree with No.7 & No.12
I have a similar situation where our users needs to access their mails when they are either on business trips or holidays. OWA is the way to go and best of all, it is easy to setup and not much config on the usersend. Let me know if you need some guide on how to setup OWA.

regards

by christotg

A couple of answers come to mind:

1. In the recipient properties, Delivery Options tap, set an Alternate Recipient and enable the Deliver messages to both button.
That is the simple way to do it.

2. Install Outlook Web Access and restrict access to the http protocol to that user only.

3. Set them up with IMAP or POP3 and set up their email client for it.

4. Replace the user with one who never leaves the office.

by paul

I don't see the use in forwarding the emails to the aol account. If she has an aol account on her computer at home, most likely she has outlook express. I think you should set up an imap account on her internet express at her house so she can access her mail that way. Outlook Express - tools - accounts and add mail. Make sure the imap protocol is enabled in your Exchange Server for the recipient.

by kblandford

I can say this. I am not sure if it helps. I have a similar set up in my Network. The 'Rules Wizard' in Outlook is what I used to foward external emails to an external source. It seems to be effective.

by cookie1967

Tclere, in order clear up the LAN connection for my e-mail client, I cleared the box for connection in my properties to stop that "disconnect when finished" and not use the "connect using..." dialog. Since my system uses a LAN for its internet use and external e-mail is used for retreival, Outlook still has functionality with e-mail and people can still retreive their mail through forwarding, etc. After reading other answers, the same functions using a consumer-based Outlook app can apply to your intranet/extranet with a little tweaking.

by mmouser

Most of these answers sound good. I'd go with the Exchange custom recp. route or upgrading your client.

by mikecaskey

Aside from the security work... OWA is the pimpest of all solutions. If you want to get a hold of your stuff, don't let the users administer thier accounts! Over time things get messy. If you want to go with the alternate recipient route (a good one... this just takes more of YOUR time) keep a list of users that are "out of office" at any given time and have them notify you when they need thier stuff forwarded and when they don't.

by shmaltz

I figured I'll also grab some point's, since I'm sure you are either not going to rate it or you will unacept every one. So why not take a chance.
By the way I have the answer, I know what the problem is if you are really reading all this, email meand we will make arrangements.

by tclere

Did not help me yet. Working outside of the forum to see if we can come up with an answer. If we find it, we will post it here and I will award the points.

by shmaltz

Rating History for TCLERE:

# Of Questions Asked 2
Questions With No Reponses 0
Questions Closed Due To Rating Inactivity 0
Answers Accepted 0% 0
Answers Rejected 23% 7
Answers Not Rated 77% 24

by donb

The custom recipient is the best way to go. Outlook Web Access is convenient for people who travel and can't use POP3, but it can be slow on dial-up and there are some security issues. If you set up POP3/SMTP, be sure to use the correct account name when setting up your Email client(Outlook, etc) for POP3. It should be: NT_DOMAIN\NT_USERNAME\EXCHANGE_ALIAS

by shmaltz

Here is what I'll do:
First what most answer's say you should add a custom recipient and add it in Exchange Server to deliver as an alternate recipient, is not good only as a workaround until you solve the problem, for a few reasons:
1. You want the user to use the company provided email when they come back, if you use custom recipient the user doesn?t have to use the company's email.
2. You don't want every user to call you up every time they want to leave for a few week's.

Now to start trouble shooting the problem I would enable the diagnostic logging on the IMS in the exchange server to maximum, and look at the event viewer to see what happens.

Also, what about the other Out Of Office assistant option's (like auto reply message to the sender), do they work or not?

Install the latest service packs (SP4), in older versions of Exchange this was a problem it was corrected in one of the service pack's (I don't remember which one). I might be wrong and this is not going to help, but this is what I meant by saying I know the problem.

by tclere

I have been looking for a solution rather than a workaround. I am relaying this problem to someone else, so I appologize for my delay in feedback.

by troubleshootergurl

I have a suggestion, close this question and just give me the 7000 points because I am very cute.

This really doesn't have to be difficult.

Ha-ha.

by tclere

That's what we were saying! This should be as simple as changing a couple of settings.

by nicholasp

I see you said that Outlook 2000 is not an option.

It is free if you are running Exchange, so its not a cost issue.

It is worth the trouble to install Outlook 2000

by brasslet

Here's a couple of possible solutions:

Check out Knowledge Base article Q174045 (http://support.microsoft.com/support/kb/articles/Q174/0/45), which details the use of a tool called CleanSweep. It's useful for cleaning up rules created by the Out of Office Assistant that are somehow 'broken'.

Another suggestion that will work is to forget using the Out of Office Assistant for this. Instead, deliver mail to an alternate recipient. First, create a custom recipient for the user's external mail address. Then open the user's mailbox properties and click on the Delivery Options tab. Toward the bottom of the screen, click on the MOdify... button and select the custom recipient you've just created for the user's external e-mail. Click on OK and if you desire, you can check the box to deliver the mail to both locations. Now click on OK again and any mail that is delivered to the users' mailbox will be rerouted to the custom receipient. You can hide the custom receipient from the Global Address list and it will continue to work. This is how we forward mail in our organization and it's always worked well.

by brasslet

Have you tried using CleanSweep? IMO, this problem has nothing to do with your Outlook client's settings. I think the rule created by OOA are simply broken (I have seen problems like this before with rules) and CleanSweep is likely to correct this. OOA does create rules that determine things like how mail is forwarded, etc. but most of the other settings (such connect/disconnect etc.) have no bearing on these things.

by techdictator

Well, by now it looks like you're just yanking everyone's chain. I've seen several good response that will work just fine. I don't think you can get anymore help here if you're rejecting them all.

by tclere

Again, we are not looking for a workaround. The software is capable of performing the task, but we are missing something in the configuration. There are still a couple of suggestions that we have not tested yet:

nicholasP: Didn't know Outlook 2K was free. That may change the upgrade decision.

brasslet: We can not look into this until next week. We'll let you know.

newyorker211: We'll get back to you on your suggestions.

by bytemi

What I did when someone from my Office had to have bypass surgery, was I created and internet account in Exchange going to his AOL account. Then in exchange, I went to his account properties and on the Delivery Options tab, Under Alternate recipient, deselected the none button and click on modify and added the internet account that I had just created. I hope this works for you.

by juan363

We had the same issue with my boss and his laptop that he uses at home. He wanted to access his account from home, but we got rid of Exchange server, because it is CRAP. We just set up RAS and he is able to connect to his account with exactly the same settings and without the security issue. That is something to think about.

by kralljd

Have you tried setting diagnostic logging in the IMC and watched the event log to see what is happening?

Are there any NDRs being generated?

by philando

Ok.
I just test this senario and it works. Here's my config.
Client is win95 with office 97 pro and outlook 97 installed ( I checked add/remove programs). Outlook ver. is (8.03.4629). There are no service release installed for outlook specificallynor for the office suite.
Server is exchange 5.5 sp4 running on Nt4 sp6.

I setup an out of office on the client with a simple rule forwarding all incoming mail to two separate internet email address. I did not define any of these on exchange server.
Here's the result:
> Sent: Monday, July 30, 2001 7:52:38 PM
> To: Koppel, Ted
> Subject: ted outside test 1
> Auto forwarded by a Rule
>
ted outside test 1

Thats the actual forwarded message to my yahoo account. I received both theautoreply and the forwarded message.
I dont know what exactly is the problem with your config, but make sure ex server is at the latest service pack. Try getting your config as close to mine as possible. You might also try installing the rules wizard for outlook 97 on the client.
I think its a combination of the server's service pack level and the version of outlook 97. Either way good luck;I know whats its like to plagued by a problem like this. Let me know how it turns out.

by john

If OOA gets Exchange to forward some mail then exchange is working and, as far as I can see, so is Outlook. In any case, once OOA is set up, Exchange doesn't really care whether Outlook is on or not. The question is: when you set up the OOA, which mail did you tell it to forward and how?

by tclere

The internal e-mail is forwarded properly. It is the external (incoming) mail that does not get forwarded.

by tclere

Feedback as of 7/31/01:

Again, I am fielding this problem for someone else. Here are his comments:

Everybody seems to be coming up with the same few ideas. I have already tried everything that anybody has suggested plus a few that I thought up on my own. I would continue to state that not only has no solution been posted, but that none of the work arounds have worked either.

Without any concrete facts, I believe that the root of the problem is a conflict between two Outlook agents that might not typically be installed simultaneously. We are using the Outlook Exchange agent to send/retrieve internal mail and the Outlook Internet Email agent to send/retrieve external email. I believe that the conflict centers around the fact that the external email is retrieved via the Internet Email agent and the Out of Office Assistant attempts the reply through the Exchange agent by default. Our Exchange server has no ability to send to the outside world and therefore it errors. It simply doesn?t attempt the Internet email route. Without a masters in Exchange/Outlook, nor the time to thoroughly investigate, I simply don?t know.

by ice-tech

I can't give you a solution but I had a thought. . .

I read through your post a few times to make sure you didn't touch on this. Will externally generated email forward internally at all? Maybe it has something to do with externally generated email specifically. You mentioned internally generated mail forwarding.

Perhaps also you could do a search for the registry hack that would, at the registry level (of course), force those two settings you mentioned: ?Disable Out of Office responses to the Internet? and ?Disable Automatic Replies to the Internet?.

by tclere

Yes, external e-mail is forwarded as long as the client's machine is on and Outlook is running. When they are gone, Exchange should forward the mail, but it doesn't.

by jlo63

It may not be an Exchange problem at all. Do you have a firewall? Check with them to see if they are blocking POP3 email. Many companies prevent send and/or receive of POP3 email since it is a common way for unwitting users to introduce viruses inside a company. Hotmail, AOl etc popular sites and their emails are targeted.

by timmycb

I suggest the following: run CleanSweep on the user's account to make sure rule processing abilities are functional. Create a simple rule that does what you want. Double-check that your Exchange setting for "Auto replies to Internet" is indeed enabled, stop and restart the service. Talk to your security group about your firewall - I'll bet that is what is blocking your mail.

by john

I have just re-read the stuff at the top and now I understand!

The Out Of Office Assistant in the client simply tells the Server what to do with mail addressed to that recipient. Because the server doesn't know or care about the Internet Email configuration of the clients, it can only send email out to the internet through the Internet Email Connector so it is not possible to getthat configuration to work.

Incidentally, why isnt the server configured to handle internet email? Isn't it rather like having a dog and barking yourself?

by bradheld

Would a dial-up account for the user into the network be a viable solution? If that users dials in then the exchange server would be local to the user. Remote Access is fairly easy to set up.

by estebandelatorre

What i think you need to do, is create a custom recipient. Point it to the AOL account. Then go in to the mailbox for the person who is on leave, and go to the tab for the delivery option. Then go to alternate recipient the none option is checked bydefault. Change that you do this by clicking on bottom radio button then clicks on modify. That will bring you address book, select the new custom recipient you created. this will work do not check the deliver message to both because the mail box will get full if you have limit set on mail boxes.

Good luck

by genesiswave

Create the custom recipient as recommended. Use that as the forward for the Out of Office Assistant - Being a good administrator for Exchange you probably have disabled forwarding - this essentially what the OOA is attempting to do, I have had the same issue and this is the best result that I have found, unless of course you want to turn relaying back on

by hthoden

This is done to prevent SPAM and Unauthorized Mail Relaying Both of these are an increasingly severe problem.

*****Exchange 5.5 SP1 - It adds an interface for configuring ALLOWED relays and other anti-spam measures. See the release notes for configuration instruction.******

Blocking SPAM is pretty tough, though Outlook 98 adds a rather efficient rules engine to handle a good bit of the mail (it's cutting out about 75% of our junk mail). You can also block inbound mail from particularly nefarious IP addresses. The problem with this is that most of you have secondary MX records (you really should too). When you block delivery from a particular IP address, it will fall back to your secondary MX and deliver it there. The secondary host will then, with full acceptability, deliver the message to you. You could remove the secondary MX, but this would create other reliability problems. You could also have your ISP block the same list of IP's - though they may be unwilling to maintain this list for you as a special case.

Blocking relaying is a bit easier.

Exchange 4.0 - will not relay mail unless the BOResKit IMCEXT.DLL is installed. Solution - do not install it.

Exchange 5.0 - will relay mail with IMS/Routing enabled. Solution - disable it. As long as you don't have POP clients this shouldn't be a problem.

Exchange 5.5 - There is a ton of new stuff including the ability to build accept/reject lists of IP addresses. So, you can Accept relays just from your internal IP networks. It is still registry config, but documented pretty well in the 5.5 release notes. Exchange 5.5 also includes new features to require clients to be authenticated before they can relay mail.

Exchange 5.5 SP1 - It adds an interface for configuring allowed relays and other anti-spam measures. See the release notes for configuration instruction.

by turambar386

Hey tclere. Correct me if I have got this wrong, but here is how I see the situation:

-Client running Outlook 97 with Exchange and Internet Mail wants to forward email to an external email address
-When client is running, this works fine, because the client takes care of the fowarding.
-When client is not running, this does not work, because the Exchange server is trying to do the forwarding and cannot.

As you and your friend are guessing, this is an Exchange Server issue. The Exchange Server is trying to forward the email externally, but as your friend says, the server "has no ability to send to the outside world and therefore it errors".

Obviously, the client is configured to use an external SMTP server to send Internet email, rather than going through the Exchange server. As someone said, this is kind of silly.

Unless I am mistaken, you must have the Internet Mail Service set up on every client system in order to send (and possibly to recieve!) external email withthis configuration. This is just simply a tedious set up which is a total waste of the features of your Exchange Server!

Anyway, to sum things up, I do not see any way to get this to work without allowing your Exchange Server outgoing SMTP access to the Internet. So.. Do it! Or let us know why you cannot.

by mike (from canada)

Delete all software involved then re-install it. check to see that your ISP can handle this. If it cant then switch ISPs. Be sure you have a fast enough modem and computer too. If all that fails, then I assume your computer is messed up.

by tclere

As others have mentioned, it is a problem with our system configuration.

by jb007

This may be a little long winded but here it goes..

Your problem intrigued me so I did a little digging.

In the end I did the following to get this working:

I created a win95 standard build machine in VMware with full access to my corporatelan.

I created two test mailboxes on exchange 5.5 (sp3) test1 and test2.

I created two external email address one at hotmail and one at zipmail.

I installed outlook 97 sr2 standard build and connected it to test1 mailbox on exchange server.

I created a server based rule within the inbox assistant thus:

a) Tools, Inbox Assistant, Add Rule
b) Tick forward box then add address in the TO box (in my case 3 addresses 1 internal 2 external)
c) Drop down option in Method section to LEAVE MESSAGE INTACT
d) Press ok and a message will appear that says.. "This rule will fire for all incoming messages. Is this what you want?"
e) Press Yes and the rule will be pushed up to the exchange server as a SERVER-BASED Rule.

At this stage I sent myself a few test messages and they all got through. Including from external parties back in.

Peripheral changes included:

IMS settings disabled for:

Disable Out Of Office responses to the Internet

Disable Automatic Replies to the Internet

I think thats about it.

If you have any questions at all I'd be happy to answer them regarding the build.

Otherwise it was fun and it only took 5 hours *laughs*

thanks,

jb

by tclere

We appologize for leaving this thread open for so long. We, with the help of everyone here, have determined that this is a system configuration problem on our end. Unfortunately, we are in the middle of installing an additional server, so we do not have the time to solve this problem. We would like to keep this open so that we can distribute the points.

Thanks to everyone for all of your help.

by estebandelatorre

Why don't consider a client upgrade to Outlook 2000, have WNT SP 6a and Exchange SP 4. It should work!
The server is a push system for new e-mail. By checking this box you have an additional push-pull system.
Double check (firewall's filter) if the "server itself" is able to deliver messages not the client...
I have no experience with AOL. So I don?t know if this would give any additional problems.
Let us hear if this works.
Next week I may be at a site where they have such a configuration. So I could check this and other possibilities.
Good luck

by billc124

I think you just answered your own question with that last post. If the Exchange server was setup for SMTP instead of using the agent, your problem would be solved. I think the way you are configured currently is going to prevent this from happening. I don't think there is an answer to this question other than to upgrade or change to SMTP instead of that agent.

by tclere

I believe that you are correct. Until we finally fix this problem, we would like to keep this post open so we can distribute the points to those that have helped us out.

Thanks to all!

by juanita marquez

From the User's PC with the User logged into the network, open Outlook and select Tools - Services. Click on the Delivery tab and change the setting from Personal Folder to the other Mailbox setting (in our case, the person's name.) Click on OK. Don't forget to reverse this when the person returns.

Go to Contacts and create a new Contact for the person with the User's internet address in the window beside E-mail. Put the person's name in Company and File As windows. Save and close.

Click on Inbox. Go to Tools - Out of Office Assistant. Put a dot beside I am currently out of the office. Add a message for display. Click on Add Rule. In the Sent to box, browse to the User's internal email ID on your global list and Add it.

Put a check beside Forward and in the Forward "To" box, browse to the Contact you created for the User with their forwarding address and put that in so it will forward to that Contact. Click OKs to exit.

We called MS about this very problem and the answer is kind of convoluted, but it works for us. Hope it helps.

by joseph moore

Part 1
Ok. Your users use Outook97 and have 2 connections to the Exchange server. One connection is an ?Internet E-mail? type, using POP3 for mail retrieval, and SMTP for outbound e-mail. They also have a ?Corporate Workgroup? connection, using LDAP to connect to the mail server for all internal originated and destinated e-mail.
When an internal user (InternalUserA) sends a e-mail to another internal user (InternalUserB), here is how it works. UserA pushes Send; e-mail is sent via LDAP to theExchange server. Exchange checks the Recipients container(s) for a match of all destination e-mails first. Technically, the Alias column in the mailboxes is what is checked for a match against the destination address. Eventhough UserB made the mail out to InternalUserA, that name resolves to an alias (IntUsrA, for example). When a match is found, the mail is delivered to the Inbox for that mailbox.
The IMS connection is not used at all. Also, no DNS resolution of domain names is done.
It all stays internal.

by joseph moore

Part 2
For the external destination e-mail (ExternalUser@externaldomain.com, for example), the same steps apply. It doesn?t matter if the mail originator was internal or external. The Recipients container(s) is/are checked for a match. When there is none, the mail is sent to the IMS connector for outbound delivery. The server does a DNS query to find out what the IP address the MX records for externaldomain.com possess. It gets this, and sends it out over SMTP port 25 to its default gateway. The routers take it from there.
So, yes, the fact that your users had 2 mail profiles, 1 Internet POP3/SMTP based, and the other LDAP corporate/workgroup based, explains why the server-based out of office mail forwarding did not work. The externally-originated e-mail would come into their mailboxes, but your mail server did not do anything with them, since it was config?d to hold the mail until the POP3 connection was made. Therefore, the out of office server rule would not see the mail.
It would only work when LDAP is used.
I don?t think you can assign a server role like this for a SMTP connection.
So, reconfigure your mail server to treat all mail as the corporate/workgroup method. Have your Exchange server clients only use LDAP as their connection method.
Good luck.

by icrovop

This may be hard to believe, but you cannot do what you want with your current configuration. In a nutshell you can not automatically forward email while using the internet email service if the client is turned off. Internet email may be running onthe Outlook client, but is not a part of the Exchange server and as such the Exchange server cannot process a rule it knows nothing about. There are 2 kinds of rules. Server based and Client based. You are running two separate services (exchange and internet email.) This means that you have 2 rules running when using the out of office assistant. The server rule takes care of anything relating to Exchange and the client rules take care of everything else (Internet email, MS Mail, Lotus Notes, etc.) Think of it another way. You say that your exchange server cannot send or retrieve external emails. This means that the exchange server can not retrieve the external email for your user. Only the outlook client is setup to do that. Even if you could get the external email, how is the email going to be sent back out to the outside world? Your exchange server is not setup to do that. The only way to resolve your issue is to allow the Exchange server to process all incoming and outgoing external emails or leave the client computer on. Hope this helps you stop looking for a solution to a problem that cannot be solved with your existing configuration.

by icrovop

I have several clients using VPN and TS.

1: Most of the users are internal users who need access from home or on the road. They use both their own PC's and company owned PC's.
2: All of the users are required to use and maintain anti-virus software on their computers. All of the servers and or PC's that they connect to have enterprise Anti-virus software installed. Maintaining your anti-virus software at your servers is the key to good protection.
3: They have either been installed at the office or they have been given the software and detailed instructions on how to install it. However most users that try and do it themselves need phone support to install it properly.
4: I have used both TS and PCanywhere in VPN situations. PCanywhere requires a PC for each user coming in. Pcanywhere was used because software they are using is not compatible with TS.
5: Compaq has a good white-paper to determine hardware requirements. http://www.compaq.com/support/techpubs/whitepapers/207a0996.html. Citrix claims that a Terminal Services connection uses 11K of bandwidth per user.
6: Yes I have, but it was decided that there were to many downsides to using it. Security being the main issue. A Web-server is difficult to lock down and keep locked down, due to bugs and holes. However, using a web-browser is the more economical way to go, because of Licensing requirements. Web-based TS's reliabilty can leave alot to be desired. Especially on disconnect.

see below for continuation...