Like some others, I ran into problems where MANUALLY applying message
rules didn't seem to work. After playing around with various
combinations for the last couple of hours, I've identified a BUG in my
version of WLM.
I'll describe the bug below.
Bob if you can confirm if this bug explains your problem, that would
Winston, if you can check the rules you tested to see if you see the
problem or not, that would help as well.
The Bug applies to rule criteria Where From Contains 'X'.
A From header can be of two forms:
1) From: Name <e-mail address>
2) From: e-mail address
When Manually applied, the rule does NOT check the e-mail address in
form #1 within the <:>.
It will match the e-mail address in form #2. And it will match if
checking for Name.
The rule works perfectly when automatically applied to incoming POP3
message. It will match on the e-mail address in the <>.
The bug just appears to be with the From header. Testing on the To
header when Manually applying rules works fine.
Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm
"...winston" <winstonmvp@xxxxxx> wrote in message
> Hello Bob,
> Which folder is the destination for the messages to be moved.
> - subfolder in the Pop3 account
> - subfolder in a user created folder in the Storage folders.
> I've created a rule to move a message(your scenario - moved from a
> Hotmail inbox to a pop3 account's Inbox) to each of the above
> locations with success.
> Note: When applying the rule manually the Storage Folder may be the
> default location requiring one to to 'browse' to the Account(select
> include subfolders) or the Account Inbox.
> ms-mvp mail
> "Bob K" <BobK@xxxxxx> wrote in message
>> OK color me dumb, but here is my problem. In Outlook Express I was
>> able to
>> move messages for my Hotmail Inbox (or any other folder) to my POP3
>> inbox and
>> then apply Message Rules to the POP3 Inbox. The rules (either all or
>> those selected) would then work properly and the messages would be
>> moved from
>> the POP3 Inbox to the various Storage Folders. It seems as though I
>> lost this capability in WLM. Am I missing something simple? or is
>> there a
>> workaround that will provide me the same capability?