and from there back to the new mail folder - then all display is correct.
If forcing PM to "reload" the message corrects the issue (I don't think you need to alter properties or do anything else, that ALSO forces PM to reload the message in whole or part methinks), then something is interfering with PM reading it correctly the first time.
Brian is correct. this isn't a PM issue..
What I would do first is open task manager, and see what else is running, for a suspect list..
If just disabling AV completely before retrieving messages doesn't "correct the problem", then, I'd turn off "auto-retrieve" and use the File/Selected Mail Download option to retrieve messages, but do NOT delete them from the server until after they have been retrieved and displayed properly, or you have isolated the problem. The idea is to retain some messages on the server that you know fall victim, for troubleshooting.
Once you have a victim message or two on the server, you can start using Task Manager to kill various running programs prior to downloading them again, and see which one(s) appear to be the culprit. Note - it could easily be two different programs not playing nice with each other, or it's even possible that using the Selected Mail Download option avoids the problem completely if it changes the timing of the retrieve/load/scan activity. Again, if forcing PM to "rescan" the messages works, you've got a timing "race condition" between PM and something else accessing the message file at the same time during initial retrieval and load,.
[Conceptually, if three people can't enter through the door simultaneously, it may not be any one of them is "too fat" (the "culprit" ), just someone/any one of them has to enter before (or after) the others.. ]
Once the suspect(s) is/are isolated and the reason identified, now you can start figuring out what to do about it.
And it could be a hardware issue.. only one or two of all the computers are experiencing it, and it isolates to a particular manufacturer/model what's different there? Amount of memory, processor cores, hard drive access speeds, as I'm oft fond of noting: "It could be anything, and probably is..".
BUT - I'm still betting it's the AV.. could it be you've turned off scanning PM while PM is retrieving messages, but AV is still triggered to scanning files when they are being "saved to disk" regardless of location?? As I noted first above, once you have some suspects saved on the server, suspend/disable AV completely and then retrieve them from the server and see if they get loaded properly.
If the affected messages are those with attachment payloads only, then, are the attachments being saved to a different path than x:\PMail..\?
[quote="pid:56791, uid:28210"]and from there back to the new mail folder - then all display is correct.[/quote]
If forcing PM to "reload" the message corrects the issue (I don't think you need to alter properties or do anything else, that ALSO forces PM to reload the message in whole or part methinks), then something is interfering with PM reading it correctly the first time.
Brian is correct. this isn't a PM issue..
What I would do first is open task manager, and see what else is running, for a suspect list..
If just _disabling AV completely_ before retrieving messages doesn't "correct the problem", then, I'd turn off "auto-retrieve" and use the File/Selected Mail Download option to retrieve messages, but do NOT delete them from the server until after they have been retrieved and displayed properly, or you have isolated the problem. The idea is to retain some messages on the server that you know fall victim, for troubleshooting.
Once you have a victim message or two on the server, you can start using Task Manager to kill various running programs prior to downloading them again, and see which one(s) appear to be the culprit. Note - it could easily be two different programs not playing nice with each other, or it's even possible that using the Selected Mail Download option avoids the problem completely if it changes the timing of the retrieve/load/scan activity. Again, if forcing PM to "rescan" the messages works, you've got a timing "race condition" between PM and something else accessing the message file at the same time during initial retrieval and load,.
[Conceptually, if three people can't enter through the door simultaneously, it may not be any one of them is "too fat" (the "culprit" ), just someone/any one of them has to enter before (or after) the others.. ]
Once the suspect(s) is/are isolated and the reason identified, now you can start figuring out what to do about it.
_And it could be a hardware issue.. only one or two of all the computers are experiencing it, and it isolates to a particular manufacturer/model what's different there? Amount of memory, processor cores, hard drive access speeds, as I'm oft fond of noting: "It could be anything, and probably is.."._
BUT - I'm still betting it's the AV.. could it be you've turned off scanning PM while PM is retrieving messages, but AV is still triggered to scanning files when they are being "saved to disk" regardless of location?? As I noted first above, once you have some suspects saved on the server, suspend/disable AV completely and then retrieve them from the server and see if they get loaded properly.
If the affected messages are those with attachment payloads only, then, are the attachments being saved to a different path than x:\PMail\..\? ;)
edited Jul 1 at 4:17 pm