<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style id="signatureStyle" type="text/css"><!--#x07bf846aa0cf48a #xc42d577871334d2cbca17ccda13140c5 p.MsoNormal
{margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;}
#x07bf846aa0cf48a #xc42d577871334d2cbca17ccda13140c5 a:link
{color: rgb(5, 99, 193); text-decoration: underline;}
#x07bf846aa0cf48a #xc42d577871334d2cbca17ccda13140c5 a:visited
{color: rgb(149, 79, 114); text-decoration: underline;}
--></style><style id="css_styles" type="text/css"><!--blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: center; '], li[style='text-align: right;'], li[style='text-align: right; '] { list-style-position: inside;}
body { font-family: 'Segoe UI'; font-size: 12pt; }
.quote { margin-left: 1em; margin-right: 1em; border-left: 5px #ebebeb solid; padding-left: 0.3em; }
--></style>
</head>
<body>
<div><br>
</div>
<div id="xb4791814b3b9402">
<blockquote cite="20221001124913.E5D52A6327@smtp02.mail.de" type="cite" class="cite2">
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi there,</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I can confirm this behavior. A few months ago I introduced a milter which is checking for multiple headers when the RFC says that there just should be one of them For example "Message-Id".</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I found the described problem in an email coming from Alibaba, which had an invalid "Message-Id" header. It didn't contain an "@" sign or similar. It was RFC-invalid.</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
This email was sent from Alibaba to a German email provider. There was a redirect at that email provider, pointing to my mailserver.</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
My server rejected the email because there were 2 "Message-Id" headers: The original invalid "Message-Id" header from Alibaba, and a new "Message-Id" header from the German provider, which seems to have been added during the redirect. There were "Dovecot-sieve"
headers in that mail, so my guess was that it happened because of Dovecot-sieve/pigeonhole implementation.
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I contacted the email provider, asking for help. Asking if it really is a bug in pigeonhole (or maybe some other system at that provider, who knows). And I contacted Alibaba, so they fix the invalid "Message-Id". I got responses from both, but until now, as
far as I can see, it has not been fixed. </div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The best fix would be (if it really is a bug in pigeonhole), if pigeonhole fixes the problem, then it's fixed for all users of Dovecot. I guess Alibaba is not the only sender with an invalid "Message-ID" header, but that's the only one I saw.</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Michael</div>
<div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div><br>
</div>
</blockquote>
<div id="xb4791814b3b9402">Hello Michael,</div>
<div id="xb4791814b3b9402"><br>
</div>
<div id="xb4791814b3b9402">Thanks a lot for your feedback. It comfort me that I'm maybe on the right track about this issue.</div>
<div id="xb4791814b3b9402"><br>
</div>
<div id="xb4791814b3b9402">The mail I used to troubleshoot the issue was a mail from aliexpress containing a funky Message-ID. Probably the same people behind Aliexpress/Alibaba.</div>
<div id="xb4791814b3b9402">But for sure there are probably other mail senders that generate RFC-invalide Message-ID.</div>
<div id="xb4791814b3b9402"><br>
</div>
<div id="xb4791814b3b9402">If Pigeonhole consider the Message-ID is bad and add it's own, it should maybe at least remove the original one... ?</div>
<div id="xb4791814b3b9402"><br>
</div>
<div id="xb4791814b3b9402">Kind regards</div>
</div>
</body>
</html>