I just updated to 4.91 from 4.81 and found when I check POP3 host, no mails were downloaded, an error was shown.

Using "Selective mail download" worked fine though.

I found that in the host setup, under download control, I had a server-side filtering rule set. Clearing this solved the issue.

I guess something broke in during the transition to 4.91.

I hope this might help someone else out there.

Cheers,

Torben

Thank you for your post Toben. I am glad that you figured out what was going on but I am puzzled by it considering that mail filtering rules and associated settings are stored in a mailbox directory, the contents of which should not be touched during a version upgrade. Your record of the issue may indeed be helpful to someone else in the future.

Hi Brian,

If you need anything to clarify this issue, please let me know. I would be happy to offer logs or more details if needed. Just let me know.

Best regards
Torben

Thanks Torben. I am not aware of any logs associated with an upgrade. I am curious about whether there is something unique with your installation. If you are so inclined, a post containing the content of the Info button in Help would show the installation details without revealing anything of personal or security concern.

Edit: Also, do you use Identities? I'm wondering if after the update Pegasus Mail opened as a different Identity.

Hi Brian,
No problem, below is the info.

Yes, I use multiple identities, but Pegasus behaved using the proper id for starters. I do check multiple identities when checking for emails. The behaviour of not retrieving emails was the same for other ids.

Thanks,

Torben

WinPMail version: Version v4.91.1746, 11 Aug 2025 18:19:07, build ID 1746
Language resources: Standard UK English resources (EN,0,LL)
Extension Manager version: 1.14
Operating mode: Standalone
User name and ID: tj, 0
Windows version: 6.2
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: M:\tj
New mailbox location: M:\tj
TMP environment variable: C:\Users\torbe\AppData\Local\Temp
TEMP environment variable: C:\Users\torbe\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.DLLCommandline: -A -I tjActive -Z options: 32768PMR variable: (None)PML variable: (None)MAI variable: (None)NB variable: (None)Autofiltering folders: 115 (115 active, 0 inactive)Last new mail count: 23Message size soft limit: 0 bytesMessage size hard limit: 0 bytesAttachment size soft limit: 0 bytesAttachment size hard limit: 0 bytes

Thank you for those details Torben. Whatever occurred during the upgrade to 4.91 remains a mystery.

The enabling of server-side filtering is controlled by a "Ruleset :" entry in the POP3 configuration file (.PND). It is either blank (no filtering), or it contains the name of the server-side filtering rule file (.PNP) (eg: "Ruleset : GMAILPOP.PNP" ). These files are not touched by the installer so I am clueless.

Hi Brian,

I am not worried about it. I started using this when there were no real spam filtering available, so these entries are being caught by existing spam filter, if they show up at all.

I did get curious and played a bit with it:

• Creating a new entry from scratch, with one entry and using it. Still caused the error.
• Removed that entry, still caused it to fail.

I did the tcp log, if it has any interest. But as I said, do not waste too much time on it. I live without the serverside filtering just fine;-)

Cheers,

Torben

14:18:06.376: --- 30 Jul 2026, 14:18:06.376 ---
14:18:06.400: Connect to 'post.dandomain.dk', timeout 45 seconds, flags 16842753.
14:18:07.403: [] Setting SNI hostname to 'post.dandomain.dk'
14:18:07.418: [] SSL/TLS session established
14:18:07.434: [] TLS_AES_256_GCM_SHA384, TLSv1.3, Kx=any, Au=any, Enc=AESGCM(256), Mac=AEAD<lf>
14:18:07.434: [] Peer's certificate name is '/CN=*.dandomain.dk'.
14:18:07.450: >> +OK Server ready. 3c8.39a4a1a.6a6b40fe.x0omv2fn0rJn699Yo7PstA==@director1.mf.dandomain.dk<cr><lf>
14:18:07.450: << USER XXXXXXXXXXXXXXX<cr><lf>
14:18:07.466: >> +OK<cr><lf>
14:18:07.482: << PASS YYYYYYYYYYYYYYYYYYY<cr><lf>
14:18:07.546: >> +OK Logged in.<cr><lf>
14:18:07.562: << STAT<cr><lf>
14:18:07.578: >> +OK 1 8705<cr><lf>
14:18:07.594: << LIST<cr><lf>
14:18:07.610: >> +OK 1 messages:<cr><lf>
14:18:07.626: >> 1 8705<cr><lf>
14:18:07.626: >> .<cr><lf>
14:18:09.503: << QUIT<cr><lf>
14:18:09.525: >> +OK Logging out.<cr><lf>
14:18:09.549: [!] Warning [Benign]: SSL connection improperly closed by remote host.
14:18:09.559: --- Connection closed at 30 Jul 2026, 14:18:09.559. ---
14:18:09.568:

