Hi Neustradamus,
the initial bug was reported as "Upon upgrading to bionic, amavisd-new DKIM
signing no longer works." so no one thought about former releases.
This also matches that there were no bugs about that issue, prior to Bionic
being released.
Also there is an increased risk the further changes are backported.
In this case all >=Bionic was on 2.11, but Xenial is 2.10 and Trusty even on
2.7.
So even if it happens in older versions the tradeoff between regressions for
current users vs the benefit of the fix for others might be different.
Especially with a somewhat dead upstream and a patch that existed in three
variants - also the test instructions are ok'ish but not totally complete to
try it in different variants. Therefore the risk is too high to apply it
further back (IMHO).
The old patch applies, but with a 788 line offset in a 34k line perl
file - oO
For now - for me personally - this is Won't Fix, but I'm open to be
convinced if we get enough confirmation and confidence in it. So if you
really think the very same issue affects Xenial, please share some
details about why you think so. Do the testing steps above trigger it
for you, if you can add extra details about testing if needed for
Xenial.
** Also affects: amavisd-new (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: amavisd-new (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770532
Title:
DKIM signing not working in bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1770532/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
