[Mailman-Users] Received mail not always going to list

[Jeffrey Hugo]

I don't suppose there is a patch for the patch?  That would be too easy.

It looks like after running unshunt, the same thing happens.  I do not see
anything that appears to be a pattern among the shunted messages.  Are there
any suggestions as to how I might fix this?  I am not too familiar with the
Mailman set up on this machine, but I would like to get it fixed.  Thank
you.

-Jeff

On Dec 3, 2007 7:06 PM, Mark Sapiro <mark at msapiro.net> wrote:

> Jeffrey Hugo wrote:
> >
> >The machine is running Ubuntu 6.06 (Dapper Drake), Mailman 2.1.5installed
> >with apt-get, and Postfix.  Any help would be appreciated.
> >
> >-Jeff
> >
> >Dec 03 18:09:53 2007 (4532) Uncaught runner exception: (104, 'Connection
> >reset by peer')
> >Dec 03 18:09:53 2007 (4532) Traceback (most recent call last):
> >  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
> >    self._onefile(msg, msgdata)
> >  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
> >    keepqueued = self._dispose(mlist, msg, msgdata)
> >  File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
> >_dispose
> >    more = self._dopipeline(mlist, msg, msgdata, pipeline)
> >  File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
> >_dopipeline
> >    sys.modules[modname].process(mlist, msg, msgdata)
> >  File "/usr/lib/mailman/Mailman/Handlers/SpamAssassin.py", line 76, in
> >process
> >    score, symbols = check_message(mlist, str(msg))
> >  File "/usr/lib/mailman/Mailman/Handlers/SpamAssassin.py", line 62, in
> >check_message
> >    res = connection.check(spamd.SYMBOLS, message)
> >  File "/usr/lib/mailman/Mailman/Handlers/spamd.py", line 122, in check
> >    response = fp.readline()
> >  File "/usr/lib/python2.4/socket.py", line 332, in readline
> >    data = self._sock.recv(self._rbufsize)
> >error: (104, 'Connection reset by peer')
>
>
> Someone has apparently patched your Mailman with
> <
> https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103
> >.
> The spamd.py handler's SpamdConnection.check() method doesn't catch
> socket exceptions that occur while reading from the socket. Thus if
> something happens to the connection between the spamd.py handler and
> the spamd daemon, an uncaught exception like the above occurs.
>
> This may be transient glitches or they may depend on message content or
> there may be some more fundamental problem with spamd.py.
>
>
> >Dec 03 18:09:54 2007 (4532) SHUNTING:
> >1195172718.109622+5f2a18798e1a2c35cac4085a04731996cdb017d9
>
>
> You could try running bin/unshunt to reprocess these shunted messages
> and see if they work a second time. However, I recommend first running
> 'bin/show_qfiles qfiles/shunt/*' and removing any entries you don't
> actually want.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>
>