I have Win2K and work in company with exchange server.
I want to move all messages arriving from outside the company to
Deleted folder, in order not to be cluttered by them, and examine
them later.

In Outlook 2003 I made a rule:
" Apply this rule after message arrives
move it to folderName folder
except if sender is in Global Address List Address Book"

But this rule moves also all messages sent to me from within the
company!

(What is ridiculous, that in OutLook 2000 it apparently worked!)

it may work in classic mode but not cached, since you aren't actually using
the GAL in cached mode, but the office address book copy of the GAL. Thr a
rule that moves all items containing a @ in the header. Trash cans make
terrible file cabinets.... I do not recommend moving items to the deleted
folder - create a new folder to store them - unless you are 100% sure that
it's only junk that can be trashed.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



wrote in message
oups.com...
I have Win2K and work in company with exchange server.
I want to move all messages arriving from outside the company to
Deleted folder, in order not to be cluttered by them, and examine
them later.

In Outlook 2003 I made a rule:
" Apply this rule after message arrives
move it to folderName folder
except if sender is in Global Address List Address Book"

But this rule moves also all messages sent to me from within the
company!

(What is ridiculous, that in OutLook 2000 it apparently worked!)

wrote in message

In Outlook 2003 I made a rule:
" Apply this rule after message arrives
move it to folderName folder
except if sender is in Global Address List Address Book"

But this rule moves also all messages sent to me from within the
company!

I have been looking down the headers to see if there were any posts on this
subject.

I have Outlook 2002 and setup a number of folders under 'Inbox' and made
rules to put messages from my different e-mail addresses to a folder
identified to each address.

Unfortunately, some messages get put in the wrong folder, which in itself is
annoying, but when replying the address used is not the one that the e-mail
arrived with, but the wrong address of the wrong folder.

Is there a way of getting the rules to work correctly or is this yet another
case of Windows not working correctly without a solution?

Alan Morris

Alan Morris wrote:

I have Outlook 2002 and setup a number of folders under 'Inbox' and
made rules to put messages from my different e-mail addresses to a
folder identified to each address.

Unfortunately, some messages get put in the wrong folder, which in
itself is annoying, but when replying the address used is not the one
that the e-mail arrived with, but the wrong address of the wrong
folder.

This sounds to me like you have two rules acting on the same message because
it matches the considtions of both rules. Do each of your rules that move
messages have the "stop processing more rules" action? If not, add that
action and see if that helps. If not, post again.
--
Brian Tillman

"Brian Tillman" wrote in message
...
Alan Morris wrote:

I have Outlook 2002 and setup a number of folders under 'Inbox' and
made rules to put messages from my different e-mail addresses to a
folder identified to each address.

Unfortunately, some messages get put in the wrong folder, which in
itself is annoying, but when replying the address used is not the one
that the e-mail arrived with, but the wrong address of the wrong
folder.

This sounds to me like you have two rules acting on the same message
because
it matches the considtions of both rules. Do each of your rules that move
messages have the "stop processing more rules" action? If not, add that
action and see if that helps. If not, post again.
--
Brian Tillman


At first I had not discovered the stop processing, but quickly found it and
it's now on all rules.

Sometimes, I get a duplicate of a message. One in the Inbox and another
moved - yes, I have move and not copy set.

I have more than one address at the same server. No not the Freeserve type
where anything can got before @.

The rule order has been adjusted for best processing.

It appears that this is another example where Windows (XP in this case)
processes differently from time to time, for no apparent reason.

Alan Morris.

Alan Morris wrote:

At first I had not discovered the stop processing, but quickly found
it and it's now on all rules.

Sometimes, I get a duplicate of a message. One in the Inbox and
another moved - yes, I have move and not copy set.

This is usually a symptom of not having the "stop processing" action.

I have more than one address at the same server. No not the
Freeserve type where anything can got before @.

If you have two accounts and they're both accessing the same mailbox on the
server, you can get multiple messages if both accounts are set in the
Send/Receive group to receive. In this case, set one account to not
receive.

The rule order has been adjusted for best processing.

It appears that this is another example where Windows (XP in this
case) processes differently from time to time, for no apparent reason.

Are you saying, then. that your problem has been solved? If so, that's good
to hear.
--
Brian Tillman

"Brian Tillman" wrote in message
...
Alan Morris wrote:

If you have two accounts and they're both accessing the same mailbox on
the
server, you can get multiple messages if both accounts are set in the
Send/Receive group to receive. In this case, set one account to not
receive.

No each account has a separate mailbox. I have six accounts on three ISPs.
I use an address for NGs, normal mail and private accounts to reduce spam.

Are you saying, then. that your problem has been solved? If so, that's
good
to hear.

Sorry Brian the problem remains. Maybe I need to reinstall Outlook 2002 to
solve these problems.