From owner-svn-doc-all@FreeBSD.ORG Fri May 9 17:02:55 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E7C81B0; Fri, 9 May 2014 17:02:55 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A499B66; Fri, 9 May 2014 17:02:55 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s49H2tFd066280; Fri, 9 May 2014 17:02:55 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s49H2tjM066279; Fri, 9 May 2014 17:02:55 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405091702.s49H2tjM066279@svn.freebsd.org> From: Dru Lavigne Date: Fri, 9 May 2014 17:02:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44799 - head/en_US.ISO8859-1/books/handbook/mail X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 17:02:55 -0000 Author: dru Date: Fri May 9 17:02:54 2014 New Revision: 44799 URL: http://svnweb.freebsd.org/changeset/doc/44799 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mail/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Fri May 9 16:17:58 2014 (r44798) +++ head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Fri May 9 17:02:54 2014 (r44799) @@ -5,30 +5,31 @@ $FreeBSD$ --> - Electronic Mail + + Electronic Mail + - BillLloydOriginal work by + BillLloydOriginal + work by - JimMockRewritten by + JimMockRewritten + by - - Synopsis email Electronic Mail, better known as email, is - one of the most widely used forms of communication today. - This chapter provides a basic introduction to running a mail - server on &os;, as well as an introduction to sending and - receiving email using &os;. - For more complete coverage of this subject, - refer to the books listed in - . + one of the most widely used forms of communication today. This + chapter provides a basic introduction to running a mail server + on &os;, as well as an introduction to sending and receiving + email using &os;. For more complete coverage of this subject, + refer to the books listed in . After reading this chapter, you will know: @@ -49,8 +50,8 @@ - How to block spammers from illegally using a mail - server as a relay. + How to block spammers from illegally using a mail server + as a relay. @@ -98,7 +99,8 @@ - Properly set up a network connection (). + Properly set up a network connection (). @@ -135,7 +137,7 @@ mail server daemons Exim - + email receiving @@ -144,139 +146,149 @@ There are five major parts involved in an email exchange: the Mail User Agent (MUA), the Mail Transfer - Agent (MTA), a mail host, a remote - or local mailbox, and DNS. This section provides an + Agent (MTA), a mail host, a remote or local + mailbox, and DNS. This section provides an overview of these components. - + Mail User Agent (MUA) The Mail User Agent (MUA) is an - application which is used to compose, send, and receive - emails. This application can be a command line program, such as - the built-in mail utility or a third-party - application from the Ports Collection, such as - mutt, - alpine, or - elm. - Dozens of graphical programs are also available in the Ports Collection, including - Claws Mail, Evolution, and - Thunderbird. Some organizations provide a web mail program - which can be accessed through a web browser. More information - about installing and using a MUA on &os; can be - found in . - - + application which is used to compose, send, and receive + emails. This application can be a command line program, + such as the built-in mail utility or a + third-party application from the Ports Collection, such as + mutt, + alpine, or + elm. Dozens of graphical + programs are also available in the Ports Collection, + including Claws Mail, + Evolution, and + Thunderbird. Some + organizations provide a web mail program which can be + accessed through a web browser. More information about + installing and using a MUA on &os; can + be found in . + + - + Mail Transfer Agent (MTA) - The Mail Transfer Agent (MTA) is - responsible for receiving incoming mail and delivering - outgoing mail. &os; ships with Sendmail as the - default MTA, but it also supports numerous - other mail server daemons, including Exim, - Postfix, and - qmail. - Sendmail configuration is described - in . If another - MTA is installed using the Ports - Collection, refer to its post-installation message for - &os;-specific configuration details and the application's - website for more general configuration instructions. - - + The Mail Transfer Agent (MTA) is + responsible for receiving incoming mail and delivering + outgoing mail. &os; ships with + Sendmail as the default + MTA, but it also supports numerous + other mail server daemons, including + Exim, + Postfix, and + qmail. + Sendmail configuration is + described in . If another + MTA is installed using the Ports + Collection, refer to its post-installation message for + &os;-specific configuration details and the application's + website for more general configuration + instructions. + + - + Mail Host and Mailboxes - The mail host is a server that is responsible for - delivering and receiving mail for a host or a network. The - mail host collects all mail sent to the domain and stores it - either in the default mbox or the - alternative Maildir format, depending on the configuration. - Once mail has been stored, it may either be read locally using - a MUA or remotely accessed and collected - using protocols such as POP or - IMAP. If mail is read locally, - a POP or IMAP server - does not need to be installed. - - To access mailboxes remotely, a - POP or IMAP server is - required as these protocols allow users to connect to their - mailboxes from remote locations. IMAP offers - several advantages over POP. These - include the ability to store a copy of messages on a - remote server after they are downloaded and concurrent - updates. IMAP can be useful over - low-speed links as it allows users to fetch the - structure of messages without downloading them. It can - also perform tasks such as searching on the server in - order to minimize data transfer between clients and - servers. - - Several POP and - IMAP servers are available in the Ports - Collection. These include mail/qpopper, - mail/imap-uw, - mail/courier-imap, and - mail/dovecot2. - - - It should be noted that both POP - and IMAP transmit information, - including username and password credentials, in - clear-text. To secure the transmission of information - across these protocols, consider tunneling sessions over - &man.ssh.1; () or - using SSL (). - - - + The mail host is a server that is responsible for + delivering and receiving mail for a host or a network. + The mail host collects all mail sent to the domain and + stores it either in the default mbox + or the alternative Maildir format, depending on the + configuration. Once mail has been stored, it may either + be read locally using a MUA or remotely + accessed and collected using protocols such as + POP or IMAP. If + mail is read locally, a POP or + IMAP server does not need to be + installed. + + To access mailboxes remotely, a POP + or IMAP server is required as these + protocols allow users to connect to their mailboxes from + remote locations. IMAP offers several + advantages over POP. These include the + ability to store a copy of messages on a remote server + after they are downloaded and concurrent updates. + IMAP can be useful over low-speed links + as it allows users to fetch the structure of messages + without downloading them. It can also perform tasks such + as searching on the server in order to minimize data + transfer between clients and servers. + + Several POP and + IMAP servers are available in the Ports + Collection. These include + mail/qpopper, + mail/imap-uw, + mail/courier-imap, and + mail/dovecot2. + + + It should be noted that both POP + and IMAP transmit information, + including username and password credentials, in + clear-text. To secure the transmission of information + across these protocols, consider tunneling sessions over + &man.ssh.1; () + or using SSL (). + + + - + Domain Name System (DNS) - The Domain Name System (DNS) and its - daemon named play a large role in the - delivery of email. In order to deliver mail from one site to - another, the MTA will look up the remote - site in DNS to determine which host will - receive mail for the destination. This process also occurs - when mail is sent from a remote host to the - MTA. - - In addition to mapping hostnames to IP - addresses, DNS is responsible for storing information - specific to mail delivery, known as Mail eXchanger - MX records. The MX - record specifies which hosts will receive mail for a - particular domain. - - To view the MX records for a domain, - specify the type of record. Refer to &man.host.1;, for more - details about this command: + The Domain Name System (DNS) and + its daemon named play a large role in + the delivery of email. In order to deliver mail from one + site to another, the MTA will look up + the remote site in DNS to determine + which host will receive mail for the destination. This + process also occurs when mail is sent from a remote host + to the MTA. + + In addition to mapping hostnames to + IP addresses, DNS is + responsible for storing information specific to mail + delivery, known as Mail eXchanger + MX records. The MX + record specifies which hosts will receive mail for a + particular domain. + + To view the MX records for a + domain, specify the type of record. Refer to + &man.host.1;, for more details about this command: - &prompt.user; host -t mx FreeBSD.org + &prompt.user; host -t mx FreeBSD.org FreeBSD.org mail is handled by 10 mx1.FreeBSD.org - Refer to for more - information about DNS and its - configuration. - - - + Refer to for more + information about DNS and its + configuration. + + + - <application>Sendmail</application> Configuration + + <application>Sendmail</application> Configuration + - ChristopherShumwayContributed by + ChristopherShumwayContributed + by - Sendmail @@ -408,17 +420,19 @@ okay.cyberspammer.com OK routine. The message is sent to the remote host when a mail matches the left side of the table. The third entry rejects mail from a specific host on the Internet, - another.source.of.spam. The fourth entry - accepts mail connections from okay.cyberspammer.com, which is - more specific than the cyberspammer.com line above. - More specific matches override less exact matches. The last - entry allows relaying of email from hosts with an IP address - that begins with 128.32. These hosts can - send mail through this mail server that is destined for other - mail servers. + another.source.of.spam. The fourth + entry accepts mail connections from okay.cyberspammer.com, + which is more specific than the cyberspammer.com line + above. More specific matches override less exact matches. + The last entry allows relaying of email from hosts with an IP + address that begins with 128.32. + These hosts can send mail through this mail server that is + destined for other mail servers. - Whenever this file is updated, run - make in /etc/mail/ to update the + Whenever this file is updated, run make + in /etc/mail/ to update the database. @@ -441,24 +455,27 @@ procmail: "|/usr/local/bin/procmail"The mailbox name on the left side of the colon is expanded to the target(s) on the right. The first entry expands the - mailbox root to the mailbox - localuser, which is then looked up again - in the aliases database. If no match is - found, the message is delivered to - localuser. The second entry shows a - mail list. Mail to the mailbox ftp-bugs - is expanded to the three local mailboxes - joe, eric, and - paul. A remote mailbox could be - specified as user@example.com. The third + mailbox root to the + mailbox localuser, + which is then looked up again in the + aliases database. If no match is found, + the message is delivered to localuser. The second entry + shows a mail list. Mail to the mailbox ftp-bugs is expanded to the + three local mailboxes joe, eric, and paul. A remote mailbox could + be specified as user@example.com. The third entry shows how to write mail to a file, in this case /dev/null. The last entry demonstrates how to send mail to a program, /usr/local/bin/procmail, through a &unix; pipe. - Whenever this file is updated, run - make in /etc/mail/ to update the + Whenever this file is updated, run make + in /etc/mail/ to update the database. @@ -466,11 +483,13 @@ procmail: "|/usr/local/bin/procmail"This is a list of hostnames &man.sendmail.8; is to accept as the local host name. Place any domains or hosts that - Sendmail will receive mail - for. For example, to configure a mail server to accept mail - for the domain example.com - and the host mail.example.com, - add these entries to + Sendmail will receive mail for. + For example, to configure a mail server to accept mail for the + domain example.com and the host + mail.example.com, add + these entries to local-host-names: example.com @@ -478,7 +497,6 @@ mail.example.com Whenever this file is updated, &man.sendmail.8; needs to be restarted so that it will read the changes. - @@ -521,32 +539,38 @@ postmaster@example.com postmast The above example contains a mapping for the domain - example.com. This file - is processed in a first match order. The first item maps - root@example.com to the local mailbox - root. The second entry maps - postmaster@example.com to the mailbox - postmaster on the host noc.example.net. Finally, if - nothing from example.com - has matched so far, it will match the last mapping, which - matches every other mail message addressed to someone at - example.com to the local + example.com. + This file is processed in a first match order. The first item + maps root@example.com to the local mailbox + root. The second + entry maps postmaster@example.com to the + mailbox postmaster + on the host noc.example.net. Finally, + if nothing from example.com has matched so + far, it will match the last mapping, which matches every other + mail message addressed to someone at example.com to the local mailbox joe. - Changing the Mail Transfer Agent + + Changing the Mail Transfer Agent + - AndrewBoothmanWritten by + AndrewBoothmanWritten + by - GregoryNeil ShapiroInformation taken from emails written - by + GregoryNeil + ShapiroInformation taken + from emails written by - email @@ -568,7 +592,8 @@ postmaster@example.com postmast Install a New <acronym>MTA</acronym> A wide choice of MTAs is available - from the mail category of the &os; Ports Collection. + from the mail category of the &os; Ports Collection. Once a new MTA is installed, configure the new software and decide if it really fulfills your needs @@ -681,7 +706,6 @@ mailq /usr/local/supermailer/bin/mailq- newaliases /usr/local/supermailer/bin/newaliases-compat hoststat /usr/local/supermailer/bin/hoststat-compat purgestat /usr/local/supermailer/bin/purgestat-compat - @@ -693,7 +717,6 @@ purgestat /usr/local/supermailer/bin/pur reboot. Rebooting provides the opportunity to ensure that the system is correctly configured to start the new MTA automatically on boot. - @@ -714,10 +737,15 @@ purgestat /usr/local/supermailer/bin/pur The host may actually be in a different domain. - For example, in order for a host in foo.bar.edu to reach a host - called mumble in the bar.edu domain, refer to - it by the Fully-Qualified Domain Name - FQDN, mumble.bar.edu, instead of just + For example, in order for a host in foo.bar.edu to + reach a host called mumble in + the bar.edu domain, + refer to it by the Fully-Qualified Domain Name + FQDN, mumble.bar.edu, + instead of just mumble. This is because the version of @@ -726,14 +754,17 @@ purgestat /usr/local/supermailer/bin/pur &os; no longer provides default abbreviations for non-FQDNs other than the local domain. An unqualified host such as - mumble must either be found as - mumble.foo.bar.edu, + mumble must either be found + as mumble.foo.bar.edu, or it will be searched for in the root domain. In older versions of - BIND, - the search continued across mumble.bar.edu, and - mumble.edu. RFC + BIND, the search continued + across mumble.bar.edu, + and mumble.edu. RFC 1535 details why this is considered bad practice or even a security hole. @@ -759,7 +790,8 @@ purgestat /usr/local/supermailer/bin/pur - This is answered in the Sendmail + This is answered in the Sendmail FAQ as follows. This FAQ is recommended reading when tweaking the mail setup. @@ -794,8 +826,10 @@ to /etc/mail/sendmail.cf.One way to do this is to get a full-time Internet server to provide secondary MX MX record services for the - domain. In this example, the domain is example.com and the ISP has - configured example.net to provide + domain. In this example, the domain is example.com and the ISP + has configured example.net to provide secondary MX services to the domain: @@ -805,21 +839,23 @@ to /etc/mail/sendmail.cf.Only one host should be specified as the final recipient. For Sendmail, add Cw example.com in - /etc/mail/sendmail.cf on - example.com. + /etc/mail/sendmail.cf on example.com. When the sending MTA attempts to deliver mail, it will try to connect to the system, - example.com, over the PPP - link. This will time out if the destination is offline. - The MTA will automatically deliver it to - the secondary MX site at the Internet - Service Provider (ISP), example.net. The secondary - MX site will periodically try to connect - to the primary MX host, example.com. + example.com, + over the PPP link. This will time out if the destination is + offline. The MTA will automatically + deliver it to the secondary MX site at + the Internet Service Provider (ISP), + example.net. + The secondary MX site will periodically + try to connect to the primary MX host, + example.com. - Use something like this as a login - script: + Use something like this as a login script: #!/bin/sh # Put me in /usr/local/bin/pppmyisp @@ -828,8 +864,9 @@ to /etc/mail/sendmail.cf.When creating a separate login script for users, instead use sendmail -qRexample.com in the script - above. This will force all mail in the queue for example.com to be processed - immediately. + above. This will force all mail in the queue for + example.com to + be processed immediately. A further refinement of the situation can be seen from this example from the &a.isp;: @@ -956,7 +993,8 @@ www.example.org Make sure that the lowest-numbered - MXMX record record in + MXMX + record record in DNS points to the host's static IP address. @@ -977,10 +1015,12 @@ example.FreeBSD.org &prompt.root; host example.FreeBSD.org example.FreeBSD.org has address 204.216.27.XX - In this example, mail sent directly to yourlogin@example.FreeBSD.org - should work without problems, assuming + In this example, mail sent directly to yourlogin@example.FreeBSD.org should + work without problems, assuming Sendmail is running correctly on - example.FreeBSD.org. + example.FreeBSD.org. For this example: @@ -988,9 +1028,10 @@ example.FreeBSD.org has address 204.216. example.FreeBSD.org has address 204.216.27.XX example.FreeBSD.org mail is handled (pri=10) by hub.FreeBSD.org - All mail sent to example.FreeBSD.org will be - collected on hub under the same username - instead of being sent directly to your host. + All mail sent to example.FreeBSD.org will + be collected on hub under the same + username instead of being sent directly to your host. The above information is handled by the DNS server. The DNS @@ -999,20 +1040,22 @@ example.FreeBSD.org mail is handled (pri record exists, mail will be delivered directly to the host by way of its IP address. - The MX entry for freefall.FreeBSD.org at one time looked - like this: + The MX entry for freefall.FreeBSD.org at + one time looked like this: freefall MX 30 mail.crl.net freefall MX 40 agora.rdrop.com freefall MX 10 freefall.FreeBSD.org freefall MX 20 who.cdrom.com - freefall 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 next lower-numbered host will - accept messages temporarily, and pass it along when a - lower-numbered host becomes available. + freefall 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 next lower-numbered host will accept messages + temporarily, and pass it along when a lower-numbered host + becomes available. Alternate MX sites should have separate Internet connections in order to be most useful. Your @@ -1053,18 +1096,24 @@ freefall MX 20 who.cdrom.com The following is an example of virtual email hosting. - Consider a customer with the domain customer1.org, where all the mail - for customer1.org should be - sent to mail.myhost.com. The + Consider a customer with the domain customer1.org, where all + the mail for customer1.org should be + sent to mail.myhost.com. The DNS entry should look like this: customer1.org MX 10 mail.myhost.com An A> record is - not needed for customer1.org in order to only - handle email for that domain. However, running - ping against customer1.org will not work - unless an A record exists for it. + not needed for customer1.org in order to + only handle email for that domain. However, running + ping against customer1.org will not + work unless an A record exists for + it. Tell the MTA which domains and/or hostnames it should accept mail for. Either of the following @@ -1074,10 +1123,10 @@ freefall MX 20 who.cdrom.com Add the hosts to /etc/mail/local-host-names when - using the FEATURE(use_cw_file). - For versions of - Sendmail earlier than 8.10, - edit /etc/sendmail.cw instead. + using the FEATURE(use_cw_file). For + versions of Sendmail earlier + than 8.10, edit /etc/sendmail.cw + instead. @@ -1092,14 +1141,15 @@ freefall MX 20 who.cdrom.com - Setting Up to Send Only + + Setting Up to Send Only + - BillMoranContributed by + BillMoranContributed + by - - There are many instances where one may only want to send mail through a relay. Some examples are: @@ -1133,7 +1183,8 @@ freefall MX 20 who.cdrom.com&prompt.root; cd /usr/ports/mail/ssmtp &prompt.root; make install replace clean - Once installed, mail/ssmtp can be configured with + Once installed, mail/ssmtp can be + configured with /usr/local/etc/ssmtp/ssmtp.conf: root=yourrealemail@example.com @@ -1141,19 +1192,19 @@ mailhub=mail.example.com rewriteDomain=example.com hostname=_HOSTNAME_ - Use the real email address for root. - Enter the ISP's outgoing mail relay in place - of mail.example.com. Some - ISPs call this the outgoing mail + Use the real email address for root. Enter the + ISP's outgoing mail relay in place of + mail.example.com. + Some ISPs call this the outgoing mail server or SMTP server). - Make sure to disable - Sendmail, including the outgoing mail - service. See for - details. + Make sure to disable Sendmail, + including the outgoing mail service. See for details. - mail/ssmtp has some - other options available. Refer to the examples in + mail/ssmtp has some other options + available. Refer to the examples in /usr/local/etc/ssmtp or the manual page of ssmtp for more information. @@ -1175,14 +1226,18 @@ hostname=_HOSTNAME_ When using a dynamically assigned IP address and a dialup PPP connection to the Internet, one usually has a mailbox on the ISP's mail server. In this example, the - ISP's domain is example.net, the user name is - user, the hostname is bsd.home, and the ISP - has allowed relay.example.net as a mail relay. + ISP's domain is example.net, the user name + is user, the hostname + is bsd.home, and + the ISP has allowed relay.example.net as a mail + relay. In order to retrieve mail from the ISP's mailbox, install a retrieval agent from the Ports Collection. - mail/fetchmail is a good - choice as it supports many different protocols. Usually, the + mail/fetchmail is a good choice as it + supports many different protocols. Usually, the ISP will provide POP. When using user PPP, email can be automatically fetched when an Internet connection is established @@ -1202,23 +1257,26 @@ hostname=_HOSTNAME_ !bg su user -c "sendmail -q" In this example, there is an account for - user on bsd.home. In the home directory of - user on bsd.home, create a + user on bsd.home. In the home + directory of user on + bsd.home, create a .fetchmailrc which contains this line: poll example.net protocol pop3 fetchall pass MySecret This file should not be readable by anyone except - user as it contains the password - MySecret. + user as it contains + the password MySecret. In order to send mail with the correct from: header, configure Sendmail to use - user@example.net rather than user@bsd.home and to send all mail - via relay.example.net, allowing - quicker mail transmission. + user@example.net rather than user@bsd.home and to send all mail via + relay.example.net, + allowing quicker mail transmission. The following .mc file should suffice: @@ -1241,21 +1299,21 @@ define(`confDOMAIN_NAME',`bsd.home')dnl define(`confDELIVERY_MODE',`deferred')dnl Refer to the previous section for details of how to convert - this file into the - sendmail.cf format. Do not forget to - restart Sendmail after updating - sendmail.cf. + this file into the sendmail.cf format. Do + not forget to restart Sendmail after + updating sendmail.cf. - SMTP Authentication + + SMTP Authentication + - JamesGorhamWritten by + JamesGorhamWritten + by - - Configuring SMTP authentication on the MTA provides a number of benefits. SMTP authentication adds a layer @@ -1275,8 +1333,8 @@ define(`confDELIVERY_MODE',`deferred')dn - After installing security/cyrus-sasl2, - edit + After installing + security/cyrus-sasl2, edit /usr/local/lib/sasl2/Sendmail.conf, or create it if it does not exist, and add the following line: @@ -1285,9 +1343,10 @@ define(`confDELIVERY_MODE',`deferred')dn - Next, install security/cyrus-sasl2-saslauthd - and add the following line to - /etc/rc.conf: + Next, install + security/cyrus-sasl2-saslauthd and add + the following line to + /etc/rc.conf: saslauthd_enable="YES" @@ -1297,11 +1356,10 @@ define(`confDELIVERY_MODE',`deferred')dn This daemon serves as a broker for sendmail to authenticate against - the &os; &man.passwd.5; database. This - saves the trouble of creating a new set of usernames and - passwords for each user that needs to use - SMTP authentication, and keeps the login - and mail password the same. + the &os; &man.passwd.5; database. This saves the trouble of + creating a new set of usernames and passwords for each user + that needs to use SMTP authentication, + and keeps the login and mail password the same. @@ -1312,10 +1370,10 @@ define(`confDELIVERY_MODE',`deferred')dn SENDMAIL_LDFLAGS=-L/usr/local/lib SENDMAIL_LDADD=-lsasl2 - These lines provide - Sendmail the proper configuration - options for linking to cyrus-sasl2 at compile time. - Make sure that cyrus-sasl2 has been installed + These lines provide Sendmail + the proper configuration options for linking to + cyrus-sasl2 at compile time. Make sure + that cyrus-sasl2 has been installed before recompiling Sendmail. @@ -1332,9 +1390,8 @@ SENDMAIL_LDADD=-lsasl2 &prompt.root; make cleandir && make obj && make && make install This compile should not have any problems if - /usr/src has not - changed extensively and the shared libraries it needs are - available. + /usr/src has not changed extensively + and the shared libraries it needs are available. @@ -1358,8 +1415,9 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI - Finally, run &man.make.1; while in /etc/mail. That will run the - new .mc and create a + Finally, run &man.make.1; while in + /etc/mail. That will run the new + .mc and create a .cf named either freebsd.cf or the name used for the local .mc. Then, run make @@ -1377,17 +1435,20 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI to 13 and watch /var/log/maillog for any errors. - For more information, refer to + For more information, refer to SMTP authentication. - Mail User Agents + + Mail User Agents + - MarcSilverContributed by + MarcSilverContributed + by - Mail User Agents @@ -1427,9 +1488,10 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI &prompt.user; mail *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***