Pegasus Mail & Mercury

Welcome to the Community for Pegasus Mail and
The Mercury Mail Transport System, the Internet's longest-serving PC e-mail system!
Welcome to Pegasus Mail & Mercury Sign in | Join | Help
in
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview Wiki

problem after windows 10 April Update, version 1803

Last post 05-22-2019, 9:36 by gprit. 24 replies.
Page 1 of 2 (25 items)   1 2 Next >
Sort Posts: Previous Next
  •  05-03-2018, 17:30

    • elems is not online. Last active: 07-05-2018, 12:26 elems
    • Not Ranked
    • Joined on 05-03-2018
    • Member
    • Points 115

    problem after windows 10 April Update, version 1803

    Hello, we report an error that occurred after the update windows 10 to windows 10 April update 1803.

    An error occurs  when we are sending and receiving mail:
     
    A network error occurred during connection to the host

    16:32:38.961: --- 3 May 2018, 16:32:38.961 ---
    16:32:38.961: Connect to 'pop3.xxxxxxxxxxxxxx.it', timeout 60 seconds.
    16:32:38.961: 3: Socket failed, 10022 (no error description available)
     
    ------------------------------------------------------------------------------------------------- 
     
    This information is shown when i open pegasus in my pc without any local installation of pegasus: 
    Pegasus Mail for Microsoft Windows
    WinPMail version: Version 4.72.572, Feb 19 2016, build ID 572
    Language resources: Standard UK English resource set
    Extension Manager version: 1.14
    Operating mode: Standalone
    User name and ID: xxxxxxx, 0
    Windows version: 6.2
    Windows flag word: 0
    WINPMAIL.EXE directory: F:\PMAIL
    Home mailbox location: F:\PMAIL\MAIL\xxxxxxxxx
    New mailbox location: F:\PMAIL\MAIL\xxxxxxxxx
    TMP environment variable: C:\Users\xxx\AppData\Local\Temp
    TEMP environment variable: C:\Users\xxxxx\AppData\Local\Temp
    LAN-based SMTP support: N, N, N
    NetWare MHS support: N, N, N
    Built-in TCP/IP support: Enabled
      - WINSOCK version: WinSock 2.0
      - WINSOCK path: WSOCK32.DLL
    Commandline: 
    Active -Z options: 32768
    PMR variable: (None)
    PML variable: (None)
    MAI variable: (None)
    NB variable: (None)
    Autofiltering folders: 0 (0 active, 0 inactive)
    Last new mail count: 0
    Message size soft limit: 0 bytes
    Message size hard limit: 0 bytes
    Attachment size soft limit: 0 bytes
    Attachment size hard limit: 0 bytes
    --------------------------------------------------------------------- 
     
    Before update everything worked right.

    We have pegasus mail intalled on a windows server and users logged in other pc  (without any local installation of pegasus) access to pegasus mail with a shortcut on their desktop.
    The shortcut point to the executable on a network folder.
     
    we have tryed with another pc with a local installation of pegasus 4.71 and the error does not occur. 
    we have to do some more tests with this solution (with 4.72 version) even if we prefer do not install pegasus locally on all PCs.
     
    any idea to fix the problem without install pegasus on all our pcs?
     
    Thank you
     
    Elena 
  •  05-03-2018, 18:28

    • Brian Fluet is not online. Last active: 07-20-2019, 3:08 Brian Fluet
    • Top 10 Contributor
    • Joined on 12-24-2014
    • North Carolina, USA
    • SuperStar
    • Points 25,455

    Re: problem after windows 10 April Update, version 1803

    That Socket 10022 error can be an indication that the executable is being blocked.  I sure hope MS hasn't done something to block executables on servers.  A quick web search specific to 1803 didn't find any hits but a more general one found this socket error  several came up associated with Win7 in 2013 . 

    I don't have an answer specific to 1803 but suggest you confirm that users have Read permissions to F: and Read and Execute to \PMAIL.  You might also disconnect F: and then remap it.  I would add a hard boot in between.

    Also, an issue with Windows Firewall comes to mind.  Confirm winpm-32.exe is an allowed app. 

  •  05-04-2018, 12:38

    • elems is not online. Last active: 07-05-2018, 12:26 elems
    • Not Ranked
    • Joined on 05-03-2018
    • Member
    • Points 115

    Re: problem after windows 10 April Update, version 1803

    hello,

    with a local installation of pegasus 4.72 pointing to the server mail folder it works.

    but the direct launch of the executable from the network folder still provides the Socket 10022 error


    i confirm that users have Read permissions to F: and Read and Execute to \PMAIL.

    i try to disable antivirus firewall and windows defender firewall 


    maybe MS changes some library or something else is blocking the network functions of the program.

    we will continue to look for a solution

     

     Elena 



     

  •  05-23-2018, 10:47

    • ferret04 is not online. Last active: 01-29-2019, 21:52 ferret04
    • Not Ranked
    • Joined on 05-23-2018
    • Member
    • Points 5

    Re: problem after windows 10 April Update, version 1803

    Hi,

     

    I've had the same problem with a server installation, and agree this appears to be caused by the 1803 update. Only one PC on my network updated to 1803 and couldn't download email for any account. I tried allowing Winpm-32.exe through the firewall, but this made no difference. Other PCs that weren't updated to 1803 could open the same user account and all worked as normal.

     

    For now, we rolled back the 1803 update, and all works as before. We've disabled Windows updates until we find out why this happened.

  •  05-24-2018, 3:21

    • David Harris is not online. Last active: 11-16-2018, 3:14 David Harris
    • Top 25 Contributor
    • Joined on 01-31-2007
    • New Zealand
    • Star
    • Points 9,950
    • SystemAdministrator

    Re: problem after windows 10 April Update, version 1803

    Just to let you know that this problem has been brought to my attention.  If, as it appears, MS is preventing executables to be run from server volumes, then I doubt there is much I can do about it, but should a viable solution present itself, I'll happily work on implementing it.

    Cheers!

    -- David --

  •  05-25-2018, 10:57

    • Joerg is not online. Last active: 07-17-2019, 15:43 Joerg
    • Top 25 Contributor
    • Joined on 03-25-2008
    • German Baltic Sea Coast
    • Contributor
    • Points 7,415

    AW: Re: problem after windows 10 April Update, version 1803

    Hi guys,

    Could you more detail your problem please? Is starting Pmail from a server share the problem, or could you start Pmail but sending mails returns the error? "Elems" wrote that sending mails is the problem, while "Ferret04" wrote that accessing the user account is the problem. But maybe I've missunderstood it.

    Further, is your Pmail installation working together with a Mercury Mail Server or is it a stand-alone Pmail installation where Pmail is sending the mails to the internet itself?

    At the moment we are using a Pmail multi-user server installation, where Pmail executables reside at a Windows Server 2016 (which is using the Windows10 engine). But Windows Server systems are still on version 1607. Also our Mercury Mail Server is running at this server. Client computers are still on Windows 7 but will be upgraded to W10 soon (at the latest when MS ceases the support for W7). At the moment all works fine here, but I would like being prepared.

    Thanks

    Joerg

  •  05-26-2018, 19:07

    • irelam is not online. Last active: 07-17-2019, 0:04 irelam
    • Top 10 Contributor
    • Joined on 03-23-2007
    • Edmonton, Alberta, Canada
    • SuperStar
    • Points 20,590
    • BetaTeam Moderator

    Re: problem after windows 10 April Update, version 1803

    My Windows 10 64-bit PC crashed with blue screen. It offered that the only solution was a rebuild of my system. As I has no other solution I agreed. The rebuilt system ran long enough for me to run some diagnostics such as MemCheck before crashing again.  This time I was given the option to use a recovery point restore, which I pointed at the restore prior to the May upgrade.  After I got through the restore, everything is fine and I have had no further problems.  I am now trying to find out how to stop further Microsoft upgrades until they fix their problem.

    Martin

  •  05-28-2018, 8:03

    • stuzz78 is not online. Last active: 06-26-2019, 7:23 stuzz78
    • Top 150 Contributor
    • Joined on 02-22-2008
    • Member
    • Points 600

    Re: problem after windows 10 April Update, version 1803

    This looks like some more info on the problem, with some workarounds - http://woshub.com/windows-10-1803-cant-run-exe-files-shared-folders/

     

    Their summary:

    It can be concluded that Windows 10 update 1803 for security reasons does not allow you to open network connections in programs running from shared folders that are accessible only using the SMBv1 protocol. As network folders, you need to use devices that support SMBv2 or SMBv3. 

     

    Meanwhile, the commentors of the above story blame Windows Defender.  This site mentions some changes to it in 1803 - https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-exploit-guard.  Specifically under Attack Surface Reduction Rules is listed five new rules, one of which is:

    • Block executable files from running unless they meet a prevalence, age, or trusted list criteria

     

  •  12-07-2018, 8:38

    • Joerg is not online. Last active: 07-17-2019, 15:43 Joerg
    • Top 25 Contributor
    • Joined on 03-25-2008
    • German Baltic Sea Coast
    • Contributor
    • Points 7,415

    AW: Re: problem after windows 10 April Update, version 1803

    Hi Guys,

    Although we've got some Windows 10 machines running since a couple of weeks, now our first user machine has been upgraded from W7 to W10 (1803). And despite of the obove said in this thread Pegasus is running fine so far, especially since every user is starting its Pmail session from a server share. Pmail is not locally installed. I put only a link to "\\serverpath\winpm-32.exe -i user" at the user's desktop.

    Only one thing is a little bit annoying: When starting Pmail it needs a quite long time for folder localization, scanning of folder hierachy etc.. Defender exclusion from scanning of the affected user mailbox doesn't show effect. Has anybody an idea to shorten the startup time of Pmail?

  •  12-07-2018, 14:04

    • Brian Fluet is not online. Last active: 07-20-2019, 3:08 Brian Fluet
    • Top 10 Contributor
    • Joined on 12-24-2014
    • North Carolina, USA
    • SuperStar
    • Points 25,455

    Re: AW: Re: problem after windows 10 April Update, version 1803

    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).

     

  •  12-07-2018, 14:13

    • Joerg is not online. Last active: 07-17-2019, 15:43 Joerg
    • Top 25 Contributor
    • Joined on 03-25-2008
    • German Baltic Sea Coast
    • Contributor
    • Points 7,415

    AW: Re: AW: Re: problem after windows 10 April Update, version 1803

    Hi Brian,

    Under W7 the startup with more than 1000 folders takes round about 3-5 seconds. Under W10 it takes about 15-25 seconds. Sounds not soo much, but when sitting in front of the machine - tick tack, tick tack Wink

  •  12-07-2018, 14:24

    • Brian Fluet is not online. Last active: 07-20-2019, 3:08 Brian Fluet
    • Top 10 Contributor
    • Joined on 12-24-2014
    • North Carolina, USA
    • SuperStar
    • Points 25,455

    Re: AW: Re: AW: Re: problem after windows 10 April Update, version 1803

    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.

  •  12-07-2018, 14:35

    • Joerg is not online. Last active: 07-17-2019, 15:43 Joerg
    • Top 25 Contributor
    • Joined on 03-25-2008
    • German Baltic Sea Coast
    • Contributor
    • Points 7,415

    AW: Re: AW: Re: AW: Re: problem after windows 10 April Update, version 1803

    Just checked with another W10 machine. The first start, until the inbox is showing all messages, lasts 21 seconds. The seconds start takes 15 seconds.
  •  12-07-2018, 22:18

    • Brian Fluet is not online. Last active: 07-20-2019, 3:08 Brian Fluet
    • Top 10 Contributor
    • Joined on 12-24-2014
    • North Carolina, USA
    • SuperStar
    • Points 25,455

    Re: AW: Re: AW: Re: AW: Re: problem after windows 10 April Update, version 1803

    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.


  •  12-08-2018, 10:40

    • PaulW is not online. Last active: 11 Jul 2019, 13:48 PaulW
    • Top 10 Contributor
    • Joined on 05-08-2007
    • UK
    • SuperStar
    • Points 18,285

    Re: AW: Re: AW: Re: AW: Re: problem after windows 10 April Update, version 1803

    Joerg:
    Just checked with another W10 machine. The first start, until the inbox is showing all messages, lasts 21 seconds. The seconds start takes 15 seconds.

     

    I've got used to either fast (5 seconds) or very slow (70-90 secs) on Win7 with a similar server-based setup.

    About 2 months ago I noticed a speedup of the slowest times to 15 to 20 seconds.  I've never been able to find what causes this behaviour.

Page 1 of 2 (25 items)   1 2 Next >
View as RSS news feed in XML

Contact | Advertise | Host provider: PraktIT | Terms of Use | Privacy Statement
Copyright © 2007-2011 David Harris / Peter Strömblad. | Pegasus Mail Home Page