playground:s-nail
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
playground:s-nail [2021/10/27 06:05] – added PATH and manpage location info zilog | playground:s-nail [2021/11/01 04:58] – zilog | ||
---|---|---|---|
Line 4: | Line 4: | ||
In the beginning.. there was //mail//, which was included in Unix 1st Edition in 1971 according to the ancient texts (manuals). At this time, Unix had no remote communication facility at all, so //mail// would simply write to other users' files on a single machine. | In the beginning.. there was //mail//, which was included in Unix 1st Edition in 1971 according to the ancient texts (manuals). At this time, Unix had no remote communication facility at all, so //mail// would simply write to other users' files on a single machine. | ||
- | ===Getting Started=== | + | ====Getting Started==== |
One of the great features of //mailx// is it behaves like most traditional Unix commands; you can pipe the output of other commands to it or use it in a shell script or crontab. | One of the great features of //mailx// is it behaves like most traditional Unix commands; you can pipe the output of other commands to it or use it in a shell script or crontab. | ||
- | < | + | < |
The sender will generally be prompted to enter a // | The sender will generally be prompted to enter a // | ||
Line 13: | Line 13: | ||
To further automate sending simple messages the subject and an input file can generally be specified on the command line like so: | To further automate sending simple messages the subject and an input file can generally be specified on the command line like so: | ||
- | < | + | < |
Most //mailx// implementations allow multiple addressees as well as CC / BCC recipients to be specified on the command line which makes it's fairly easy to automate the sending of regular broadcast-type emails. | Most //mailx// implementations allow multiple addressees as well as CC / BCC recipients to be specified on the command line which makes it's fairly easy to automate the sending of regular broadcast-type emails. | ||
Line 46: | Line 46: | ||
To read use any pager like //more// or //less//, or even the //lynx// browser. | To read use any pager like //more// or //less//, or even the //lynx// browser. | ||
- | ==native | + | ====Basic mailx Usage==== |
+ | Each of the 3 mailx programs are sufficently different that beyond the very basics they need to be covered separately in this tutorial. | ||
+ | |||
+ | ^ mailx cmd ^ description | ||
+ | | header | ||
+ | | type | prints message(s); accepts range. | ||
+ | | forward | ||
+ | | delete | ||
+ | | | ||
+ | | write | write message(s) to file; allows MIME splits | ||
+ | | reply | reply to sender(s); use Reply for just primary | | ||
+ | | list | list all mailx commands | ||
+ | |||
+ | Most mailx commands can be abbreviated to their first letter and several aliases exist, for example '' | ||
+ | |||
+ | Similarly, in composition mode there are several tilde commands that are common to all mailx clients: | ||
+ | |||
+ | ^ tilde cmd ^ description | ||
+ | | ~p | print current header and body of message buffer | ||
+ | | ~f | read in a message; accepts range, curr. default | ||
+ | | ~d | read in contents of dead.letter (DEAD) | ||
+ | | ~m | read message in as ref.; usually prefixed with '>' | ||
+ | | ~e | open message buffer in default editor | ||
+ | | ~h | edit the message headers; use ~c, ~b for CC and BCC| | ||
+ | | ~r | read a local file into message buffer | ||
+ | | ~? | list all tilde commands and their usage | | ||
+ | |||
+ | Once a composed message is ready to be sent an EOF ('' | ||
+ | |||
+ | |||
+ | ====Specific mailx Client Configurations==== | ||
+ | |||
+ | [[playground: | ||
+ | |||
+ | [[playground: | ||
+ | |||
+ | [[playground: |