Client-Only rule stops working

I have a machine that I dual boot between XP Pro and Vista Ultimate. I have
Office 2007 installed on both and I connect to the same Exchange 2003 server.

On my XP box, I created a rule that when new mail arrives through my Comcast
account, it moves it to a Comcast folder in my mailbox. It works great. So,
I created the same rule on my Vista box.

When I reboot from one OS to the other, the rule stops working. I have to
delete the rule and recreate it. It doesn't to matter which way I go. Is
there a way to prevent this failure?

Andy Siegel wrote:

I have a machine that I dual boot between XP Pro and Vista Ultimate.
I have Office 2007 installed on both and I connect to the same
Exchange 2003 server.

On my XP box, I created a rule that when new mail arrives through my
Comcast account, it moves it to a Comcast folder in my mailbox. It
works great. So, I created the same rule on my Vista box.

When I reboot from one OS to the other, the rule stops working. I
have to delete the rule and recreate it. It doesn't to matter which
way I go. Is there a way to prevent this failure?

Rules appear to contain more than just the conditions and actions you can
see. They also appear to contain information about the PC that created them
and that information you can't see. Is your PC named identically no matter
which OS you've booted? Is the Exchange mailbox your delivery location?
Are you accessing the Exchange server with an Exchange account and a VPN or
RPC over HTTP connection or are you accessing it with an IMAP or POP
account?

Since you use Outlook 2007, why not configure it to delivery the Comcast
messages directly to the secondary PST instead of using a rule?
--
Brian Tillman [MVP-Outlook]

The two "PC's" have different names and different IP addresses. Yes. The
mail is delivered into my Exchange mailbox. I have the POP account setup but
there's no pst for it. It all comes into my Exchange mailbox and the rule
should move it into the specified folder. I'm accessing exchange over the
network using Outlook 2007.

Something I never noticed before. In Account Settings, I can select my POP
account and at the bottom select where it's delivered. So, I selected the
desired folder and deleted my rule. So, I'm going to try that for a while.

"Brian Tillman" wrote:

Andy Siegel wrote:

I have a machine that I dual boot between XP Pro and Vista Ultimate.
I have Office 2007 installed on both and I connect to the same
Exchange 2003 server.

On my XP box, I created a rule that when new mail arrives through my
Comcast account, it moves it to a Comcast folder in my mailbox. It
works great. So, I created the same rule on my Vista box.

When I reboot from one OS to the other, the rule stops working. I
have to delete the rule and recreate it. It doesn't to matter which
way I go. Is there a way to prevent this failure?

Rules appear to contain more than just the conditions and actions you can
see. They also appear to contain information about the PC that created them
and that information you can't see. Is your PC named identically no matter
which OS you've booted? Is the Exchange mailbox your delivery location?
Are you accessing the Exchange server with an Exchange account and a VPN or
RPC over HTTP connection or are you accessing it with an IMAP or POP
account?

Since you use Outlook 2007, why not configure it to delivery the Comcast
messages directly to the secondary PST instead of using a rule?
--
Brian Tillman [MVP-Outlook]

Andy Siegel wrote:

The two "PC's" have different names and different IP addresses.

The PC's name seems to be a hidden part of the rule and that could very well
be why it wasn't running. Useing Outlook 2007's ability to have multiple
Inboxes is, I think, the better solution.
--
Brian Tillman [MVP-Outlook]