Hi Peter,
I believe the security team were stuck between this behaviour and
leaving users vulnerable. See http://www.ubuntu.com/usn/usn-2933-1/ for
details. There's also information in
/usr/share/doc/exim4-config/NEWS.Debian.
If there's some way to solve this that fixes the security problem and
also doesn't hit some users with customised configurations then we'd
love to hear it. But otherwise, this was known by the security team at
the time of issuing the update, and the alternative of not leaving users
vulnerable was chosen, so I'm marking this bug as Won't Fix.
If you can propose some other solution, please do so and set the bug
status back to New. Thanks!
** Changed in: exim4 (Ubuntu)
Status: New => Won't Fix
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558310
Title:
Latest updated stopped exim4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1558310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
