Your message dated Sat, 21 Mar 2020 18:55:29 +0000
with message-id <[email protected]>
and subject line Bug#954446: Removed package(s) from unstable
has caused the Debian Bug report #732411,
regarding monkeysign: Being nicer with systems without a SMTP server
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.)
--
732411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732411
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: monkeysign
Version: 1.1
Severity: wishlist
X-Debbugs-Cc: [email protected]
Hi,
unless we revert this change, Tails 0.23, scheduled for March 4, will
ship with monkeysign. Yay.
However, this raises one serious usability issue: there is no SMTP
server in Tails, and we include two MUA (namely: Mutt and Claws Mail).
So, users have to:
1. either use the --smtp* options (I've not looked at the kind of
SSL/TLS encryption that is supported, and I've seen no way of
pinning the remote server's certificate to a particular CA, nor to
provide its fingerprint; besides, the password either is set on the
command-line, or prompted interactively, one being unsafe, and the
other being a pain usability-wise, so I'll assume this is not good
enough for us)
2. or use the --no-mail option, and manually copy'n'paste the email
into their MUA (assuming it supports the MIME format output by
monkeysign, which I have not tried, and TBH I slightly doubt it
will work).
At this point, it should be clear that, in the current state of
things, monkeysign will be mostly unusable for our usecase (if I'm
wrong, I'd be delighted to be explained how one should do :)
It would be great to have a simple way to:
* either save the output email to a file (that one can manually feed
into Mutt later)
* or to pipe it to Mutt (which does not work yet, as monkeysign's
stdout is used by its interactive UI; perhaps printing it to a FD
greater than 2 would be doable?);
* or to do both internally, and to directly invoke the preferred MUA,
providing it with the email headers and body in the way it wants it.
I'm aware this is related to #720047, and likely solving the one will
solve the other usecase.
Thoughts? Any other way this usecase could be taken care of?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--- End Message ---
--- Begin Message ---
Version: 2.2.4+rm
Dear submitter,
as the package monkeysign has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/954446
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
