It makes perfect sense for a user to trust that a new package version will come with all the features announced upstream.... thanks for bringing up this point.
I checked spamassassin versions and we are in 4.0.0 since Mantic, so new features that can come in -proposed libmail-dkim-perl version are not in use yet:
spamassassin | 3.4.6-1ubuntu0.22.04.1 | jammy-updates | source, all
spamassassin | 4.0.0-7ubuntu1 | mantic | source, all
spamassassin | 4.0.0-8ubuntu1 | noble | source, all
for libmail-dmar-perl is the same case:
libmail-dmarc-perl | 1.20230215-1 | mantic/universe | source, all
libmail-dmarc-perl | 1.20230215-1 | noble/universe | source, all
Only for the records, the changes that come with the dkim -proposed version are:
1.20240124 2024-01-24 UTC
* ARC: Return fail for any ARC set with an instance number greater than 50.
This brings ARC verification in line with DKIM verification limits.
1.20230911 2023-09-11 UTC
* Option to add custom tags to generated ARC signatures and seals
1.20230630 2023-06-30 UTC
* Add support for Ed25519 signature types
Thanks to Matthäus Wander @mwander
* Option to add custom tags to generated signatures
So I'm okay with adding libmail-dkim-perl to the sync-blocklist.
Thanks Andreas!
It makes perfect sense for a user to trust that a new package version will come with all the features announced upstream.... thanks for bringing up this point.
I checked spamassassin versions and we are in 4.0.0 since Mantic, so new features that can come in -proposed libmail-dkim-perl version are not in use yet:
spamassassin | 3.4.6-1ubuntu0. 22.04.1 | jammy-updates | source, all
spamassassin | 4.0.0-7ubuntu1 | mantic | source, all
spamassassin | 4.0.0-8ubuntu1 | noble | source, all
for libmail-dmar-perl is the same case:
libmail-dmarc-perl | 1.20230215-1 | mantic/universe | source, all
libmail-dmarc-perl | 1.20230215-1 | noble/universe | source, all
Only for the records, the changes that come with the dkim -proposed version are:
1.20240124 2024-01-24 UTC
* ARC: Return fail for any ARC set with an instance number greater than 50.
This brings ARC verification in line with DKIM verification limits.
1.20230911 2023-09-11 UTC
* Option to add custom tags to generated ARC signatures and seals
1.20230630 2023-06-30 UTC
* Add support for Ed25519 signature types
Thanks to Matthäus Wander @mwander
* Option to add custom tags to generated signatures
So I'm okay with adding libmail-dkim-perl to the sync-blocklist.