Out of office, Exchange 2000, third party connector

Out of Office to the Internet is disabled by default.
You need to enable it.

ESM, Global Settings, Internet Message Formats. Right click on the default and choose Properties. Click on the tab Advanced and enable the option "Allow Out of Office Responses". Apply/OK out.

Simon.

I already enabled that part and still no go...

Are the messages actually being created?

You will need to enable message tracking to see.
http://www.amset.info/exchange/message-tracking.asp

It isn't unusual for OOTO messages to be swallowed by antivirus and antispam tools, but you have no way of knowing until you can confirm that the messages are being generated.

How does the POP3 connector put the messages in to the mailboxes? Does it use the usual method of dropping the messages in to the pickup folder of the SMTP virtual server?

Simon.

It seems to me that it's not generated at all.

Did message tracking, and it shows the message received AND it ships out an notice of reception. That all shows up in log. But still no OOTO

The POP connector seems to drop the messages in the SMPT folder and waits to be picked up. That what it seems to says in tracking.

I use IgetMail, 3rd party software.

If the OOTO is being generated, does it show it being delivered to an external host? Message tracking should show the delivery and the SMTP banner of the machine it was delivered to.

Simon.

No, like I said, it doesn't show the OOTO and seems not to be generated at all.

If I log on with OWA and open the message, it does send and show a notice of reception thow. But no OOTO generated nor sent.

I misunderstood what you wrote.
In that case, I would have to presume that the POP3 connector is delivering the email in such a way that doesn't trigger the Out of Office message.

Simon.

That's what I think...

Nothing else to try? Another POP Connector maybe?

If you are on any kind of permanent internet connection then dump POP3 connectors totally. I don't deploy POP3 connectors unless the client is on a dial up connection and there are no alternatives.

Simon.

I need the POP connector because some users use OWA from time to time. Since there session is not open on there workstation, their Outlook can't get the mail from external mail server...

And uninstalling the connector wouldn't solve my OOTO probleme anyway.

Maybe the only solution is to switch to SBS2003 but I would limite myself to 1 domaine on local network. And switching to Win2003 serveur AND Exchange 200x seems to be quit expensive for just an OOTO.

Just can't beleive their's no solution for this! it's a very frustrating bug... :(

If you switch your email to SMTP delivery, then email comes straight in to Exchange. You would drop the POP3 accounts at the ISP, webhost or whoever.
If you have users accessing email via OWA then you must have some kind of permanent connection to the Internet.

POP3 connectors are a fudge - because Exchange is not a POP3 client. Therefore there are always compromises to get them to work.
If you want the full feature set, then use exchange as it was designed - an SMTP server with email delivered directly.

Simon.

You're write.

We should use Exchange as it was designed. Administration always want to save some $ and IT's are stuck with the probreme often.

From Administration point of view, using exernal hosting uses less IT resources and since the ISP allready have a top grate Antivirus and junkmail slash... It's also a little less problematic with spam and hackers.

It's all a question of $

Speak to the ISP and see if they will provide a scanned SMTP or ETRN feed. That will give you the best of both worlds.

Simon.

I just fund the answer myself,

with IGetMail, you must use the Group account instead of the individuel account for the OOTO to work.

individuel account will send OOTO to postmaster@domaine.com and group account will send it to original sender.