https://bugs.exim.org/show_bug.cgi?id=2904
Bug ID: 2904
Summary: "bad memory reference" errors in paniclog
Product: Exim
Version: 4.96
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Unfiled
Assignee: unallocated@exim.org
Reporter: dpc22@cam.ac.uk
CC: exim-dev@exim.org
We have been running Exim 4.96 for a couple of weeks now.
This morning I saw a spate of:
2022-07-18 09:45:59 +0100 1oDMO7-000jWS-RX
bad memory reference; pool not found, at gstring_grow 1122
for about 20 minutes between 09:30 and 09:50.
No such errors were recorded after that point (and it has been almost 4 hours
now). No such errors before that point, or when we were running 4.95 with an
identical configuration.
There were about 50 such errors in total spread evenly across the four separate
systems which constitute mx.cam.ac.uk.
I imagine that a spammer sent around a dozen messages which were broken in some
fashion to each IP address of mx.cam.ac.uk in turn, and they have now gone
away.
There haven't been any repeated delivery attempts causing the same errors after
that point, which is what I would expect from legitimate email stuck on a
sending system.
There isn't any other information in the Exim logs relating to each queue ID
(e.g: 1oDMO7-000jWS-RX). Nothing in /var/log/messages either.
Obviously that isn't much to go on, but I thought that I ought to at least flag
that there is a potential issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Bug ID: 2904
Summary: "bad memory reference" errors in paniclog
Product: Exim
Version: 4.96
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Unfiled
Assignee: unallocated@exim.org
Reporter: dpc22@cam.ac.uk
CC: exim-dev@exim.org
We have been running Exim 4.96 for a couple of weeks now.
This morning I saw a spate of:
2022-07-18 09:45:59 +0100 1oDMO7-000jWS-RX
bad memory reference; pool not found, at gstring_grow 1122
for about 20 minutes between 09:30 and 09:50.
No such errors were recorded after that point (and it has been almost 4 hours
now). No such errors before that point, or when we were running 4.95 with an
identical configuration.
There were about 50 such errors in total spread evenly across the four separate
systems which constitute mx.cam.ac.uk.
I imagine that a spammer sent around a dozen messages which were broken in some
fashion to each IP address of mx.cam.ac.uk in turn, and they have now gone
away.
There haven't been any repeated delivery attempts causing the same errors after
that point, which is what I would expect from legitimate email stuck on a
sending system.
There isn't any other information in the Exim logs relating to each queue ID
(e.g: 1oDMO7-000jWS-RX). Nothing in /var/log/messages either.
Obviously that isn't much to go on, but I thought that I ought to at least flag
that there is a potential issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##