https://bugs.exim.org/show_bug.cgi?id=2903
--- Comment #3 from David Carter <dpc22@???> ---
No sign of a core dump with:
echo "/tmp/core.%e.%t.%p" > /proc/sys/kernel/core_pattern
echo 2 > /proc/sys/fs/suid_dumpable
ulimit -c unlimited
I attach the output from:
/opt/exim/bin/exim -d+all -bh 127.0.0.1 -oMi "[127.0.0.1]:25" -d+all 2>&1 | tee
/tmp/out.txt
with the following minimal Exim configuration:
---8<---
spool_directory = /spool/exim
keep_environment = ""
never_users = root
log_file_path = /spool/exim/log/%slog
acl_smtp_rcpt = accept hosts = : @[]
begin rewrite
*@*.hermes.cam.ac.uk $1@??? hF
begin routers
dnslookup:
driver = dnslookup
transport = smtp
begin transports
smtp:
driver = smtp
--8<--
That ends:
16:00:01 2891 rewrite_one_header: type=F:
16:00:01 2891 From: <dpc22@>
16:00:01 2891 LOG: MAIN
16:00:01 2891 rewrite: domain missing or malformed
16:00:01 2891 search_tidyup called
16:00:01 2891 >>>>>>>>>>>>>>>> Exim pid=2891 (fresh-exec) terminating with
rc=1 >>>>>>>>>>>>>>>>
which looks like Exim bailing out with "rc=1" right after the rewrite rule is
applied. It doesn't wait for the message body after the headers, or the "."
termination.
--
You are receiving this mail because:
You are on the CC list for the bug.
