simple smtp mail cmdline client written in GO (GOLANG)
windows (x86 and x64), linux, solaris 11 (intel x64), freebsd, openbsd, dragonfly, darwin (mac os)
windows x64, solaris 11.3 (intel x64), linux x64 (Linux Mint)
- base64 encoding
- possibility to use cmdline arguments and/or config file settings
- supports piped input from cmdline
- crossplatform support
- AUTH LOGIN and AUTH PLAIN authentication
- plain and TLS encryption (out-of-the-box supported by GOLANG)
- attachments
- hashing of user and password in config file (in case used on a public shared folder)
./smtpmail -s smtpsrv.domain.ext -p 25 -f [email protected] -t [email protected],[email protected] -b "mail message" -sub "mail subject" -u <authuser> -pwd <password> [-al|-ap] [-q] [-c <config file>|-nf] [-v|-debug]-s = -smtpserver or -server
-p = -smtpport or -port
-u = -user
-pwd = -password
-al = -authlogin
-ap = -authplain
-b = -body
-sub = -subject or -ti or -title
-f = -from
-t = -to
-v = -verbose
-q = -silent or -quiet
-c = -config or -cfg or -file or -conf
-nf = -nofile, -skip, -skipconfig
You can pipe input ( | ) to smtpmail. For example:
echo "some text to be mailed" | smtpmail -s smtpsrv.domain.ext -p 25 -f [email protected] -t [email protected] -u <authuser> -pwd <password>By piping a string to smtpmail, the piped input string will be used as mail body. And by default, if -sub (subject) is not provided, the first characters of the input string (up to 30 chars) will be used as subject. Notice that if the subject and body are set through the config file, the config file will overwrite the piped input ( see also paragraph on config file ).
Parameter -verbose outputs basic operational information. You can use the short version -v instead of -verbose.
Parameter -debug has no short version. Instead you can use -walk or -dump, but those serve the same purpose as -debug. Debug can be seen as a "very verbose" parameter.
The smtpmail.conf.example config file can be used as skeleton to create a working config file. Simply copy the .example file and rename it to smtpmail.conf. (*)
On Windows, the config file should be placed in the working directory (!= current directory).
On unix/bsd/mac flavors, the same rule applies then for Windows, but the file may also reside under folder /etc.
(*) Naming convention of the config file should be <executable name>.conf. On windows, the ".exe" extension should be stripped off.
The config file may contain parameters, but not all are required. You could easly make a combination or mix of config file parameters (acting as persistent settings) and variable ones provided through the cmdline.
config file structure follows the following rules/parameters:
// double slash is a comment line
// you can make more the one comment line
server=smtp.domain.ext
port=25
authuser=authuser@domain
authpwd=authuserpwd
[email protected]
subject=some subject
body=a body message
authlogin=0|1
verbose=0|1
silent=0|1
The order of paramter appearance in the config file, does not matter.
Because the config file takes precendence over piped input and cmdline arguments, always be aware if you want to provide or use custom input for subject and body to exclude those lines in the config file. You can do this by, simple deleting the lines body= and subject= or by placing them in comment.
AUTH LOGIN and AUTH PLAIN, serve the purpose of the smtp server authentication method.
I've noticed that MS Exchange servers from MS Exchange 2010 or upward, prefer to use AUTH LOGIN instead of AUTH PLAIN.
The authentication method can be changed with the parameters ´-ap´ or ´al´ from the cmdline or by setting authlogin= to 0 or 1 in the config file.
User credentials can be provided on the cmdline arguments using -u (user) and -p (password). Notice for sending mails in a Windows Domain, you need to sue -u user@domain as user account.
smtpmail wil automatically try using plain or TLS encryption. This is a buildin feature of the GOLANG net/smtp package.
smtpmail always uses base64 encoding in the mail header it sends.