tcp-investigation.sh doc
This commit is contained in:
parent
eea60320c7
commit
519e2dfa7f
1 changed files with 2 additions and 2 deletions
|
@ -33,7 +33,7 @@ You can use **git**.
|
|||
|
||||
git clone https://git.lattuga.net/netico/code-library.git
|
||||
|
||||
And then look for the script **tcp-investigation.sh**.
|
||||
and then look for the script **tcp-investigation.sh**.
|
||||
|
||||
### Post installation
|
||||
|
||||
|
@ -62,7 +62,7 @@ The script requires **root privileges**. Run
|
|||
|
||||
Sending e-mail in a shell environment is not as easy as it sounds. It is even more complicated to send HTML instead of plain text. **mutt** and some versions of **mailx** support sending HTML, but require a working mail server.
|
||||
|
||||
To work around these problems, the script attempts to build a standards-compliant message so that it can be passed to a **Sendmail** wrapper (there are wrappers for **Exim**, **Postfix**, **qmail**) or [sent by **curl](https://everything.curl.dev/usingcurl/smtp) (also read [Using curl to send email](https://stackoverflow.com/questions/14722556/using-curl-to-send-email)).
|
||||
To work around these problems, the script attempts to build a standards-compliant message so that it can be passed to a **Sendmail** wrapper (there are wrappers for **Exim**, **Postfix**, **qmail**) or [sent by curl](https://everything.curl.dev/usingcurl/smtp) (also read [Using curl to send email](https://stackoverflow.com/questions/14722556/using-curl-to-send-email)).
|
||||
|
||||
Some recommended reading on email message format: [RFC822](https://datatracker.ietf.org/doc/html/rfc822), [RFC2822](https://www.rfc-editor.org/rfc/rfc2822).
|
||||
|
||||
|
|
Loading…
Reference in a new issue