From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: 'git send-email...' works - but 'SSL.pm' complains about an "Undefined SSL object"!?
Date: Fri, 21 Jan 2022 18:40:52 +0100 [thread overview]
Message-ID: <5817ea4a-75dc-5f4a-facf-01a831336405@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Hi,
could someone please give me a clue how to handle - or ignore!? - the
"DEBUG error" about an "Undefined SSL object" down there?
This happened while sending my last patches today.
Everything was sent, but I'm getting this error.
***SNIP***
root(a)Devel64-1: /git/ipfire-2.x # git send-email --annotate -1
/tmp/GIKtdU954W/0001-log.dat-Fix-an-error-with-monit-logging-too-much-dat.patch
DEBUG: .../IO/Socket/SSL.pm:1177: global error: Undefined SSL object
Password for 'smtp://mfischer(a)submissions.ipfire.org:465':
OK. Log says:
Server: submissions.ipfire.org
MAIL FROM:<matthias.fischer(a)ipfire.org>
...
***SNAP***
Thanks in advance!
Best,
Matthias
next reply other threads:[~2022-01-21 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 17:40 Matthias Fischer [this message]
2022-01-29 10:04 ` Michael Tremer
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=5817ea4a-75dc-5f4a-facf-01a831336405@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/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