Jeroen van Aart via Exim-users <exim-users@???> (Sa 12 Mai 2018 01:30:05 CEST): > For about a decade I have been using a configuration which routes email
> submitted on port 587 to port 24 on localhost, on which exim is listening as
> well. It then will be sent out.
First, why don't you send it imediatly, instead of doing that "loop
routing"?
> I do this using the following configuration:
>
> smarthost:
> debug_print = "R: smarthost for $local_part@$domain"
> driver = manualroute
> domains = ! +local_domains
> transport = remote_smtp_smarthost
> route_list = * DCsmarthost byname
> host_find_failed = defer
> same_domain_copy_routing = yes
> no_more
> self = send
>
>
> This has been working great for many years. However the last couple of years
> I tend to get the following behaviour every now and then or very often,
> depending:
>
> 2018-05-11 11:59:20 2qHDGC-0004TT-26 <= example@???
You should not obfuscate, please.
> H=host.example.org [192.0.2.1] P=esmtpsa
> X=TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256 A=login_saslauthd_server:example S=786
> id=3a16b96b-172c-36d6-c06c-04aa4b1e4d6e@???
> 2018-05-11 11:59:20 2qHDGC-0004TT-26 127.0.0.1 [127.0.0.1] Connection reset
> by peer
> 2018-05-11 11:59:20 2qHDGC-0004TT-26 == control@??? R=smarthost
> T=remote_smtp_smarthost defer (104): Connection reset by peer
> 2018-05-11 12:07:11 Start queue run: pid=17411
If the refusal would be caused by "overloaded" Exim, there would be a
response like "4xx too many SMTP connections" or similar.
Are you sure, that an Exim instance is listening your local port 24
always? What does `exiwhat` tell you?
Does the Exim "server" process log something? The +pid log_selector may
help.
> My question is how can I configure exim to stop refusing and deferring the
> connection to itself at 127.0.0.1 port 24 and send it out right away?
> Removing the retry file and restarting exim did not work.
