Quantcast
Channel: Pegasus Mail Community Support
Viewing all articles
Browse latest Browse all 1735

problem after windows 10 April Update, version 1803

$
0
0
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 

Viewing all articles
Browse latest Browse all 1735

Trending Articles