I just discovered that (with 1.62) a malformed `receiver_unqualified_nets'
line causes Exim to dump core. The offending code is this, from
verify.c:verify_setup_netlist().
If the string has no '/' character in it, then `slash' is NULL and *slash
causes a segmentation fault.
Is this fixed in the latest testing releases? If not, Philip, perhaps you
could put a check in. It would be nice actually if Exim could try to catch
SIGSEGV and other usually-fatal signals and write out a panic log entry (even
if it's just "killed by SIGSEGV". Otherwise, when this sort of problem
happens the Exim processes just vanish without trace.