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
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview Wiki

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

  •  12-07-2018, 8:38

    • Joerg is not online. Last active: 08-16-2019, 10:55 Joerg
    • Top 25 Contributor
    • Joined on 03-25-2008
    • German Baltic Sea Coast
    • Contributor
    • Points 7,615

    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?

View Complete Thread

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