Quoting Todd Lyons <[email protected]>:
At least on CentOS, the init script that stops and (re)starts exim, just stops the listening processes, allowing any existing sessions to continue to completion. If you tell it to stop a second time, it will kill all processes (i.e. those that were in the process of delivering and those that were in the process of receiving). Is it possible that when you restarted exim that there were some processes left which were in the process of delivery/reception that were using the old config?
On Debian systems, a dpkg-reconfigure of the exim4-config package results in Exim being restarted. I guess it's possible that some previously forked processes were still hanging around that didn't know about the new configuration, but it's not as if there was a problem sending the test messages using the new domain name, and I thought callouts were really just about checking the local part of an address. Besides, how come my manual callout using a telnet session to the same host did work when the Exim-to-Exim callout did not?
Cheers, Jaap -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
