Package: reportbug
Version: 3.38
Severity: normal

Like a lot of people, I recently submitted a bug report.  Afterwards I realised 
exim4
wasn't properly configured to send it, as I hadn't yet set up the AUTH stuff 
for SMTP
to my smarthost.

Anyway, after exim4 was reconfigured, I sent my email.  My smarthost doesn't
like CC without some configuration option set on their end.  Running 
dpkg-reconfigure (with or without -plow) never brings up anything having
to do with CC.  I would think the CC without any options (in the reportbug.conf
file) would allow for exim4 rewrites (which would still trigger my smarthosts
problem), but CC with an option would CC the message to the option.  For
example:
 CC [EMAIL PROTECTED]
where %u is the username, and %l is "localhost" or hostname.  I could
easily see "[EMAIL PROTECTED]" as being the default answer in debconf.
So, reportbug should at least allow this sort of thing to be set from debconf
questioning.

As an aside, when I sought to report a bug on reportbug, it presented a series
of options to me before anything went forward.  Should this questioning at 
least be
able to determine if I am using a smarthost?  I have to configure enough stuff 
to
do it.

-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/ghaverla/.reportbugrc:
reportbug_version "1.99.50"
mode standard
ui text
offline
realname "Gordon Haverland"
email "[EMAIL PROTECTED]"

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.21 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reportbug depends on:
ii  apt                         0.6.46.4-0.1 Advanced front-end for dpkg
ii  python                      2.4.4-6      An interactive high-level object-o
ii  python-central              0.5.14       register and build utility for Pyt

reportbug recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to