reportbug (3.48) unstable; urgency=low There were some infrastructure changes, in order to provide a better BTS service, that made the previous SMTP server 'bugs.debian.org' no more working as expected, so we now provide another host for SMTP for reportbug: 'reportbug.debian.org'. If you are using any other debian.org host to act as SMTP host for reportbug, we encourage you to update your configuration accordingly. At the same time, if you use 'reportbug.debian.org' we set automatically the port to '587' (but even '25' port can be used) in order to work around the filter some ISPes apply to outcoming connections to port '25'. As a side effect, using 'reportbug.debian.org' the '--debug' option stops working, since relay is not allowed by that host, but since it's mainly an interal-use-only option, we're sure it won't impact you a lot. -- Sandro Tosi Sun, 14 Dec 2008 15:15:23 +0100 reportbug (3.18) unstable; urgency=high The proper SMTP setting for reporting bugs to Debian without a working local mailer has changed to 'bugs.debian.org'. reportbug will noisily override any .reportbugrc settings for the old mail relay... however, you would be best advised to update .reportbugrc files accordingly. -- Chris Lawrence Tue, 29 Nov 2005 23:19:45 -0500 reportbug (2.47) unstable; urgency=medium The dependency relationships between reportbug and Python's locale support modules have changed in this version of reportbug: . python2.3-iconvcodec is now a Recommendation. . python2.3-cjkcodec is now recommended as an alternative. Users of Unicode (UTF-*), ISO-8859-*, and KOI8 locales may use reportbug without either module installed. These encodings are supported by the base install of Python 2.3. Users of Chinese, Japanese, and Korean-language locales who do not use a UTF encoding should use python2.3-cjkcodec. Users of other locales should use python2.3-iconvcodec. In addition, reportbug will now issue a warning on startup if the encoders installed on your system are insufficient for encoding the character set used by your locale. (Previously, this would lead to a mysterious crash with a "LookupError" later in the reporting process.) -- Chris Lawrence Sat, 14 Feb 2004 15:35:29 -0600