Rules won't apply to received messages

N

Nikolai Franke

Hello

Although I do exactly as I'm told in Entourage Help (select messages, choose
'Apply Rules' from Message menu), none of the set and active rules is beeing
applied to the selected messages. Is there anything else I have to know?

Thanks a lot
 
J

Jay

Hello

Although I do exactly as I'm told in Entourage Help (select messages, choose
'Apply Rules' from Message menu), none of the set and active rules is beeing
applied to the selected messages. Is there anything else I have to know?

Thanks a lot

If you can provide some more details of exactly what the rules are etc. we
may be able to help. I take it from your post that the rules have never
worked - is that correct?

Describe what you are trying to achieve & how your rules are presently set &
I'll see if I can help (Can't promise I'll know though :).



-Jay-
 
N

Nikolai Franke

If you can provide some more details of exactly what the rules are etc. we
may be able to help. I take it from your post that the rules have never
worked - is that correct?

Describe what you are trying to achieve & how your rules are presently set &
I'll see if I can help (Can't promise I'll know though :).



-Jay-

You are absolutely right, and I must ask for forgivenes, because when I sat
down to write a detailed report, the writing took me where the thinking
didn't. I found that rules are applied one after another, by the order in
the rules panel, and usually only one rule is applied to each message. That
did it. Once again my appologies. It won't happen again. Thanks for you
patience.

Nikolai
 
P

Paul Berkowitz

You are absolutely right, and I must ask for forgivenes, because when I sat
down to write a detailed report, the writing took me where the thinking
didn't. I found that rules are applied one after another, by the order in
the rules panel, and usually only one rule is applied to each message. That
did it. Once again my appologies. It won't happen again. Thanks for you
patience.

"Usually only one rule is applied to each message" - that is only if "Do not
apply other rules to messages which meet these criteria" is checked. If the
rule moves a message to a folder, then that checkbox is enabled and not
alterable. for other actions, you do not have to check that box. So in the
case of moving messages to folders, you do have to decide which
criteria/rules are more important and move them higher up the list. For
other cases multiple rules can run on a message. Also you can specify
multiple actions for a single rule, too.

--
Paul Berkowitz
MVP MacOffice
Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html>
AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

PLEASE always state which version of Microsoft Office you are using -
**2004**, X or 2001. It's often impossible to answer your questions
otherwise.
 
J

Jay

You are absolutely right, and I must ask for forgivenes, because when I sat
down to write a detailed report, the writing took me where the thinking
didn't. I found that rules are applied one after another, by the order in
the rules panel, and usually only one rule is applied to each message. That
did it. Once again my appologies. It won't happen again. Thanks for you
patience.

Nikolai

No problem, Nikolai, glad you've figure it out. If you want any help with
any rules in particluar just post the details & I'd be glad to have a
look.(although I'm no MVP)

I've found that once you understand the rules'logic' then they *can* be
pretty simple. Although, there are, of course, exceptions:)

Regards


-Jay-
 
N

Nikolai Franke

"Usually only one rule is applied to each message" - that is only if "Do not
apply other rules to messages which meet these criteria" is checked. If the
rule moves a message to a folder, then that checkbox is enabled and not
alterable. for other actions, you do not have to check that box. So in the
case of moving messages to folders, you do have to decide which
criteria/rules are more important and move them higher up the list. For
other cases multiple rules can run on a message. Also you can specify
multiple actions for a single rule, too.

I see. I was wondering why I couldn't uncheck that box. Thanks a lot, Paul.
 
M

Martin Rep

Hi all ;-)



"Usually only one rule is applied to each message" - that is only if "Do not
apply other rules to messages which meet these criteria" is checked. If the
rule moves a message to a folder, then that checkbox is enabled and not
alterable. for other actions, you do not have to check that box. So in the
case of moving messages to folders, you do have to decide which
criteria/rules are more important and move them higher up the list. For
other cases multiple rules can run on a message. Also you can specify
multiple actions for a single rule, too.

A question about this. I have a number of rules, all about moving incoming
POP3 mail to specified folders (the last rule is a Spamsieve rule). They run
well for a while, but now they have stopped doing so... Does anyone have a
hint what might cause this?





| Martin Rep
| The Independent Internet Mahjong Newspaper
| http://www.mahjongnews.com
 
F

FarmerBob

What version are you running? If it's 11.2.3, that's why. Mine stopped
working in 11.2.3.
 
M

Martin Rep

