Pegasus Mail & Mercury

I'm stuck with Win7 until the company upgrades its accounting system.  Win10 causes database corruption which we believe is due to a dependency on SMB1.

Since changing to v0.101.0 this entry is in the freshclam log associated with each download.        Can't query daily.25186.101.1.1.6810BD8A.ping.clamav.net This follows the entry stating that the daily.cld has updated.  I don't know what the query is attempting to do so have posted on the clam-users list ...

I wish I could help but I don't have a clue.  Thinking out loud... - Default printer issue? - Test with the -A commandline option added (I don't hold much hope that it will make any difference)  - Mapped drive paths instead of unc paths??? That's not an easy thing to test in environments like ours.

15-25 does sound like a long time.  It it every startup? On my Win7 the 10ish second start only applies to the first start of the morning and that time is mostly spent processing the folders.  If I restart during the day its 3-5 seconds.

How long in time?  I don't have any Win10 machines so I don't have any advice but I'm curious to compare what you are experiencing to my startup of around 10 seconds for just over 1000 folders and 80-100 messages in the NMF (usually around 20 unread).  

Three messages with sanesecurity test content were detected.  It appears that all is well.

I just uninstalled 0.100.2 replacing it with portable 0.101.0.  Freshclam downloaded the sig files normally. ClamD started as expected. No errors logged in either log. The ClamWall header is being added to incoming messages. Looks good based on the first MercD cycle.  I just got pulled away so am a little nervous about not being ...

ClamAV 0.101.0 has been released.  Details here: https://blog.clamav.net/2018/12/clamav-01010-has-been-released.html Note:  New .exe installer built using InnoSetup 5.  Files look very different.  Don't use it to upgrade (overwrite) existing per a response to my inquiry on their support forum.  I'm leaning towards ...

It's working!  The PMR environment variable is now set in Group Policy. Prior to that I got it to work on my machine which had the environment variable set manually but I can't explain why since I don't think I had changed anything since yeste

Thanks for confirming that just setting a pmr environment variable should work. Now to figure out why mine isn't.