- priority: 5 --> 7
It is to expect that gmail servers are rarely returning
internall server error, hence it isn't that easy to
catch, or test, this error. However, it got caught in
my notifier.py (using libgmail) sessions few days ago,
and notifier did not recover from it. I had to kill the
process and restart it. Needless to say, errors should
be handled gracefuly, and geting internal server error
should not impact further running of libgmail.
My suggestion is that, once this error is caught, it is
logged to syslog
(http://docs.python.org/lib/module-syslog.html).
=============
checking for new mail (2006/02/23 21:09:22)
HTTP Error 500: Internal Server Error
connecting...
connection successful... continuing
HTTP Error 500: Internal Server Error
Traceback (most recent call last):
File "./notifier.py", line 196, in mail_check
attrs = self.has_new_messages()
File "./notifier.py", line 253, in has_new_messages
inboxmessagescount=self.connection.getUnreadMsgCount()
File "/usr/local/gmail-notify-1.6/libgmail.py", line
498, in getUnreadMsgCount
q = "is:" + U_AS_SUBSET_UNREAD)
File "/usr/local/gmail-notify-1.6/libgmail.py", line
379, in _parseSearchResult
return self._parsePage(_buildURL(**params))
File "/usr/local/gmail-notify-1.6/libgmail.py", line
352, in _parsePage
items = _parsePage(self._retrievePage(urlOrRequest))
File "/usr/local/gmail-notify-1.6/libgmail.py", line
92, in _parsePage
lines = pageContent.splitlines()
AttributeError: 'NoneType' object has no attribute
'splitlines'
===================