[quote user="paul.wolstenholme"]

Steffan - I do think that this is unexpected behaviour.  When a message is moved from the new mail folder to any other folder I do expect attributes, such as colour, to be moved with the message.  This is the case when the actions are performed without automating the actions with a filter. 

[/quote]

Paul, I stand corrected. I tried to reproduce this and it works as you say, which is unexpected indeed. I can add, btw, that if I manually move a message that has had its colour changed by a filter rule, the message also loses its colour. If I perform all actions manually, it works as it  should. Sorry I couldn't help.

Cheers!
Steffan

I'm setting up pegasus 4.51 for our 2 user office and find that my new mail filtering rule on open is not working as expected.  The system messages window confirms my belief that the colour of the message is set "1 message coloured bright cyan" and the following rule executes as confirmed by the system message "1 message moved to 'PaulW Inbox'" and the fact that the message gets moved there.  Unfortunately the moved message does not have its colour set.  The folder 'PaulW Inbox' is a regular folder with global attributes in a public folder tree on a shared network drive (peer networking on another XP machine). It is only 2 levels down the tree and one of 188 folders in the tree.

To make the picture even more strange, if I preview the destination folder at the time the message arrives (via regular polling, not via the 'check your pop3..." button because this will change the previewed folder) then I am able to scroll through the folder and see the new message appear WITH the associated colour.  If, however, I preview another folder and return to target folder, the colour is gone.

What can be wrong here and how do I work around it?  The general idea is that mail arriving in the New Mail folder (which is always private, so to speak) is categorised and placed into public folders accessible by the 2 concurrent users.

I don't think there is actually anything wrong here. The mail rule you've created applies to the new mail folder, not to any other folders. For those, you can create general rule sets which you can attach to a folder as either folder-open or folder-close filter sets.

As for previewing the message, I suspect that you have Pegasus Mail set to mark previewed messages as having been read, see Options | Incoming mail | Preview mode settings. Hope this helps.

Cheers!
Steffan

Steffan - I do think that this is unexpected behaviour.  When a message is moved from the new mail folder to any other folder I do expect attributes, such as colour, to be moved with the message.  This is the case when the actions are performed without automating the actions with a filter.  Can you point me to any documentation that indicates using a filter to change attributes before moving a message is not intended to ignore the attribute changes?

It is true that I can use a general rule set on the folder that the message is being moved to.  My intention was to change the colour according to the addressing of the message.  If I am to maintain that philiosophy then I would need to repeat the address analysis logic in the general rule set so that it is not applied to other messages manually moved to that folder.

As for previewing - no I do NOT allow Pegasus to mark previewed messages as having been read.  For me, 'read' doesn't mean I glanced at it or looked at part of it - it actually means I've dealt with the matter.  I therefore find it an anoyance that closing the new mail folder (if opened as a separate window) marks all messages in the new mail folder as read - but that is a separate issue.

[quote user="paul.wolstenholme"]

To make the picture even more strange, if I preview the destination folder at the time the message arrives (via regular polling, not via the 'check your pop3..." button because this will change the previewed folder) then I am able to scroll through the folder and see the new message appear WITH the associated colour.  If, however, I preview another folder and return to target folder, the colour is gone.

[/quote]

Your second paragraph (quoted above) quite clearly indicates an issue. Your filter is obviously working as intended - the problem is that the message property of colour is somehow lost/forgotten.

I've not really used public folders but you state that you have global attributes, so that destroyed my first idea. That said, if you've got so many public folders, it might be worth double-checking that this particular folder IS set to global attributes (and that you didn't lose concentration when setting them all up!).

My next thought was that perhaps the permissions on the drive share are interfering but I can't see how the colour would be reset but the message could be copied with no other issues. Can't be that then.

Apologies if this is what Steffan was alluding to, but can you perhaps work around the issue by moving the message-colouring part of the filter into a general folder-open filter applied to the public folder? This splitting of the two functions in your process may be a few minutes of awkwardness for you but it will at least allow us to perceive whether the problem lies in the concatenation of the tasks within one filter or, if the problem persists, that there may be some wider issue regarding colouring in public folders.

You could also use such a general rule set to test whether it is only this one particular public folder that has the issue or many/all. That information might also be useful in resolving the problem.