1. Update the example showing how to extract sendmail from the scontrib
tarball. PR: docs/15697 Submitted by: alex@frustum.clara.co.uk While I'm in here, fix up the rest of the markup for this question. Translation teams: There were some white space changes, but only in the <programlisting> or <screen> elements. You can safely cut and paste these sections in to your translations without needing to translate them. 2. Add a "Why is /bin/sh so minimal?" question, with an answer from Garrett Wollman. 3. Include a link to xfce in the "Where can I get CDE?" question, and mention that both KDE and xfce are in the ports tree. Submitted by: Jerason Banes <jbanes@accelgen.com> 4. Delete the word "open" from "The Problem Report database of all open user change requests..." as closed reports can be viewed as well.
This commit is contained in:
Nik Clayton
parent
811a3b7b1f
commit
464eeda1d4
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=6516
2 changed files with 182 additions and 136 deletions
|
|
@ -14,7 +14,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.34 2000/02/07 21:41:36 tom Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.35 2000/02/08 19:39:09 peter Exp $</pubdate>
|
||||
|
||||
<abstract><para> This is the FAQ for FreeBSD versions 2.X and 3.X. All entries are
|
||||
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
|
||||
|
|
@ -582,7 +582,7 @@ FreeBSD CDROM often has newer versions).</para>
|
|||
<qandaentry><question>
|
||||
<para>How do I access your Problem Report database?</para></question><answer>
|
||||
|
||||
<para>The Problem Report database of all open user change requests
|
||||
<para>The Problem Report database of all user change requests
|
||||
may be queried (or submitted to) by using our web-based PR
|
||||
<ulink URL="http://www.FreeBSD.org/send-pr.html">submission</ulink>
|
||||
and <ulink URL="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">query</ulink> interfaces. The <command>send-pr(1)</command> command
|
||||
|
|
@ -2852,7 +2852,11 @@ future this will change to a unified CD distribution like their CDE.</para>
|
|||
FreeBSD, but no longer do.</para>
|
||||
|
||||
<para><ulink URL="http://www.kde.org/">KDE</ulink> is an open source
|
||||
X11 desktop which is similar to CDE in many respects.</para>
|
||||
X11 desktop which is similar to CDE in many respects.
|
||||
You might also like the look and feel of <ulink
|
||||
url="http://www.xfce.org/">xfce</ulink>. KDE and xfce are both
|
||||
in the <ulink url="http://www.FreeBSD.org/ports/">ports
|
||||
system</ulink>.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
|
|
@ -3060,6 +3064,38 @@ at the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink> m
|
|||
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why is <command>/bin/sh</command> so minimal? Why doesn't
|
||||
FreeBSD use <command>bash</command> or another shell?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Because POSIX says that there shall be such a shell.</para>
|
||||
|
||||
<para>The more complicated answer: many people need to write shell
|
||||
scripts which will be portable across many systems. That's why
|
||||
POSIX specifies the shell and utility commands in great detail.
|
||||
Most scripts are written in Bourne shell, and because several
|
||||
important programming interfaces (&man.make.1;, &man.system.3;,
|
||||
&man.popen.3;, and analogues in higher-level scripting languages
|
||||
like Perl and Tcl) are specified to use the Bourne shell to
|
||||
interpret commands. Because the Bourne shell is so often and
|
||||
widely used, it is important for it to be quick to start, be
|
||||
deterministic in its behavior, and have a small memory
|
||||
footprint.</para>
|
||||
|
||||
<para>The existing implementation is our best effort at meeting as
|
||||
many of these requirements simultaneously as we can. In order to
|
||||
keep <command>/bin/sh</command> small, we have not provided many
|
||||
of the convenience features that other shells have. That's why the
|
||||
Ports Collection includes more featureful shells like bash, scsh,
|
||||
tcsh, and zsh. (You can compare for yourself the memory
|
||||
utilization of all these shells by looking at the
|
||||
<quote>VSZ</quote> and <quote>RSS</quote> columns in a <command>ps
|
||||
-u</command> listing.)</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry><question>
|
||||
<para>Where do I find libc.so.3.0?</para></question><answer>
|
||||
|
||||
|
|
@ -4071,29 +4107,24 @@ something for purists. Sendmail version 8 comes with a
|
|||
new approach of generating config files via some
|
||||
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?m4">m4</ulink> preprocessing, where the actual hand-crafted configuration
|
||||
is on a higher abstraction level. You should use the
|
||||
configuration files under</para>
|
||||
configuration files under
|
||||
|
||||
<para>
|
||||
<literallayout> /usr/src/usr.sbin/sendmail/cf
|
||||
</literallayout>
|
||||
<filename>/usr/src/usr.sbin/sendmail/cf</filename>
|
||||
</para>
|
||||
|
||||
<para>If you didn't install your system with full sources, the sendmail
|
||||
config stuff has been broken out into a separate source distribution
|
||||
tarball just for you. Assuming you've got your CD-ROM mounted, do:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> cd /usr/src
|
||||
tar -xvzf /cdrom/dists/src/ssmailcf.aa
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /cdrom/src</userinput>
|
||||
&prompt.root; <userinput>cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail</userinput></screen>
|
||||
|
||||
<para>Don't panic, this is only a few hundred kilobytes in size.
|
||||
The file <acronym>README</acronym> in the <emphasis remap=tt>cf</emphasis> directory can
|
||||
The file <filename>README</filename> in the <filename>cf</filename> directory can
|
||||
serve as a basic introduction to m4 configuration.</para>
|
||||
|
||||
<para>For UUCP delivery, you are best advised to use the
|
||||
<emphasis>mailertable</emphasis> feature. This constitutes a database
|
||||
<literal>mailertable</literal> feature. This constitutes a database
|
||||
that sendmail can use to base its routing decision upon.</para>
|
||||
|
||||
<para>First, you have to create your <filename>.mc</filename> file. The
|
||||
|
|
@ -4103,37 +4134,34 @@ examples. Assuming you have named your file <filename>foo.mc</filename>,
|
|||
all you need to do in order to convert it into a valid
|
||||
<filename>sendmail.cf</filename> is:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> cd /usr/src/usr.sbin/sendmail/cf/cf
|
||||
make foo.cf
|
||||
cp foo.cf /etc/sendmail.cf
|
||||
</literallayout>
|
||||
</para>
|
||||
<screen>
|
||||
&prompt.root; <userinput>cd /usr/src/usr.sbin/sendmail/cf/cf</userinput>
|
||||
&prompt.root; <userinput>make foo.cf</userinput>
|
||||
&prompt.root; <userinput>cp foo.cf /etc/sendmail.cf</userinput>
|
||||
</screen>
|
||||
|
||||
<para>A typical <filename>.mc</filename> file might look like:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> include(`../m4/cf.m4')
|
||||
VERSIONID(`Your version number')
|
||||
OSTYPE(bsd4.4)
|
||||
|
||||
FEATURE(nodns)
|
||||
FEATURE(nocanonify)
|
||||
FEATURE(mailertable)
|
||||
<programlisting>include(`../m4/cf.m4')
|
||||
VERSIONID(`<replaceable>Your version number</replaceable>')
|
||||
OSTYPE(bsd4.4)
|
||||
|
||||
FEATURE(nodns)
|
||||
FEATURE(nocanonify)
|
||||
FEATURE(mailertable)
|
||||
|
||||
define(`UUCP_RELAY', your.uucp.relay)
|
||||
define(`UUCP_MAX_SIZE', 200000)
|
||||
define(`UUCP_RELAY', <replaceable>your.uucp.relay</replaceable>)
|
||||
define(`UUCP_MAX_SIZE', 200000)
|
||||
|
||||
MAILER(local)
|
||||
MAILER(smtp)
|
||||
MAILER(uucp)
|
||||
MAILER(local)
|
||||
MAILER(smtp)
|
||||
MAILER(uucp)
|
||||
|
||||
Cw your.alias.host.name
|
||||
Cw youruucpnodename.UUCP
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>The <emphasis>nodns</emphasis> and <emphasis>nocanonify</emphasis> features will
|
||||
Cw <replaceable>your.alias.host.name</replaceable>
|
||||
Cw <replaceable>youruucpnodename.UUCP</replaceable></programlisting>
|
||||
|
||||
<para>The <literal>nodns</literal> and <literal>nocanonify</literal> features will
|
||||
prevent any usage of the DNS during mail delivery. The
|
||||
<symbol>UUCP_RELAY</symbol> clause is needed for bizarre reasons,
|
||||
don't ask. Simply put an Internet hostname there that
|
||||
|
|
@ -4144,19 +4172,17 @@ you will enter the mail relay of your ISP there.</para>
|
|||
<filename>/etc/mailertable</filename>. A typical example of this
|
||||
gender again:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> #
|
||||
# makemap hash /etc/mailertable.db < /etc/mailertable
|
||||
#
|
||||
horus.interface-business.de uucp-dom:horus
|
||||
.interface-business.de uucp-dom:if-bus
|
||||
interface-business.de uucp-dom:if-bus
|
||||
.heep.sax.de smtp8:%1
|
||||
horus.UUCP uucp-dom:horus
|
||||
if-bus.UUCP uucp-dom:if-bus
|
||||
. uucp-dom:sax
|
||||
</literallayout>
|
||||
</para>
|
||||
<programlisting>#
|
||||
# makemap hash /etc/mailertable.db < /etc/mailertable
|
||||
#
|
||||
horus.interface-business.de uucp-dom:horus
|
||||
.interface-business.de uucp-dom:if-bus
|
||||
interface-business.de uucp-dom:if-bus
|
||||
.heep.sax.de smtp8:%1
|
||||
horus.UUCP uucp-dom:horus
|
||||
if-bus.UUCP uucp-dom:if-bus
|
||||
. uucp-dom:</programlisting>
|
||||
|
||||
|
||||
<para>As you can see, this is part of a real-life file. The first
|
||||
three lines handle special cases where domain-addressed mail
|
||||
|
|
@ -4169,9 +4195,9 @@ to allow for a ``uucp-neighbor!recipient'' 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 world. All of
|
||||
the node names behind the <emphasis remap=tt>uucp-dom:</emphasis> keyword must
|
||||
the node names behind the <literal>uucp-dom:</literal> keyword must
|
||||
be valid UUCP neighbors, as you can verify using the
|
||||
command <emphasis remap=tt>uuname</emphasis>.</para>
|
||||
command <literal>uuname</literal>.</para>
|
||||
|
||||
<para>As a reminder that this file needs to be converted into a
|
||||
DBM database file before being usable, the command line to
|
||||
|
|
@ -4188,19 +4214,16 @@ internal mail agent, the destination host this agent will be
|
|||
called with, and the (possibly translated) address. Leave
|
||||
this mode by typing Control-D.</para>
|
||||
|
||||
<para>
|
||||
<literallayout> j@uriah 191% sendmail -bt
|
||||
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
|
||||
Enter <ruleset> <address>
|
||||
> 0 foo@interface-business.de
|
||||
rewrite: ruleset 0 input: foo @ interface-business . de
|
||||
...
|
||||
rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
|
||||
< @ interface-business . de >
|
||||
> ^D
|
||||
j@uriah 192%
|
||||
</literallayout>
|
||||
</para>
|
||||
<screen>&prompt.user; <userinput>sendmail -bt</userinput>
|
||||
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
|
||||
Enter <ruleset> <address>
|
||||
<prompt>></prompt> <userinput>0 foo@interface-business.de</userinput>
|
||||
rewrite: ruleset 0 input: foo @ interface-business . de
|
||||
...
|
||||
rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
|
||||
< @ interface-business . de >
|
||||
<prompt>></prompt> <userinput>^D</userinput></screen>
|
||||
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.34 2000/02/07 21:41:36 tom Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.35 2000/02/08 19:39:09 peter Exp $</pubdate>
|
||||
|
||||
<abstract><para> This is the FAQ for FreeBSD versions 2.X and 3.X. All entries are
|
||||
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
|
||||
|
|
@ -582,7 +582,7 @@ FreeBSD CDROM often has newer versions).</para>
|
|||
<qandaentry><question>
|
||||
<para>How do I access your Problem Report database?</para></question><answer>
|
||||
|
||||
<para>The Problem Report database of all open user change requests
|
||||
<para>The Problem Report database of all user change requests
|
||||
may be queried (or submitted to) by using our web-based PR
|
||||
<ulink URL="http://www.FreeBSD.org/send-pr.html">submission</ulink>
|
||||
and <ulink URL="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">query</ulink> interfaces. The <command>send-pr(1)</command> command
|
||||
|
|
@ -2852,7 +2852,11 @@ future this will change to a unified CD distribution like their CDE.</para>
|
|||
FreeBSD, but no longer do.</para>
|
||||
|
||||
<para><ulink URL="http://www.kde.org/">KDE</ulink> is an open source
|
||||
X11 desktop which is similar to CDE in many respects.</para>
|
||||
X11 desktop which is similar to CDE in many respects.
|
||||
You might also like the look and feel of <ulink
|
||||
url="http://www.xfce.org/">xfce</ulink>. KDE and xfce are both
|
||||
in the <ulink url="http://www.FreeBSD.org/ports/">ports
|
||||
system</ulink>.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
|
|
@ -3060,6 +3064,38 @@ at the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink> m
|
|||
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why is <command>/bin/sh</command> so minimal? Why doesn't
|
||||
FreeBSD use <command>bash</command> or another shell?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Because POSIX says that there shall be such a shell.</para>
|
||||
|
||||
<para>The more complicated answer: many people need to write shell
|
||||
scripts which will be portable across many systems. That's why
|
||||
POSIX specifies the shell and utility commands in great detail.
|
||||
Most scripts are written in Bourne shell, and because several
|
||||
important programming interfaces (&man.make.1;, &man.system.3;,
|
||||
&man.popen.3;, and analogues in higher-level scripting languages
|
||||
like Perl and Tcl) are specified to use the Bourne shell to
|
||||
interpret commands. Because the Bourne shell is so often and
|
||||
widely used, it is important for it to be quick to start, be
|
||||
deterministic in its behavior, and have a small memory
|
||||
footprint.</para>
|
||||
|
||||
<para>The existing implementation is our best effort at meeting as
|
||||
many of these requirements simultaneously as we can. In order to
|
||||
keep <command>/bin/sh</command> small, we have not provided many
|
||||
of the convenience features that other shells have. That's why the
|
||||
Ports Collection includes more featureful shells like bash, scsh,
|
||||
tcsh, and zsh. (You can compare for yourself the memory
|
||||
utilization of all these shells by looking at the
|
||||
<quote>VSZ</quote> and <quote>RSS</quote> columns in a <command>ps
|
||||
-u</command> listing.)</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry><question>
|
||||
<para>Where do I find libc.so.3.0?</para></question><answer>
|
||||
|
||||
|
|
@ -4071,29 +4107,24 @@ something for purists. Sendmail version 8 comes with a
|
|||
new approach of generating config files via some
|
||||
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?m4">m4</ulink> preprocessing, where the actual hand-crafted configuration
|
||||
is on a higher abstraction level. You should use the
|
||||
configuration files under</para>
|
||||
configuration files under
|
||||
|
||||
<para>
|
||||
<literallayout> /usr/src/usr.sbin/sendmail/cf
|
||||
</literallayout>
|
||||
<filename>/usr/src/usr.sbin/sendmail/cf</filename>
|
||||
</para>
|
||||
|
||||
<para>If you didn't install your system with full sources, the sendmail
|
||||
config stuff has been broken out into a separate source distribution
|
||||
tarball just for you. Assuming you've got your CD-ROM mounted, do:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> cd /usr/src
|
||||
tar -xvzf /cdrom/dists/src/ssmailcf.aa
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /cdrom/src</userinput>
|
||||
&prompt.root; <userinput>cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail</userinput></screen>
|
||||
|
||||
<para>Don't panic, this is only a few hundred kilobytes in size.
|
||||
The file <acronym>README</acronym> in the <emphasis remap=tt>cf</emphasis> directory can
|
||||
The file <filename>README</filename> in the <filename>cf</filename> directory can
|
||||
serve as a basic introduction to m4 configuration.</para>
|
||||
|
||||
<para>For UUCP delivery, you are best advised to use the
|
||||
<emphasis>mailertable</emphasis> feature. This constitutes a database
|
||||
<literal>mailertable</literal> feature. This constitutes a database
|
||||
that sendmail can use to base its routing decision upon.</para>
|
||||
|
||||
<para>First, you have to create your <filename>.mc</filename> file. The
|
||||
|
|
@ -4103,37 +4134,34 @@ examples. Assuming you have named your file <filename>foo.mc</filename>,
|
|||
all you need to do in order to convert it into a valid
|
||||
<filename>sendmail.cf</filename> is:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> cd /usr/src/usr.sbin/sendmail/cf/cf
|
||||
make foo.cf
|
||||
cp foo.cf /etc/sendmail.cf
|
||||
</literallayout>
|
||||
</para>
|
||||
<screen>
|
||||
&prompt.root; <userinput>cd /usr/src/usr.sbin/sendmail/cf/cf</userinput>
|
||||
&prompt.root; <userinput>make foo.cf</userinput>
|
||||
&prompt.root; <userinput>cp foo.cf /etc/sendmail.cf</userinput>
|
||||
</screen>
|
||||
|
||||
<para>A typical <filename>.mc</filename> file might look like:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> include(`../m4/cf.m4')
|
||||
VERSIONID(`Your version number')
|
||||
OSTYPE(bsd4.4)
|
||||
|
||||
FEATURE(nodns)
|
||||
FEATURE(nocanonify)
|
||||
FEATURE(mailertable)
|
||||
<programlisting>include(`../m4/cf.m4')
|
||||
VERSIONID(`<replaceable>Your version number</replaceable>')
|
||||
OSTYPE(bsd4.4)
|
||||
|
||||
FEATURE(nodns)
|
||||
FEATURE(nocanonify)
|
||||
FEATURE(mailertable)
|
||||
|
||||
define(`UUCP_RELAY', your.uucp.relay)
|
||||
define(`UUCP_MAX_SIZE', 200000)
|
||||
define(`UUCP_RELAY', <replaceable>your.uucp.relay</replaceable>)
|
||||
define(`UUCP_MAX_SIZE', 200000)
|
||||
|
||||
MAILER(local)
|
||||
MAILER(smtp)
|
||||
MAILER(uucp)
|
||||
MAILER(local)
|
||||
MAILER(smtp)
|
||||
MAILER(uucp)
|
||||
|
||||
Cw your.alias.host.name
|
||||
Cw youruucpnodename.UUCP
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>The <emphasis>nodns</emphasis> and <emphasis>nocanonify</emphasis> features will
|
||||
Cw <replaceable>your.alias.host.name</replaceable>
|
||||
Cw <replaceable>youruucpnodename.UUCP</replaceable></programlisting>
|
||||
|
||||
<para>The <literal>nodns</literal> and <literal>nocanonify</literal> features will
|
||||
prevent any usage of the DNS during mail delivery. The
|
||||
<symbol>UUCP_RELAY</symbol> clause is needed for bizarre reasons,
|
||||
don't ask. Simply put an Internet hostname there that
|
||||
|
|
@ -4144,19 +4172,17 @@ you will enter the mail relay of your ISP there.</para>
|
|||
<filename>/etc/mailertable</filename>. A typical example of this
|
||||
gender again:</para>
|
||||
|
||||
<para>
|
||||
<literallayout> #
|
||||
# makemap hash /etc/mailertable.db < /etc/mailertable
|
||||
#
|
||||
horus.interface-business.de uucp-dom:horus
|
||||
.interface-business.de uucp-dom:if-bus
|
||||
interface-business.de uucp-dom:if-bus
|
||||
.heep.sax.de smtp8:%1
|
||||
horus.UUCP uucp-dom:horus
|
||||
if-bus.UUCP uucp-dom:if-bus
|
||||
. uucp-dom:sax
|
||||
</literallayout>
|
||||
</para>
|
||||
<programlisting>#
|
||||
# makemap hash /etc/mailertable.db < /etc/mailertable
|
||||
#
|
||||
horus.interface-business.de uucp-dom:horus
|
||||
.interface-business.de uucp-dom:if-bus
|
||||
interface-business.de uucp-dom:if-bus
|
||||
.heep.sax.de smtp8:%1
|
||||
horus.UUCP uucp-dom:horus
|
||||
if-bus.UUCP uucp-dom:if-bus
|
||||
. uucp-dom:</programlisting>
|
||||
|
||||
|
||||
<para>As you can see, this is part of a real-life file. The first
|
||||
three lines handle special cases where domain-addressed mail
|
||||
|
|
@ -4169,9 +4195,9 @@ to allow for a ``uucp-neighbor!recipient'' 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 world. All of
|
||||
the node names behind the <emphasis remap=tt>uucp-dom:</emphasis> keyword must
|
||||
the node names behind the <literal>uucp-dom:</literal> keyword must
|
||||
be valid UUCP neighbors, as you can verify using the
|
||||
command <emphasis remap=tt>uuname</emphasis>.</para>
|
||||
command <literal>uuname</literal>.</para>
|
||||
|
||||
<para>As a reminder that this file needs to be converted into a
|
||||
DBM database file before being usable, the command line to
|
||||
|
|
@ -4188,19 +4214,16 @@ internal mail agent, the destination host this agent will be
|
|||
called with, and the (possibly translated) address. Leave
|
||||
this mode by typing Control-D.</para>
|
||||
|
||||
<para>
|
||||
<literallayout> j@uriah 191% sendmail -bt
|
||||
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
|
||||
Enter <ruleset> <address>
|
||||
> 0 foo@interface-business.de
|
||||
rewrite: ruleset 0 input: foo @ interface-business . de
|
||||
...
|
||||
rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
|
||||
< @ interface-business . de >
|
||||
> ^D
|
||||
j@uriah 192%
|
||||
</literallayout>
|
||||
</para>
|
||||
<screen>&prompt.user; <userinput>sendmail -bt</userinput>
|
||||
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
|
||||
Enter <ruleset> <address>
|
||||
<prompt>></prompt> <userinput>0 foo@interface-business.de</userinput>
|
||||
rewrite: ruleset 0 input: foo @ interface-business . de
|
||||
...
|
||||
rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
|
||||
< @ interface-business . de >
|
||||
<prompt>></prompt> <userinput>^D</userinput></screen>
|
||||
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue