Expose nodemailer's requireTLS option so that when secure is false
(e.g. STARTTLS on port 587), the connection aborts if the server
does not support/negotiate STARTTLS, instead of silently sending
credentials in clear text.
* Take the proxy from SMTP_PROXY instead of HTTP_PROXY
HTTP_PROXY says how to reach the web, and on a self-hosted runner it is
routinely set machine-wide while the mail server has to be reached
directly. Sending SMTP through it makes such a proxy refuse the
connection, and there was no way to opt out.
Read the protocol-specific SMTP_PROXY instead, and honour NO_PROXY so a
host can be exempted from it.
Co-Authored-By: Claude (Opus 5) <noreply@anthropic.com>
* Accept smtps_proxy too, and prefer the lowercase spelling
curl reads the lowercase name first and falls back to the uppercase one,
and an implicit TLS connection is configured through smtps_proxy rather
than smtp_proxy.
Co-Authored-By: Claude (Opus 5) <noreply@anthropic.com>
---------
Co-authored-by: Claude (Opus 5) <noreply@anthropic.com>
* Relax from check
- Print a warning instead of an error, if envelope_from is set.
- In case of an error, provide a hint about envelope_from.
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Misc. fixes
- Do not expose 'username' to a potential recipient.
- Make 'from' mandatory, because there is no fallback anymore.
- Validate 'from' to make shure, it contains an email address.
- Avoid namespace pollution: Use let instead of var.
* Suggested changes from codereview
Allows dynamic subjects to be generated at action runtime
(e.g., "Foobar version 1.2.3 is released", where 1.2.3
is not known at action config time).
Leverages the existing file:// support for body, but renames
getBody to getText, in keeping with this expanded role.
* Add ability to set In-Reply-To tag
This is useful to reply to a specific email, e.g. to a patch sent by
email on a mailing list.
Please note that both the In-Reply-To and the References tags are
filled-in. In theory, only the In-Reply-To tag should be enough but they
are both linked to the same idea and in theory most emails readers
should support a Message-ID given in In-Reply-To tag. So just in case,
we fill both to imitate many email clients.
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
* Update test.yml
Co-authored-by: Dawid Dziurla <dawidd0811@gmail.com>
Bernhard