mirror of
https://github.com/dawidd6/action-send-mail.git
synced 2026-02-10 05:41:07 +07:00
node_modules: update (#261)
Co-authored-by: dawidd6 <9713907+dawidd6@users.noreply.github.com>
This commit is contained in:
4
node_modules/nodemailer/lib/smtp-connection/index.js
generated
vendored
4
node_modules/nodemailer/lib/smtp-connection/index.js
generated
vendored
@@ -15,6 +15,7 @@ const CONNECTION_TIMEOUT = 2 * 60 * 1000; // how much to wait for the connection
|
||||
const SOCKET_TIMEOUT = 10 * 60 * 1000; // how much to wait for socket inactivity before disconnecting the client
|
||||
const GREETING_TIMEOUT = 30 * 1000; // how much to wait after connection is established but SMTP greeting is not receieved
|
||||
const DNS_TIMEOUT = 30 * 1000; // how much to wait for resolveHostname
|
||||
const TEARDOWN_NOOP = () => {}; // reusable no-op handler for absorbing errors during socket teardown
|
||||
|
||||
/**
|
||||
* Generates a SMTP connection object
|
||||
@@ -505,6 +506,9 @@ class SMTPConnection extends EventEmitter {
|
||||
socket.removeListener('end', this._onSocketEnd);
|
||||
socket.removeListener('error', this._onSocketError);
|
||||
socket.removeListener('error', this._onConnectionSocketError);
|
||||
// Absorb errors that may fire during socket teardown (e.g. server
|
||||
// sending cleartext after TLS shutdown triggers ERR_SSL_BAD_RECORD_TYPE)
|
||||
socket.on('error', TEARDOWN_NOOP);
|
||||
socket[closeMethod]();
|
||||
} catch (_E) {
|
||||
// just ignore
|
||||
|
||||
8
node_modules/nodemailer/lib/well-known/services.json
generated
vendored
8
node_modules/nodemailer/lib/well-known/services.json
generated
vendored
@@ -147,6 +147,14 @@
|
||||
"secure": true
|
||||
},
|
||||
|
||||
"GmailWorkspace": {
|
||||
"description": "Gmail Workspace",
|
||||
"aliases": ["Google Workspace Mail"],
|
||||
"host": "smtp-relay.gmail.com",
|
||||
"port": 465,
|
||||
"secure": true
|
||||
},
|
||||
|
||||
"GMX": {
|
||||
"description": "GMX Mail",
|
||||
"domains": ["gmx.com", "gmx.net", "gmx.de"],
|
||||
|
||||
Reference in New Issue
Block a user