[exim] Re: How to tell which authentication is failing when doing authenticated binds

This is truly puzzling. I've changed out my authenticator to add parameters where I think they should go: server_condition = ${if and{ \ { !eq{}{$auth1} } \ { ldapauth { \ user=${lookup ldapdn{user="CN=outer_account,OU=SVCAccounts,OU=ITS,OU=Organizations,DC=ad,DC=ualr,DC=edu" pas

[exim] Re: How to tell which authentication is failing when doing authenticated binds

This makes sense, and yet, I've tried adding {true}{false} (along with {yes}{no} and now it is failing when I use good account information. I've tried this, which I believe should be right: user=${lookup ldapdn{user="CN=svc_domainjoin,OU=SVCAccounts,OU=ITS,OU=Organizations,DC=ad,DC=example,DC=com"

[exim] Re: How to tell which authentication is failing when doing authenticated binds

On Fri, Apr 11, 2025 at 6:22 PM Slavko via Exim-users < exim-users@lists.exim.org> wrote: > Dňa 10. 4. o 23:04 Johnnie W Adams via Exim-users napísal(a): > > > The coding should take both of the 'foo's in, because they are the > > credentials to be used in

[exim] Re: How to tell which authentication is failing when doing authenticated binds

On Fri, Apr 11, 2025 at 11:52 AM Chris Siebenmann via Exim-users < exim-users@lists.exim.org> wrote: > > On Thu, Apr 10, 2025 at 09:06:34PM +0100, Jeremy Harris via Exim-users > wrote: > > > On 2025/04/10 8:19 PM, Johnnie W Adams via Exim-users wrote: > > > > 1

[exim] How to tell which authentication is failing when doing authenticated binds

Hi, I'm following the information in the manual section 9.11.4 and getting a 435 Unable to authenticate at present message when I test on the command line. How do I determine if it's the bind auth or the real auth that's failing? Thanks, John A -- John Adams Senior Linux/Middle

[exim] Re: How to tell which authentication is failing when doing authenticated binds

On Thu, Apr 10, 2025 at 3:42 PM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 2025/04/10 9:31 PM, Johnnie W Adams via Exim-users wrote: > > That combination should be user=foo password=foo, because that's what I'm > > putting into openss

[exim] Re: How to tell which authentication is failing when doing authenticated binds

On Thu, Apr 10, 2025 at 3:07 PM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 2025/04/10 8:19 PM, Johnnie W Adams via Exim-users wrote: > > 14:16:37 121712 re-binding with user= password=foo > > > > 14:16:37 121712 Bind succeeded: ldapauth r

[exim] Re: How to tell which authentication is failing when doing authenticated binds

nted) 14:16:37 121712 SMTP>> 235 Authentication succeeded 14:16:37 121712 tls_write(0x56246e2fd368, 30) 14:16:37 121712 SSL_write(0x56246e60e870, 0x56246e2fd368, 30) 14:16:37 121712 outbytes=30 error=0 14:16:37 121712 Calling SSL_read(0x56246e60e870, 0x56246e611768, 409

[exim] Re: How to tell which authentication is failing when doing authenticated binds

t permitted - contact IT Services for assistance domains = +local_domains : +relay_to_domains require verify = recipient accept Thanks, John A On Thu, Apr 10, 2025 at 11:07 AM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 2025/04/10 4:43 PM, Johnnie W Ada

[exim] Re: How to tell which authentication is failing when doing authenticated binds

120872 SMTP>> 235 Authentication succeeded On Thu, Apr 10, 2025 at 9:31 AM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 2025/04/10 3:00 PM, Johnnie W Adams via Exim-users wrote: > > I don't know how much of the configuration you want to see, but

[exim] Re: How to tell which authentication is failing when doing authenticated binds

John A On Thu, Apr 10, 2025 at 5:21 AM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 2025/04/09 9:49 PM, Johnnie W Adams via Exim-users wrote: > > What is strange is that I have made this work; however, I get 235 > > Authentication succeede

[exim] Re: How to tell which authentication is failing when doing authenticated binds

Hi, I'm following up on this now that I've gotten a little further and am getting a very strange result. What is strange is that I have made this work; however, I get 235 Authentication succeeded when I put in bad account information. It's almost as though Exim is seeing the bind authen

[exim] Re: How to tell which authentication is failing when doing authenticated binds

As you can see, using "foo" and "bar" as my account information gets me authenticated: AUTH LOGIN 334 VXNlcm5hbWU6 Zm9v 334 UGFzc3dvcmQ6 YmFy 235 Authentication succeeded On Wed, Apr 9, 2025 at 3:49 PM Johnnie W Adams wrote: > Hi, > > I'm following up on this now that I've gotten a li

[exim] Re: exim -bh giving unexpected results

ect? On Tue, Feb 25, 2025 at 10:48 AM Johnnie W Adams wrote: > Thanks! That's got me on the right path now. > > On Tue, Feb 25, 2025 at 10:43 AM Evgeniy Berdnikov via Exim-users < > exim-users@lists.exim.org> wrote: > >> On Tue, Feb 25, 2025 at 10:03:45AM -0600, Johnnie

[exim] Re: exim -bh giving unexpected results

Thanks! That's got me on the right path now. On Tue, Feb 25, 2025 at 10:43 AM Evgeniy Berdnikov via Exim-users < exim-users@lists.exim.org> wrote: > On Tue, Feb 25, 2025 at 10:03:45AM -0600, Johnnie W Adams via Exim-users > wrote: > > I'm troubleshooting an a

[exim] exim -bh giving unexpected results

Hi, I'm troubleshooting an acl and having an issue using exim -bh. Here's the command line: exim -d+acl -bh 100.10.10.10.587 -oMai allo...@example.com Here's the acl that's failing (not the one I'm trying to troubleshoot): acl_check_connect: denymessage = Connection no

[exim] Suddenly getting "R=smarthost T=remote_smtp defer (-54) DT=0s: retry time not reached for any host for"

Hi, folks, I've suddenly started getting errors like "R=smarthost T=remote_smtp defer (-54) DT=0s: retry time not reached for any host for" in our ingress node. I haven't changed anything on it recently other than unratelimiting a specific node; on our egress node, I've added smtp_accept_queu

[exim] Re: Exim logging--how reliable?

On Fri, Oct 4, 2024 at 2:58 PM Jeremy Harris via Exim-users < exim-users@lists.exim.org> wrote: > On 04/10/2024 19:04, Johnnie W Adams via Exim-users wrote: > > The SIEM claims that ports 587 and 465 > > are generating traffic on a high-numbered port. > > Urghh. P

[exim] Re: Exim logging--how reliable?

któbra 2024 18:04:31 UTC používateľ Johnnie W Adams via Exim-users > napísal: > > > I'm trying to interpret some results from an SIEM regarding our Exim > >servers and am having difficulty. The SIEM claims that ports 587 and 465 > >are generating traffic o

[exim] Exim logging--how reliable?

Hi, folks, I'm trying to interpret some results from an SIEM regarding our Exim servers and am having difficulty. The SIEM claims that ports 587 and 465 are generating traffic on a high-numbered port. I think it's seeing artifacts from failed authentications and, in about two-thirds of the ca

[exim] Not staying enabled over reboot

Hi, folks, EPEL's exim 4.96|7 is not staying enabled through a reboot on my RHEL 7 servers. Has anyone else seen this? Have you found a way to cope with it? It's very strange. I'm a big fan of systemd and not used to it acting up. Thanks, John A -- John Adams Senior Linux/Middl

[exim] Fwd: Can I tell exim to accept messages and queue them rather than send them on?

Hi, folks, The man page wasn't helpful for this. I'm going to be replacing our mail nodes over the next few weeks and I've been sequencing events in the move. It would be very handy if it were possible to tell one of my nodes to keep accepting mail but to stop trying to deliver it. Can

[exim] Re: Fwd: Upon applying 4.96-1 on test, "Tainted arg 2" appears

value for $domain should be test.ualr.edu, not lists.test.ualr.edu, and I'm unsure where the bad value is coming from. On Thu, Nov 9, 2023 at 1:27 PM Evgeniy Berdnikov via Exim-users < exim-users@lists.exim.org> wrote: > On Thu, Nov 09, 2023 at 01:03:50PM -0600, Johnnie W Adams

[exim] Re: Fwd: Upon applying 4.96-1 on test, "Tainted arg 2" appears

hem). What am I missing? On Thu, Nov 9, 2023 at 12:38 PM Evgeniy Berdnikov via Exim-users < exim-users@lists.exim.org> wrote: > On Thu, Nov 09, 2023 at 10:29:46AM -0600, Johnnie W Adams via Exim-users > wrote: > > Thanks! That's got me almost there. This works when I test wi

[exim] Re: Fwd: Upon applying 4.96-1 on test, "Tainted arg 2" appears

dc=edu?cn(mail=$%7Bquote_ldap:$local_part@$domain%7D)%7Dfail> > }" > > 09.11.23 18:29, Johnnie W Adams via Exim-users: > > Thanks! That's got me almost there. This works when I test with exim -be, > > but in exim.conf, it fails with missing lookup type: > > &g

[exim] Re: Fwd: Upon applying 4.96-1 on test, "Tainted arg 2" appears

tserv/bin/lsv_amin /opt/lsoft/listserv/spool > ${lookup ldap{...}{$value}fail}" > > 08.11.23 22:11, Johnnie W Adams via Exim-users: > > I believe I understand what I'm to do here--use LDAP to look up the > > $local_part and return it, thus untainting it--but I'm fi

[exim] Fwd: Upon applying 4.96-1 on test, "Tainted arg 2" appears

I believe I understand what I'm to do here--use LDAP to look up the $local_part and return it, thus untainting it--but I'm finding the examples in the documentation less than clear. Can someone point me elsewhere? On Wed, Nov 8, 2023 at 8:44 AM Kurt Jaeger wrote: > Hi! > > > I applied 4.96-

[exim] Upon applying 4.96-1 on test, "Tainted arg 2" appears

Hi, folks, I applied 4.96-1 to our test systems and routing to the LISTSERVer began to fail with "*Tainted arg 2* for listserv_transport transport command: The transport is quite simple: # Hand off to LISTSERV lsv_admin script listserv_transport: driver = pipe command = "/opt/l

[exim] Re: Fwd: Requires: libpcre2-8.so.0()(64bit)

I eventually figured that out, but am now frustrated that it will. not. install for some reason. But I'll fix that. On Wed, Oct 11, 2023 at 3:46 PM Tim Jackson via Exim-users < exim-users@lists.exim.org> wrote: > On 11/10/2023 21:47, Johnnie W Adams via Exim-users wrote: > &

[exim] Re: Fwd: Requires: libpcre2-8.so.0()(64bit)

ote: > On 11/10/2023 20:51, Johnnie W Adams via Exim-users wrote: > > > I was installing 4.96.1 on my dev systems and hit this dependency > > problem: Requires: libpcre2-8.so.0()(64bit). I'm not finding it in any of > > the usual places (RHEL, EPEL). > > What OS/v

[exim] Fwd: Requires: libpcre2-8.so.0()(64bit)

Hi, folks, I was installing 4.96.1 on my dev systems and hit this dependency problem: Requires: libpcre2-8.so.0()(64bit). I'm not finding it in any of the usual places (RHEL, EPEL). Where would you recommend getting it from? Thanks, John A -- John Adams Senior Linux/Middleware A

[exim] Mitigation statement for CVE-2023-42119

Hi, folks, What I take from this mitigation statement--Use a trustworthy DNS resolver which is able to validate the data according to the DNS record types--is that if our DNS service is solid, we are not vulnerable. Is this accurate, or am I oversimplifying things? The mitigation statement fr