Hello!
It seems that Pegasus is using a separate imap sessions for each folder operation. As on the server side the number of sessions is usually limited (as also gmail limits this) then there seem to be a problem when the number of allowed sessions is exceeded. In my installation the mailer sometimes produces an error but in some instances it crashes.
Is there a way to set the limit inside the pmail config so that pmail will not be hitting the server limit? Just for info that we are talking about the 4.7 version of pmail but the same issue was also in older 4.63 version.
[quote user="Paavo"]
Is there a way to set the limit inside the pmail config so that pmail will not be hitting the server limit? Just for info that we are talking about the 4.7 version of pmail but the same issue was also in older 4.63 version.
[/quote]
So does anybody know how to limit the number of IMAP connections pmail establishes?
[quote user="Paavo"]
[quote user="Paavo"]
Is there a way to set the limit inside the pmail config so that pmail will not be hitting the server limit? Just for info that we are talking about the 4.7 version of pmail but the same issue was also in older 4.63 version.
[/quote]
So does anybody know how to limit the number of IMAP connections pmail establishes?[/quote]
Have you tried creating internet session logs (Tools / Internet options) ? Those will show you what is going on in IMAP and may help to give more information.
I'm also not sure what you mean by 'IMAP session' or 'IMAP connection'. From my experience PMail uses just one logged-in connection at a time when accessing one mailbox (from a single program) while other clients may use multiple connections.
What is the error message you sometimes receive? Are you just using a single copy of PMail and nothing else (smartphone/tablet etc) to access the mailbox?
[quote]
[quote]
So does anybody know how to limit the number of IMAP connections pmail establishes?[/quote]
Have you tried creating internet session logs (Tools / Internet options) ? Those will show you what is going on in IMAP and may help to give more information.
I'm also not sure what you mean by 'IMAP session' or 'IMAP connection'. From my experience PMail uses just one logged-in connection at a time when accessing one mailbox (from a single program) while other clients may use multiple connections.
What is the error message you sometimes receive? Are you just using a single copy of PMail and nothing else (smartphone/tablet etc) to access the mailbox?
[/quote]
I am pretty sure that there are parallel IMAP sessions in use as I have access to corp. mailserver logs and that is my recollection that for every opened folder a separate login is performed and new IMAP session is established.
I haven't tested thought will the pmail acts differently if I would tell in imap profile that mailbox is accessed exclusively.
This message is just to rise the question again - is there any possibility to have control over the number of IMAP sessions used by PMAIL?
There is similar thread about controlling the IMAP sessions in Thunderbird that explains the nature of the issue and why such adjustable parameter is necessary - https://support.mozilla.org/en-US/questions/1082511
[quote user="Paavo"]
This message is just to rise the question again - is there any possibility to have control over the number of IMAP sessions used by PMAIL?
[/quote]
Probably not. Are you connecting with that mailbox from other devices, particularly a cell phone?
[quote user="Paavo"]
It seems that Pegasus is using a separate imap sessions for each folder operation. As on the server side the number of sessions is usually limited (as also gmail limits this) then there seem to be a problem when the number of allowed sessions is exceeded. In my installation the mailer sometimes produces an error but in some instances it crashes.
Is there a way to set the limit inside the pmail config so that pmail will not be hitting the server limit? Just for info that we are talking about the 4.7 version of pmail but the same issue was also in older 4.63 version.
Hello!
Thanks for reply!
[quote user="David Harris"]
The IMAP protocol is such that you *have* to use a connection for each open folder...
As a result, the simplest way to limit the number of open connections to the server is to limit the number of open folders you have at any time. Since it's unusual to have lots and lots of folders open at once, I suspect this might actually be another problem that is manifesting as a session limit issue.
If you can capture a Pegasus Mail session log of a failed session, then I'd be happy to take a look at it - I should be able to tell you what the problem is and whether there's a workaround. Mail it to me offline at my normal address, David.Harris@pmail.gen.nz. Please only include the log for the failed session - I can't really wade through 100 logs trying to find the one that has the errors.
[/quote]
I will try to gather the "clean" log of this issue and send it. Many folders opened simulatneously is not unusual case for myself. I use Pmail in corporate environment like the last Mochican :) and I manage perhaps several hundreds of subfolders in my mailbox (I do not use preview mode). The easiest real-life scenario to replicate the situations would be that you have many folders that have folder close rule attached (rule like delete mails over 90days old). In order to execute these rules and "clean" these folders you have to open each such folder and then close. If done rapidly in succession in my case the pmail terminates fatally then I go over the limit. My limit is around 8-9 folders (my IMAP server has a limit at 10 connections per client). When each new folder is opened the previous operation gets suspended and waits for the latest operation to finish. Note however however - then I simply start opening the folders then there is just a pmail error on opening operation on 10th folder but nothinfg fatal.
Maybe there is a slight workaround to the whole situation that with each new folder opened the folder with oldest TCP session should be closed in the background and data in the folder is cashed for display. Definetely it is important that the mail client can cope with the situation when mail server is temporarily refusing connection.