Yeah, 11.2.3... You mean in 11.2.3 these rules won't work anymore??? [insane
laughter]
Is there any documemntation about this topic?


On 30-05-2006 10:59, in article
 
B

Barry Wainwright [MVP]

Well, I'm running 11.2.3 and rules are working fine, for me and for
thousands of others.

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Check out the Entourage User's WebLog for hints, tips and troubleshooting
From: Martin Rep <[email protected]>
Newsgroups: microsoft.public.mac.office.entourage
Date: Tue, 30 May 2006 18:02:28 +0200
Conversation: Rules won't apply to received messages
Subject: Re: Rules won't apply to received messages

Yeah, 11.2.3... You mean in 11.2.3 these rules won't work anymore??? [insane
laughter]
Is there any documemntation about this topic?


On 30-05-2006 10:59, in article
What version are you running? If it's 11.2.3, that's why. Mine stopped
working in 11.2.3.
 
D

Diane Ross

A question about this. I have a number of rules, all about moving incoming
POP3 mail to specified folders (the last rule is a Spamsieve rule). They run
well for a while, but now they have stopped doing so... Does anyone have a
hint what might cause this?

I have seen reports of Rule corruption after an update. Usually, the folder
specified in the rule defaults back to the Inbox or another folder is
selected causing the rule appear to misfire.

First, check all your Rules and MLM rules for folder destination. If there
is no problem, uncheck your rules and test for the problem rule. It's
possible you will need to delete some or all of your Rules and recreate them
from scratch.

More on Rules here:

<http://www.entourage.mvps.org/troubleshoot/rules.html>
 
F

FarmerBob

Barry said:
Well, I'm running 11.2.3 and rules are working fine, for me and for
thousands of others.

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Check out the Entourage User's WebLog for hints, tips and troubleshooting
<http://homepage.mac.com/barryw/weblog/weblog.html>

Well great for you and those "thousands(?)". I wish I was that lucky.
But since I did the 11.2.3 update Entourage has become the worst piece
of software I have ever used. And I'm seeing in your own boards many
more people with problems since the update.

Everything is failing. I have a minimum of 5-8 crashes a day (Love the
crash reporter. Never knew it was there until now. I never needed it. I
have never had Entourage crash on me until now.); garbled text; rules
not working; repeated database corruption errors (never having had one
before) and the database verifies as fine; settings in both Word and
Entourage not staying set from one start up to another; spellcheck not
being able to identify words that are one letter off; and God knows
what more that I haven't stumbled on in PowerPoint and Excel. Prior to
the update, Entourage was the best, greatest, most reliable piece of
software I have ever encountered. Now it is the bain of my existence.
As I am reading it is for "hundreds" of others.

There are problems due to this update that need to be addressed and
soon. I have never read where more people are looking to change
products than wait for a fix. This is serious whether you wish to
believe it or not. Some of us did not end up so lucky.
 
F

FarmerBob

P.S.
I forgot to mention that Junk Mail no longer works as it did, nor do
any of the Safe Domains in the list that I have told through the Not
Junk pop up multiple times to approve for the same eMail over and over.


If it weren't for the problems that I have with the 11.2.3 version, I
would never have found these boards. I was looking for help, fixes, and
to see that I wasn't the only one having problems. You would never have
know I ever existed and I would be very happy Entourage user. I guess
we're all stuck.
 
B

Barry Wainwright [MVP]

Well great for you and those "thousands(?)". I wish I was that lucky.
But since I did the 11.2.3 update Entourage has become the worst piece
of software I have ever used. And I'm seeing in your own boards many
more people with problems since the update.

Everything is failing. I have a minimum of 5-8 crashes a day (Love the
crash reporter. Never knew it was there until now. I never needed it. I
have never had Entourage crash on me until now.); garbled text; rules
not working; repeated database corruption errors (never having had one
before) and the database verifies as fine; settings in both Word and
Entourage not staying set from one start up to another; spellcheck not
being able to identify words that are one letter off; and God knows
what more that I haven't stumbled on in PowerPoint and Excel. Prior to
the update, Entourage was the best, greatest, most reliable piece of
software I have ever encountered. Now it is the bain of my existence.
As I am reading it is for "hundreds" of others.

There are problems due to this update that need to be addressed and
soon. I have never read where more people are looking to change
products than wait for a fix. This is serious whether you wish to
believe it or not. Some of us did not end up so lucky.

I certainly believe it is serious for you, but your experience is not
typical of most users who have had a trouble free upgrade experience.

