Re: [Exim] Re: SIGCHLD complaints back in exim 4.20

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Nigel Metheringham
Datum:  
To: Philip Hazel
CC: exim-users
Betreff: Re: [Exim] Re: SIGCHLD complaints back in exim 4.20
On Fri, 2003-05-23 at 10:14, Philip Hazel wrote:
> You need to have SIG_IGN_WORKS defined to skip the code that causes
> this. It should be defined in OS/os.h-Linux.


It definitely is defined.
The interesting part is that it looks as though this is caused by the
verify code - if I comment out the line in my rcpt acl reading:-
  require verify        = sender/callout=30s,defer_ok


then I don't see the kernel message.  Just to make things even more
obscure.  I can simplify that down to
  require verify        = sender


and I still see the same result *unless* the sender is a locally defined
address (ie no DNS etc). There are no entries in the acl prior to that
which would prevent that acl being run.

The kernel message is also definitely being generated after the rcpt to
SMTP line.

This implies to me that this is happening in the verify path, maybe in
the dnslookup router (the only one run for remote addresses). It is not
being seen for outgoing messages or locally run verify (ie exim -bt
etc).

I'm rather foxed here...

    Nigel.



--
[ Nigel Metheringham           Nigel.Metheringham@??? ]
[ - Comments in this message are my own and not ITO opinion/policy - ]