This just bit me too on an upgrade to testing now pulling in postgrey. This is a serious problem because changing the port under postfix gives you an invalid SMPT configuration ... it won't just time out on the check, it returns a 451 invalid SMTP config to all callers. This doesn't get fixed until the admin checks the log and notices the problem.
You can't seriously be a server distribution if you're going to do something as stupid as break a standard postfix/postgrey/clamav/spamassassin setup without warning: That's the gold standard for debian based email servers on the internet. You cannot allow this to go into stable ... and a warning isn't enough, it would have to be a preconfig that forces the admin to pay attention (or preferably something that detects postfix is using a different port). James Bottomley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
