We are having a fair amount of duplicate Message-id problems from alibaba / aliexpress. I would like to get this solved. I am happy to pay for pigeonhole to be updated / sponsor this fix. I tried to sign up for support and the website hangs. Does anyone have any suggestions on how to help move this along?
EnglishDuplicate Message-ID header generated by Sieve redirect
I can’t help with your problem, but I was wondering why mailcow contained an older version of Pigeonhole, especially since mailcow simply installs the Alpine Linux package of dovecot-pigeonhole-plugin when 
building the Dovecot Docker image. GitHub
Also it is the lastest package available (see the .21):
root@mailcow# docker compose exec dovecot-mailcow apk info dovecot-pigeonhole-plugin
dovecot-pigeonhole-plugin-2.3.21-r17 description:
Sieve and managesieve plugin for DovecotBut looking at the respective Alpine package souces
, they are explicitly using git.alpinelinux.org
dovecot-pigeonhole-0.5.19.tar.gz to build the Pigeonhole sub-package for Dovecot.
According to the 0.5.21 release notes
, Dovecot indeed fixed a problem with Message-ID headers. dovecot.org
0.5.20 (and even 0.5.19) were just releases to keep the version numbers synced between Dovecot and Pigeonhole. GitHub
Long story short: If this fix in 0.5.21 is the solution to your problems, either Alpine must update their package sources to .21 (which would also be less misleading regarding the version number) or mailcow should use a different way to install the current version of Pigeonhole.
- Edited
accolon Thank you for all of that explanation. This makes a lot of sense as to why the older version is happening.
Ideally, it would be great to get pigeonhole updated so the fix is elegant. I see there is lobbying of other groups that may be necessary.
Less ideally here is the scenario:
The original email comes in with this message-id:
Message-ID: 9833819030155984$ba6dfc7f00d0457e96aaa5b6ecb7a02e
Because it is malformed a new message-id is added to the headers like
Message-ID: <dovecot-sieve-1720341929-837352-1@72f9e7376ada>
Then reputable mail servers reject the forward on the basis that there are multiple message-ids. Any work around hack idea where I can remove one of the message-ids in a way that I can comment out later when the fix ultimately makes it out?
5 days later
I’ve added the following at the end of
data/conf/postfix/anonymize_headers.pcre
as a VERY hacky solution for the moment, that solved the issue:
/^(?i)Message-ID:\s+<dovecot-sieve.*?@.*?>/ IGNORE
Don’t forget to reload postfix with:
docker compose exec postfix-mailcow postfix reload
Mechanic - I love you. It works perfectly until a proper solution is implemented.
Thank you.
It looks like an upgraded Alpine package should be available soon:
main/dovecot: upgrade pidgeonhole to 0.5.21 - aports - Alpine packages build scripts
git.alpinelinux.org
Thanks for the heads up. I requested they update the version and I also filed a support ticket with mailcow who said they would request it as well. Happy to see everyone working together.
6 days later
It would be great to see this finally resolved, looks like there might be some light at the end of the tunnel!
6 months later
Bump! still not resolved in version 2025-01…
mechanic
Please bump the issue on github (or open an issue)
No one is typing