Solution for adding STARTTLS support #269
Comments
|
Kudos for that!
I took a different tack, and set up (free) accounts at SMTP2go.com
for my clients/users. Did not have to do their "domain
verification" step, and I was able to substitute the smtp2go
server for the smtp server that had previously been provided by
the local ISP (Shaw Cable) for the past >20 years. Less
secure, in theory, but the vast majority of the reports are ending
up in mailboxes hosted by google or microsoft, in one form or
another, so they are thoroughly indexed and recorded already,
regardless of TLS. My lawyer clients have long used their own
mail server via local LAN or VPN.
Do the the script modifications need to be tested with more than
one smtp relay host? I can use the smtp2go.com server for that,
if desired. We know TLS works between smtp2go and certain
photocopiers (scan-to-mail was actually the precipitating event --
we didn't relish to dealing with the Cable Co "customer support"
to set up an account for the sole purpose of relaying mail).
Cheers!
d.
On 2022-09-07 07:51, Feribv wrote:
I managed to make emailing functional in ghettoVCB
with email servers that require STARTTLS before any mail
commands. netcat/nc does not support this, so I needed to switch
to openssl (included in ESXi).
Here is what needs to be modified in ghettoVCB.sh
The lines:
cat "${EMAIL_LOG_CONTENT}" |
sendDelay| "${NC_BIN}" "${EMAIL_SERVER}"
"${EMAIL_SERVER_PORT}" > /dev/null 2>&1
will be replaced by:
cat "${EMAIL_LOG_CONTENT}" | sendDelay
| openssl s_client -starttls smtp -crlf -pause -connect
"${EMAIL_SERVER}":"${EMAIL_SERVER_PORT}"
in the If/else just before the "Start of Main Script" Section
In the SendDelay() function, we need to modify the
line:
[ $c -lt 4 ] && sleep
${EMAIL_DELAY_INTERVAL}
to:
[ $c -lt 15 ] && sleep
${EMAIL_DELAY_INTERVAL}
With these applied ghettovcb.sh will connect to the
mail server using TLS and will be able to send the log file
reports.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this
thread.Message
ID: ***@***.***>
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#269",
"url": "#269",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
|
This dosent work with smtp.gmail.com port 587. |
|
you could try increasing EMAIL_DELAY_INTERVAL=3 in the conf file. |
|
Still didnt work. I got this in the log |
|
Hello , I have the following error: Or all seems ok at the end I have the DONE |
|
I also get this error: |
|
I had the same problems like @Admin-andjaro and @craigywsm, I could find the following solution for me.
|
Hello @ryder-hook , Many thanks |
|
@lucadp76 I hope this helps you. |
|
Thank you very much @ryder-hook, |
|
Hello `235 2.7.0 Authentication successful postfix log Regards |
|
I also struggle my self again with getting no e-mails. Do you know any why how to debug the error and/or how to send test e-mails with ghettoVCB without doing a backup job. |
|
i fixed this adding IP of my esxi to mynetworks ( postfix main.cf ). |
I managed to make emailing functional in ghettoVCB with email servers that require STARTTLS before any mail commands. netcat/nc does not support this, so I needed to switch to openssl (included in ESXi).
Here is what needs to be modified in ghettoVCB.sh
The lines:
cat "${EMAIL_LOG_CONTENT}" | sendDelay| "${NC_BIN}" "${EMAIL_SERVER}" "${EMAIL_SERVER_PORT}" > /dev/null 2>&1will be replaced by:
cat "${EMAIL_LOG_CONTENT}" | sendDelay | openssl s_client -starttls smtp -crlf -pause -connect "${EMAIL_SERVER}":"${EMAIL_SERVER_PORT}"in the If/else just before the "Start of Main Script" Section
In the SendDelay() function, we need to modify the line:
[ $c -lt 4 ] && sleep ${EMAIL_DELAY_INTERVAL}to:
[ $c -lt 15 ] && sleep ${EMAIL_DELAY_INTERVAL}With these applied ghettovcb.sh will connect to the mail server using TLS and will be able to send the log file reports.
The text was updated successfully, but these errors were encountered: