On 2009-01-04 02:02:21, Diane Poremsky [MVP] wrote:

A. Are you selecting the pop account as the sending acct? Unless you
choose it at the time you compose the message, it will go out through
the default acct, which is usually the exchange acct. Replies and
forwards should use the acct that the message arrived on.

My default sending account is one of my own POP accounts. I know that if
I don't change this, that's what it is.

When I wrote "A) it doesn't seem to be possible to prevent the Exchange
account from delivering email", I meant that I don't want the Exchange
account to deliver emails it receives into my Inbox.


B. Rules work just fine on exchange acct.

They don't, at least not in my case, which is an Exchange account with a
delivery location that is my local .pst file. That's just a simple fact.
The rules work on all other accounts, including when receiving emails
through the Exchange POP account, but not on the emails that are placed
into my Inbox through the Exchange account (direct, no POP).

The same rules work on these messages if I run them manually on the
Inbox after the messages have been placed there. It looks as if the
rules don't get triggered when receiving emails through an Exchange
account into a .pst file as default delivery location.

(Maybe this is related to the fact that it is not possible to select a
delivery folder for the Exchange account? All POP accounts allow the
selection of an arbitrary delivery folder in the .pst file, but the
Exchange account is hardcoded to the Inbox folder in the default
delivery location.)

It's possible the slow connection is causing a problem as rules don't
run until the message is downloaded in full.

I don't think this is the case. The messages may have been in my Inbox
for hours or days. I may have closed and re-opened Outlook in the
meantime. But they always are being filtered the moment I run the rules
manually.

The connection speed is likely the cause of the slow update.

Yes, I know. I have a latency of 300 ms to 500 ms. The question is what
it is updating. All my rules are "client-only". There must be a lot
going on, even though I don't have a single rule for the Exchange server
-- it is possible to transfer megabytes over that VPN conniction in
those 20 seconds it takes to update the information that I still don't
have any filters for Exchange.

Gerhard

"Gerhard Fiedler" wrote in message
...

(Maybe this is related to the fact that it is not possible to select a
delivery folder for the Exchange account? All POP accounts allow the
selection of an arbitrary delivery folder in the .pst file, but the
Exchange account is hardcoded to the Inbox folder in the default
delivery location.)

I believe this is a true statement. I don't know of any way for you to
prevent Outlook's delivery of the Exchange Inbox to the delivery location
Inbox. Did you try altering the send/receive group to exclude the Exchange
account?

I'm still of the opinion that if you don't want to mix personal and private
data that you should employ separate mail profiles.
--
Brian Tillman [MVP-Outlook]

On 2009-01-05 12:03:25, Brian Tillman [MVP - Outlook] wrote:

(Maybe this is related to the fact that it is not possible to select
a delivery folder for the Exchange account? All POP accounts allow
the selection of an arbitrary delivery folder in the .pst file, but
the Exchange account is hardcoded to the Inbox folder in the default
delivery location.)

I believe this is a true statement. I don't know of any way for you
to prevent Outlook's delivery of the Exchange Inbox to the delivery
location Inbox. Did you try altering the send/receive group to
exclude the Exchange account?

Yes, I did. There are two entries that seem to be related to the
Exchange server account: one for the Exchange account and one for
"Remote Mail". I had both disabled. The effect was that email was still
delivered into my Inbox through the Exchange account, but if I replied
to it, it wasn't sent and just stayed in the Outbox.

Currently I have the Exchange account enabled, but only the send
function. I still get the emails through the Exchange account,
client-only filters still don't work on them when they arrive (but work
on them when I run them manually after they are in my Inbox), but at
least if I reply to an email that came in through the Exchange account,
it goes out

Next thing I'll try is working with filters on the server and see
whether I can do anything there. Maybe filter the emails out of the
Inbox at the server before it puts them into my local Inbox...

I'm still of the opinion that if you don't want to mix personal and
private data that you should employ separate mail profiles.

The problem with this is that with separate profiles I only have access
to one of them at any time. I need concurrent access. (Another option
would be to run a second instance of Outlook on a second computer. But
that's both inconvenient and expensive.)

BTW, did you know that the guys connected to the Exchange server see the
appointments that are in my local .pst file -- not the contents, but
their existence (including start/stop times)? That's quite unexpected.

What do people do who need to connect to two Exchange servers (say their
own and the one of a client)? The way this is a mess, it seems to be the
perfect argument for me to never get an Exchange server for my own use.

Gerhard

1. Exchange is not controlled by the s/r settings -it's a push acct and s/r
settings are pull.
2. If you are publishing free/busy to the server, anyone using the same
free/busy server will see your free/busy info.
3. People who need to access 2 exchange servers use OWA or IMAP for the
second server - the choice depends on whether or not more than email access
is required. Or they use 2 outlook profiles. It's also possible to use fast
user switching to open 2 outlooks.

--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Gerhard Fiedler" wrote in message
...
On 2009-01-05 12:03:25, Brian Tillman [MVP - Outlook] wrote:

(Maybe this is related to the fact that it is not possible to select
a delivery folder for the Exchange account? All POP accounts allow
the selection of an arbitrary delivery folder in the .pst file, but
the Exchange account is hardcoded to the Inbox folder in the default
delivery location.)

I believe this is a true statement. I don't know of any way for you
to prevent Outlook's delivery of the Exchange Inbox to the delivery
location Inbox. Did you try altering the send/receive group to
exclude the Exchange account?

Yes, I did. There are two entries that seem to be related to the
Exchange server account: one for the Exchange account and one for
"Remote Mail". I had both disabled. The effect was that email was still
delivered into my Inbox through the Exchange account, but if I replied
to it, it wasn't sent and just stayed in the Outbox.

Currently I have the Exchange account enabled, but only the send
function. I still get the emails through the Exchange account,
client-only filters still don't work on them when they arrive (but work
on them when I run them manually after they are in my Inbox), but at
least if I reply to an email that came in through the Exchange account,
it goes out