Torben,

What was/is the error? The log doesn't show any problem.

BTW, the entry "14:18:09.549: [!] Warning [Benign]: SSL connection improperly closed by remote host." is common and not a problem. I have not yet seen an explanation for it.

Hi Brian,

Well, I think the problem is that it quits after seeing there is a message, instead of performing the server side commands. I can only show you a log, where it does retrieve the message. I have removed much of the email message itself.

Thanks,

Torben

16:11:49.451: --- 30 Jul 2026, 16:11:49.451 ---
16:11:49.460: Connect to 'post.dandomain.dk', timeout 45 seconds, flags 16842753.
16:11:50.488: [] Setting SNI hostname to 'post.dandomain.dk'
16:11:50.522: [] SSL/TLS session established
16:11:50.530: [] TLS_AES_256_GCM_SHA384, TLSv1.3, Kx=any, Au=any, Enc=AESGCM(256), Mac=AEAD<lf>
16:11:50.537: [] Peer's certificate name is '/CN=*.dandomain.dk'.
16:11:50.543: >> +OK Server ready. 3c8.39ec59a.6a6b5ba5.cBjp5dSpbEK7XK3t20f22g==@director1.mf.dandomain.dk<cr><lf>
16:11:50.550: << USER XXXXXXXX<cr><lf>
16:11:50.566: >> +OK<cr><lf>
16:11:50.573: << PASS sYYYYYYYYYYYYY<cr><lf>
16:11:50.638: >> +OK Logged in.<cr><lf>
16:11:50.656: << STAT<cr><lf>
16:11:50.674: >> +OK 1 8368<cr><lf>
16:11:50.681: << LIST<cr><lf>
16:11:50.696: >> +OK 1 messages:<cr><lf>
16:11:50.703: >> 1 8368<cr><lf>
16:11:50.710: >> .<cr><lf>
16:11:50.721: << RETR 1<cr><lf>
16:11:50.741: >> +OK 8368 octets<cr><lf>
16:11:50.752: >> Return-Path: <><cr><lf>
16:11:50.760: >> Delivered-To: XXXXXXXXX<cr><lf>
16:11:50.768: >> Received: from scan3.mf.dandomain.dk ([10.10.68.139])<cr><lf>
16:11:50.776: >> by box4.mf.dandomain.dk with LMTP<cr><lf>

.....

16:11:53.140: >> <cr><lf>
16:11:53.154: >> <cr><lf>
16:11:53.167: >> --68C961801A09.1785420552/outscan1.mf.dandomain.dk--<cr><lf>
16:11:53.179: >> .<cr><lf>
16:11:53.196: << DELE 1<cr><lf>
16:11:53.219: >> +OK Marked to be deleted.<cr><lf>
16:11:53.233: << QUIT<cr><lf>
16:11:53.261: >> +OK Logging out, messages deleted.<cr><lf>
16:11:53.292: [!] Warning [Benign]: SSL connection improperly closed by remote host.
16:11:53.305: --- Connection closed at 30 Jul 2026, 16:11:53.305. ---
16:11:53.320:

Maybe it is easier if you see them compared...

Cheers

Torben

We must be misunderstanding each other. Based on those logs, one appears to be counting messages but not downloading (one counted). That setting is not enabled is it? Could the server-side filter be leaving it there?
The other shows that it found one new message and downloaded it.

An unknown to me is whether server-side filtering activity is recorded in a log. I just enabled logging to see if what mine shows, but my email volume for that account is low so it may take awhile to get a log of a connection where there was mail.

I suspect you already know this, but I will say it just in case: server-side filtering only acts on new messages.

Hi Brian,

I am sorry to say it, but the only difference between the two logs is the filter file being present or cleared. I am using the same button on top to retrieve the messages in both cases.
So you are probably right, any filtering is not shown there.

And yes, I understand about the server side filtering. It has been working great earlier, where unwanted messages simply were deleted from the server without being downloaded.

And again, do not worry, this is not crucial anymore for me. I would still be happy to provide info, if you want.

But thanks for looking into it!

Torben

Torben,

Check this setting please.

Hi Brian,

Thanks for the suggestion. I tried it, but the result is just the same. I tried "Delete on server" now I was at it, and still no luck.
I did not have the "Download only unread mail", so I tried that too. Still no luck.

I did also add a new pop definition to a completely different server. I did base it on the the identity with issues, but changed the server details. The issue persisted.

