Your message dated Sat, 14 Jun 2025 17:17:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#1104605: signing-party: caff returns 0 with ok message
without sending email
has caused the Debian Bug report #1104605,
regarding signing-party: caff returns 0 with ok message without sending email
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.)
--
1104605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104605
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: signing-party
Version: 2.11-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Caff prints the following:
Mail signature for 'XXXXXX <[email protected]>' to
'[email protected]'? [Y/n] y
[INFO] Key 0xXXXXXXXXXXXXXXXXXXX done
It gives the impression the email was send but it didn't send. I don't
have mta configured.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Signing use caff
* What was the outcome of this action?
It signed but didn't send the email, without print an error
* What outcome did you expect instead?
To send email or print an error
-- System Information:
Debian Release: 12.10
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-34-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages signing-party depends on:
ii gnupg 2.2.40-1.1
ii libc6 2.36-9+deb12u10
ii libclass-methodmaker-perl 2.24-2+b3
ii libgnupg-interface-perl 1.02-3
ii libmailtools-perl 2.21-2
ii libmd0 1.0.4-2
ii libmime-tools-perl 5.510-1
ii libnet-idn-encode-perl 2.500-3+b1
ii libterm-readkey-perl 2.38-2+b1
ii libtext-template-perl 1.61-1
ii perl 5.36.0-7+deb12u2
ii python3 3.11.2-1+b1
ii qprint 1.1.dfsg.2-2.1
Versions of packages signing-party recommends:
ii exim4-daemon-light [mail-transport-agent] 4.96-15+deb12u7
ii libgd-perl [libgd-gd2-perl] 2.76-4+b1
ii libpaper-utils 1.1.29
ii whiptail 0.52.23-1+b1
Versions of packages signing-party suggests:
ii fonts-noto-cjk 1:20220127+repack1-1
ii fonts-noto-mono 20201225-1
ii imagemagick 8:6.9.11.60+dfsg-1.6+deb12u2
ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.6+deb12u2
pn mutt | neomutt <none>
pn qrencode <none>
pn texlive-font-utils <none>
pn texlive-latex-extra <none>
pn texlive-latex-recommended <none>
pn texlive-xetex <none>
pn wipe <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 14 Jun 2025 at 12:08:22 -0300, Ana Oliveira wrote:
> I belive my email client is not configured and that is why it doesn't
> send the email. But shouldn't caff say something?
It has now way to detect whether mails got stuck downstream. See caff(1)
and/or the wiki page at https://wiki.debian.org/caff .
If fixing the local MTA is not an option then msmtp might work per
https://wiki.debian.org/caff/msmtp .
--
Guilhem.
signature.asc
Description: PGP signature
--- End Message ---
