Hello,
Sorry for answering to myself. An update. Two more events:
Mar 31 01:32:07 cloud /kernel: pid 5446 (exim-4.12-1), uid 26: exited on signal 11
Mar 31 03:36:10 cloud /kernel: pid 7517 (exim-4.12-1), uid 26: exited on signal 11
Relevant debug log snippets:
01:29:58 2710 Listening...
01:32:07 2710 ---0 Get 614688 0 daemon.c 164
01:32:07 2710 ---0 Get 614688 16 string.c 344
01:32:07 2710 Connection request from 210.22.102.30 port 49811
01:32:07 2710 1 SMTP accept process running
01:32:07 2710 ---0 Rst 614688 ** daemon.c 613 24600
01:32:07 2710 Listening...
01:32:07 5446 ---0 Get 614704 24 string.c 344
01:32:07 5446 host in rfc1413_hosts? yes (matched "*")
01:32:07 5446 doing ident callback
01:32:07 2710 child 5446 ended: status=0xb
01:32:07 2710 0 SMTP accept processes now running
01:32:07 2710 Listening...
03:35:23 2710 Listening...
03:36:10 2710 ---0 Get 614688 0 daemon.c 164
03:36:10 2710 ---0 Get 614688 16 string.c 344
03:36:10 2710 Connection request from 210.22.102.30 port 49963
03:36:10 2710 1 SMTP accept process running
03:36:10 2710 ---0 Rst 614688 ** daemon.c 613 24600
03:36:10 2710 Listening...
03:36:10 7517 ---0 Get 614704 24 string.c 344
03:36:10 7517 host in rfc1413_hosts? yes (matched "*")
03:36:10 7517 doing ident callback
03:36:10 2710 child 7517 ended: status=0xb
03:36:10 2710 0 SMTP accept processes now running
03:36:10 2710 Listening...
Note: the same host (210.22.102.30), the same debug log pattern.
Not that it bothers me much (for this is obviousely some spammers
trying to feed my Exim their junk), but I'd rather prefer Exim to
end these connections in more graceful way...
--
Olwi
