In <5B0D267B3C47D1119326080009DE9BA601CF8A@SEQUOYAH> [log in to unmask] writes:

> In MS Exchange there is a setting in the Internet Mail Connector to
> disable out-of-office responses to the internet. Other than that, I
> don't know of a way using Outlook, to disable these responses.

> > A lot of us use Micro$oft Outlook at our offices, and we are mandated
> > by
> > policy to set our out-of-office notification when we are gone.  I do
> > not
> > know of a way to selectively send out-of-office notifications in
> > Outlook, so if anyone does know of a way, please let me (and others)
> > know.

Just another FYI for those struggling with Outlook; some other bugs you
should be aware of:

Most Outlook clients gag and are unable to send mail through any SMTP server
with a multiline initial (220) response sequence. I *think* the latest Outlook
98 fixed this, but earlier releases definitely are unable to send mail at all
if pointed to such a system. (*1)

All current and past Outlook releases gag if using an SMTP server that
actually adheres to the mail standards and dares to check recipient addresses.
Earlier releases die when trying to send mail, citing a network problem. The
latest Outlook 98 echoes the SMTP error dialogue back to the Outlook user,
which usually doesn't help much - i.e. "550 Nobody by that name here" when it
doesn't even report WHICH recipient it was that was invalid. If there was more
than one recipient, the user can't tell which one caused the problem. In the
latest Outlook 98, it does at least go ahead and deliver the message to the
other (valid) recipients (if any); previous releases just gave up and didn't
attempt to deliver the message at all. (*2)

All of the above were reported to MS. *2 is still an issue, and a severe one
if you're not using a broken mail server (like Exchange, which is braindead
when it accepts recipients; it accepts anything and tries to issues non-deliv-
ery notices later if the recipient was invalid. This makes it horribly
vulnerable to spam-relay attacks, which 90% of the time have bogus return
addresses...leaving the relay host to try in vain to deliver thousands of
bogus non-delivery messages). Both *1 and *2 are violations of the RFCs
(standards governing SMTP mail transport), though we've gotten no response at
all to our reports to Microsoft. Last I checked the bugs weren't even showing
up in their knowledge base...

Lookout! it's Outlook! ;-)

Personally, I'd recommend Eudora or Pegasus mail. Eudora users can even change
their own mailbox passwords on the mail server from the clients. :-)

                  -Chris Bartram