On 10/05/2023 12:02, Robert Nicholson via Exim-users wrote:
> Exim version 4.96-58-g4e9ed49f8 #2 built 07-Jan-2023 06:47:04
Who built it? What is the provenance of the sourcecode?
> mainlog:2023-05-09 13:49:51 1pwUHO-0005xx-1O SIGSEGV (null pointer indirection)
Definitely a bug; you should not be able to induce this by doing
something odd in a .forward.
For debugging it, it'd help if you could provide the matching .forward
rule (if there is indeed one), and even more if you could get a coredump.
The "failure to transfer data" log is a follow-on resulting from
the transport process dying (and not providing data) not ignore that.
Is the message successfully delivered on a subsequent queue-run
(grep the log for the message ID)? I see several failed tries in
the log extract you gave.
If not, and the message is still queued, please try forcing a delivery
with debug enabled ("exim -d+all -M 1pwUHO-0005xx-1O 2>&1 | tee debuglog")
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