Something has obviously gone badly wrong in your case. Have you tried the
following trouble-shooting tips:

1. under the system preferences, Accounts, <your account>, login items,
make sure there is only one instance of the Microsoft Database Daemon
listed. If you see more than one (and they may be called just 'Database
Daemon' as well, depending on what versions of office you have previously
had installed) then delete them all. The right one will be re-created when
you start an office app. If you found ore than one, start up 'Activity
Monitor' (in the /Applications/Utilities folder), and see if more than one
Database Daemon is running. If it is, quit all office apps, then quit
both/all Database Daemons before starting another office app.

2. start a new identity. Under the 'Entourage' menu, select 'switch
identity...' and then click the 'new' button to create a brand new identity.
This will not import any of your account settings, rules, folder structures
or data, but it may be worth trying it to see if the crashing & bad
behaviour stops. If it does, it points to some deep seated corruption in the
data structure, and we can give tips & pointers to transferring your data
over.

3. remove & re-install Office entirely. Use the 'remove office' utility
(find it at "/Applications/Microsoft Office 2004/Additional Tools/Remove
Office/Remove Office") to remove all trace if the office application &
support files. Make sure you remove office for all versions it finds. Your
'Microsoft User Data" folder will not be touched though, so all your data is
retained. After re-installing from the CD, BEFORE you run any office apps
update to 11.2.3 by using the updater downloaded from Microsoft Office 2004
for Mac 11.2.3 Update
<http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/down
load/office2004/Office2004_11.2.3.xml&secid=4&ssid=29&flgnosysreq=True>
(read the notes first!)

If, after following all these steps there is still something wrong, then I
suspect you need to start looking at errors in the disk structure or OS
installation.

I repeat, your experience is not typical of most users, and I haven't seen a
vast amount of reported problems with the update in these newsgroups - some
people with problems fir sure, but not in vast numbers, and none reporting
the level of problems you seem to be seeing. I have to assume your problems
are primarily due to some other issues with your own installation.
 
F

FarmerBob

Thank you very much for your reply. I have done it all . . . plus. The
problems is the 11.2.3 update and since you haven't had the problems
that I or others have had, you haven't done any where near the
extensive research that we, or I have since I have clients that are in
the same boat, therefore not seen all the terror that is out there. I
can't even quit Entourage without getting a crash report. And this is
all since the 11.2.3 update. As I have said prior to Entourage was a
rock.

I have a client that just bought a new Intel Mac. He has been using
Office 2004 pre 11.2.3 since day one. The first thing that he installed
was install Office 2004 because he needed mail. On a pristine OSX
10.4.6 system he installed Office 2004 and updated, only to get his
first eMail, from me, telling him not to do the update. In horror he
called me since this machine needs to support a very large media output
company. So we thought to just let it ride and see what happens. He is
having the same problems that I am. And this is on a brand new Intel
Mac with nothing else. We reformatted the drive, installed to 10.4.4,
installed Office 2004 up to 11.2.3 and all is FANTASTIC. Explain that.
And don't use 10.4.6 as an excuse. My pre 11.2.3 Office was great in
10.4.6. Better than 10.4.6 itself.

All of what you suggest is the same that the Apple higher arcs are
saying to fix 10.4.6. The same ol' stuff to accommodate the myriad of
new problems. And it is not working there and not here.

What needs to happen is M$ to release a fix for this abomination or a
utility that will revert the database so that we can go back to the
last version that was a gift from God.

It will come out on the history books that this was a very big problem
and bad thing, and since we'll be long, hopefully, past it, laugh. I'm
not laughing and M$ is getting at least 10 error reports as Entourage
crashes a day from me. Plus nice little suggestions (with lots of
profanity) via the help pull down.

There is no subtle pacification on this. Just the need for a COLD HARD
FIX. M$ now it's time for you to step up and produce. Who am I foolin'?
 
B

Barry Wainwright [MVP]

As things have been as bad (for you) as you describe, why have you not
reverted to 11.2.1?

You could export all items from the current database and re-import them into
a new one in 11.2.1. Yes, it would be a pain to do so, but surely better
than suffering what you are.

As for 'demanding' a fix, you seem unclear as to whether that fix should
come from Apple or Microsoft. I reiterate that your experience is different
to the vast majority. There must be something unique about your situation
that causes this trouble.
 
F

FarmerBob

This is clearly a M$ problem and you know it. As I said pre 11.2.3
versions worked great in 10.4.6 and prior Mac OS versions without ANY
incident. So for once Apple is off the hook even thought 10.4.6 is a
DOG on PPC machines and Apple is in the process of phasing out the PPC
platform via questionably compatible and operational software (as per
developers and that this has become a major topic a the dev
conferences). More to come on this in the future.

I would love to revert but since the last update altered the database,
we can't. My major mistake was not copying the database prior to the
update, which would have been way too easy. But I TRUSTED the update.
Yup, I'm a fool. A Mac person trusting M$. Yup very foolish.

As far as Exporting, that was my first action. IT FAILED. Since the
update I get errors upon exporting.

"There was a problem saving one of your messages. Your Office database
may be damaged. Start the Database Utility to verify your database."

I have verified and all is reported as just fine. So . . . what do I
do? This operation is not an option. That is why I now "demand" that M$
come up with a utility to revert the database for us to revert. Hmmm, I
see a possible Class Action Suit here. The last time I did a search in
Entourage it said that it was searching over 30,000 eMails. I have mail
and info there from 1995 at least and use Entourage to "safely" store
important information since it has been flawless since I started using
it in 1995. FLAWLESS SINCE 1995! Maybe I put too much trust in Office
to support me and my clients. I learned to remotely attach the MUD from
a remote drive/partition of which I have seen my instructions recanted
religiously in many many forums since the mid 90's and it's safely
backed up daily, but what good is it if the application is crap?

As I have said and am finding in all Office apps, many problems that I
have been able to reproduce on new Intel machines. Basic mindless
operations no longer working 11.2.3, where they do in pre versions. SO
.. . . this is CLEARLY a M$ problem and they need to take responsibility
for it. New concept, huh?

Barry, it is obvious that you and your cohorts have the best of
intentions. Thank you. But this is bigger than you and the run of the
mill fixes. M$, it's your turn. Do us right and fix this. If only a
utility revert our databases to use a previous version of Office. That
would be the most incredibly thankful thing that you could ever do.
 
B

Barry Wainwright [MVP]

"There was a problem saving one of your messages. Your Office database
may be damaged. Start the Database Utility to verify your database."

Therein, in all likelihood, lies your problem.

If the export fails then it is pretty certain that the database is damaged,
whatever the verify routines say.

Have you tried rebuilding? You say you verified, but haven't said you
rebuilt. Now it is possible that the if the corruption takes some form that
the verify engine doesn't catch that the rebuild routines won't catch it
either, but since the rebuild no longer tries to capture the original
database indexes but recreates them from scratch, there is probably an equal
chance that it will be able to repair it.

In any event, I would seriously advise you to export as much data as you
can. If the export routine can get all the contacts, events, notes and
tasks then do that now. For messages, if that is the area that is causing
problems, you may have to export a folder at a time by dragging to the
desktop. This way you may be able to identify the folder(s) containing
corrupt messages. Then you can work through these folders dragging out the
good messages until you identify the areas of corruption.

Failure to move your data over to a new identity will not only leave you
experiencing your current problems, but will, in all likelihood, result in
the corruption developing and progressing to the point where you may
potentially suffer a total loss of the data.

I am quite happy to continue working with you on this issue, as long as we
are moving forward. Frankly, the tirades and polemics in your messages
aren't particularly encouraging. You seem to be unable to accept that your
case is different to the general user experience and must, therefore, be
entirely Microsoft's 'fault'. Instead of laying blame, can we work to put
things right for you?
 
C

Corentin Cras-Méneur

Barry Wainwright said:
Therein, in all likelihood, lies your problem.

If the export fails then it is pretty certain that the database is damaged,
whatever the verify routines say.


I second that. Version 11.2.6 seems extremely stable on our machines
here at work (same system) and we haven't seen a crash in ages. This
message really points towards a serious database corruption,

Have you tried rebuilding? You say you verified, but haven't said you
rebuilt. Now it is possible that the if the corruption takes some form that
the verify engine doesn't catch that the rebuild routines won't catch it
either, but since the rebuild no longer tries to capture the original
database indexes but recreates them from scratch, there is probably an equal
chance that it will be able to repair it.

At worst, you can try exporting everything to a folder on the desktop
through drag and drop (though I believe there is a limit to the number
of items you can drag at the time). You'll later reimport in a fresh new
identity through a drag and drop the other way around.

Repairing the database and using the export tool instead should be
tremendously better though,

Corentin
 
Top