>
>Hello,
>In my opinion, an option c) should be considered.
>Bogus or not, if a Message-ID is present in the header you should not touch it.
>For it own use, dovecot should continue to not use it as it is bogus.The only
>thing to do is to warn in logs in the dovecot core.
>In a forwarding scenari
Le 02/10/2022 à 06:35, Sébastien Riccio a écrit :
Hi,
After reading a bit the code and trying to understand it, here is what
I think happens here:
Given a bogus Message-ID, for example (notice it's missing angle
brackets < >:
Message-ID:
1883biz_pay_after_purchase:0:0_572392900$ae7ed6e4d5
On 2022-10-01 22:59, michael.z...@feierfighter.de wrote:
Hi Zakaria,
I'm very happy about your email to the mailing list, I thought I'm
alone with my problem, and it's nice to see that the problem might be
a bug/problem in pigeonhole. I was not sure about it because I didn't
get a technical answ