Next thing I'll try is working with filters on the server and see
whether I can do anything there. Maybe filter the emails out of the
Inbox at the server before it puts them into my local Inbox...

I'm still of the opinion that if you don't want to mix personal and
private data that you should employ separate mail profiles.

The problem with this is that with separate profiles I only have access
to one of them at any time. I need concurrent access. (Another option
would be to run a second instance of Outlook on a second computer. But
that's both inconvenient and expensive.)

BTW, did you know that the guys connected to the Exchange server see the
appointments that are in my local .pst file -- not the contents, but
their existence (including start/stop times)? That's quite unexpected.

What do people do who need to connect to two Exchange servers (say their
own and the one of a client)? The way this is a mess, it seems to be the
perfect argument for me to never get an Exchange server for my own use.

Gerhard

On 2009-01-06 02:08:56, Diane Poremsky [MVP] wrote:

1. Exchange is not controlled by the s/r settings -it's a push acct and s/r
settings are pull.

Yes, that's what it looks like. This leads to two questions:

1.1 What is the functionality of the configuration item for the Exchange
account in the s/r settings? The "Send mail items" checkbox seems to
prevent sending emails through the Exchange account (if it is not
checked, the emails sent through this account just stay in my Outbox
forever), but the "Receive mail items" checkbox doesn't seem to do
anything (emails are placed into my Inbox by the Exchange server,
whether this is checked or not).

1.2 Is there a way (undocumented setting, client or server, etc.) to
avoid the Exchange server's push activity?


2. If you are publishing free/busy to the server, anyone using the same
free/busy server will see your free/busy info.

I don't remember enabling the publication of free/busy information. This
seems to be a consequence of adding the Exchange server account and
setting the delivery location to my local .pst file. How/where is the
publication of free/busy info controlled?


3. People who need to access 2 exchange servers use OWA or IMAP for
the second server - the choice depends on whether or not more than
email access is required.

The only reason I have added the Exchange server to my accounts is so
that I have access to the calendars of shared resources. This is the
only thing that I need that wasn't available when using POP access only.
Is there a way to make this work with OWA or IMAP? It seems that OWA (at
least in the version they use) doesn't allow me to see any calendars
besides my own.

Or they use 2 outlook profiles. It's also possible to use fast user
switching to open 2 outlooks.

Yes, that may be another option. Rather a pain, though... would I hear
audio from notifications from the instance that is in the currently not
active Windows user?

Thanks,
Gerhard

I was running a pop email account fine. I added an exchange account. The
pop account or pst account quit recieving mail as soon as the .ost account
was active.

I tested the pop or .pst account and it sent a test email fine, why isn't it
receiving emails? Where can I look to make adjustments.

"Brian Tillman [MVP - Outlook]" wrote:

"Gerhard Fiedler" wrote in message
...

(Maybe this is related to the fact that it is not possible to select a
delivery folder for the Exchange account? All POP accounts allow the
selection of an arbitrary delivery folder in the .pst file, but the
Exchange account is hardcoded to the Inbox folder in the default
delivery location.)

I believe this is a true statement. I don't know of any way for you to
prevent Outlook's delivery of the Exchange Inbox to the delivery location
Inbox. Did you try altering the send/receive group to exclude the Exchange
account?

I'm still of the opinion that if you don't want to mix personal and private
data that you should employ separate mail profiles.
--
Brian Tillman [MVP-Outlook]

brainstewn wrote:

I was running a pop email account fine. I added an exchange account.
The pop account or pst account quit recieving mail as soon as the
.ost account was active.

I tested the pop or .pst account and it sent a test email fine, why
isn't it receiving emails? Where can I look to make adjustments.

Maybe check your send/receive groups and make sure the POP account is
still enabled. Also verify where your default delivery location is, and
look for your emails there I'm not sure, but probably the default
delivery location after adding an Exchange account is the Exchange
account Inbox -- which means that your POP emails also go there.

Gerhard