For good measure, here is the pnd file with the pnp file in place.

Thanks,

Torben

Pegasus Mail POP3 definition, 31 Jul 2026, 10:10:08

Title : pop-tj-dandomain
Type : POP3
Flags1 : 16
Flags2 : 0
Timeout : 45
Port : 995
Host : post.dandomain.dk
Username : XXXXXXXXXXXXXXXXX
Password : YYYYYYYYYYYYYYY
Mailbox :
Memfile : POPCWWX9.PM3
Threshold : 0
SSLMode : 2
Max_Msgs : 0
Min_Interval : 0
Ruleset : SPAMREMO.PNP
Top_lines : 0
Def_action : 0

Torben,

For review, please confirm that this discussion regards two issues. One, the automatic addition of a server-side filter to a POP3 definition, and two, the failure to download messages when a server-side filter exists.

Regarding issue one, I am walking back my opinion that the upgrade did not cause the problem but remain skeptical that it was the upgrade itself. I say this because I found a server-side filter enabled in one of my POP3 definitions where it should not have been. In my case, it was a Gmail specific server-side filter set that was enabled in a non-Gmail definition. I have brought both of our cases to the attention of the developer David Harris.

Regarding issue two, I can't duplicate the failure to download when a server-side filter is in place. If the POP3 definition is configured to download unread mail and download after filtering, then...
... is it just one message that won't download, or is it all messages in the host inbox?
... does neutering the server-side filter make any difference? By "neutering" I mean adding an "Always exit" rule as the first rule in the filter set. The filter set will then be invoked but immediately exited which is a way to identify whether something within the filter set is causing the problem.

Hi Brian,

I am not sure I follow what you mean by the first issue. The filter was in place on previous version and thus got inherited at the installation of 4.91. Nothing odd in this.
It is only if a server side filter is chosen, the messages residing on server are not downloaded.

I am sure you saw it, this is not a gmail account causing it. Is there a difference in serverside list for gmail compared to other servers?
I just added a gmail account identity, and it did the exact same thing.

It is all the messages that is left on the server. Note pegasus does show a failure dialog when this happens, see attached image.

I have tried an empty server side list, but also one with an entry "neutered", which will fail and thus exit. Still causing the issue.

This installation of Pegasus is ancient. Could there be any files that have a different format causing this? I did try to create serverside filter from the bottom, but it was still the same. Any other files that might be causing an issue? I did notice some entries in the ini files are from before multiple identities were an option.

Thanks,

Torben

Ahhh... I DID misunderstand. I thought the filter got added by the 4.91 upgrade process.

Yes, I saw it, and AFAIK, there is not a difference in server-side filter for Gmail versus others. I mentioned Gmail because that is an account that I am doing serverside filtering on.

I don't think the old installation should be this issue. The files at play here are only a .PND and a .PNP file and, IIUC, you have tested with a new filter rule set and a new POP3 definition. That said, I have seen odd behaviors get fixed by a rebuild of PMAIL.INI but that is a last resort, especially when multiple Identities are involved.

The only configuration option that I can think of that could affect this is not having the "Download" option enabled after filtering. If that is enabled, then perhaps an issue between your host and the serverside filter process in 4.91? IDK! I hope other forum members are following this and doing their own testing in an effort to duplicate your issue.

Hi Brian,

Well, I do hope they are not spending too much time on it;-)

To your comment on the setting "Default action for messages still present after filtering", it is indeed sat to "download", but we have checked all three options, still the same issue.

I did a test, and I think it is time for me to disclose more about my setup. Honestly, everything has been working fine, so it never crossed my mind this might be an issue.

I have installed the Pegasus mail program on my c-drive. To start the program, I have a batch file checking if there is a pmail.ini on a server location (linux system, running samba). If it is found it uses a pmail.cfg file that points to this server location. If not found, it uses another pmail.cfg file which points to the c-drive. Mostly I am working on the server, but every now and then when I travel, I can still work with my emails. I am not using the c-drive side much, as I can VPN into the server.

So as a test, I had it pointing to mails on my c-drive, and voilá everything is peachy. Running it pointing to the server, still no dice.

I compared the pnd files, the pmail.ini (I actually copied the one from c to the server) and still the issue persisted.
I have checked for access rights, and all files are accessible to Pegasus.

I did re-create the two cfg files, just in case something had changed, but it did not help.

I do appreciate the effort you put in to my issue. And I would be happy to help in any way I can, but remember, I am quite happy with the program as it is, the feature is not my preferred solution to avoid unsolicited mail, now Spamhalter is part of the equation.

Cheers,

Torben