Your message dated Fri, 8 Jul 2005 08:10:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317311: mutt-ng: does not strip BCC: from headers before
sending
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Jul 2005 15:41:42 +0000
>From [EMAIL PROTECTED] Thu Jul 07 08:41:42 2005
Return-path: <[EMAIL PROTECTED]>
Received: from h155.251.140.67.ip.alltel.net (mail.renich.org) [67.140.251.155]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DqYVS-0006zB-00; Thu, 07 Jul 2005 08:41:42 -0700
Received: from squeeks.wdw ([192.168.213.130] helo=[127.0.0.1])
by mail.renich.org with esmtp (Exim 4.50)
id 1DqYVQ-0005Ez-9A; Thu, 07 Jul 2005 11:41:40 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Marvin Renich <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mutt-ng: does not strip BCC: from headers before sending
X-Mailer: reportbug 3.8
Date: Thu, 07 Jul 2005 11:41:39 -0400
Message-Id: <[EMAIL PROTECTED]>
X-SA-Exim-Connect-IP: 192.168.213.130
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
X-SA-Exim-Scanned: No (on mail.renich.org); SAEximRunCond expanded to false
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: mutt-ng
Version: 0.0.svn+r316-1
Severity: normal
muttng does not strip BCC header lines before sending the message,
leaving potentially private information in the message (i.e. defeating
the purpose of BCC).
....Marvin
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages mutt-ng depends on:
ii exim [mail-transport-agent] 3.36-16 An MTA (Mail Transport Agent)
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libesmtp5 1.0.3-1 LibESMTP SMTP client library
ii libgnutls11 1.0.16-13.1 GNU TLS library - runtime library
ii libidn11 0.5.13-1.0 GNU libidn library, implementation
ii libncursesw5 5.4-8 Shared libraries for terminal hand
ii libqdbm11 1.8.30-1 QDBM Database Libraries [runtime]
ii libsasl2 2.1.19-1.5 Authentication abstraction library
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
-- no debconf information
---------------------------------------
Received: (at 317311-done) by bugs.debian.org; 8 Jul 2005 12:10:54 +0000
>From [EMAIL PROTECTED] Fri Jul 08 05:10:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ispmxmta05-srv.alltel.net [166.102.165.166]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Dqrgz-0000B5-00; Fri, 08 Jul 2005 05:10:54 -0700
Received: from squeeks ([67.140.248.245]) by ispmxmta05-srv.alltel.net
with ESMTP
id <[EMAIL PROTECTED]>;
Fri, 8 Jul 2005 07:10:23 -0500
Received: from mrvn by squeeks with local (Exim 3.36 #1 (Debian))
id 1DqrgU-0007EL-00; Fri, 08 Jul 2005 08:10:22 -0400
Date: Fri, 8 Jul 2005 08:10:22 -0400
From: Marvin Renich <[EMAIL PROTECTED]>
To: Elimar Riesebieter <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#317311: mutt-ng: does not strip BCC: from headers before
sending
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: mutt-ng devel-r316 (Debian)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
* Elimar Riesebieter <[EMAIL PROTECTED]> [050707 14:04]:
> Try
> unset write_bcc
> in your muttngrc. Please refer to chapter 6 of the manual.
>
> Elimar
>
Ooh! I didn't see that. I was comparing mutt and muttng, and my
personal muttrc and muttngrc files, and didn't see any reason why mutt
would strip BCC and muttng wouldn't. Upon further investigation (now
that I know what to look for), the system /etc/Muttrc file has "unset
write_bcc", while /etc/Muttngrc does not.
This is a difference between mutt's and muttng's default (Debian)
configuration that might surprise a lot of people switching to muttng.
Do some MTA's require the BCC header to figure out recipients? What are
the negative consequences of changing Debian's /etc/Muttngrc to work
better with Debian's default MTA (exim4) out of the box, the way
/etc/Muttrc does?
Thanks for the quick response! I'm closing this bug. Should I file a
new wishlist bug to change write_bcc in /etc/Muttngrc?
...Marvin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
