Your message dated Thu, 14 Feb 2019 06:34:14 +0000
with message-id <[email protected]>
and subject line Bug#921244: fixed in nmh 1.7.1-4
has caused the Debian Bug report #921244,
regarding broken bcc handling with transport sendmail/pipe
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
921244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921244
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nmh
Version: 1.7.1-3
Severity: normal
Hi,
when drafting a message with comp(1) and including something like the
following in the headers:
| To: [email protected]
| Bcc: [email protected]
I get the following error:
| What now? send
| sendmail: No recipients specified although -t option used
| exit 1
Both recipients get messages with different Message-Ids, but the
content seems to be exactly the same. I believe this is in conflict
with the man page of send(1), which states that Bcc-recipients will
receive a message with a clear indication in the body, warning them
not to disclose their status as recipients by replying.
See the discussion von Bcc: vs. Dcc: fields in the man page of send(1)
for details.
I believe the body of bcc messages used to start with:
| ------- Blind-Carbon-Copy
|
| From: [email protected]
| To: [email protected]
| Bcc: [email protected]
| Subject: ...
| [more headers]
|
| [original body]
Best regards and thanks for maintaining nmh.
Harald
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nmh depends on:
ii libc6 2.28-5
ii libcurl4 7.63.0-1
ii libdb5.3 5.3.28+dfsg1-0.2
ii liblockfile1 1.14-1.1
ii libsasl2-2 2.1.27+dfsg-1
ii libssl1.1 1.1.1a-1
ii libtinfo6 6.1+20181013-1
ii mime-support 3.61
ii netbase 5.5
ii sensible-utils 0.0.12
Versions of packages nmh recommends:
ii ssmtp [mail-transport-agent] 2.64-8+b2
Versions of packages nmh suggests:
pn exmh <none>
ii libmailtools-perl 2.18-1
ii libmime-tools-perl 5.509-1
pn mh-book <none>
pn mh-e <none>
pn par <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nmh
Source-Version: 1.7.1-4
We believe that the bug you reported is fixed in the latest version of
nmh, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexander Zangerl <[email protected]> (supplier of updated nmh package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 12 Feb 2019 14:58:31 +1000
Source: nmh
Binary: nmh nmh-dbgsym
Architecture: source amd64
Version: 1.7.1-4
Distribution: unstable
Urgency: high
Maintainer: Alexander Zangerl <[email protected]>
Changed-By: Alexander Zangerl <[email protected]>
Description:
nmh - set of electronic mail handling programs
Closes: 921244
Changes:
nmh (1.7.1-4) unstable; urgency=high
.
* fix bcc: handling for mts sendmail/pipe (closes: #921244)
Checksums-Sha1:
317b03ecfc48b70f4fd0a64af818490bec863199 1794 nmh_1.7.1-4.dsc
9e3252b6b41419437dd1b82cd176a8bf5a45e6fd 21364 nmh_1.7.1-4.debian.tar.xz
df578994843ed6dd198fdc05a5eaaf2530ae7f67 8537820 nmh-dbgsym_1.7.1-4_amd64.deb
44c5cb695477ceb559bef38778ef24cdbef07007 7162 nmh_1.7.1-4_amd64.buildinfo
b5773d348c99298d0f7852265fe3ebb53cfba4e1 1437388 nmh_1.7.1-4_amd64.deb
Checksums-Sha256:
fbda40571fff2f10ba04abd6f8fe79039c28fdbd2f8226eca68d82672967e4f2 1794
nmh_1.7.1-4.dsc
40598df75f9c0765485288f33e484c9fd234049185eda7d13248650885125648 21364
nmh_1.7.1-4.debian.tar.xz
f8cd078344d227957ca809ba12e778f5bee35f91b52a459d0805aba3a8d57e69 8537820
nmh-dbgsym_1.7.1-4_amd64.deb
557ae978f83bbed25c4736e4d31430ea5219532f6fc0fd1b93492b77b0db21cb 7162
nmh_1.7.1-4_amd64.buildinfo
946ee9c214b2f1ec84c60b017004cd08f8d831de097fd7699720c2bcdaca5a5e 1437388
nmh_1.7.1-4_amd64.deb
Files:
790893a7ed4d62104ac0c02a10754b8c 1794 mail optional nmh_1.7.1-4.dsc
65288b7c2a7a24a9f032636310e920b1 21364 mail optional nmh_1.7.1-4.debian.tar.xz
64c5c784bd80362f32aaf40f6228923c 8537820 debug optional
nmh-dbgsym_1.7.1-4_amd64.deb
e5783fcd219aedd5a0eb715592ac2e04 7162 mail optional nmh_1.7.1-4_amd64.buildinfo
e61640a5b5547eaa13eddafa7764f2bc 1437388 mail optional nmh_1.7.1-4_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJcZQcUAAoJED06g4g30PqNFHYP/3gyFy9FrXCThTH3CgxA6Wkp
Has5UhqGjcf3fQWpXhiVbk128CZZm9OKuS7r55iNdb8Wfc7jXFnnfAb0hzZPXWdo
8Jad+7MxhdVrWooBTO4QMFQDoz36Mj1JRP5zWAH75puVGeg+zVnVWsu/bn+yP23S
lp5IzqfmmlEAcYRB3efiBv8g7palDqG6uFS0lCZEREYNlCY4rY7JBAuFJzOHHfuT
QWFyQbWiANewywfiQZikv5sKu5+xY9b6q9bwzbtbszB12rE8EGV0jAjYdsVkU+re
ze7QTFRdQRtcgjwYh7VypzeKachQ/N4z7kMi4VFlcjY2YYh76WdYQ6K3CmA+Vyl+
PQvMLI09zs7f3UfcPAg69Q4k0ymx3ZAvmjcOl3lTaKFCb4ziE/6ROcG1Jra9EiPH
6LQx+6/d+b2oKtfzM82T1rp5gSh9LQ2qL3p1NjFQcbNLez/Ya5M2wZBb5v4zjOCH
q9T/6MTAnMwN9Xv3pkTIGSvdJCSFEfoQHRvpjzLnBHk6eHKczi5wIYFk2TWM92U5
fEYtlZtczEa+JMwCiypf6rSQGHeGTg7AGZQmIZ/uqRqCGI3dPXmo1+rPQ+vl4bFI
3UH1dnm+1HOzRY8Rnbbz+AWkgTCrZbQ09o7gY4hviI8CzMXCYB2hheqUyRPG9lrG
xjx6d5WBNAC79AHXtAHv
=dXXq
-----END PGP SIGNATURE-----
--- End Message ---
