Again, it depends on whether or not the IMAP mail client sends the NOOP or
IDLE command and how the mail server is configured to deal with said
commands. For example, I used to run a mDaemon mail server it is a great
product in supporting IMAP mail clients. However its default configuration
is set where once the mail server receives the NOOP command from the mail
client, it forces the IMAP connection is forced closed in 1 minute. This is
contradiction of what the intention is for the NOOP command. The idea
behind NOOP is just that... mail client telling server, I have No Operation
(read changes) to do, but I want my connection to stay alive.
"redshift=0" <redshift=(E-Mail Removed)> wrote in message
news

D93FDFC-457F-4058-AF50-(E-Mail Removed)...
> If "nope" is the final answer, then this is a potentially flaw from my
> point
> of view.
>
> I've used Thunderbird for years and it doesn't have this problem. (Someone
> told me that even Outlook express doesn't have this problem either, but I
> haven't tested it.) When I'm trying to run Outlook, however, those
> messages
> pop up frequently and annoyingly stop other things from continuing until
> they're closed.
>
> I was looking forward to using Outlook in the Office 2007 suite to take
> advantage of the interoperability, but instead it has turned into playing
> "whack-a-mole"!
>
> "neo [mvp outlook]" wrote:
>
>> Nope.
>>
>