Differences

This shows you the differences between two versions of the page.

--- playground:s-nail [2021/11/01 01:40] – [Basic mailx Usage] zilog
+++ playground:s-nail [2021/11/03 01:20] – zilog
@@ Line 7: / Line 7: @@
 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.  With just the default settings a user should be able to send a message to themselves or another account on the local system like so:
-<code>$ mailx //localuser//</code>
+<code>$ mailx localuser</code>
 The sender will generally be prompted to enter a //Subject:// after which they simply type their message then press ''CTRL+D'' to signal //end of file// (EOF) and off it goes.
@@ 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:
-<code>$ mailx -s "simple test" //some_user// < myfile </code>
+<code>$ mailx -s "simple test" some_user < myfile </code>
 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 49: / Line 49: @@
 Each of the 3 mailx programs are sufficently different that beyond the very basics they need to be covered separately in this tutorial.  That said, the following should work on all implementations:
-  * headers [msg range]
+^ mailx cmd  ^ description                                    ^
-  * Reply/reply [msg]
+|  header    | lists message headers; accepts range and +/-   |
-  * mail [recepient]
+|  type      | prints message(s); accepts range.              |
-  * file/folder [mail_folder]
+|  forward   | forwards current message with all headers      |
-  * folders
+|  delete    | deletes mesaages; accepts range                |
-  * delete [msg range]
+|  mail      | compose a mew message; accepts multiple addrs  |
-  * save [msg range] [folder]
+|  write     | write message(s) to file; allows MIME splits   |
+|  reply     | reply to sender(s); use Reply for just primary |
+|  list      | list all mailx commands                        |
+Typing ''help'' within an active mailx session will list the most common commands and their usage.  Most mailx commands can be abbreviated to their first letter and several aliases exist, for example ''type'' and ''print'' are the same, so are ''file'' and ''folder''.  See the **Mail Command Reference** document for more info.
+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 (''CTRL+D'') is entered on a new line (traditionally BSD mail also accepts a single "." (dot) on a new line; enable the ''bsdcompat'' option in the config file for this behavor).  See the **Mail Tilde Command Ref** document and the manpages for additional info.
+====Specific mailx Client Configurations and Usage====
 [[playground:native Mail|playground:NetBSD Mailx (mail)]]
-[[playground:native Mail|playground:Heirloom Mailx (nail)]
+[[playground:native Mail|playground:Heirloom Mailx (nail)]]
 [[playground:native Mail|playground:S-mailx (s-nail)]]