If you pipeline to yahoo, you will almost always have issues. They somewhat greylist all servers sending to them using pipelining. To be honest, enabling pipelining will very often lead to unexpected issues. IMHO, they should just remove that feature. That's of course no excuse for breaking it ;) Thanks for keeping me informed.
22 oct. 2021 17:10:03 Stuart Henderson <s...@spacehopper.org>: > Only a minor one in that they've broken something with pipelining resulting > in multiple copies of mail getting delivered in some cases, see the open > ticket about yahoo.co.jp[http://yahoo.co.jp], and I was waiting to see if > they were going to do anything with it before I committed the update.. > > -- > Sent from a phone, apologies for poor formatting. > > > On 22 October 2021 08:46:42 Renaud Allard <ren...@allard.it> wrote: > >> Is there a major problem with that diff? >> >> On 10/6/21 8:49 AM, Renaud Allard wrote: >>> ping >>> >>> >>> -------- Forwarded Message -------- >>> Subject: [update] mail/exim -> 4.95 >>> Date: Wed, 29 Sep 2021 08:40:40 +0200 >>> From: Renaud Allard <ren...@allard.it> >>> To: ports <ports@openbsd.org> >>> >>> Hi, >>> >>> This is an update for mail/exim to version 4.95. >>> >>> It includes the patch from sthen@ to disable the printf %n checks (by >>> default in 4.95 source). >>> It also includes a patch to be able to compile properly with libressl >>> 3.4.0, therefore removing the hack in the Makefile >>> The specific OpenBSD os.h patch can also be removed as this has been >>> included in exim by default too. >>> >>> Best Regards >>> >
smime.p7s
Description: S/MIME cryptographic signature
