push(8) [php man page]
PUSH(8) BSD System Manager's Manual PUSH(8) NAME
push -- fetch mail via POP SYNOPSIS
push [-5 | --krb5] [-v | --verbose] [-f | --fork] [-l | --leave] [--from] [-c | --count] [--headers=headers] [-p port-spec | --port=port-spec] po-box filename DESCRIPTION
push retrieves mail from the post office box po-box, and stores the mail in mbox format in filename. The po-box can have any of the follow- ing formats: 'hostname:username' 'po:hostname:username' 'username@hostname' 'po:username@hostname' 'hostname' 'po:username' If no username is specified, push assumes that it's the same as on the local machine; hostname defaults to the value of the MAILHOST environ- ment variable. Supported options: -5, --krb5 use Kerberos 5 (if compiled with support for Kerberos 5) -f, --fork fork before starting to delete messages -l, --leave don't delete fetched mail --from behave like from. -c, --count first print how many messages and bytes there are. --headers=headers a list of comma-separated headers that should get printed. -p port-spec, --port=port-spec use this port instead of the default 'kpop' or '1109'. The default is to first try Kerberos 5 authentication and then, if that fails, Kerberos 4. ENVIRONMENT
MAILHOST points to the post office, if no other hostname is specified. EXAMPLES
$ push cornfield:roosta ~/.emacs-mail-crash-box tries to fetch mail for the user roosta from the post office at ``cornfield'', and stores the mail in ~/.emacs-mail-crash-box (you are using Gnus, aren't you?) $ push --from -5 havregryn tries to fetch From: lines for current user at post office ``havregryn'' using Kerberos 5. SEE ALSO
from(1), pfrom(1), movemail(8), popper(8) HISTORY
push was written while waiting for movemail to finish getting the mail. HEIMDAL
May 31, 1998 HEIMDAL
Check Out this Related Man Page
CALENDARSERVER_MONITOR_NOTIFICATIONS(8) BSD System Manager's Manual CALENDARSERVER_MONITOR_NOTIFICATIONS(8) NAME
calendarserver_monitor_notifications -- Darwin Calendar Server push notification monitor SYNOPSIS
calendarserver_monitor_notifications [--admin username] [--config file] [--host hostname] [--node pubsub-node-name] [--port port-number] [--ssl] [--verbose] [--help] username DESCRIPTION
calendarserver_monitor_notifications is a tool for making sure XMPP push notifications are working properly. Given a username and password it will connect to the calendar server and determine which pubsub node(s) correspond to that user's calendar home, as well as those of any user which has delegated calendar access. Next it will subscribe to those nodes and await notifications, printing them to stdout. An admin- istrator can monitor the push notifications for another user by passing the --admin option. Exit by hitting Control-C. OPTIONS
-a, --admin Authenticate using the credentials of the given administrator. -h, --help Display usage information. -f, --config FILE Use the Calendar Server configuration specified in the given file. Defaults to /etc/caldavd/caldavd.plist. -H, --host HOSTNAME Connect to the specified calendar server. If not passed on the command line, the host name is looked up in the configuration file. -n, --node NODENAME Bypass the auto-discovery of pubsub nodes and specify one explicitly. Useful on calendar servers which don't support the push-trans- ports DAV property. When using this option, the host and port options instead refer to the XMPP server host and port numbers. -p, --port NUMBER Connect to the specified port number. If not passed on the command line, the port number is looked up in the configuration file. -s, --ssl Use https to connect to calendar server (default is http). -v, --verbose Print debugging information. FILES
/etc/caldavd/caldavd.plist The Calendar Server configuration file. SEE ALSO
caldavd(8) BSD
Feb 3, 2011 BSD