[exim] Re: No immediate delivery for emails locally submitted in systemd unit

2023-09-01 Thread Jasen Betts via Exim-users
On 2023-09-01, Andreas Metzler via Exim-users wrote: > On 2023-09-01 Slavko via Exim-users wrote: > [...] >> You have several options: > >> + use forking type unit (not appropriate in all cases) >> + disable kill in unit (not very good idea) >> + setup sendwait in mailx (not with bsd-mailx) >> +

[exim] Re: No immediate delivery for emails locally submitted in systemd unit

2023-09-01 Thread Andreas Metzler via Exim-users
On 2023-09-01 Slavko via Exim-users wrote: [...] > You have several options: > + use forking type unit (not appropriate in all cases) > + disable kill in unit (not very good idea) > + setup sendwait in mailx (not with bsd-mailx) > + use exim directly with -odf > + use cron for repeated tasks + I

[exim] Re: No immediate delivery for emails locally submitted in systemd unit

2023-09-01 Thread Slavko via Exim-users
Ahoj, Dňa Thu, 24 Aug 2023 19:46:50 +0200 Charles Leclerc via Exim-users napísal: > I've tried looking in the configuration but didn't find anything. Why > would delivering of identical, locally submitted emails, differ ? I will guess only, but exim is forking transport process for delivery, b

[exim] No immediate delivery for emails locally submitted in systemd unit

2023-09-01 Thread Charles Leclerc via Exim-users
Hello, I have a very strange behaviour on my exim servers (debian 11, version 4.94.2). I have systemd timers and units which send email in case of error. When email is submitted this way, it is placed on the exim queue without being immediately delivered and waits the next queue run as specif

[exim] Re: Inconsistent detection of tainted command in ${run} 4.96

2023-09-01 Thread Tapio Peltonen via Exim-users
On Fri, 1 Sept 2023 at 10:50, Andrew Hearn via Exim-users wrote: > > Hi mailing list, > > We have an external tool for checking user authentication, but running > it seems to be labelled as tainted inconsistently after upgrading to > 4.96. > > Here is our PLAIN auth: > > plain: >driver = plai

[exim] Re: Inconsistent detection of tainted command in ${run} 4.96

2023-09-01 Thread Jeremy Harris via Exim-users
On 01/09/2023 08:48, Andrew Hearn via Exim-users wrote: If it's by design is there any more documentation about how ${run} is expanded please? The docs I'm looking at, https://exim.org/exim-html-current/doc/html/spec_html/ch-string_expansions.html say, for ${run...} :- "If the option preexpan

[exim] Inconsistent detection of tainted command in ${run} 4.96

2023-09-01 Thread Andrew Hearn via Exim-users
Hi mailing list, We have an external tool for checking user authentication, but running it seems to be labelled as tainted inconsistently after upgrading to 4.96. Here is our PLAIN auth: plain: driver = plaintext public_name = PLAIN server_prompts = : server_condition = ${run,preexp

[exim] Inconsistent detection of tainted command in ${run} 4.96

2023-09-01 Thread Andrew Hearn via Exim-users
Hi mailing list, We have an external tool for checking user authentication, but running it seems to be labelled as tainted inconsistently after upgrading to 4.96. Here is our PLAIN auth: plain: driver = plaintext public_name = PLAIN server_prompts = : server_condition = ${run,preexp