From: usenet2006_05@duhanic.com.com.invalid (Mario F. Duhanic)
Subject: Re: s/mime with openssl, additional newline
Date: Fri, 26 May 2006 13:17:41 +0200 [thread overview]
Message-ID: <ac95qbl6.fsf@duhanic.com.com.invalid> (raw)
In-Reply-To: <4pzdix0t.fsf@duhanic.com.com.invalid>
It seems somehow to be Gnus' fault, because it keeps asking me twice for
my passphrase:
once at the very beginning of the sending process and
once when smtpmail is somewhere in the middle of the body-send-process.
Because I am not a "real gnuser", could anybody tell me how to correctly
backtrace the whole sending process of smtpmail (e.g. writing everything
into a file)? I've already tried to work with the debugging facility but
I failed to gain the information I needed.
I've also tried to s/mime-sign (pkcs#7) a "message" manually via openssl and
there it worked fine.
Regards and thanks,
Mario
prev parent reply other threads:[~2006-05-26 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 22:01 Mario F. Duhanic
2006-05-26 11:17 ` Mario F. Duhanic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac95qbl6.fsf@duhanic.com.com.invalid \
--to=usenet2006_05@duhanic.com.com.invalid \
--cc=usenet2006_05@duhanic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).