Am 18.01.2015 um 06:14 schrieb Viktor Dukhovni:
On Sun, Jan 18, 2015 at 12:02:24AM -0500, Scott Kitterman wrote:
better make a bugreport at your distribution
https://www.google.at/search?q=postfix+debian+chroot+problems
Assuming this is Debian, there's no bug report needed. It's an intentional
maintainer choice and not a bug.
I think the "intentional maintainer choice" has long proved unwise.
So though not a bug, it is definitely misfeature. Since the default
chroot is far from seamless:
- Lost logs
- Milter socket problems
- SASL problems
- DNS resolution problems
- ...
If the level of integration were such that none of these issues
were to ever happen, I'd accept this as a valid maintainer choice.
Given that problems come up all the time, I rather see this is a
maintainer mistake that should finally be corrected.
Chroot is for experts willing and able to figure out what needs to
be done to get it working. As a default Debian/Ubuntu configuration
I think it just needlessly gives Postfix on these systems a bad
name.
that's all true
but if each and every day a new user opens a fresh bugreport claiming
the defualts are broken and stupid over the time the "intentional
maintainer choice" may change
that won't happen by explain the same porblem on that list each week
______________________________________
honestly postfix is not completly innocent because the internal default
should be "no" for "-" instead "yes", i saw way too much people believe
it's disabled untill someone explained that this is only the case with
an explicit "n"
having it enabled builtin but with the shipped default config disabled
is not really the best way to explain people it's a bad idea enable it
until you know exactly what you are doing
