Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
open both for
further recipients and for eventual delivery.
|
|
|
|
Now `runtest <number> +` and `runtest --range <number> +`
do the same.
|
|
Support for flavours isn't dropped, but currently
we do not have flavour specific files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
expansion tracing messages
|
|
|
|
|
|
|
|
These wrong markers didn't have any impact.
|
|
Suboptimal, but sufficient to regression-test the reason it was added (a live acl_m_
variable being store_reset over, after reception (and ACLs) and then referenced
later. The problem was, child procs of the daemon were still running as the following
0373 started up, and left unexpected output files there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
extra internal checking
(cherry picked from commit 10919584f8ad580434442c7d971083f91c315bc0)
Signed-off-by: Phil Pennock <pdp@exim.org>
|
|
between message receptions in an SMTP connection
|
|
An emulated PPC, running as a VM on x86_64, was seeing testcase fails where
the trailing few log line were missing in munged output, despite on inspection
being present in the spool. Adding a delay before the munge-and-compare
made the issue go away.
|
|
|
|
|
|
|
|
This permits a library-sourced error to be associated with an address
being delivered, collapsing pairs of log lines
|
|
Broken-by: e1d04f48a45c
|
|
|