[issue2551014] Broken pipe when sending mails (entries in nosy list)

Paul Spooren <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.devel
Message-ID <1543231495.96.0.788709270274.issue2551014@psf.upfronthosting.co.za>
New submission from Paul Spooren:

The interface works fine except when sending emails by putting entries
to the nosy list. The interface loads until it times out, no matter what
timeout I set in the proxy.

Receiving emails via mailgw works just fine.

The error message looks like that:

127.0.0.1 - - [26/Nov/2018 11:18:18] "POST /support/issue4 HTTP/1.0" 500 -
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 46082)
Traceback (most recent call last):
  File "/usr/lib/python2.7/SocketServer.py", line 571, in process_request
    self.finish_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 331, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.7/SocketServer.py", line 654, in __init__
    self.finish()
  File
"/usr/local/lib/python2.7/dist-packages/roundup/scripts/roundup_server.py",
line 683, in finish
    RoundupRequestHandler.finish(self)
  File "/usr/lib/python2.7/SocketServer.py", line 713, in finish
    self.wfile.close()
  File "/usr/lib/python2.7/socket.py", line 283, in close
    self.flush()
  File "/usr/lib/python2.7/socket.py", line 307, in flush
    self._sock.sendall(view[write_offset:write_offset+buffer_size])
error: [Errno 32] Broken pipe
----------------------------------------

----------
messages: 6299
nosy: aparcar
severity: major
status: new
title: Broken pipe when sending mails (entries in nosy list)
type: crash
versions: 1.6

________________________________________________
Roundup tracker <[email protected]>
<http://issues.roundup-tracker.org/issue2551014>
________________________________________________
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.