roundup-mailgw(1) [debian man page]
ROUNDUP-MAILGW(1) General Commands Manual ROUNDUP-MAILGW(1) NAME
roundup-mailgw - mail gateway for roundup SYNOPSIS
roundup-mailgw instance_home [method] OPTIONS
-v Print version and exit. -C hyperdb class specify a tracker class - one of msg (the default), issue, file, user - to manipulate with -S options -S property=value[;property=value] pairs specify the values to set on the class specified by -C using the same format as the Subject line property manipulations DESCRIPTION
The roundup mail gateway may be called in one of three ways: o with an instance home as the only argument, o with both an instance home and a mail spool file, or o with both an instance home and a pop server account. PIPE In the first case, the mail gateway reads a single message from the standard input and submits the message to the roundup.mailgw module. UNIX mailbox In the second case, the gateway reads all messages from the mail spool file and submits each in turn to the roundup.mailgw module. The file is emptied once all messages have been successfully handled. The file is specified as: mailbox /path/to/mailbox In all of the following the username and password can be stored in a ~/.netrc file. In this case only the server name need be specified on the command-line. The username and/or password will be prompted for if not supplied on the command-line or in ~/.netrc. POP In the third case, the gateway reads all messages from the POP server specified and submits each in turn to the roundup.mailgw module. The server is specified as: pop username:password@server The username and password may be omitted: pop username@server pop server are both valid. The username and/or password will be prompted for if not supplied on the command-line. APOP Same as POP, but using Authenticated POP: apop username:password@server IMAP Connect to an IMAP server. This supports the same notation as that of POP mail. imap username:password@server It also allows you to specify a specific mailbox other than INBOX using this format: imap username:password@server mailbox IMAPS Connect to an IMAP server over ssl. This supports the same notation as IMAP. imaps username:password@server [mailbox] AUTHOR
This manpage was written by Bastian Kleineidam <calvin@debian.org> for the Debian distribution of roundup. The main author of roundup is Richard Jones <richard@users.sourceforge.net>. 24 January 2003 ROUNDUP-MAILGW(1)
Check Out this Related Man Page
MSGCHK(1) [nmh-1.5] MSGCHK(1) NAME
msgchk - check for messages SYNOPSIS
msgchk [-date | -nodate] [-notify all/mail/nomail ] [-nonotify all/mail/nomail ] [-host hostname] [-user username] [-sasl] [-saslmech mech- anism] [-snoop] [users ... ] [-version] [-help] DESCRIPTION
The msgchk program checks all known mail drops for mail waiting for you. For those drops which have mail for you, msgchk will indicate if it believes that you have seen the mail in question before. The -notify type switch indicates under what circumstances msgchk should produce a message. The default is -notify all which says that msgchk should always report the status of the users maildrop. Other values for `type' include `mail' which says that msgchk should report the status of waiting mail; and, `nomail' which says that msgchk should report the status of empty maildrops. The -nonotify type switch has the inverted sense, so -nonotify all directs msgchk to never report the status of maildrops. This is useful if the user wishes to check msgchk's exit status. A non-zero exit status indicates that mail was not waiting for at least one of the indicated users. If msgchk produces output, then the -date switch directs msgchk to print out the last date mail was read, if this can be determined. Using POP msgchk will normally check all the local mail drops, but if the option "pophost:" is set in the mts configuration file "mts.conf", or if the -host hostname switch is given, msgchk will query this POP service host as to the status of mail waiting. The default is for msgchk to assume that your account name on the POP server is the same as your current username. To specify a different username, use the `-user username' switch. When using POP, you will normally need to type the password for your account on the POP server, in order to retrieve your messages. It is possible to automate this process by creating a ".netrc" file containing your login account information for this POP server. For each POP server, this file should have a line of the following form. Replace the words mypopserver, mylogin, and mypassword with your own account information. machine mypopserver login mylogin password mypassword This ".netrc" file should be owned and readable only by you. For debugging purposes, there is also a switch -snoop, which will allow you to watch the POP transaction take place between you and the POP server. If nmh has been compiled with SASL support, the -sasl switch will enable the use of SASL authentication. Depending on the SASL mechanism used, this may require an additional password prompt from the user (but the ".netrc" file can be used to store this password). The -saslmech switch can be used to select a particular SASL mechanism. If SASL authentication is successful, inc will attempt to negotiate a security layer for session encryption. Encrypted traffic is labelled with `(encrypted)' and `(decrypted)' when viewing the POP transaction with the -snoop switch. FILES
$HOME/.mh_profile The user profile /etc/nmh/mts.conf nmh mts configuration file /var/mail/$USER Location of mail drop PROFILE COMPONENTS
None SEE ALSO
inc(1) DEFAULTS
`user' defaults to the current user `-date' `-notify all' CONTEXT
None MH.6.8 11 June 2012 MSGCHK(1)