N
Norman R. Nager, Ph.D.
Help, please, each time I quit Entourage, another port closes.
I installed the script "Delete Junk Folder X," created a junk folder, and
changed a number of my rules from "move to delete folder" to "move to junk
folder." I set an empty on quit schedule.
Thereafter, every time I quit Entourage X SR1 today (operating with OS
10.2.6) I got the following dialogue:
"Microsoft Entourage got an error: can't read status of every message of
folder id 244 to read"
Immediately after this dialogue appeared, my personal firewall put up
another dialogue saying that a new port (number) has closed.
I then changed the Delete Junk Folder X schedule to "manually" when I
figured that the problem might be a conflict between the delete junk folder
schedule and the empty Deleted Items Folder schedule, also set for "on
quit."
I no longer get the Entourage dialogue, but every quit of Entourage still is
followed immediately by a new firewall dialogue telling me another port has
closed.
I then did a Typical Rebuild and then an Advance Rebuild. Neither solved
the problem.
I installed the script "Delete Junk Folder X," created a junk folder, and
changed a number of my rules from "move to delete folder" to "move to junk
folder." I set an empty on quit schedule.
Thereafter, every time I quit Entourage X SR1 today (operating with OS
10.2.6) I got the following dialogue:
"Microsoft Entourage got an error: can't read status of every message of
folder id 244 to read"
Immediately after this dialogue appeared, my personal firewall put up
another dialogue saying that a new port (number) has closed.
I then changed the Delete Junk Folder X schedule to "manually" when I
figured that the problem might be a conflict between the delete junk folder
schedule and the empty Deleted Items Folder schedule, also set for "on
quit."
I no longer get the Entourage dialogue, but every quit of Entourage still is
followed immediately by a new firewall dialogue telling me another port has
closed.
I then did a Typical Rebuild and then an Advance Rebuild. Neither solved
the problem.