M
Martin C 007
Guest
We use email rules to process certain emails.
In essence the rule applies to messages that are received that are sent to a distribution list (containing two recipients), moves the email to a specific folder, runs a script that files any email attachment to a specified network directory, marks the email as read and stops processing more rules.
Over the past couple of years apart from having to modify the user's regedit to add an EnableUnsafeClientMailRules entry under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security.an entry to allow scripts to be run, the rules were executed reliably.
Over the past few months the rules do not run, and when managing the rules, the rule is still listed and there are no errors, but when I try and run the rule manually the rule then doesn't show up in the Run Rules Now list.
If I go back to the main manage rule display and just click on the script's name and click on okay, then when I go into the Run Rules Now display the rule is displayed and it will then allow me to run it manually.
This will then allow the rule to be run automatically for new emails but the problem soon reoccurs.
I am using Outlook running through a personal Office365 account and the email account that the rule is associated to is associated to a company Office365 Exchange server. This combination has worked reliably in the past.
It seems to be an issue with the script.
In order for the rule to be listed in Run Rules Now.. list, I have to click on the script name of the rule, it then displays the scripts that are available with the correct one highlighted, and if I click okay, then it will appear in the Run Rules Now list and will, for a period of time, run automatically.
(I have tried just clicking on the other rule variables to see if it is just a case of rewriting the rule but it is only when the script is highlighted and confirmed that the rule is then listed in the Run Rules Now list).
So the problem seems to be that Outlook is not running the rule because it can't find the script, but if I tell it to look for the script it finds it, in the right place. Once I have reestablished the connection the rule runs, until such time as it doesn't.
There is nothing unusual about the script, it is in an Outlook Developer Visual Basic Module.
It does not appear to be a problem with the specific script as it happens with different scripts, although they are all defined in the same module.
I use multiple laptops and the behaviour is consistent, but intermittent across both devices, so it would not seem to be related to a corrupted email account.
The problem might relate to the other intermittent problem where when the rules are edited a message is sometimes displayed.
"The rules on this computer do not match the rules on Microsoft Exchange. Only one set of rules can be kept. You will usually want to keep the rules on the server. Which rules do you want to keep?"
This is a problem across a number of different machines and accounts.
I understand that to be a known Microsoft problem that doesn't yet have a fix.
However when this error is displayed, and client selected, the rule will run manually without having to first click on the script name so that it is displayed in the run now list.
Can anyone offer any insight in how to resolve this problem?
Continue reading...
In essence the rule applies to messages that are received that are sent to a distribution list (containing two recipients), moves the email to a specific folder, runs a script that files any email attachment to a specified network directory, marks the email as read and stops processing more rules.
Over the past couple of years apart from having to modify the user's regedit to add an EnableUnsafeClientMailRules entry under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security.an entry to allow scripts to be run, the rules were executed reliably.
Over the past few months the rules do not run, and when managing the rules, the rule is still listed and there are no errors, but when I try and run the rule manually the rule then doesn't show up in the Run Rules Now list.
If I go back to the main manage rule display and just click on the script's name and click on okay, then when I go into the Run Rules Now display the rule is displayed and it will then allow me to run it manually.
This will then allow the rule to be run automatically for new emails but the problem soon reoccurs.
I am using Outlook running through a personal Office365 account and the email account that the rule is associated to is associated to a company Office365 Exchange server. This combination has worked reliably in the past.
It seems to be an issue with the script.
In order for the rule to be listed in Run Rules Now.. list, I have to click on the script name of the rule, it then displays the scripts that are available with the correct one highlighted, and if I click okay, then it will appear in the Run Rules Now list and will, for a period of time, run automatically.
(I have tried just clicking on the other rule variables to see if it is just a case of rewriting the rule but it is only when the script is highlighted and confirmed that the rule is then listed in the Run Rules Now list).
So the problem seems to be that Outlook is not running the rule because it can't find the script, but if I tell it to look for the script it finds it, in the right place. Once I have reestablished the connection the rule runs, until such time as it doesn't.
There is nothing unusual about the script, it is in an Outlook Developer Visual Basic Module.
It does not appear to be a problem with the specific script as it happens with different scripts, although they are all defined in the same module.
I use multiple laptops and the behaviour is consistent, but intermittent across both devices, so it would not seem to be related to a corrupted email account.
The problem might relate to the other intermittent problem where when the rules are edited a message is sometimes displayed.
"The rules on this computer do not match the rules on Microsoft Exchange. Only one set of rules can be kept. You will usually want to keep the rules on the server. Which rules do you want to keep?"
This is a problem across a number of different machines and accounts.
I understand that to be a known Microsoft problem that doesn't yet have a fix.
However when this error is displayed, and client selected, the rule will run manually without having to first click on the script name so that it is displayed in the run now list.
Can anyone offer any insight in how to resolve this problem?
Continue reading...