Am Do, Okt 8, 2020 at 20:39 schrieb Jeremy Harris via Exim-users
:
On 08/10/2020 17:50, Cyborg via Exim-users wrote:
Am 08.10.20 um 17:11 schrieb Graeme Fowler via Exim-users:
...but if the client never managed to actually connect to Exim,
there is nothing to log.
In this case, you
On 08/10/2020 17:50, Cyborg via Exim-users wrote:
> Am 08.10.20 um 17:11 schrieb Graeme Fowler via Exim-users:
>> ...but if the client never managed to actually connect to Exim, there is
>> nothing to log.
> In this case, you could see the messages exim sent for the smtp session
> with tcpdump,
Am 08.10.20 um 17:11 schrieb Graeme Fowler via Exim-users:
> ...but if the client never managed to actually connect to Exim, there is
> nothing to log.
In this case, you could see the messages exim sent for the smtp session
with tcpdump, but it never showed up in the logs.
and honestly, I don't
Hello.
On Thu, Oct 08, 2020 at 03:55:48PM +0200, Sander Smeenk via Exim-users wrote:
> Our current log_selector looks like this:
>
> log_selector = +all_parents \
> +delivery_size \
> +incoming_interface \
> +incoming_port \
>
Quoting Graeme Fowler via Exim-users (exim-users@exim.org):
> ...but if the client never managed to actually connect to Exim, there is
> nothing to log.
But the client was connected!
It issued EHLO, STARTTLS and -then- boogered off.
> You can already add the log selector "smtp_connection" to
On 8 Oct 2020, at 15:34, Cyborg via Exim-users wrote:
> @Devs: Maybe a nice FR to put a "421 client aborted connection from ip
> x.x.x.x." in the logs.
...but if the client never managed to actually connect to Exim, there is
nothing to log.
You can already add the log selector
On 08/10/2020 15:34, Cyborg via Exim-users wrote:
> @Devs: Maybe a nice FR to put a "421 client aborted connection from ip
> x.x.x.x." in the logs.
Not sure what the significance of the "@" is, nor what an FR might be...
If it was supposed to be an RFE, bugs.exim.org is the place to record
it.
Am 08.10.20 um 15:55 schrieb Sander Smeenk via Exim-users:
> Hi,
>
> Spent a few minutes today figuring out what happens to a certain client
> trying to send mail to our Exim 4.93 #3 MTA since no traces of their IP
> could be found in our logs. But tcpdumping shows the session being
> terminated
Hi,
Spent a few minutes today figuring out what happens to a certain client
trying to send mail to our Exim 4.93 #3 MTA since no traces of their IP
could be found in our logs. But tcpdumping shows the session being
terminated after STARTTLS, with Exim sending '421 lost input connection'
over the
Could you get a debug run using "-d+timestamp" and with
log_selector = +millisec
in the config?
Also, since you think it's the queue-write, you could add queue_only
so that we don't do the delivery (and get the full debug of that).
--
Cheers,
Jeremy
--
## List details at
10 matches
Mail list logo