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
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
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
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
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
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
