>> 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
> 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
>
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
this hack fixes, but i suspect that it is the wrong hack
% diff -c /etc/cron.daily/exim4-bas
iphone -> mail.rg.net:465
mail.rg.net -> psg.com:25+tls
psg.com -> ran.opsg.com:25+tls
ran.psg.com -> laptop:imap
From: Randy Bush
Subject: Test
To: Randy Bush
Date: Fri, 5 Jan 2024 08:58:45 -0800
Return-path:
Received: from psg.com ([2001:418:1::62])
by ran.
>> with gobble et alia forcing ARC upon us[0]. i would hope it would be
>> in the distributed .debs
>
> To be fair to Debian, we still regard it as experimental - having had
> little evidence of it's actual use in the wild, and interoperability
> of the Exim implementation.
i am not seeking to bla
>> "exim -bV" and look at the "support for" line. If it include
>> "Experimental_ARC" then yes.
debian bookworm amd64
mail.rg.net:/home/randy> exim -bV
Exim version 4.96 #2 built 18-Nov-2023 10:07:57
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and
does exim on current deb packages support ARC signing? DKIM support is
nice, so i am hoping for ARC too.
randy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## e
and, hours later
DKIM_CANON = relaxed
DKIM_DOMAIN = ${sender_address_domain}
DKIM_F = ${lookup {DKIM_DOMAIN.private} dsearch,ret=full {CONFDIR/dkim}}
DKIM_PRIVATE_KEY = ${if exists{DKIM_F}{DKIM_F}{0}}
DKIM_SELECTOR = rgnet-mail
works
yoiks
--
## subscription configuration (requires account):
#
> 2023-12-10 00:44:14 1rC7vZ-Do-25 Tainted filename
> '/etc/exim4/dkim/psg.com.private'
>
> for
>
> DKIM_CANON = relaxed
> DKIM_DOMAIN = ${sender_address_domain}
> DKIM_PRIVATE_KEY = CONFDIR/dkim/${sender_address_domain}.private
> DKIM_SELECTOR = rgnet-mail
>
> is there a si
2023-12-10 00:44:14 1rC7vZ-Do-25 Tainted filename
'/etc/exim4/dkim/psg.com.private'
for
DKIM_CANON = relaxed
DKIM_DOMAIN = ${sender_address_domain}
DKIM_PRIVATE_KEY = CONFDIR/dkim/${sender_address_domain}.private
DKIM_SELECTOR = rgnet-mail
is there a simple hack?
randy
--
> https://seclists.org/oss-sec/2023/q3/254
i tried putting that in my exim config and it threw errors
Others have excuses, I have my reasons why...
-- Nickel Creek in "Reasons Why"
randy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists
> https://jimbobmcgee.wordpress.com/2020/07/29/de-tainting-exim-configuration-variables/
that bogus lookup("*") is definitely not for post prandial use.
randy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
##
>> 2023-07-30 14:23:11 1qQ7KA-000BIX-27 ** f...@foo.com R=force_uucp T=uux:
>> Tainted
>> arg 4 for uux transport command: '(@foo.com)'
>>
>> uux:
>>driver = pipe
>>command = "/usr/local/bin/uux - -r $host!rmail
>> ($local_part_suffix@$domain)"
>>path = "/usr/local/bin:/usr/bin:/bin"
2023-07-30 14:23:11 1qQ7KA-000BIX-27 ** f...@foo.com R=force_uucp T=uux:
Tainted
arg 4 for uux transport command: '(@foo.com)'
uux:
driver = pipe
command = "/usr/local/bin/uux - -r $host!rmail ($local_part_suffix@$domain)"
path = "/usr/local/bin:/usr/bin:/bin"
return_fail_output
user =
14 matches
Mail list logo
