Re: [exim] multiple cc: headers

2022-05-09 Thread Slavko via Exim-users
Dňa 9. 5. o 10:53 Julian Bradfield via Exim-users napísal(a): I'd never seen this before, so I went off to check RFC5822, and I see that in the 5822 version, only one of the To:, CC: or BCC: headers is allowed to be generated. RFC 5822 doesn't exists. However, the RFC says that

[exim] multiple cc: headers

2022-05-09 Thread Julian Bradfield via Exim-users
I've just had a bounce from the MTA running on mx1.solardns.com, which advertises itself as Exim 20220503.1020 The bounce was: 550 Messages should have one or no Cc headers, not 2 I'd never seen this before, so I went off to check RFC5822, and I see that in the 5822 version, only one of the

Re: [exim] multiple cc: headers

2022-05-09 Thread Jeremy Harris via Exim-users
On 09/05/2022 09:53, Julian Bradfield via Exim-users wrote: Coming to the point: is the bounce message coming from some (hopefully experimental) part of Exim, or must it have been maliciously hand-crafted in a config file by the solardns administrators? I can't find anything relevant in the

Re: [exim] multiple cc: headers

2022-05-09 Thread Graeme Fowler via Exim-users
On 9 May 2022, at 09:53, Julian Bradfield via Exim-users wrote: > Coming to the point: is the bounce message coming from some (hopefully > experimental) part of Exim, or must it have been maliciously > hand-crafted in a config file by the solardns administrators? > > I can't find anything

Re: [exim] multiple cc: headers

2022-05-09 Thread Julian Bradfield via Exim-users
On 2022-05-09, Slavko via Exim-users wrote: > Dňa 9. 5. o 10:53 Julian Bradfield via Exim-users napísal(a): >> I'd never seen this before, so I went off to check RFC5822, and I see >> that in the 5822 version, only one of the To:, CC: or BCC: headers is >> allowed to be generated. > > RFC 5822

Re: [exim] multiple cc: headers

2022-05-09 Thread Slavko (tblt) via Exim-users
Dňa 9. mája 2022 11:37:35 UTC používateľ Julian Bradfield via Exim-users napísal: >My error - google autocorrected me to 5322 and I didn't >notice. (Happens every time...) No problem, it happens, only to be sure what was the typo, in that case, it was nice, because one can guess the 5 as typo

[exim] Spurious "BDAT command used when CHUNKING not advertised"?

2022-05-09 Thread Jesse Hathaway via Exim-users
Just recently, starting on May 4th, we began bouncing some messages from Gmail with the following error: 2022-05-09 15:32:48 H=mail-lj1-x234.google.com [2a00:1450:4864:20::234]:46864 I=[2620:0:861:3:208:80:154:76]:25 X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no F= rejected

[exim] test Mon, 09 May 2022 16:50:44 -0500

2022-05-09 Thread Martin McCormick via Exim-users
swaks test -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/

Re: [exim] Spurious "BDAT command used when CHUNKING not advertised"?

2022-05-09 Thread Jesse Hathaway via Exim-users
On Mon, May 9, 2022 at 4:44 PM Jesse Hathaway wrote: > We are currently running exim 4.94 on Debian. In trying to understand the root > cause of the issue I noticed a recent commit included in 4.96: I forgot to mention that disabling chunking stopped the bounces. -- ## List details at

Re: [exim] Spurious "BDAT command used when CHUNKING not advertised"?

2022-05-09 Thread Jeremy Harris via Exim-users
On 09/05/2022 22:44, Jesse Hathaway via Exim-users wrote: Just recently, starting on May 4th, we began bouncing some messages from Gmail with the following error: 2022-05-09 15:32:48 H=mail-lj1-x234.google.com [2a00:1450:4864:20::234]:46864 I=[2620:0:861:3:208:80:154:76]:25