Well, well, well.
I am certainly not used to debian packages breaking my systems without a
warning. In this case I realized something was wrong only after users
started to complain that they were not receiving any mail from outside.
After that it was not difficult to find hte cause of the error and
correct it.
I consider this a serious flaw. There definitely should be some kind of
a warning that "springs to the eye" if a package is probable to stop
acting the way it's supposed to. How about a debconf warning *without* a
grep? If you don't know how to accomplish this. Just letting mailservers
die and waiting for people to notice is not very admin-friendly :-/
Otherwise, thanks for the package. It is an awfully useful piece of
software that reliably keeps away at least 95% of our spam.
Best wishes, Erwin
--
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Erwin Rennert, IT Services
Center for Social Innovation
A-1150 Wien, Linke Wienzeile 246
Austria, Europe
Phone: ++43-1-495 04 42 - 61
Facsimile: ++43-1-495 04 42 - 40
http://www.zsi.at/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
