[spambayes-bugs] [ spambayes-Bugs-791027 ] pop3proxy hangs when starting to receiving emails

Tue Aug 19 02:37:45 EDT 2003

Bugs item #791027, was opened at 2003-08-19 19:14
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=791027&group_id=61702

Category: pop3proxy
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Ingo Schmiegel (cfi)
Assigned to: Nobody/Anonymous (nobody)
Summary: pop3proxy hangs when starting to receiving emails

Initial Comment:
I'm running:
===========
Linux foo 2.4.20 #4 Sat Mar 15 11:36:12 CET 2003 i686
unknown

Python 2.2.2 (#1, Oct 27 2002, 21:53:16) 
[GCC 3.2] on linux2

Email package:
__version__ = '2.4.3'
===========

For the last two weeks I have successfully been using
spambayes. It is setup to be used with pop3proxy.py and
local users' email clients to parse incoming email upon
request of the client.
I am using the webinterface to train messages.

Today I got the following hang:
 /usr/local/bin/pop3proxy.py -u 29291
SpamBayes POP3 Proxy Beta1, version 0.1 (May 2003),
using SpamBayes POP3 Proxy Web Interface Alpha2,
version 0.02
and engine SpamBayes Beta2, version 0.2 (July 2003).

Loading database... Done.
Listener on port 29292 is proxying pop.gmx.net:110
User interface url is http://localhost:29291/
error: uncaptured python exception, closing channel
<__main__.ServerLineReader connected at 0x8351f14>
(exceptions.UnicodeError:ASCII decoding error: ordinal
not in range(128)
[/usr/local/lib/python2.2/asyncore.py|poll|99]
[/usr/local/lib/python2.2/asyncore.py|handle_read_event|396]
[/usr/local/lib/python2.2/asynchat.py|handle_read|130]
[/usr/local/bin/pop3proxy.py|found_terminator|148]
[/usr/local/bin/pop3proxy.py|onServerLine|216]
[/usr/local/bin/pop3proxy.py|onResponse|277]
[/usr/local/bin/pop3proxy.py|onTransaction|378]
[/usr/local/bin/pop3proxy.py|onRetr|485]
[/usr/local/lib/python2.2/email/Header.py|__init__|164]
[/usr/local/lib/python2.2/email/Header.py|append|230])
Traceback (most recent call last):
  File "/usr/local/bin/pop3proxy.py", line 778, in ?
    run()
  File "/usr/local/bin/pop3proxy.py", line 772, in run
    main(state.servers, state.proxyPorts, state.uiPort,
state.launchUI)
  File "/usr/local/bin/pop3proxy.py", line 711, in main
    Dibbler.run(launchBrowser=launchUI)
  File
"/usr/local/lib/python2.2/site-packages/spambayes/Dibbler.py",
line 528, in run
    asyncore.loop(map=context._map)
  File "/usr/local/lib/python2.2/asyncore.py", line
205, in loop
    poll_fun (timeout, map)
  File "/usr/local/lib/python2.2/asyncore.py", line 83,
in poll
    r,w,e = select.select (r,w,e, timeout)
KeyboardInterrupt
==============================

As you can see the whole thing hung (for more than 15
minutes) before I finally sent it a kill thyself signal.

The corresponding log of the pop3 email client
(sylpheed) looks like this:
===============================
* Connecting to POP3 server: localhost...
[08:42:15] POP3< +OK obsfuscated POP3 StreamProxy ready
<obsfuscated>
[08:42:15] POP3> USER obsfuscated
[08:42:15] POP3< +OK May I have your password, please?
[08:42:15] POP3> PASS ********
[08:42:15] POP3< +OK mailbox has 14 messages (153406
octets)
[08:42:15] POP3> STAT
[08:42:15] POP3< +OK 14 160574
[08:42:15] POP3> UIDL
[08:42:15] POP3< +OK mailbox has 14 messages (153406
octets)
[08:42:15] POP3> LIST
[08:42:15] POP3< +OK mailbox has 14 messages (153406
octets)
[08:42:15] POP3> RETR 1
** Connection closed by the remote host.
====================================
The "connection closed" only appears after killing
pop3proxy.py.

I can workaround this problem by reconfiguring my email
client to not use pop3proxy.py but my email provider
directly. Then I can retrieve those 14 emails. Finally
I can switch back to using spambayes' pop proxy and
everything works fine again.
(Including retrieving new emails)

Unfortunately I did not check which of those 14 emails
I got was the first one - which may have caused the
hang. It looks like it had been the usual "CRISIS IN
LIBERIA". That emails source code does not contain
unusual/unicode characters. But that impression might
be wrong, because it's already been fitlered/converted
by my email client.

Still, I'd like to thank ye all for this great tool.
Even with only a hundred or so messages it is very good
at seperating ham from spam.

Cheers,
  cfi

----------------------------------------------------------------------

>Comment By: Tony Meyer (anadelonbrin)
Date: 2003-08-19 20:37

Message:
Logged In: YES 
user_id=552329

This is fixed in CVS - see 
http://mail.python.org/pipermail/spambayes/2003-
August/006779.html

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=791027&group_id=61702