VACATION(1) | General Commands Manual | VACATION(1) |
vacation | -dIi [-f databasefile] [-m messagefile] [-r interval] [-t interval] |
vacation | -dj [-a alias] [-F F|R|S] [-f databasefile] [-m messagefile] [-s sender] [-T A|D] login |
\eric, "|/usr/bin/vacation -a allman eric"which would send messages to you (assuming your login name was eric) and reply to any messages for “eric” or “allman”.
Available options:
infinite
” (actually, any non-numeric character) will never send more than one reply. It should be noted that intervals of “0
” are quite dangerous, as it allows mailers to get into “I am on vacation” loops.No message will be sent unless login (or an alias supplied using the -a option) is part of either the “To:” or “Cc:” headers of the mail. No messages from “???-REQUEST”, “Postmaster”, “UUCP”, “MAILER”, or “MAILER-DAEMON” will be replied to (where these strings are case insensitive) nor is a notification sent if a “Precedence: bulk” “Precedence: list” or “Precedence: junk” line is included in the mail headers. The people who have sent you messages are maintained as a db(3) database in the file .vacation.db in your home directory.
vacation expects a file .vacation.msg, in your home directory, containing a message to be sent back to each sender. It should be an entire message (including headers). If the message contains the string $SUBJECT then it will will be replaced with the subject of the original message. For example, it might contain:
From: eric@CS.Berkeley.EDU (Eric Allman) Subject: I am on vacation Delivered-By-The-Graces-Of: The Vacation program Precedence: bulk I am on vacation until July 22. Your mail regarding "$SUBJECT" will be read when I return. If you have something urgent, please contact Keith Bostic <bostic@CS.Berkeley.EDU>. --eric
vacation reads the first line from the standard input for a UNIX “From” line to determine the sender. sendmail(8) includes this “From” line automatically.
Fatal errors, such as calling vacation with incorrect arguments, or with non-existent logins, are logged in the system log file, using syslog(3).
August 19, 2004 | NetBSD 6.1 |