-
Notifications
You must be signed in to change notification settings - Fork 26
"mail" command
There is a lot of useful information in navi that others on your team may benefit from. A simple way to share the output of a command is to mail yourself or someone else the output or export.
This capability is more of a proof-of-concept than a production capability and is not implemented with security as a focus. If you are going to use it in production, create a dummy email account for navi to authenticate to for mailing out information. Navi sends your UN/PW through a TLS connection but it isn't as secure as using OAUTH 2.0.
While there should be no reason this feature can not work with other mail providers; I've only tested with Gmail. So, I might suggest setting up a gmail account for navi if you are going to use this feature. After creating your new account go into Security Settings and turn on 'less secure app access'. In the future, I will look to incorporate OAUTH 2.0.
This command requires the "navi smtp" command be run and your SMTP information inputted.
- --message --> Email a custom message for automation. Concatenate a navi command.
- --to --> Email address to send to
- --subject TEXT --> Subject of the email
- -v --> Display a copy of the message on screen
- --file TEXT --> File you want to attach to your email.
navi mail --latest --to "[email protected]" --subject "This is my subject line"
Send a Special note to support automation
navi mail --to "[email protected]" --subject "navi automation note" --message "Download Finished"
Send the output of a Navi command using --message
navi mail --to "[email protected]" --subject "WAS Report" --message "`navi was --sd 35b54d95-f1b5-40f1-a98e-4f4c82a2a719`"
Send an CSV attachment
navi mail --to "[email protected]" --subject "CSV Export" --message "See attached" --file "risk_report.csv"
Navi mail was removed to from navi. It was moved to another project of mine called willit. This was to keep navi focused on T.io usecases.