Previous | Contents | Index |
List currently queued messages.
DIRECTORY [type]
Command Qualifiers Defaults None. None.
type
An optional parameter specifying the type of messages to display (e.g.,FAX
,Internet
,cc:Mail
, etc.). Wild cards are permitted.
Use the
DIRECTORY
command to list any messages which you've sent but which have not yet been delivered. The optional type argument can be used to restrict the listing to certain types of messages such as messages sent to the Internet or other TCP/IP connected machines such as UNIX workstations, cc:Mail users, FAX machines, etc. A complete list of the available types are shown below. You can also use the?
key to obtain a listing of the available types as shown in the examples below.3
Type Message Types Listed all_in_1 Messages sent to ALL-IN-1 users bitnet Messages set to BITNET users ccmail Messages sent to Lotus cc:Mail users decnet Messages sent to DECnet users fax Messages sent as FAXes via PMDF-FAX groupwise Messages to GroupWise Office users internet Messages sent to Internet users local Messages sent to local VMS MAIL users lotus_notes Messages sent to Lotus Notes users mailbus_400 Messages sent to MAILbus 400 users mailworks Messages sent to MailWorks users message_router Messages sent to Message Router users microsoft_mail Messages sent to Microsoft Mail users netdata Messages sent to Netdata (PROFS) users novell_mhs Messages sent to Novell MHS users ovvm Messages sent to OV/VM (PROFS) users pager Messages sent to personal pagers popstore Messages sent to popstore users snads Messages sent to SNADS users tcpip Messages sent to TCP/IP users teamlinks Messages sent to TeamLinks users uucp Messages sent to UUCP users wordperfect Messages sent to WordPerfect Office users x400 Messages sent to X.400 users In the directory listing, each message is assigned a message identification number, or "message id" for short. The message id appears in the leftmost column. These identification numbers can be used with the
READ
,RETURN
, andEDIT_FAX
commands to identify which messages to read, return, or edit.It is important to note that when you send a message to more than one recipient, the message might split into multiple message copies. Consequently, the same message might appear multiple times as being queued to different networks (or possibly even for the same network). Such would be the case for a message sent both to local users and remote users.
#1 |
---|
qm.user> DIRECTORY ? Optional keyword, must be chosen from: (1) all_in_1 Messages sent to ALL-IN-1 users (2) bitnet Messages sent to BITNET users (3) ccmail Messages sent to cc:Mail users (4) decnet Messages sent to DECnet users (5) fax Messages sent as FAXes with PMDF-FAX (6) groupwise Messages sent to GroupWise Office users (7) internet Messages sent to Internet users (8) local Messages sent to local users (9) lotus_notes Messages sent to Lotus Notes users (10) mailbus_400 Messages sent to MAILbus 400 users (11) mailworks Messages sent to MailWorks users (12) message_router Messages sent to Message Router users (13) microsoft_mail Messages sent to Microsoft Mail users (14) netdata Messages sent to Netdata (PROFS) users (15) novell_mhs Messages sent to Novell MHS users (16) ovvm Messages sent to OV/VM (PROFS) users (17) pager Messages sent to personal pagers (18) popstore Messages sent to popstore users (19) snads Messages sent to SNADS users (20) tcpip Messages sent to TCP/IP users (21) teamlinks Messages sent to TeamLinks users (22) uucp Messages sent to UUCP users (23) wordperfect Messages sent to WordPerfect Office users (24) x400 Messages sent to X.400 users qm.user> |
This example shows how to obtain a list of the recognized message types. Whenever you are entering a command, you can always press the question mark key, ?, to obtain help on what to type next.
#2 |
---|
qm.user> DIRECTORY Fri, 2 Aug 2012 18:49:40 PDT Id Network From To Size Queued since ------------------------------------------------------------------------ 1 Internet (TCP/IP) bob@example.com service@example.com 8 2-AUG 17:31 service@internode.co 2 Internet (TCP/IP) bob@example.com ietf-822@dimacs.rut 8 2-AUG 15:07 3 Internet (TCP/IP) bob@example.com mwalnut@cnri.reston 16 2-AUG 15:26 4 Internet (TCP/IP) bob@example.com jbakin@adoc.xerox.c 8 2-AUG 17:18 5 Internet (TCP/IP) bob@example.com klensin@MAIL1.RESTO 16 2-AUG 15:26 6 Internet (TCP/IP) bob@example.com MAILSERV@EXAMPLE.C 8 2-AIG 15:38 7 Internet (TCP/IP) bob@example.com john@EXAMPLE.COM 8 2-AUG 17:18 8 Message Router bob@example.com john%doof@am.naples. 8 2-AUG 12:25 9 Local delivery bob@example.com john 8 2-AUG 16:11 10 Internet (TCP/IP) bob@example.com mailserv@example.org 8 2-AUG 12:43 11 Internet (TCP/IP) bob@example.com MARKJOSEPH@delphi.com 8 2-AUG 15:07 -------------------------------------------------------------------------- Total size: 104 qm.user> |
In this example, the
DIRECTORY
command is used to list all queued messages. When a message has more than one envelopeTo:
recipient, the additional recipients are shown on additional lines of the listing as with message 1 which is addressed to service@example.com and service@internode.com.au.
3 Note for system managers: unlike QM's maintenance mode, in user mode the directory listing is always generated from the queue cache database. |
Previous | Next | Contents | Index |