diff options
Diffstat (limited to 'pl_PL.ISO8859-2/books/handbook/mail/chapter.xml')
| -rw-r--r-- | pl_PL.ISO8859-2/books/handbook/mail/chapter.xml | 377 |
1 files changed, 153 insertions, 224 deletions
diff --git a/pl_PL.ISO8859-2/books/handbook/mail/chapter.xml b/pl_PL.ISO8859-2/books/handbook/mail/chapter.xml index 6dddfe3c82..8f31cd62b1 100644 --- a/pl_PL.ISO8859-2/books/handbook/mail/chapter.xml +++ b/pl_PL.ISO8859-2/books/handbook/mail/chapter.xml @@ -4,29 +4,19 @@ $FreeBSD$ --> - -<chapter id="mail"> - <chapterinfo> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="mail"> + <info><title>Electronic Mail</title> <authorgroup> - <author> - <firstname>Bill</firstname> - <surname>Lloyd</surname> - <contrib>Original work by </contrib> - </author> + <author><personname><firstname>Bill</firstname><surname>Lloyd</surname></personname><contrib>Original work by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Jim</firstname> - <surname>Mock</surname> - <contrib>Rewritten by </contrib> - <!-- 2 Dec 1999 --> - </author> + <author><personname><firstname>Jim</firstname><surname>Mock</surname></personname><contrib>Rewritten by </contrib></author> </authorgroup> - </chapterinfo> + </info> - <title>Electronic Mail</title> + - <sect1 id="mail-synopsis"> + <sect1 xml:id="mail-synopsis"> <title>Synopsis</title> <indexterm><primary>email</primary></indexterm> @@ -123,20 +113,18 @@ </itemizedlist> </sect1> - <sect1 id="mail-using"> + <sect1 xml:id="mail-using"> <title>Using Electronic Mail</title> <indexterm><primary>POP</primary></indexterm> <indexterm><primary>IMAP</primary></indexterm> <indexterm><primary>DNS</primary></indexterm> <para>There are five major parts involved in an email exchange. They - are: <link linkend="mail-mua">the user program</link>, <link - linkend="mail-mta">the server daemon</link>, <link - linkend="mail-dns">DNS</link>, <link linkend="mail-receive">a + are: <link linkend="mail-mua">the user program</link>, <link linkend="mail-mta">the server daemon</link>, <link linkend="mail-dns">DNS</link>, <link linkend="mail-receive">a remote or local mailbox</link>, and of course, <link linkend="mail-host">the mailhost itself</link>.</para> - <sect2 id="mail-mua"> + <sect2 xml:id="mail-mua"> <title>The User Program</title> <para>This includes command line programs such as @@ -152,7 +140,7 @@ daemons</link> available, or delivering it over <acronym>TCP</acronym>.</para> </sect2> - <sect2 id="mail-mta"> + <sect2 xml:id="mail-mta"> <title>Mailhost Server Daemon</title> <indexterm> <primary>mail server daemons</primary> @@ -209,7 +197,7 @@ </warning> </sect2> - <sect2 id="mail-dns"> + <sect2 xml:id="mail-dns"> <title>Email and DNS</title> <para>The Domain Name System (DNS) and its daemon @@ -240,7 +228,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen> </sect2> - <sect2 id="mail-receive"> + <sect2 xml:id="mail-receive"> <title>Receiving Mail</title> <indexterm> <primary>email</primary> @@ -260,7 +248,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen> wish to read mail locally, you are not required to install a <acronym>POP</acronym> or <acronym>IMAP</acronym> server.</para> - <sect3 id="pop-and-imap"> + <sect3 xml:id="pop-and-imap"> <title>Accessing remote mailboxes using <acronym>POP</acronym> and <acronym>IMAP</acronym></title> <indexterm><primary>POP</primary></indexterm> @@ -351,7 +339,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen> </warning> </sect3> - <sect3 id="local"> + <sect3 xml:id="local"> <title>Accessing local mailboxes</title> <para>Mailboxes may be accessed locally by directly utilizing @@ -362,7 +350,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen> </sect3> </sect2> - <sect2 id="mail-host"> + <sect2 xml:id="mail-host"> <title>The Mail Host</title> <indexterm><primary>mail host</primary></indexterm> @@ -372,17 +360,13 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen> </sect2> </sect1> - <sect1 id="sendmail"> - <sect1info> + <sect1 xml:id="sendmail"> + <info><title><application>sendmail</application> Configuration</title> <authorgroup> - <author> - <firstname>Christopher</firstname> - <surname>Shumway</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Christopher</firstname><surname>Shumway</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> - <title><application>sendmail</application> Configuration</title> + </info> + <indexterm> <primary><application>sendmail</application></primary> @@ -512,13 +496,13 @@ okay.cyberspammer.com OK handling routine. The message is printed to the remote host when a mail matches the left hand side of the table. The next entry rejects mail from a specific host on the Internet, - <hostid>another.source.of.spam</hostid>. The next entry accepts + <systemitem>another.source.of.spam</systemitem>. The next entry accepts mail connections from a host - <hostid role="fqdn">okay.cyberspammer.com</hostid>, which is more exact than - the <hostid role="domainname">cyberspammer.com</hostid> line above. More specific + <systemitem class="fqdomainname">okay.cyberspammer.com</systemitem>, which is more exact than + the <systemitem class="fqdomainname">cyberspammer.com</systemitem> line above. More specific matches override less exact matches. The last entry allows relaying of electronic mail from hosts with an IP address that - begins with <hostid>128.32</hostid>. These hosts would be able + begins with <systemitem>128.32</systemitem>. These hosts would be able to send mail through this mail server that are destined for other mail servers.</para> @@ -546,14 +530,14 @@ procmail: "|/usr/local/bin/procmail"</programlisting> <para>The file format is simple; the mailbox name on the left side of the colon is expanded to the target(s) on the right. The - first example simply expands the mailbox <username>root</username> - to the mailbox <username>localuser</username>, which is then + first example simply expands the mailbox <systemitem class="username">root</systemitem> + to the mailbox <systemitem class="username">localuser</systemitem>, which is then looked up again in the aliases database. If no match is found, then the message is delivered to the local user - <username>localuser</username>. The next example shows a mail - list. Mail to the mailbox <username>ftp-bugs</username> is - expanded to the three local mailboxes <username>joe</username>, - <username>eric</username>, and <username>paul</username>. Note + <systemitem class="username">localuser</systemitem>. The next example shows a mail + list. Mail to the mailbox <systemitem class="username">ftp-bugs</systemitem> is + expanded to the three local mailboxes <systemitem class="username">joe</systemitem>, + <systemitem class="username">eric</systemitem>, and <systemitem class="username">paul</systemitem>. Note that a remote mailbox could be specified as <email>user@example.com</email>. The next example shows writing mail to a file, in this case <filename>/dev/null</filename>. The last example shows sending @@ -572,8 +556,8 @@ procmail: "|/usr/local/bin/procmail"</programlisting> the local host name. Place any domains or hosts that <application>sendmail</application> is to be receiving mail for. For example, if this mail server was to accept mail for the - domain <hostid role="domainname">example.com</hostid> and the host - <hostid role="fqdn">mail.example.com</hostid>, its + domain <systemitem class="fqdomainname">example.com</systemitem> and the host + <systemitem class="fqdomainname">mail.example.com</systemitem>, its <filename>local-host-names</filename> might look something like this:</para> @@ -626,37 +610,29 @@ postmaster@example.com postmaster@noc.example.net </example> <para>In the above example, we have a mapping for a domain - <hostid role="domainname">example.com</hostid>. This file is processed in a + <systemitem class="fqdomainname">example.com</systemitem>. This file is processed in a first match order down the file. The first item maps - <email>root@example.com</email> to the local mailbox <username>root</username>. The next entry maps - <email>postmaster@example.com</email> to the mailbox <username>postmaster</username> on the host - <hostid role="fqdn">noc.example.net</hostid>. Finally, if nothing from <hostid role="domainname">example.com</hostid> has + <email>root@example.com</email> to the local mailbox <systemitem class="username">root</systemitem>. The next entry maps + <email>postmaster@example.com</email> to the mailbox <systemitem class="username">postmaster</systemitem> on the host + <systemitem class="fqdomainname">noc.example.net</systemitem>. Finally, if nothing from <systemitem class="fqdomainname">example.com</systemitem> has matched so far, it will match the last mapping, which matches every other mail message addressed to someone at - <hostid role="domainname">example.com</hostid>. - This will be mapped to the local mailbox <username>joe</username>.</para> + <systemitem class="fqdomainname">example.com</systemitem>. + This will be mapped to the local mailbox <systemitem class="username">joe</systemitem>.</para> </sect2> </sect1> - <sect1 id="mail-changingmta"> - <sect1info> + <sect1 xml:id="mail-changingmta"> + <info><title>Changing Your Mail Transfer Agent</title> <authorgroup> - <author> - <firstname>Andrew</firstname> - <surname>Boothman</surname> - <contrib>Written by </contrib> - </author> + <author><personname><firstname>Andrew</firstname><surname>Boothman</surname></personname><contrib>Written by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Gregory</firstname> - <surname>Neil Shapiro</surname> - <contrib>Information taken from e-mails written by </contrib> - </author> + <author><personname><firstname>Gregory</firstname><surname>Neil Shapiro</surname></personname><contrib>Information taken from e-mails written by </contrib></author> </authorgroup> - </sect1info> - <title>Changing Your Mail Transfer Agent</title> + </info> + <indexterm> <primary>email</primary> <secondary>change mta</secondary> @@ -700,7 +676,7 @@ postmaster@example.com postmaster@noc.example.net chosen.</para> </sect2> - <sect2 id="mail-disable-sendmail"> + <sect2 xml:id="mail-disable-sendmail"> <title>Disable <application>sendmail</application></title> <para>The procedure used to start @@ -805,7 +781,7 @@ sendmail_msp_queue_enable="NO"</programlisting> <para>Add a script to <filename>/usr/local/etc/rc.d/</filename> that ends in <filename>.sh</filename> and is executable by - <username>root</username>. The script should accept <literal>start</literal> and + <systemitem class="username">root</systemitem>. The script should accept <literal>start</literal> and <literal>stop</literal> parameters. At startup time the system scripts will execute the command</para> @@ -906,7 +882,7 @@ purgestat /usr/local/supermailer/bin/purgestat-compat</programlisting> </sect2> </sect1> - <sect1 id="mail-trouble"> + <sect1 xml:id="mail-trouble"> <title>Troubleshooting</title> <indexterm> <primary>email</primary> @@ -922,27 +898,22 @@ purgestat /usr/local/supermailer/bin/purgestat-compat</programlisting> <answer> <para>You will probably find that the host is actually in a different domain; for example, if you are in - <hostid role="fqdn">foo.bar.edu</hostid> and you wish to reach - a host called <hostid>mumble</hostid> in the <hostid - role="domainname">bar.edu</hostid> domain, you will have to - refer to it by the fully-qualified domain name, <hostid - role="fqdn">mumble.bar.edu</hostid>, instead of just - <hostid>mumble</hostid>.</para> + <systemitem class="fqdomainname">foo.bar.edu</systemitem> and you wish to reach + a host called <systemitem>mumble</systemitem> in the <systemitem class="fqdomainname">bar.edu</systemitem> domain, you will have to + refer to it by the fully-qualified domain name, <systemitem class="fqdomainname">mumble.bar.edu</systemitem>, instead of just + <systemitem>mumble</systemitem>.</para> <para>Traditionally, this was allowed by BSD BIND<indexterm> <primary>BIND</primary></indexterm> resolvers. However the current version of <application>BIND</application> that ships with FreeBSD no longer provides default abbreviations for non-fully qualified domain names other than the domain you - are in. So an unqualified host <hostid>mumble</hostid> must - either be found as <hostid - role="fqdn">mumble.foo.bar.edu</hostid>, or it will be searched + are in. So an unqualified host <systemitem>mumble</systemitem> must + either be found as <systemitem class="fqdomainname">mumble.foo.bar.edu</systemitem>, or it will be searched for in the root domain.</para> <para>This is different from the previous behavior, where the - search continued across <hostid - role="domainname">mumble.bar.edu</hostid>, and <hostid - role="domainname">mumble.edu</hostid>. Have a look at RFC 1535 + search continued across <systemitem class="fqdomainname">mumble.bar.edu</systemitem>, and <systemitem class="fqdomainname">mumble.edu</systemitem>. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole.</para> @@ -989,7 +960,7 @@ itself as domain.net. Add domain.net to /etc/mail/local-host-names to /etc/mail/sendmail.cf.</programlisting> <para>The <application>sendmail</application> FAQ can be found at - <ulink url="http://www.sendmail.org/faq/"></ulink> and is + <uri xlink:href="http://www.sendmail.org/faq/">http://www.sendmail.org/faq/</uri> and is recommended reading if you want to do any <quote>tweaking</quote> of your mail setup.</para> </answer> @@ -1013,8 +984,8 @@ to /etc/mail/sendmail.cf.</programlisting> <para>Another way is to get a full-time Internet server to provide secondary MX<indexterm><primary>MX record</primary></indexterm> services for your domain. For example, if your company's domain is - <hostid role="domainname">example.com</hostid> and your Internet service provider has - set <hostid role="domainname">example.net</hostid> up to provide secondary MX services + <systemitem class="fqdomainname">example.com</systemitem> and your Internet service provider has + set <systemitem class="fqdomainname">example.net</systemitem> up to provide secondary MX services to your domain:</para> <programlisting>example.com. MX 10 example.com. @@ -1022,15 +993,15 @@ to /etc/mail/sendmail.cf.</programlisting> <para>Only one host should be specified as the final recipient (add <literal>Cw example.com</literal> in - <filename>/etc/mail/sendmail.cf</filename> on <hostid role="domainname">example.com</hostid>).</para> + <filename>/etc/mail/sendmail.cf</filename> on <systemitem class="fqdomainname">example.com</systemitem>).</para> <para>When the sending <command>sendmail</command> is trying to - deliver the mail it will try to connect to you (<hostid role="domainname">example.com</hostid>) over the modem + deliver the mail it will try to connect to you (<systemitem class="fqdomainname">example.com</systemitem>) over the modem link. It will most likely time out because you are not online. The program <application>sendmail</application> will automatically deliver it to the - secondary MX site, i.e. your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX + secondary MX site, i.e. your Internet provider (<systemitem class="fqdomainname">example.net</systemitem>). The secondary MX site will then periodically try to connect to - your host and deliver the mail to the primary MX host (<hostid role="domainname">example.com</hostid>).</para> + your host and deliver the mail to the primary MX host (<systemitem class="fqdomainname">example.com</systemitem>).</para> <para>You might want to use something like this as a login script:</para> @@ -1043,7 +1014,7 @@ to /etc/mail/sendmail.cf.</programlisting> <para>If you are going to create a separate login script for a user you could use <command>sendmail -qRexample.com</command> instead in the script above. This will force all mail in your - queue for <hostid role="domainname">example.com</hostid> to be processed immediately.</para> + queue for <systemitem class="fqdomainname">example.com</systemitem> to be processed immediately.</para> <para>A further refinement of the situation is as follows:</para> @@ -1133,13 +1104,13 @@ www.example.org</programlisting> </qandaset> </sect1> - <sect1 id="mail-advanced"> + <sect1 xml:id="mail-advanced"> <title>Advanced Topics</title> <para>The following section covers more involved topics such as mail configuration and setting up mail for your entire domain.</para> - <sect2 id="mail-config"> + <sect2 xml:id="mail-config"> <title>Basic Configuration</title> <indexterm> <primary>email</primary> @@ -1155,15 +1126,13 @@ www.example.org</programlisting> <itemizedlist> <listitem> <para>Run your own name server and have your own domain. For - example, <hostid - role="domainname">FreeBSD.org</hostid></para> + example, <systemitem class="fqdomainname">FreeBSD.org</systemitem></para> </listitem> <listitem> <para>Get mail delivered directly to your host. This is done by delivering mail directly to the current DNS name for your - machine. For example, <hostid - role="fqdn">example.FreeBSD.org</hostid>.</para> + machine. For example, <systemitem class="fqdomainname">example.FreeBSD.org</systemitem>.</para> </listitem> </itemizedlist> @@ -1200,7 +1169,7 @@ example.FreeBSD.org has address 204.216.27.XX</screen> <para>If that is what you see, mail directly to <email role="nolink">yourlogin@example.FreeBSD.org</email> should work without problems (assuming <application>sendmail</application> is - running correctly on <hostid role="fqdn">example.FreeBSD.org</hostid>).</para> + running correctly on <systemitem class="fqdomainname">example.FreeBSD.org</systemitem>).</para> <para>If instead you see something like this:</para> @@ -1208,9 +1177,8 @@ example.FreeBSD.org has address 204.216.27.XX</screen> example.FreeBSD.org has address 204.216.27.XX example.FreeBSD.org mail is handled (pri=10) by hub.FreeBSD.org</screen> - <para>All mail sent to your host (<hostid - role="fqdn">example.FreeBSD.org</hostid>) will end up being - collected on <hostid>hub</hostid> under the same username instead + <para>All mail sent to your host (<systemitem class="fqdomainname">example.FreeBSD.org</systemitem>) will end up being + collected on <systemitem>hub</systemitem> under the same username instead of being sent directly to your host.</para> <para>The above information is handled by your DNS server. The DNS @@ -1219,8 +1187,7 @@ example.FreeBSD.org mail is handled (pri=10) by hub.FreeBSD.org</screen> no MX record exists, mail will be delivered directly to the host by way of its IP address.</para> - <para>The MX entry for <hostid - role="fqdn">freefall.FreeBSD.org</hostid> at one time looked like + <para>The MX entry for <systemitem class="fqdomainname">freefall.FreeBSD.org</systemitem> at one time looked like this:</para> <programlisting>freefall MX 30 mail.crl.net @@ -1228,7 +1195,7 @@ freefall MX 40 agora.rdrop.com freefall MX 10 freefall.FreeBSD.org freefall MX 20 who.cdrom.com</programlisting> - <para>As you can see, <hostid>freefall</hostid> had many MX entries. + <para>As you can see, <systemitem>freefall</systemitem> had many MX entries. The lowest MX number is the host that receives mail directly if available; if it is not accessible for some reason, the others (sometimes called <quote>backup MXes</quote>) accept messages @@ -1241,14 +1208,13 @@ freefall MX 20 who.cdrom.com</programlisting> you.</para> </sect2> - <sect2 id="mail-domain"> + <sect2 xml:id="mail-domain"> <title>Mail for Your Domain</title> <para>In order to set up a <quote>mailhost</quote> (a.k.a. mail server) you need to have any mail sent to various workstations directed to it. Basically, you want to <quote>claim</quote> any - mail for any hostname in your domain (in this case <hostid - role="fqdn">*.FreeBSD.org</hostid>) and divert it to your mail + mail for any hostname in your domain (in this case <systemitem class="fqdomainname">*.FreeBSD.org</systemitem>) and divert it to your mail server so your users can receive their mail on the master mail server.</para> @@ -1275,20 +1241,18 @@ freefall MX 20 who.cdrom.com</programlisting> <para>If you are doing virtual email hosting, the following information will come in handy. For this example, we will assume you have a customer with his own domain, in this - case <hostid role="domainname">customer1.org</hostid>, and you want - all the mail for <hostid role="domainname">customer1.org</hostid> - sent to your mailhost, <hostid - role="fqdn">mail.myhost.com</hostid>. The entry in your DNS + case <systemitem class="fqdomainname">customer1.org</systemitem>, and you want + all the mail for <systemitem class="fqdomainname">customer1.org</systemitem> + sent to your mailhost, <systemitem class="fqdomainname">mail.myhost.com</systemitem>. The entry in your DNS should look like this:</para> <programlisting>customer1.org MX 10 mail.myhost.com</programlisting> - <para>You do <emphasis>not</emphasis> need an A record for <hostid role="domainname">customer1.org</hostid> if you only + <para>You do <emphasis>not</emphasis> need an A record for <systemitem class="fqdomainname">customer1.org</systemitem> if you only want to handle email for that domain.</para> <note> - <para>Be aware that pinging <hostid - role="domainname">customer1.org</hostid> will not work unless + <para>Be aware that pinging <systemitem class="fqdomainname">customer1.org</systemitem> will not work unless an A record exists for it.</para> </note> @@ -1317,7 +1281,7 @@ freefall MX 20 who.cdrom.com</programlisting> </sect2> </sect1> - <sect1 id="SMTP-UUCP"> + <sect1 xml:id="SMTP-UUCP"> <title>SMTP with UUCP</title> <para>The <application>sendmail</application> configuration that ships with FreeBSD is @@ -1421,8 +1385,8 @@ if-bus.UUCP uucp-dom:if-bus mail to the local Ethernet domain that can be delivered using SMTP. Finally, the UUCP neighbors are mentioned in the .UUCP pseudo-domain notation, to allow for a - <literal><replaceable>uucp-neighbor - </replaceable>!<replaceable>recipient</replaceable></literal> + <literal>uucp-neighbor + !recipient</literal> override of the default rules. The last line is always a single dot, matching everything else, with UUCP delivery to a UUCP neighbor that serves as your universal mail gateway to the @@ -1444,8 +1408,7 @@ if-bus.UUCP uucp-dom:if-bus by the address you wish to test for the mail routing. The last line tells you the used internal mail agent, the destination host this agent will be called with, and the (possibly - translated) address. Leave this mode by typing <keycombo - action="simul"><keycap>Ctrl</keycap><keycap>D</keycap></keycombo>.</para> + translated) address. Leave this mode by typing <keycombo action="simul"><keycap>Ctrl</keycap><keycap>D</keycap></keycombo>.</para> <screen>&prompt.user; <userinput>sendmail -bt</userinput> ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) @@ -1457,18 +1420,14 @@ parse returns: $# uucp-dom $@ <replaceable>your.uucp.relay</replaceab <prompt>></prompt> <userinput>^D</userinput></screen> </sect1> - <sect1 id="outgoing-only"> - <sect1info> + <sect1 xml:id="outgoing-only"> + <info><title>Setting Up to Send Only</title> <authorgroup> - <author> - <firstname>Bill</firstname> - <surname>Moran</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Bill</firstname><surname>Moran</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> + </info> - <title>Setting Up to Send Only</title> + <para>There are many instances where you may only want to send mail through a relay. Some examples are:</para> @@ -1500,14 +1459,14 @@ parse returns: $# uucp-dom $@ <replaceable>your.uucp.relay</replaceab <quote>mail server</quote>.</para> <para>The easiest way to fulfill those needs is to install the - <filename role="package">mail/ssmtp</filename> port. Execute - the following commands as <username>root</username>:</para> + <package>mail/ssmtp</package> port. Execute + the following commands as <systemitem class="username">root</systemitem>:</para> <screen>&prompt.root; <userinput>cd /usr/ports/mail/ssmtp</userinput> &prompt.root; <userinput>make install replace clean</userinput></screen> <para>Once installed, - <filename role="package">mail/ssmtp</filename> can be configured + <package>mail/ssmtp</package> can be configured with a four-line file located at <filename>/usr/local/etc/ssmtp/ssmtp.conf</filename>:</para> @@ -1517,8 +1476,8 @@ rewriteDomain=example.com hostname=_HOSTNAME_</programlisting> <para>Make sure you use your real email address for - <username>root</username>. Enter your ISP's outgoing mail relay - in place of <hostid role="fqdn">mail.example.com</hostid> (some ISPs call + <systemitem class="username">root</systemitem>. Enter your ISP's outgoing mail relay + in place of <systemitem class="fqdomainname">mail.example.com</systemitem> (some ISPs call this the <quote>outgoing mail server</quote> or <quote>SMTP server</quote>).</para> @@ -1526,7 +1485,7 @@ hostname=_HOSTNAME_</programlisting> including the outgoing mail service. See <xref linkend="mail-disable-sendmail"/> for details.</para> - <para><filename role="package">mail/ssmtp</filename> has some + <para><package>mail/ssmtp</package> has some other options available. See the example configuration file in <filename>/usr/local/etc/ssmtp</filename> or the manual page of <application>ssmtp</application> for some examples and more @@ -1538,7 +1497,7 @@ hostname=_HOSTNAME_</programlisting> policy or allowing your computer to be hijacked for spamming.</para> </sect1> - <sect1 id="SMTP-dialup"> + <sect1 xml:id="SMTP-dialup"> <title>Using Mail with a Dialup Connection</title> <para>If you have a static IP address, you should not need to @@ -1548,18 +1507,16 @@ hostname=_HOSTNAME_</programlisting> <para>If you have a dynamically assigned IP number and use a dialup PPP connection to the Internet, you will probably have a mailbox on your ISPs mail server. Let's assume your ISP's domain - is <hostid role="domainname">example.net</hostid>, and that your - user name is <username>user</username>, you have called your - machine <hostid role="fqdn">bsd.home</hostid>, and your ISP has - told you that you may use <hostid - role="fqdn">relay.example.net</hostid> as a mail relay.</para> + is <systemitem class="fqdomainname">example.net</systemitem>, and that your + user name is <systemitem class="username">user</systemitem>, you have called your + machine <systemitem class="fqdomainname">bsd.home</systemitem>, and your ISP has + told you that you may use <systemitem class="fqdomainname">relay.example.net</systemitem> as a mail relay.</para> <para>In order to retrieve mail from your mailbox, you must install a retrieval agent. The <application>fetchmail</application> utility is a good choice as it supports many different protocols. This program is available - as a package or from the Ports Collection (<filename - role="package">mail/fetchmail</filename>). Usually, your <acronym>ISP</acronym> will + as a package or from the Ports Collection (<package>mail/fetchmail</package>). Usually, your <acronym>ISP</acronym> will provide <acronym>POP</acronym>. If you are using user <acronym>PPP</acronym>, you can automatically fetch your mail when an Internet connection is established with the following entry in @@ -1579,16 +1536,14 @@ hostname=_HOSTNAME_</programlisting> <programlisting> !bg su user -c "sendmail -q"</programlisting> <para>Assume that you have an account for - <username>user</username> on <hostid - role="fqdn">bsd.home</hostid>. In the home directory of - <username>user</username> on <hostid - role="fqdn">bsd.home</hostid>, create a + <systemitem class="username">user</systemitem> on <systemitem class="fqdomainname">bsd.home</systemitem>. In the home directory of + <systemitem class="username">user</systemitem> on <systemitem class="fqdomainname">bsd.home</systemitem>, create a <filename>.fetchmailrc</filename> file:</para> <programlisting>poll example.net protocol pop3 fetchall pass MySecret</programlisting> <para>This file should not be readable by anyone except - <username>user</username> as it contains the password + <systemitem class="username">user</systemitem> as it contains the password <literal>MySecret</literal>.</para> <para>In order to send mail with the correct @@ -1596,8 +1551,7 @@ hostname=_HOSTNAME_</programlisting> <application>sendmail</application> to use <email>user@example.net</email> rather than <email role="nolink">user@bsd.home</email>. You may also wish to tell - <application>sendmail</application> to send all mail via <hostid - role="fqdn">relay.example.net</hostid>, allowing quicker mail + <application>sendmail</application> to send all mail via <systemitem class="fqdomainname">relay.example.net</systemitem>, allowing quicker mail transmission.</para> <para>The following <filename>.mc</filename> file should @@ -1627,18 +1581,14 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting> <filename>sendmail.cf</filename>.</para> </sect1> - <sect1 id="SMTP-Auth"> - <sect1info> + <sect1 xml:id="SMTP-Auth"> + <info><title>SMTP Authentication</title> <authorgroup> - <author> - <firstname>James</firstname> - <surname>Gorham</surname> - <contrib>Written by </contrib> - </author> + <author><personname><firstname>James</firstname><surname>Gorham</surname></personname><contrib>Written by </contrib></author> </authorgroup> - </sect1info> + </info> - <title>SMTP Authentication</title> + <para>Having <acronym>SMTP</acronym> Authentication in place on your mail server has a number of benefits. @@ -1650,10 +1600,10 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting> <procedure> <step> - <para>Install <filename role="package">security/cyrus-sasl</filename> + <para>Install <package>security/cyrus-sasl</package> from the ports. You can find this port in - <filename role="package">security/cyrus-sasl</filename>. - <filename role="package">security/cyrus-sasl</filename> has + <package>security/cyrus-sasl</package>. + <package>security/cyrus-sasl</package> has a number of compile time options to choose from and, for the method we will be using here, make sure to select the <option>pwcheck</option> option.</para> @@ -1661,7 +1611,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting> <step> - <para>After installing <filename role="package">security/cyrus-sasl</filename>, + <para>After installing <package>security/cyrus-sasl</package>, edit <filename>/usr/local/lib/sasl/Sendmail.conf</filename> (or create it if it does not exist) and add the following line:</para> @@ -1686,8 +1636,8 @@ SENDMAIL_LDADD=-lsasl</programlisting> <para>These lines will give <application>sendmail</application> the proper configuration options for linking - to <filename role="package">cyrus-sasl</filename> at compile time. - Make sure that <filename role="package">cyrus-sasl</filename> + to <package>cyrus-sasl</package> at compile time. + Make sure that <package>cyrus-sasl</package> has been installed before recompiling <application>sendmail</application>.</para> </step> @@ -1754,22 +1704,18 @@ define(`confDEF_AUTH_INFO', `/etc/mail/auth-info')dnl</programlisting> <para>For more information, please see the <application>sendmail</application> page regarding - <ulink url="http://www.sendmail.org/~ca/email/auth.html"> - <acronym>SMTP</acronym> authentication</ulink>.</para> + <link xlink:href="http://www.sendmail.org/~ca/email/auth.html"> + <acronym>SMTP</acronym> authentication</link>.</para> </sect1> - <sect1 id="mail-agents"> - <sect1info> + <sect1 xml:id="mail-agents"> + <info><title>Mail User Agents</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Silver</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Silver</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> - <title>Mail User Agents</title> + </info> + <indexterm> <primary>Mail User Agents</primary> @@ -1790,7 +1736,7 @@ define(`confDEF_AUTH_INFO', `/etc/mail/auth-info')dnl</programlisting> or <command>mail</command>, or the web interfaces used by some large organizations.</para> - <sect2 id="mail-command"> + <sect2 xml:id="mail-command"> <title>mail</title> <para>&man.mail.1; is the default Mail User Agent @@ -1805,8 +1751,7 @@ define(`confDEF_AUTH_INFO', `/etc/mail/auth-info')dnl</programlisting> <acronym>IMAP</acronym> servers, these mailboxes may be downloaded to a local <filename>mbox</filename> file using an application such as <application>fetchmail</application>, which - will be discussed later in this chapter (<xref - linkend="mail-fetchmail"/>).</para> + will be discussed later in this chapter (<xref linkend="mail-fetchmail"/>).</para> <para>In order to send and receive email, simply invoke the <command>mail</command> command as per the following @@ -1815,7 +1760,7 @@ define(`confDEF_AUTH_INFO', `/etc/mail/auth-info')dnl</programlisting> <screen>&prompt.user; <userinput>mail</userinput></screen> <para>The contents of the user mailbox in - <filename class="directory">/var/mail</filename> are + <filename>/var/mail</filename> are automatically read by the <command>mail</command> utility. Should the mailbox be empty, the utility exits with a message indicating that no mails could be found. Once the @@ -1825,7 +1770,7 @@ define(`confDEF_AUTH_INFO', `/etc/mail/auth-info')dnl</programlisting> <screen>Mail version 8.1 6/6/93. Type ? for help. "/var/mail/marcs": 3 messages 3 new ->N 1 root@localhost Mon Mar 8 14:05 14/510 "test" +>N 1 root@localhost Mon Mar 8 14:05 14/510 "test" N 2 root@localhost Mon Mar 8 14:05 14/509 "user account" N 3 root@localhost Mon Mar 8 14:05 14/509 "sample"</screen> @@ -1899,13 +1844,12 @@ EOT</screen> them very poorly. Newer <acronym>MUA</acronym>s such as <application>mutt</application> handle attachments in a much more intelligent way. But should you still wish to use the - <command>mail</command> command, the <filename - role="package">converters/mpack</filename> port may be of + <command>mail</command> command, the <package>converters/mpack</package> port may be of considerable use.</para> </note> </sect2> - <sect2 id="mutt-command"> + <sect2 xml:id="mutt-command"> <title>mutt</title> <para><application>mutt</application> is a small yet very @@ -1937,23 +1881,19 @@ EOT</screen> <para>All of these features help to make <application>mutt</application> one of the most advanced mail - user agents available. See <ulink - url="http://www.mutt.org"></ulink> for more + user agents available. See <uri xlink:href="http://www.mutt.org">http://www.mutt.org</uri> for more information on <application>mutt</application>.</para> <para>The stable version of <application>mutt</application> may be - installed using the <filename - role="package">mail/mutt</filename> port, while the current - development version may be installed via the <filename - role="package">mail/mutt-devel</filename> port. After the port + installed using the <package>mail/mutt</package> port, while the current + development version may be installed via the <package>mail/mutt-devel</package> port. After the port has been installed, <application>mutt</application> can be started by issuing the following command:</para> <screen>&prompt.user; <userinput>mutt</userinput></screen> <para><application>mutt</application> will automatically read the - contents of the user mailbox in <filename - class="directory">/var/mail</filename> and display the contents + contents of the user mailbox in <filename>/var/mail</filename> and display the contents if applicable. If no mails are found in the user mailbox, then <application>mutt</application> will wait for commands from the user. The example below shows <application>mutt</application> @@ -2014,7 +1954,7 @@ EOT</screen> keyboard shortcuts where appropriate.</para> </sect2> - <sect2 id="pine-command"> + <sect2 xml:id="pine-command"> <title>pine</title> <para><application>pine</application> is aimed at a beginner @@ -2033,8 +1973,7 @@ EOT</screen> </warning> <para>The current version of <application>pine</application> may - be installed using the <filename - role="package">mail/pine4</filename> port. Once the port has + be installed using the <package>mail/pine4</package> port. Once the port has installed, <application>pine</application> can be started by issuing the following command:</para> @@ -2064,7 +2003,7 @@ EOT</screen> specific to the task at hand are shown.</para> <para>The default directory opened by <application>pine</application> - is the <filename class="directory">inbox</filename>. To view the message index, press + is the <filename>inbox</filename>. To view the message index, press <keycap>I</keycap>, or select the <guimenuitem>MESSAGE INDEX</guimenuitem> option as seen below:</para> @@ -2117,23 +2056,19 @@ EOT</screen> <para>The <application>pine</application> application can be customized using the <guimenuitem>SETUP</guimenuitem> option from the main - menu. Consult <ulink url="http://www.washington.edu/pine/"></ulink> + menu. Consult <uri xlink:href="http://www.washington.edu/pine/">http://www.washington.edu/pine/</uri> for more information.</para> </sect2> </sect1> - <sect1 id="mail-fetchmail"> - <sect1info> + <sect1 xml:id="mail-fetchmail"> + <info><title>Using fetchmail</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Silver</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Silver</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> - <title>Using fetchmail</title> + </info> + <indexterm> <primary>fetchmail</primary> @@ -2145,7 +2080,7 @@ EOT</screen> <acronym>IMAP</acronym> and <acronym>POP</acronym> servers and save it into local mailboxes; there it can be accessed more easily. <application>fetchmail</application> can be installed using the - <filename role="package">mail/fetchmail</filename> port, and + <package>mail/fetchmail</package> port, and offers various features, some of which include:</para> <itemizedlist> @@ -2188,11 +2123,10 @@ EOT</screen> <para>The following <filename>.fetchmailrc</filename> serves as an example for downloading a single user mailbox using <acronym>POP</acronym>. It tells - <application>fetchmail</application> to connect to <hostid - role="fqdn">example.com</hostid> using a username of - <username>joesoap</username> and a password of + <application>fetchmail</application> to connect to <systemitem class="fqdomainname">example.com</systemitem> using a username of + <systemitem class="username">joesoap</systemitem> and a password of <literal>XXX</literal>. This example assumes that the user - <username>joesoap</username> is also a user on the local + <systemitem class="username">joesoap</systemitem> is also a user on the local system.</para> <programlisting>poll example.com protocol pop3 username "joesoap" password "XXX"</programlisting> @@ -2218,21 +2152,16 @@ user "john", with password "XXXXX", is "myth" here;</programlisting> <screen>&prompt.user; <userinput>fetchmail -d 600</userinput></screen> <para>More information on <application>fetchmail</application> can - be found at <ulink - url="http://fetchmail.berlios.de/"></ulink>.</para> + be found at <uri xlink:href="http://fetchmail.berlios.de/">http://fetchmail.berlios.de/</uri>.</para> </sect1> - <sect1 id="mail-procmail"> - <sect1info> + <sect1 xml:id="mail-procmail"> + <info><title>Using procmail</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Silver</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Silver</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> - <title>Using procmail</title> + </info> + <indexterm> <primary>procmail</primary> @@ -2244,7 +2173,7 @@ user "john", with password "XXXXX", is "myth" here;</programlisting> matched to incoming mails to perform specific functions or to reroute mail to alternative mailboxes and/or email addresses. <application>procmail</application> can be installed using the - <filename role="package">mail/procmail</filename> port. Once + <package>mail/procmail</package> port. Once installed, it can be directly integrated into most <acronym>MTA</acronym>s; consult your <acronym>MTA</acronym> documentation for more information. Alternatively, @@ -2292,7 +2221,7 @@ alternate</programlisting> ^Subject:.*Spam /dev/null</programlisting> - <para>A useful recipe that parses incoming <hostid role="domainname">&os;.org</hostid> mailing lists + <para>A useful recipe that parses incoming <systemitem class="fqdomainname">&os;.org</systemitem> mailing lists and places each list in its own mailbox:</para> <programlisting>:0 |