Some time after asserting SH hiccup fix I found that it wasn't true —
Pmail/Spamhalter was failing again. I decided to find more on it,
specially on what was happening behind curtains.
One thing was very evident: Pmail/Spamhalter looses its handle on
words4.db3 file every time a new mail message or a reclassification
produced an error at System Message's pane. Something in my hardware,
OS or Pmail lead it to miss control over SH database, thus the error.
Using Sysinternal's Process Explorer I found that when working
properly, words4.db3 had this status:
On SH error, the above pane was shown completely blank, that is, no application was using wrds4.db3 file. Then I decided to change mailbox address from UNC to mapped path
notation (following a hunch), so it looked like this on Process
Explorer Search pane, after the change:
As you can see the System handle
doesn't appear with this setup. With this setup I removed the Lanman
Redirector (a middle man) from the process with a gain in speed and
no more Spanhalter hiccups so far. My fingers still crossed anyway...
I still think something may be
misconfigured in my WinXP, or maybe it's just the old hardware
signaling it will give up some day, but Pegasus Mail has been running
much better (stabler?) after this change. Unless one day I return to
LAN usage (I doubt it very much) this shall remain like this.
Just to mention, Dear Wife's machine (a
WinXP SP3 desktop) still uses UNC notation without problems, probably
because she uses it very little and the SH hiccup occurs after some
time online.
I hope this can give you more to think.
Any comments will be welcomed.
<p>&nbsp;</p><p>Some time after asserting SH hiccup fix I found that it wasn't true —
Pmail/Spamhalter was failing again. I decided to find more on it,
specially on what was happening behind curtains.</p>
<p>One thing was very evident: Pmail/Spamhalter looses its handle on
words4.db3 file every time a new mail message or a reclassification
produced an error at System Message's pane. Something in my hardware,
OS or Pmail lead it to miss control over SH database, thus the error.
Using Sysinternal's Process Explorer I found that when working
properly, words4.db3 had this status:</p>
<p><img src="http://img99.imageshack.us/img99/9342/pmailonuncpath.png" mce_src="http://img99.imageshack.us/img99/9342/pmailonuncpath.png">
</p><p>&nbsp;</p><p style="margin-bottom: 0cm">On SH error, the above pane was shown completely blank, that is, no application was using wrds4.db3 file. Then I decided to change mailbox address from UNC to mapped path
notation (following a hunch), so it looked like this on Process
Explorer Search pane, after the change:</p><p style="margin-bottom: 0cm"><img src="http://img11.imageshack.us/img11/8064/pmailonmappedpath.png" mce_src="http://img11.imageshack.us/img11/8064/pmailonmappedpath.png">&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p style="margin-bottom: 0cm">As you can see the System handle
doesn't appear with this setup. With this setup I removed the Lanman
Redirector (a middle man) from the process with a gain in speed and
no more Spanhalter hiccups so far. My fingers still crossed anyway...
</p><p style="margin-bottom: 0cm">I still think something may be
misconfigured in my WinXP, or maybe it's just the old hardware
signaling it will give up some day, but Pegasus Mail has been running
much better (stabler?) after this change. Unless one day I return to
LAN usage (I doubt it very much) this shall remain like this.</p>
<p style="margin-bottom: 0cm">Just to mention, Dear Wife's machine (a
WinXP SP3 desktop) still uses UNC notation without problems, probably
because she uses it very little and the SH hiccup occurs after some
time online.</p>
<p style="margin-bottom: 0cm">I hope this can give you more to think.
Any comments will be welcomed.</p><p style="margin-bottom: 0cm">&nbsp;</p>
-- Euler
Pegasus Mail 4.81.1154 Windows 7 Ultimate
IERenderer: 2.7.1.5 AttachMenu: 1.0.1.2
PMDebug: 2.5.8.34 BearHTML 4.9.9.6