Re: [exim] [Pkg-exim4-users] rspamd spam scanning fails afte…

Top Pagina
Delete this message
Reply to this message
Auteur: Thomas Hager
Datum:  
Aan: exim-users
Onderwerp: Re: [exim] [Pkg-exim4-users] rspamd spam scanning fails after upgrade to 4.88 bpo on jessie
On Wed, 2017-01-25 at 22:57 +0000, Jeremy Harris wrote:
> On 25/01/17 21:09, Thomas Hager wrote:
> > On Wed, 2017-01-25 at 08:19 +0100, Andreas Metzler wrote:
> > > Thomas Hager <duke@???> wrote:
> > > > I updated Exim on my jessie box to 4.88-4~bpo8+1 a few days ago
> > > > and
> > > > discovered about now that the update broke spam scanning with
> > > > rspamd.
> > > > From the logs:
> > > > 2017-01-22 08:59:55 1cVD46-0004AB-QI spam acl condition: spamd:
> > > > failed
> > > > to connect to any address for 127.0.0.1: Broken pipe
> > > > 2017-01-22 08:59:55 1cVD46-0004AB-QI spam acl condition: all
> > > > spamd
> > > > servers failed
> > >
> > > [...]
> > >
> > > > Before I take this to the upstream list I'd like to verify if
> > > > this
> > > > is
> > > > an issue with the 4.88 bpo package on jessie.
> > >
> > > Hello,
> > >
> > > I would be surprised if this was Debian specific. There was a
> > > similar
> > > report in December.
> > > http://lists.alioth.debian.org/pipermail/pkg-exim4-users/2016-Dec
> > > embe
> > > r/002368.html
> >
> > Hi Andreas,
> >
> > I cc the Exim users list now, because I found the code, which
> > causes
> > the described connection failures.
> >
> > To begin with, reverting the patch described in
> > https://bugs.exim.org/show_bug.cgi?id=1802 didn't fix the error.
> >
> > So I dug deeper and found commit fb05276a ("TCP Fast Open"). 
> >
> > If TCP_FASTOPEN is defined in netinet/tcp.h, Exim 4.88 uses
> > MSG_FASTOPEN for STREAM sockets. If TFO is not available, the code
> > in
> > ip.c catches an EOPNOTSUPP error in the call to sendto() and falls
> > back
> > to connect(). On jessie, sendto() doesn't raise an EOPNOTSUPP error
> > when Exim tries to connect to rspamd with MSG_FASTOPEN, but raises
> > an
> > EPIPE error instead.
>
> Can you verify if smtp transports are similarly broken?  It's the
> same routine being used, so I'd expect all sorts of things to fail.

The smtp transports work fine, lookups to the local LDAP daemon too.
Only the spamd connectivity is broken.

> What version kernel do you have?

3.16.0-042stab120.5 (my server is hosted on a Virtuozzo-based farm)

Could this be part of the problem? I assume Heiko's server's not
running on a Virtuozzo VM, and his setup works fine...


-- 
Thomas "Duke" Hager                               duke@???
GPG: 2048R/791C5EB1            http://www.sigsegv.at/gpg/duke.gpg
=================================================================
"Never Underestimate the Power of Stupid People in Large Groups."