David H. Durgee wrote:
I have been having problems with what I refer to as constipated email
since 2.49.4 and it still continues with 2.53.3 at present. What I am
referring to is that new email for a POP3 account will no longer be
downloaded via periodic POP3 checks. When I notice that I haven't
received any new email for a long enough period I then click on the "Get
Messages For Account" in the pop-up menu and I then receive the
following pop-up error:
The POP3 mail server (pop.verizon.net) does not support UIDL or XTND
XLST, which are required to implement the ``Leave on Server'', ``Maximum
Message Size'' or ``Fetch Headers Only'' options. To download your mail,
turn off these options in the Server Settings for your mail server in
the Account Settings window.
The only way I have found to correct this problem is to restart
SeaMonkey. Thankfully I now have the "restart" add-on to do this and in
virtually all cases that solves the problem. In a rare few cases I get
the same pop-up error again and need to restart a second time.
Perhaps the biggest inconvenience of this whole thing is that the
periodic checks for new messages DO NOT display this pop-up when they
encounter it. The pop-up error is only displayed for a manual message
retrieval. Thus it can be hours before I notice that the bug has hit me
again.
Surely there is a way to request that periodic POP3 checks display error
messages when they have a problem. That would allow me to correct the
situation quickly and thus be able to respond to urgent email in a
timely manner.
At least until the problem can be corrected I would like to be notified
that the problem is occurring again. It would be even nicer if the log
of the POP3 diagnostics could be saved so that I could provide it to the
developers to allow them to correct the problem.
Dave
Reverting back to this thread, a question:
Did this behaviour start with 2.49.4 or did your usage of Seamonkey
change when that level was current? Specifically, your tendency to keep
the program running for days at a time.
Obviously, I'm wondering if this bug was introduced at around that time
or if it was there all along. I suppose you would then need to work out
what level you were using before 2.49.4.
--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
