Hi there, @Rafa is right, the recipient domain has 2 MX-es and in case of that first message, I don't wan't to my any retry on other MX. The issue it that the deferred message does not contain this very first message so I can't see it during my log analysis (bases on log message with 'to' and 'status')
@Matus : I am caching connections on all my transports and optimizing the max concurrency... So this kind of issue is really really exceptional... It just happens last time because I was sending too few messages per connection. I just need to put that message in a complete log line with 'to' and 'status'. Regards, Le mar. 12 avr. 2022 à 13:58, Jarosław Rafa <r...@rafa.eu.org> a écrit : > W dniu wto, 12.04.2022 o godzinie 13∶52 +0200, użytkownik Matus UHLAR - > fantomas napisał: > > On 12.04.22 11:21, Yves-Marie Le Pors Chauvel wrote: > > > Using Postfix 3.5.6 on debian 11, I would like to know if there is > > > any > > > possibility not to use an alternative MX for outbound email > > > > MX is for inbound e-mail by definition > > I think what the OP meant is that recipient domain has two MX-es and > the goal is that the Postfix doesn't try the second MX in case the > first one rejects with 4xx but defers the message immediately (for > this specific recipient domain). > -- > Regards, > Jaroslaw Rafa > r...@rafa.eu.org > -- > "In a million years, when kids go to school, they're gonna know: once there > was a Hushpuppy, and she lived with her daddy in the Bathtub." > > -- Yves-Marie LE PORS-CHAUVEL Email Product Manager *T: +33 2 23 45 57 99* (3043) 23, rue du Bignon - 35 135 Chantepie www.ccmbenchmark.com
