DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 889FD386F831
Date: Thu, 28 May 2020 10:33:18 -0400
Organization: Gary E. Rafe, PhD
To: cygwin@cygwin.com
Subject: email --verbose returns version info
Message-ID: <20200528143318.8jlSUSktaNFJVS4Dw1wwuZaq@gerlmrhpb.gerlmrnet>
User-Agent: s-nail s-nailv13.2
MIME-Version: 1.0
From: "Gary E. Rafe, PhD via Cygwin" <cygwin@cygwin.com>
Reply-To: gary.e.rafe@gmail.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

Shorter version:
/bin/email --verbose ... returns version info about the installed binary:
email - By Dean Jones; Version 3.2.3-git

Longer version:
I've been using email(1) since Feb 2019 or so from my office Windows desktop
to send e-mail messages from a bash script that are generated from SQL queries
using fisql(FreeTDS). Messages are sent through the smtp.office365.com SMTP
relay using my staff University credentials.

This has "just worked" until it stopped working (due to an unknown
authentication error) last Monday (18 May 2020).

In trying to diagnose this new problem, I thought "--verbose" might give me
some insight into how/where the SMTP transaction is failing when email(1)
negotiates a connection with smtp.office365.com.  Alas, "--verbose" or "-v"
simply causes email(1) to report its version, as noted above, and exit
immediately.

Having a look at the current github source for email.c, I see that both -V
(verbose) and -v (version) options are defined in the source version dated
May 17, 2019 (https://github.com/deanproxy/eMail/blob/master/src/email.c).

Is there any chance that the Cygwin maintainers could flag email(1) to be
updated from the current github source (still marked in VERSION as 3.2.3-git) ?

Thank you.
--
Gary E. Rafe, PhD | +1 419.699.1181
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple