>> this suddenly appeared on multiple system.
> Could it be that all these systems had updates applied at about the
> time of it starting? If so, that's a useful commonality to start
> an investigation with.
yes, that is my suspicion. we're pretty aggressive about updates.
randy
--
## subscri
On 19/01/2025 21:51, Randy Bush via Exim-users wrote:
this suddenly appeared on multiple system.
Could it be that all these systems had updates applied at about the
time of it starting? If so, that's a useful commonality to start
an investigation with.
--
Cheers,
Jeremy
--
## subscription
> Afaict the script does not use -t but explicitely specifies a
> recipient.
> Did randy unset/change E4BCD_DAILY_REPORT_TO and/or
> E4BCD_PANICLOG_REPORT_TO?
nope. only changed when i hacked to get past this error
> 2025-01-13 06:25:27 1tXDt8-00Aigw-35 1tXDt8-00Aigw-35 no recipients found in
>
On 2025-01-16 Jeremy Harris via Exim-users wrote:
> On 16/01/2025 15:59, Randy Bush via Exim-users wrote:
> > what happened? the symptom was
> >
> > 2025-01-13 06:25:27 1tXDt8-00Aigw-35 1tXDt8-00Aigw-35 no recipients found
> > in headers
> Exim is being fed a message useing a command-line, wit
Hi.
On Thu, Jan 16, 2025 at 07:59:05AM -0800, Randy Bush via Exim-users wrote:
> what happened? the symptom was
>
> 2025-01-13 06:25:27 1tXDt8-00Aigw-35 1tXDt8-00Aigw-35 no recipients found in
> headers
> 2025-01-13 06:25:27 1tXDt8-00Aigv-35 1tXDt8-00Aigv-35 no recipients found in
> headers
On 16/01/2025 15:59, Randy Bush via Exim-users wrote:
what happened? the symptom was
2025-01-13 06:25:27 1tXDt8-00Aigw-35 1tXDt8-00Aigw-35 no recipients found in
headers
Exim is being fed a message useing a command-line, with a "-t" option. This
means
that recipients are to be extracted fr
