Bug#506122: postgrey: Postgrey port number changes without warning on upgrade
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
Bug#506122: postgrey: Postgrey port number changes without warning on upgrade
Package: postgrey Version: 1.32-2 Severity: important The default port in use by postgrey has changed from 6 to 10023. If /etc/default/postgrey was not changed locally, it will be overwritten by a new version without warning. On restart, postgrey will be listening on a different port, which breaks mail delivery. A quick grep for '6' in /etc/postfix/main.cf would be an excellent indication that a warning should be issued to the user. Or even that the port in use should be left alone. Thanks, Bill Gribble -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.16.33-xenU (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages postgrey depends on: ii adduser 3.110 add and remove users and groups ii libberkeleydb-perl0.34-1+b1 use Berkeley DB 4 databases from P ii libnet-dns-perl 0.63-2 Perform DNS queries from a Perl sc ii libnet-server-perl0.97-1 An extensible, general perl server ii perl 5.10.0-17 Larry Wall's Practical Extraction ii ucf 3.0010 Update Configuration File: preserv Versions of packages postgrey recommends: ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith ii libnet-rblclient-perl 0.5-2 Queries multiple Realtime Blackhol pn libparse-syslog-perl none (no description available) ii postfix 2.5.5-1.1 High-performance mail transport ag postgrey suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506122: postgrey: Postgrey port number changes without warning on upgrade
Hi, (Yes, I've been waiting for that bug ;-) NEWS.Debian is there for a reason ... so the change was not without warning. Unfortunately, NEWS.Debian being displayed is not mandatory. I guess a debconf warning based on grep might work, although I think debconf is not the ideal way to handle this. The best would probably be to handle ucf in a way to not replace an unmodified configuration file but instead mark it as being modified and register the new one as the unmodified variant. I'm not exactly sure how this is to be implemented, though (bad maintainer, sorry) I'd be happy if some other people could comment on this. cheers -- vbi On Tuesday 18 November 2008 15.49:29 Bill Gribble wrote: Package: postgrey Version: 1.32-2 Severity: important The default port in use by postgrey has changed from 6 to 10023. If /etc/default/postgrey was not changed locally, it will be overwritten by a new version without warning. On restart, postgrey will be listening on a different port, which breaks mail delivery. A quick grep for '6' in /etc/postfix/main.cf would be an excellent indication that a warning should be issued to the user. Or even that the port in use should be left alone. Thanks, Bill Gribble -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.16.33-xenU (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages postgrey depends on: ii adduser 3.110 add and remove users and groups ii libberkeleydb-perl0.34-1+b1 use Berkeley DB 4 databases from P ii libnet-dns-perl 0.63-2 Perform DNS queries from a Perl sc ii libnet-server-perl0.97-1 An extensible, general perl server ii perl 5.10.0-17 Larry Wall's Practical Extraction ii ucf 3.0010 Update Configuration File: preserv Versions of packages postgrey recommends: ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith ii libnet-rblclient-perl 0.5-2 Queries multiple Realtime Blackhol pn libparse-syslog-perl none (no description available) ii postfix 2.5.5-1.1 High-performance mail transport ag postgrey suggests no packages. -- no debconf information -- featured product: the GNU Compiler Collection - http://gcc.gnu.org signature.asc Description: This is a digitally signed message part.
