meillo@0: <?xml version="1.0" standalone='no'?>
meillo@0: <!DOCTYPE spec SYSTEM "man.dtd">
meillo@0: 
meillo@0: <manpage name="masqmail" section="8" desc="An offline Mail Transfer Agent">
meillo@0: 
meillo@0: <synopsis>
meillo@0: <cmd>/usr/sbin/masqmail [-C <arg>file</arg>] [-odq] [-bd] [-q<arg>interval</arg>]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-odq] [-bs]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-bp]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-q]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-qo [<arg>name</arg>]]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-odq] [-g [<arg>name</arg>]]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-odq] [-go [<arg>name</arg>]]</cmd>
meillo@0: <cmd>/usr/sbin/masqmail [-t] [-oi] [-f <arg>address</arg>] [--] <arg>address...</arg></cmd>
meillo@0: <cmd>/usr/sbin/mailq</cmd>
meillo@0: </synopsis>
meillo@0: 
meillo@0: <description>
meillo@0: <p>MasqMail is a mail server designed for hosts that do
meillo@0: not have a permanent internet connection eg. a home network or a
meillo@0: single host at home. It has special support for connections to
meillo@0: different ISPs. It replaces sendmail or other MTAs such as qmail or
meillo@0: exim. It can also act as a pop3 client.</p>
meillo@0: </description>
meillo@0: 
meillo@0: <options>
meillo@0: <p>Since masqmail is intended to replace sendmail, it uses the same
meillo@0: command line options, but not all are implemented. There are also two
meillo@0: additional options, which are unique to masqmail (-qo <arg>connection</arg> and -g)
meillo@0: </p>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>--</opt></p>
meillo@0: <optdesc><p>Not a 'real' option, it means that all following arguments are to
meillo@0: be understood as arguments and not as options even if they begin with a
meillo@0: leading dash '-'. Mutt is known to call sendmail with this option.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-bd</opt></p>
meillo@0: <optdesc><p>Run as daemon, accepting connections, usually on port 25 if not
meillo@0: configured differently. This is usually used in the startup script at system boot and
meillo@0: together with the -q option (see below).</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-bi</opt></p>
meillo@0: <optdesc><p>Old sendmail rebuilds its alias database when invoked with this
meillo@0: option. Masqmail ignores it. Masqmail reads directly from the file
meillo@0: given with <b>alias_file</b> in the config file.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-bp</opt></p>
meillo@0: <optdesc><p>Show the messages in the queue. Same as calling masqmail as
meillo@0: 'mailq'.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-bs</opt></p>
meillo@0: <optdesc><p>Accept SMTP commands from stdin. Some mailers (eg pine) use this
meillo@0: option as an interface. It can also be used to call masqmail from
meillo@0: inetd.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-B <arg>arg</arg></opt></p>
meillo@0: <optdesc><p><arg>arg</arg> is usually 8BITMIME. Some mailers use this
meillo@0: to indicate that the message contains characters &gt; 127. Masqmail is
meillo@0: 8-bit clean and ignores this, so you do not have to recompile elm,
meillo@0: which is very painful ;-). Note though that this violates some
meillo@0: conventions: masqmail <em>does not</em> convert 8 bit messages to any
meillo@0: MIME format if it encounters a mail server which does not advertise
meillo@0: its 8BITMIME capability, masqmail does not advertise this itself. This
meillo@0: is the same practice as that of exim (but different to
meillo@0: sendmail).</p></optdesc></option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-bV </opt></p>
meillo@0: <optdesc><p>Show version information.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-C </opt><arg>filename</arg></p>
meillo@0: <optdesc><p>Use another configuration than <file>/etc/masqmail/masqmail.conf</file>. Useful for
meillo@0: debugging purposes. If not invoked by a privileged user, masqmail will drop all privileges.
meillo@0: </p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-d <arg>number</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set the debug level. This takes precedence before the value of
meillo@0: <b>debug_level</b> in the configuration file. Read the warning in the
meillo@0: description of the latter.
meillo@0: </p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-f [<arg>address</arg>]</opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set the return path address to <arg>address</arg>. Only root, the
meillo@0: user mail and anyoune in group trusted is allowed to do that.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-F [<arg>string</arg>]</opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set the full sender name (in the From: header)
meillo@0: to <arg>string</arg>.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-g [<arg>name</arg>]</opt></p>
meillo@0: <optdesc>
meillo@0: <p>Get mail (using pop3 or apop), using the configurations given
meillo@0: with <b>get.<arg>name</arg></b> in the main configuration. Without <arg>name</arg>,
meillo@0: all get configurations will be used. See also <manref
meillo@0: name = "masqmail.get" section="5" href="masqmail.get.5.html"/></p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-go [<arg>interval</arg>] [<arg>name</arg>]</opt></p>
meillo@0: <optdesc>
meillo@0: <p>Can be followed by a connection name. Use this option in your
meillo@0: script which starts as soon as a link to the internet has been set up
meillo@0: (usually ip-up). When masqmail is called with this option, the
meillo@0: specified get configuration(s) is(are) read and mail will be
meillo@0: retrieved from servers on the internet.
meillo@0: The <arg>name</arg> is defined
meillo@0: in the configuration (see <opt>online_gets.<arg>name</arg></opt>).
meillo@0: </p><p>
meillo@0: If called with an interval option (recognized by a digit
meillo@0: as the first characater), masqmail starts as a daemon and tries to
meillo@0: get mail in these intervals. It checks for the online status first.
meillo@0: Example: masqmail -go 5m will retrieve mail
meillo@0: all five minutes.
meillo@0: </p><p>
meillo@0: If called without <arg>name</arg> the online status is determined with
meillo@0: the configured method (see <opt>online_detect</opt> in <a
meillo@0: href="config.html">config.html</a>).
meillo@0: </p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-i</opt></p>
meillo@0: <optdesc><p>Same as <b>-oi</b>, see below.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-Mrm <arg>list</arg></opt></p>
meillo@0: <optdesc><p>Remove given messages from the queue. Only allowed for privileged users.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-oem</opt></p>
meillo@0: <optdesc><p>If the <b>-oi</b> ist not also given, always return with a non zero
meillo@0: return code. Maybe someone tells me what this is good for...</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-odb</opt></p>
meillo@0: <optdesc><p>Deliver in background. Masqmail always does this, which
meillo@0: makes this option pretty much useless.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-odq</opt></p>
meillo@0: <optdesc><p>Do not attempt to deliver immediately. Any messages will be queued
meillo@0: until the next queue running process picks them up and delivers
meillo@0: them. You get the same effect by setting the <i>do_queue</i> option in
meillo@0: /etc/masqmail/masqmail.conf.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-oi</opt></p>
meillo@0: <optdesc><p>A dot as a single character in a line does <em>not</em> terminate
meillo@0: the message.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-q [<arg>interval</arg>]</opt></p>
meillo@0: <optdesc><p>If not given with an argument, run a queue process, ie. try to
meillo@0: deliver all messages in the queue. Masqmail sends only to those
meillo@0: addresses that are on the <em>local</em> net, not to those that are
meillo@0: outside. Use -qo for those.</p>
meillo@0: <p>
meillo@0: If you have configured inetd to start masqmail, you can use this
meillo@0: option in a cron job which starts in regular time intervals, to mimic
meillo@0: the same effect as starting masqmail with -bd -q30m.
meillo@0: </p><p>
meillo@0: An argument may be a time interval ie. a numerical value followed
meillo@0: by one of the letters. s,m,h,d,w which are interpreted as seconds,
meillo@0: minutes, hours, days or weeks respectively. Example: -q30m. Masqmail
meillo@0: starts as a daemon and a queue runner process will be started
meillo@0: automatically once in this time interval. This is usually used
meillo@0: together with -bd (see above).
meillo@0: </p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-qo [<arg>name</arg>]</opt></p>
meillo@0: <optdesc>
meillo@0: <p>Can be followed by a connection name. Use this option in your
meillo@0: script which starts as soon as a link to the internet has been set up
meillo@0: (usually ip-up). When masqmail is called with this option, the
meillo@0: specified route configuration is read and the queued mail with
meillo@0: destinations on the internet will be sent. The <arg>name</arg> is defined
meillo@0: in the configuration (see <opt>online_routes.<arg>name</arg></opt>).
meillo@0: </p><p>
meillo@0: If called without <arg>name</arg> the online status is determined with
meillo@0: the configured method (see <opt>online_detect</opt> in <a
meillo@0: href="config.html">config.html</a>)
meillo@0: </p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-t</opt></p>
meillo@0: <optdesc><p>Read recipients from headers. Delete 'Bcc:' headers. If any
meillo@0: arguments are given, these are interpreted as recipient addresses and
meillo@0: the message will <em>not</em> be sent to these.</p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>-v</opt></p>
meillo@0: <optdesc><p>Log also to stdout. Currently, some log messages are
meillo@0: marked as 'write to stdout' and additionally, all messages with
meillo@0: priority 'LOG_ALERT' and 'LOG_WARNING' will be written to stdout
meillo@0: if this option is given. It is disabled in daemon mode.
meillo@0: </p></optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: </options>
meillo@0: 
meillo@0: <section name = "Environment for pipes and mdas">
meillo@0: 
meillo@0: <p>For security reasons, before any pipe command from an alias
meillo@0: expansion or an mda is called, the environment variables will be
meillo@0: completely discarded and newly set up. These are:</p>
meillo@0: <p>SENDER, RETURN_PATH - the return path.</p>
meillo@0: <p>SENDER_DOMAIN - the domain part of the return path.</p>
meillo@0: <p>SENDER_LOCAL - the local part of the return path.</p>
meillo@0: <p>RECEIVED_HOST - the host the message was received from (unless local).</p>
meillo@0: <p>LOCAL_PART, USER, LOGNAME - the local part of the (original) recipient.</p>
meillo@0: <p>MESSAGE_ID - the unique message id. This is not necessarily identical with the Message ID as given in the Message ID: header.</p>
meillo@0: <p>QUALIFY_DOMAIN - the domain which will be appended to unqualified addresses.</p>
meillo@0: 
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "Files">
meillo@0: <p><file>/etc/masqmail/masqmail.conf</file> is the main configuration
meillo@0: for masqmail. Depending on the settings in this file, you will also
meillo@0: have other configuration files in <file>/etc/masqmail/</file>.</p>
meillo@0: <p><file>/etc/aliases</file> is the alias file, if not set differently
meillo@0: in <file>/etc/masqmail/masqmail.conf</file>.</p>
meillo@0: <p><file>/var/spool/masqmail/</file> is the spool directory where masqmail
meillo@0: stores its spooled messages and the uniq pop ids.</p>
meillo@0: <p><file>/var/spool/mail/</file> is the directory where locally delivered mail will be put, if not configured differently in <file>masqmail.conf</file>.</p>
meillo@0: <p><file>/var/log/masqmail/</file> is the directory where masqmail stores
meillo@0: its log mesages. This can also be somewhere else if configured
meillo@0: differently by your sysadmin or the package mantainer.</p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name="Conforming to">
meillo@0: <p><b>RFC 821, 822, 1869, 1870, 2197, 2554</b> (SMTP)</p>
meillo@0: <p><b>RFC 1725, 1939</b> (POP3)</p>
meillo@0: <p><b>RFC 1321</b> (MD5)</p>
meillo@0: <p><b>RFC 2195</b> (CRAM-MD5)</p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "Author">
meillo@0: <p>masqmail was written by Oliver Kurth
meillo@0: &lt;oku@masqmail.cx&gt;</p><p>You will find the newest version of
meillo@0: masqmail at <url href="http://masqmail.cx/masqmail/"/> or search for it
meillo@0: in freshmeat (<url href="http://www.freshmeat.net"/>). There is also a mailing list,
meillo@0: you will find information about it at masqmails main site.</p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "Bugs">
meillo@0: <p>You should report them to the mailing list.</p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "See also">
meillo@0: <p>
meillo@0: <manref name="masqmail.conf" section="5" href="masqmail.conf.5.html"/>, <manref name="masqmail.route" section="5" href="masqmail.route.5.html"/>, <manref name="masqmail.get" section="5" href="masqmail.get.5.html"/>, <manref name="masqmail.aliases" section="5" href="masqmail.aliases.5.html"/>
meillo@0: </p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "Comments">
meillo@0: <p>This man page was written using <manref name="xml2man" section="1"
meillo@0: href="http://masqmail.cx/xml2man/"/> by the same author.</p>
meillo@0: </section>
meillo@0: 
meillo@0: </manpage>