Mailing List Archive

[Bug 2715] Degradation over time
https://bugs.exim.org/show_bug.cgi?id=2715

--- Comment #1 from Jeremy Harris <jgh146exb@wizmail.org> ---
What aspect of performance - and why do you think Exim is at fault rather
than your PHP or its support environment?

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2715] Degradation over time [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2715

--- Comment #2 from Maiv <matthew.moulds1@gmail.com> ---
The execution time is where we see the delay, if we telnet directly to the port
and form an email there will be a significant delay on a long running exim
service (days not months) compared to a freshly restarted exim service.

I think PHP is exacerbating the issue however, bypassing PHP and executing via
telnet also has a delay of 10+ seconds.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2715] Degradation over time [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2715

--- Comment #3 from Jeremy Harris <jgh146exb@wizmail.org> ---
Get a debug run of such a telnet-client session, by using ACL to turn
on debug for connections from the one source IP. Add +millisec to
log_selector (it affects debug timestamps also). That should show where the
time is being used.

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2715] Degradation over time [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2715

--- Comment #4 from Maiv <matthew.moulds1@gmail.com> ---
2021-04-16 09:16:49.060 1lXJeX-00054H-Eh => <EMAIL> F=<noreply@DOMAIN>
R=dnslookup T=remote_smtp S=1229 H=ASPMX.L.GOOGLE.COM [74.125.140.26]
I=[10.129.1.89] X=TLS1.2:ECDHE-ECDSA-AES128-GCM-SHA256:128 CV=yes
DN="/C=US/ST=California/L=Mountain View/O=Google LLC/CN=mx.google.com" K C="250
2.0.0 OK x12si6529630wrm.351 - gsmtp" QT=11s DT=0.380s
2021-04-16 09:16:49.060 1lXJeX-00054H-Eh Completed

Is there an example of how to enable the debugging for the ACL without having
to restart the service?

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 2715] Degradation over time [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2715

--- Comment #5 from Jeremy Harris <jgh146exb@wizmail.org> ---
You need to tell Exim to reload the config any time you change ACLs. On
many deployments this is something like "service exim reload". Some may
need a restart, not supporting just a reload; this is not under the Exim
project's control.


A suitable example for enabling debug using ACL might be:

acl_smtp_connect = accept control=debug/opt=+all


That assumes you don't already have a connect ACL, and you want to
apply debug to *every* SMTP connection. You could specify a named ACL
and, in that, select a specific source IP.

I suggest you read the documentation at

http://exim.org/exim-html-current/doc/html/spec_html/ch-access_control_lists.html

--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##