Hi,
since I'm mainly using the POP3 client to poll my mailboxes: I noticed some strange behaviour when editing the MercuryD config.
It sometimes happens whenever the MercuryD configuration is edited during a poll cycle -
Either, the list of mailboxes is incomplete (i.e. some are missing in the config window), and when the incomplete list is saved, the MercuryD.dat file is crashed/crippled/incomplete, or
While editing the list during a poll cycle, the polling process stops just at any random mailbox, and then halts until the config editor window is closed again.
This means: One can either cripple the mailbox configuration (i.e. loose configured POP3 mailboxes), or block the POP3 polling entirely until the config editor windows are all closed.
Anybody else seen tha same behaviour ? If so, it's perhaps worth a bug report ?
Kind Regards,
Andy
<p>Hi,
</p><p>since I'm mainly using the POP3 client to poll my mailboxes: I noticed some strange behaviour when editing the MercuryD config.</p><p>It sometimes happens whenever the MercuryD configuration is edited during a poll cycle -</p><p>Either, the list of mailboxes is incomplete (i.e. some are missing in the config window), and when the incomplete list is saved, the MercuryD.dat file is crashed/crippled/incomplete, or</p><p>While editing the list during a poll cycle, the polling process stops just at any random mailbox, and then halts until the config editor window is closed again.</p><p>This means: One can either cripple the mailbox configuration (i.e. loose configured POP3 mailboxes), or block the POP3 polling entirely until the config editor windows are all closed.</p><p>
Anybody else seen tha same behaviour ? If so, it's perhaps worth a bug report ?</p><p>Kind Regards,
Andy </p><p>&nbsp;</p>