public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: gary.e.rafe@gmail.com (Gary E. Rafe, PhD)
To: cygwin@cygwin.com
Subject: email --verbose returns version info
Date: Thu, 28 May 2020 10:33:18 -0400	[thread overview]
Message-ID: <20200528143318.8jlSUSktaNFJVS4Dw1wwuZaq@gerlmrhpb.gerlmrnet> (raw)

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

                 reply	other threads:[~2020-05-28 14:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200528143318.8jlSUSktaNFJVS4Dw1wwuZaq@gerlmrhpb.gerlmrnet \
    --to=gary.e.rafe@gmail.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).