|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: man2html and postlink
Subject: Re: man2html and postlink
From: Matthias Andree (ma
dt.e-technik.uni-dortmund.de)
Date: Mon Jan 03 2000 - 01:25:11 CST
- Next message: cyberms10.hinet.net: "how to config postfix as an smtp gateway?"
- Previous message: Matthias Andree: "Re: man2html and postlink"
- Next in thread: Matthias Andree: "Re: man2html and postlink"
- Maybe reply: Matthias Andree: "Re: man2html and postlink"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
wietseporcupine.org (Wietse Venema) writes:
> What is there to fix? weblint is way too pedantic to my taste.
Depends on its setting. My helper Perl script was also buggy. Still,
<blink> is not visible in MSIE, according to SelfHTML.
Major issues:
1. <a ...><h3> while <h3><a ...> is correct
2. missing closing tags for <a name=...>
3. spurious whitespace within <a> or <li> elements
Minor issues:
1. missing SGML doctype
2. <blink> is Netscape special. Was replaced by <B>
3. in section about fax support, there are unescaped < and > characters.
4. <dl> section conformized, see below
5. img link had not alt tag (for text-based browsers)
Unfixed issues:
1. excess line spacing (visible in amaya), perhaps excess <p> tags?
2. the <dl>... section is inconsistent - with respect to formatting -
with the rest of the document which uses <pre> sort of things
3. the entire thing should be texinfo or SGML or something more decent =:->
> > BTW: I fixed faq.html, diff is below.
>
> Do me a favor, and send only relevant stuff. weblint is too pedantic.
There we go, hope that fits.
NOTA BENE: this is against 19991231-pl01.
context diff below. generator: diff - GNU diffutils version 2.7
*** faq.html.orig Mon Jan 3 06:33:56 2000
--- faq.html Mon Jan 3 08:12:05 2000
***************
*** 1,3 ****
--- 1,4 ----
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<!--Warning, preformatted content! -->
***************
*** 10,16 ****
<body>
! <h1><a href="big-picture.html"><img src="small-picture.gif" width="115" height="45"></a> Postfix Frequently Asked Questions</h1>
<hr>
--- 11,19 ----
<body>
! <h1><a href="big-picture.html"><img src="small-picture.gif" alt="The
! Big Picture" width="115" height="45"></a> Postfix Frequently Asked
! Questions</h1>
<hr>
***************
*** 48,54 ****
<p>
! <a name="example_config"><h3>Example configurations</h3>
<ul>
--- 51,57 ----
<p>
! <h3><a name="example_config">Example configurations</a></h3>
<ul>
***************
*** 66,72 ****
</ul>
! <a name="sendmail_incompatibility"><h3>Sendmail incompatibility</h3>
<ul>
--- 69,75 ----
</ul>
! <h3><a name="sendmail_incompatibility">Sendmail incompatibility</a></h3>
<ul>
***************
*** 89,95 ****
</ul>
! <a name="relaying"><h3>Mail relaying</h3>
<ul>
--- 92,98 ----
</ul>
! <h3><a name="relaying">Mail relaying</a></h3>
<ul>
***************
*** 104,110 ****
</ul>
! <a name="remote_delivery"><h3>Delivery to remote systems</h3>
<ul>
--- 107,113 ----
</ul>
! <h3><a name="remote_delivery">Delivery to remote systems</a></h3>
<ul>
***************
*** 112,118 ****
</ul>
! <a name="local_delivery"><h3>Delivery to local (non-virtual) addresses</h3>
<ul>
--- 115,121 ----
</ul>
! <h3><a name="local_delivery">Delivery to local (non-virtual) addresses</a></h3>
<ul>
***************
*** 136,142 ****
</ul>
! <a name="mailing_lists"><h3>Mailing lists</h3>
<ul>
--- 139,145 ----
</ul>
! <h3><a name="mailing_lists">Mailing lists</a></h3>
<ul>
***************
*** 151,157 ****
</ul>
! <a name="virtual_domains"><h3>Virtual domains</h3>
<ul>
--- 154,160 ----
</ul>
! <h3><a name="virtual_domains">Virtual domains</a></h3>
<ul>
***************
*** 176,182 ****
</ul>
! <a name="address_rewriting"><h3>Address rewriting</h3>
<ul>
--- 179,185 ----
</ul>
! <h3><a name="address_rewriting">Address rewriting</a></h3>
<ul>
***************
*** 184,190 ****
</ul>
! <a name="content_filtering"><h3>Content filtering</h3>
<ul>
--- 187,193 ----
</ul>
! <h3><a name="content_filtering">Content filtering</a></h3>
<ul>
***************
*** 192,198 ****
</ul>
! <a name="other_transports"><h3>Other transports: UUCP, FAX, etc.</h3>
<ul>
--- 195,201 ----
</ul>
! <h3><a name="other_transports">Other transports: UUCP, FAX, etc.</a></h3>
<ul>
***************
*** 204,210 ****
</ul>
! <a name="compiling_installing"><h3>Compiling and installing Postfix</h3>
<ul>
--- 207,213 ----
</ul>
! <h3><a name="compiling_installing">Compiling and installing Postfix</a></h3>
<ul>
***************
*** 218,224 ****
<hr>
! <a name="stand_alone"><h3>Stand-alone machine</h3>
Out of the box, Postfix should work without change on a stand-alone
machine that is has direct Internet access. At least, that is how
--- 221,227 ----
<hr>
! <h3><a name="stand_alone">Stand-alone machine</a></h3>
Out of the box, Postfix should work without change on a stand-alone
machine that is has direct Internet access. At least, that is how
***************
*** 228,234 ****
<hr>
! <a name="workstation_server"><h3>Workstations and servers</h3>
This section describes a workstation-server environment. All systems
send mail as userdomain. All systems receive mail for userhostname.
--- 231,237 ----
<hr>
! <h3><a name="workstation_server">Workstations and servers</a></h3>
This section describes a workstation-server environment. All systems
send mail as userdomain. All systems receive mail for userhostname.
***************
*** 284,290 ****
<hr>
! <a name="null_client"><h3>Null clients</h3>
A null client is a machine that can only send mail. It receives no
mail from the network, and it does not deliver any mail locally. A
--- 287,293 ----
<hr>
! <h3><a name="null_client">Null clients</a></h3>
A null client is a machine that can only send mail. It receives no
mail from the network, and it does not deliver any mail locally. A
***************
*** 316,322 ****
<hr>
! <a name="intranet"> <h3>Running Postfix inside an intranet</h3> </a>
The simplest way to set up Postfix on a host inside a firewalled
network is to send all your mail to an intranet mail gateway, and
--- 319,325 ----
<hr>
! <h3><a name="intranet">Running Postfix inside an intranet</a></h3>
The simplest way to set up Postfix on a host inside a firewalled
network is to send all your mail to an intranet mail gateway, and
***************
*** 393,400 ****
<b>/etc/postfix/transport</b>:
my.domain smtp:
.my.domain smtp:
! thishost.my.domain local: <blink>!important!</blink>
! localhost.my.domain local: <blink>!important!</blink>
<b>/etc/postfix/main.cf</b>:
transport_maps = hash:/etc/postfix/transport
--- 396,403 ----
<b>/etc/postfix/transport</b>:
my.domain smtp:
.my.domain smtp:
! thishost.my.domain local: <B>!important!</B>
! localhost.my.domain local: <B>!important!</B>
<b>/etc/postfix/main.cf</b>:
transport_maps = hash:/etc/postfix/transport
***************
*** 424,430 ****
<hr>
! <a name="firewall"><h3>Running Postfix on a firewall</h3> </a>
Note: this text applies to Postfix versions dated 19991115
and later only. To find out what Postfix version you have,
--- 427,433 ----
<hr>
! <h3><a name="firewall">Running Postfix on a firewall</a></h3>
Note: this text applies to Postfix versions dated 19991115
and later only. To find out what Postfix version you have,
***************
*** 482,488 ****
<hr>
! <a name="dialup"><h3>Running Postfix on a dialup machine</h3></a>
This section applies to dialup connections that are down most of
the time. For dialup connections that are up 24x7, see the <a
--- 485,491 ----
<hr>
! <h3><a name="dialup">Running Postfix on a dialup machine</a></h3>
This section applies to dialup connections that are down most of
the time. For dialup connections that are up 24x7, see the <a
***************
*** 498,504 ****
<ul>
! <li> Route all outgoing mail to your provider.
<p>
--- 501,507 ----
<ul>
! <li>Route all outgoing mail to your provider.
<p>
***************
*** 516,522 ****
<p>
! <li> <a name="spontaneous_smtp">Disable spontaneous SMTP mail
delivery (on-demand dialup IP only).</a>
<p>
--- 519,525 ----
<p>
! <li><a name="spontaneous_smtp">Disable spontaneous SMTP mail
delivery (on-demand dialup IP only).</a>
<p>
***************
*** 536,542 ****
<p>
! <li> Disable SMTP client DNS lookups (dialup LAN only).
<p>
--- 539,545 ----
<p>
! <li>Disable SMTP client DNS lookups (dialup LAN only).
<p>
***************
*** 562,568 ****
<p>
! <li> Flush the mail queue whenever the Internet link is established.
<p>
--- 565,571 ----
<p>
! <li>Flush the mail queue whenever the Internet link is established.
<p>
***************
*** 614,620 ****
<hr>
! <a name="verbose"><h3>Postfix breaks "sendmail -v"</h3> </a>
Some people will complain that <b>sendmail -v</b> no longer shows
the actual mail delivery.
--- 617,623 ----
<hr>
! <h3><a name="verbose">Postfix breaks "sendmail -v"</a></h3>
Some people will complain that <b>sendmail -v</b> no longer shows
the actual mail delivery.
***************
*** 639,645 ****
<hr>
! <a name="delayed"><h3>Postfix sends no "delayed mail" notices</h3>
<blockquote>
--- 642,648 ----
<hr>
! <h3><a name="delayed">Postfix sends no "delayed mail" notices</a></h3>
<blockquote>
***************
*** 668,674 ****
<hr>
! <a name="duplicate"><h3>Postfix sends duplicate mail</h3> </a>
Some people will complain that Postfix sends duplicate messages.
This happens whenever one message is mailed to multiple addresses
--- 671,677 ----
<hr>
! <h3><a name="duplicate">Postfix sends duplicate mail</a></h3>
Some people will complain that Postfix sends duplicate messages.
This happens whenever one message is mailed to multiple addresses
***************
*** 705,712 ****
<hr>
! <a name="metoo"><h3>Postfix sends mail to every member of a
! distribution list</h3> </a>
Some people will complain that Postfix sends mail to every member
of a distribution list, including the poster. By default, Sendmail
--- 708,715 ----
<hr>
! <h3><a name="metoo">Postfix sends mail to every member of a
! distribution list</a></h3>
Some people will complain that Postfix sends mail to every member
of a distribution list, including the poster. By default, Sendmail
***************
*** 722,728 ****
<hr>
! <a name="open_relay"><h3>Help! Postfix is an open relay</h3>
According to some relay checking software, Postfix accepts
mail for arbitrary non-local destinations:
--- 725,731 ----
<hr>
! <h3><a name="open_relay">Help! Postfix is an open relay</a></h3>
According to some relay checking software, Postfix accepts
mail for arbitrary non-local destinations:
***************
*** 793,814 ****
<ul>
! <li> <a href="uce.html#check_relay_domains">check_relay_domains</a>:
reject when the destination is not local and when the client hostname
does not match <a href="uce.html#relay_domains">relay_domains</a>.
! <li> <a
href="uce.html#permit_auth_destination">permit_auth_destination</a>:
skip when the destination is not local.
! <li> <a
href="uce.html#reject_unauth_destination">reject_unauth_destination</a>:
reject when the destination is not local.
! <li> <a href="uce.html#permit_mx_backup">permit_mx_backup</a>:
reject when the destination is not local.
! <li> Other UCE restrictions (e.g., SMTPD access maps) are not aware
of sender-provided routing information.
</ul>
--- 796,817 ----
<ul>
! <li><a href="uce.html#check_relay_domains">check_relay_domains</a>:
reject when the destination is not local and when the client hostname
does not match <a href="uce.html#relay_domains">relay_domains</a>.
! <li><a
href="uce.html#permit_auth_destination">permit_auth_destination</a>:
skip when the destination is not local.
! <li><a
href="uce.html#reject_unauth_destination">reject_unauth_destination</a>:
reject when the destination is not local.
! <li><a href="uce.html#permit_mx_backup">permit_mx_backup</a>:
reject when the destination is not local.
! <li>Other UCE restrictions (e.g., SMTPD access maps) are not aware
of sender-provided routing information.
</ul>
***************
*** 843,849 ****
<hr>
! <a name="mobile"><h3>Relaying mail for mobile users </h3>
<blockquote>
--- 846,852 ----
<hr>
! <h3><a name="mobile">Relaying mail for mobile users</a></h3>
<blockquote>
***************
*** 923,929 ****
<hr>
! <a name="relay_restrict"><h3>Restricting what users can send mail to off-site destinations</h3>
<blockquote>
--- 926,932 ----
<hr>
! <h3><a name="relay_restrict">Restricting what users can send mail to off-site destinations</a></h3>
<blockquote>
***************
*** 1016,1022 ****
<hr>
! <a name="timeouts"><h3>Mail fails consistently with timeout or lost connection</h3></a>
Every now and then, mail fails with "timed out while sending end
of data -- message may be sent more than once", or with: "lost
--- 1019,1026 ----
<hr>
! <h3><a name="timeouts">Mail fails consistently with timeout or lost
! connection</a></h3>
Every now and then, mail fails with "timed out while sending end
of data -- message may be sent more than once", or with: "lost
***************
*** 1089,1095 ****
<hr>
! <a name="root"> <h3>Root's mail is delivered to nobody</h3>
If you use <a href="#procmail">procmail</a> (or some other command)
for local mail delivery, Postfix will not deliver mail as root.
--- 1093,1099 ----
<hr>
! <h3><a name="root">Root's mail is delivered to nobody</a></h3>
If you use <a href="#procmail">procmail</a> (or some other command)
for local mail delivery, Postfix will not deliver mail as root.
***************
*** 1132,1138 ****
<hr>
! <a name="bogus"><h3>Postfix accepts mail for non-existing local users</h3>
The information in this section applies to Postfix versions 19991216
and later. See elsewhere for <a href="#virtual_setup">unknown
--- 1136,1142 ----
<hr>
! <h3><a name="bogus">Postfix accepts mail for non-existing local users</a></h3>
The information in this section applies to Postfix versions 19991216
and later. See elsewhere for <a href="#virtual_setup">unknown
***************
*** 1176,1183 ****
<hr>
! <a name="some_local"><h3>Delivering some users locally while sending
! mail as userdomain</h3></a>
<ul>
--- 1180,1187 ----
<hr>
! <h3><a name="some_local">Delivering some users locally while sending
! mail as userdomain</a></h3>
<ul>
***************
*** 1227,1233 ****
<hr>
! <a name="maildir"><h3>Support for maildir-style mailboxes</h3> </a>
<b>Maildir</b> is a specific one-file-per-message organization that
was introduced with the <b>qmail</b> system by Daniel Bernstein.
--- 1231,1237 ----
<hr>
! <h3><a name="maildir">Support for maildir-style mailboxes</a></h3>
<b>Maildir</b> is a specific one-file-per-message organization that
was introduced with the <b>qmail</b> system by Daniel Bernstein.
***************
*** 1256,1262 ****
<hr>
! <a name="procmail"><h3>Using Procmail for system-wide local delivery</h3> </a>
Warning: if you use <b>procmail</b> in this manner, you must set
up an alias for <b>root</b> that forwards mail for <b>root</b> to
--- 1260,1266 ----
<hr>
! <h3><a name="procmail">Using Procmail for system-wide local delivery</a></h3>
Warning: if you use <b>procmail</b> in this manner, you must set
up an alias for <b>root</b> that forwards mail for <b>root</b> to
***************
*** 1328,1334 ****
<hr>
! <a name="delivered"><h3>Getting rid of the ugly Delivered-To: header</h3> </a>
Some people will complain about the ugly <b>Delivered-To:</b>
message header that Postfix prepends to their mail. By default,
--- 1332,1338 ----
<hr>
! <h3><a name="delivered">Getting rid of the ugly Delivered-To: header</a></h3>
Some people will complain about the ugly <b>Delivered-To:</b>
message header that Postfix prepends to their mail. By default,
***************
*** 1346,1362 ****
<ul>
! <li>
!
! Fortunately, many mail user agents have per-user or even system-wide
configuration files that can be set up to suppress <b>Delivered-To:</b>
headers (for example <b>~/.mailrc</b> and <b>/usr/lib/Mail.rc</b>).
<p>
! <li>
!
! With mailing lists, <b>Delivered-To:</b> can get in the way when
the list exploder uses a "secret" alias that should not be shown
in outbound mail. The recommended solution is to use a regular
expression-based filter at the SMTP port:
--- 1350,1362 ----
<ul>
! <li>Fortunately, many mail user agents have per-user or even system-wide
configuration files that can be set up to suppress <b>Delivered-To:</b>
headers (for example <b>~/.mailrc</b> and <b>/usr/lib/Mail.rc</b>).
<p>
! <li>With mailing lists, <b>Delivered-To:</b> can get in the way when
the list exploder uses a "secret" alias that should not be shown
in outbound mail. The recommended solution is to use a regular
expression-based filter at the SMTP port:
***************
*** 1365,1389 ****
<dl>
! <dt><b>/etc/postfix/main.cf:</b>
!
! <dl>
! <dt><tt>smtpd_recipient_restrictions = ... regexp:/etc/postfix/access_regexp ...</tt>
! <dt><tt>smtpd_recipient_restrictions = ... pcre:/etc/postfix/access_regexp ...</tt>
</dl>
<p>
! <dt><b>/etc/postfix/access_regexp:</b>
!
! <dl>
! <dt><tt>/^(.*)-outgoing(.*)/ 554 Use $1$2 instead</tt>
!
! </dl>
</dl>
--- 1365,1383 ----
<dl>
! <dt><b>/etc/postfix/main.cf:</b></dt>
! <dd><tt>smtpd_recipient_restrictions = ... regexp:/etc/postfix/access_regexp ...</tt></dd>
! <dd><tt>smtpd_recipient_restrictions = ... pcre:/etc/postfix/access_regexp ...</tt></dd>
</dl>
<p>
! <dl><dt><b>/etc/postfix/access_regexp:</b></dt>
! <dd><tt>/^(.*)-outgoing(.*)/ 554 Use $1$2 instead</tt></dd>
</dl>
***************
*** 1396,1404 ****
<p>
! <li>
!
! The <b>prepend_delivered_header</b> configuration parameter controls
when <b>Delivered-To:</b> is prepended. The default setting is
<b>command, file, forward</b> (translation: prepend <b>Delivered-To:</b>
when delivering to command, when delivering to file, and when
--- 1390,1396 ----
<p>
! <li>The <b>prepend_delivered_header</b> configuration parameter controls
when <b>Delivered-To:</b> is prepended. The default setting is
<b>command, file, forward</b> (translation: prepend <b>Delivered-To:</b>
when delivering to command, when delivering to file, and when
***************
*** 1414,1421 ****
<hr>
! <a name="majordomo-approve"><h3>Postfix breaks the majordomo "approve"
! command</h3> </a>
The Postfix local delivery agent prepends a <b>Delivered-To:</b>
message header to prevent mail forwarding loops. With <b>majordomo</b>
--- 1406,1413 ----
<hr>
! <h3><a name="majordomo-approve">Postfix breaks the majordomo "approve"
! command</a></h3>
The Postfix local delivery agent prepends a <b>Delivered-To:</b>
message header to prevent mail forwarding loops. With <b>majordomo</b>
***************
*** 1449,1455 ****
<hr>
! <a name="internal-list"><h3>Protecting internal email distribution lists</h3>
<blockquote>
--- 1441,1447 ----
<hr>
! <h3><a name="internal-list">Protecting internal email distribution lists</a></h3>
<blockquote>
***************
*** 1539,1545 ****
<hr>
! <a name="virtual_setup"><h3>How to configure a Postfix virtual domain</h3>
Problem:
--- 1531,1537 ----
<hr>
! <h3><a name="virtual_setup">How to configure a Postfix virtual domain</a></h3>
Problem:
***************
*** 1567,1573 ****
<ul>
! <li> Add a magical entry to the Postfix virtual maps for
each Postfix virtual domain:
<p>
--- 1559,1565 ----
<ul>
! <li>Add a magical entry to the Postfix virtual maps for
each Postfix virtual domain:
<p>
***************
*** 1579,1588 ****
<p>
! <li> Do not list Postfix virtual domains in the <a
href="basic.html#mydestination">mydestination</a> parameter.
! <li> Do not list Postfix virtual maps in the <b>local_recipient_maps</b>
parameter.
<li>As of Postfix version 19991226 it is no longer necessary to
--- 1571,1580 ----
<p>
! <li>Do not list Postfix virtual domains in the <a
href="basic.html#mydestination">mydestination</a> parameter.
! <li>Do not list Postfix virtual maps in the <b>local_recipient_maps</b>
parameter.
<li>As of Postfix version 19991226 it is no longer necessary to
***************
*** 1598,1604 ****
<hr>
! <a name="command"><h3>Commands don't work in Postfix virtual maps</h3>
Delivering mail to a command is a security-sensitive operation,
because the command must be executed with the right privileges.
--- 1590,1596 ----
<hr>
! <h3><a name="command">Commands don't work in Postfix virtual maps</a></h3>
Delivering mail to a command is a security-sensitive operation,
because the command must be executed with the right privileges.
***************
*** 1664,1670 ****
<hr>
! <a name="domain_mailbox"><h3>Receiving a virtual domain in a mailbox</h3>
Question: how to receive all mail for a domain in a mailbox without
losing the original recipient information? The Postfix Delivered-To:
--- 1656,1662 ----
<hr>
! <h3><a name="domain_mailbox">Receiving a virtual domain in a mailbox</a></h3>
Question: how to receive all mail for a domain in a mailbox without
losing the original recipient information? The Postfix Delivered-To:
***************
*** 1713,1726 ****
<ul>
! <li> Be sure to specify the <b>^</b> and <b>\</b> and <b>$</b> or
else you may have false hits.
! <li> Maps with regular expressions are searched sequentially. This
can be expensive when you list many domains in regular expression
maps.
! <li> Postfix has <b>regexp </b> map support only on modern UNIXes.
Instead of <b>regexp </b> maps your Postfix system may also support
<b>pcre</b> maps which have a similar syntax. To find out what maps
your system supports, use the command <b>postconf -m</b>.
--- 1705,1718 ----
<ul>
! <li>Be sure to specify the <b>^</b> and <b>\</b> and <b>$</b> or
else you may have false hits.
! <li>Maps with regular expressions are searched sequentially. This
can be expensive when you list many domains in regular expression
maps.
! <li>Postfix has <b>regexp </b> map support only on modern UNIXes.
Instead of <b>regexp </b> maps your Postfix system may also support
<b>pcre</b> maps which have a similar syntax. To find out what maps
your system supports, use the command <b>postconf -m</b>.
***************
*** 1729,1735 ****
<hr>
! <a name="masquerade"><h3>Address masquerading with exceptions</h3></a>
For people outside your organization it can be desirable to only
see addresses of the form <i>usercompany.com</i> rather than
--- 1721,1727 ----
<hr>
! <h3><a name="masquerade">Address masquerading with exceptions</a></h3>
For people outside your organization it can be desirable to only
see addresses of the form <i>usercompany.com</i> rather than
***************
*** 1803,1810 ****
exempt this way is originating mail as <i>usermy.domain</i> in
the first place, you can hardly exempt it.
- <p>
-
</ul>
As usual, execute the command <b>postfix reload</b> to make the changes
--- 1795,1800 ----
***************
*** 1814,1820 ****
<hr>
! <a name="scanning"><h3>Support for virus scanning</h3> </a>
Would not it be great if operating systems and applications actually
worked the way they are supposed to, instead of being as fragile
--- 1804,1810 ----
<hr>
! <h3><a name="scanning">Support for virus scanning</a></h3>
Would not it be great if operating systems and applications actually
worked the way they are supposed to, instead of being as fragile
***************
*** 1861,1867 ****
<hr>
! <a name="internet-uucp"><h3>Setting up an Internet to UUCP gateway</h3> </a>
Here is how to set up a machine that sits on the Internet and that
delivers <i>some</i> but not all non-local mail via UUCP. See the
--- 1851,1857 ----
<hr>
! <h3><a name="internet-uucp">Setting up an Internet to UUCP gateway</a></h3>
Here is how to set up a machine that sits on the Internet and that
delivers <i>some</i> but not all non-local mail via UUCP. See the
***************
*** 1961,1967 ****
<hr>
! <a name="uucp-only"><h3>Using UUCP as the default transport</h3> </a>
Here is how to relay all your mail over a UUCP link. See the <a
href="#internet-uucp">Internet to UUCP</a> FAQ entry for setting
--- 1951,1957 ----
<hr>
! <h3><a name="uucp-only">Using UUCP as the default transport</a></h3>
Here is how to relay all your mail over a UUCP link. See the <a
href="#internet-uucp">Internet to UUCP</a> FAQ entry for setting
***************
*** 1975,1981 ****
<p>
! <li> Specify that all remote mail must be sent via the <b>uucp</b>
mail transport to your UUCP gateway host, say, <i>uucp-gateway</i>:
<p>
--- 1965,1971 ----
<p>
! <li>Specify that all remote mail must be sent via the <b>uucp</b>
mail transport to your UUCP gateway host, say, <i>uucp-gateway</i>:
<p>
***************
*** 2015,2027 ****
<hr>
! <a name="fax"><h3>Sending mail to a FAX machine</h3></a>
! The following information is by Joerg Henne:
<p>
! Over here we are using the scheme <fax number>fax.our.domain with Postfix and
! HylaFax. Here's the setup used:
<p>
--- 2005,2017 ----
<hr>
! <h3><a name="fax">Sending mail to a FAX machine</a></h3>
! The following information is by Jörg Henne:
<p>
! Over here we are using the scheme <fax number>fax.our.domain
! with Postfix and HylaFax. Here's the setup used:
<p>
***************
*** 2048,2054 ****
<hr>
! <a name="bind"><h3>Undefined symbols: ___dn_expand, ___res_init etc.</h3></a>
Question: When I build Postfix I get the following errors:
--- 2038,2044 ----
<hr>
! <h3><a name="bind">Undefined symbols: ___dn_expand, ___res_init etc.</a></h3>
Question: When I build Postfix I get the following errors:
***************
*** 2079,2085 ****
<hr>
! <a name="dbm_dirfno"><h3>Undefined symbols: dbm_pagfno, dbm_dirfno etc.</h3></a>
Question: When I build Postfix I get the following errors:
--- 2069,2075 ----
<hr>
! <h3><a name="dbm_dirfno">Undefined symbols: dbm_pagfno, dbm_dirfno etc.</a></h3>
Question: When I build Postfix I get the following errors:
***************
*** 2104,2110 ****
<hr>
! <a name="db"><h3>Using DB libraries on Solaris etc.</h3> </a>
The old <b>dbm</b> UNIX database has severe limitations when you
try to store lots of information. It breaks when the number of hash
--- 2094,2100 ----
<hr>
! <h3><a name="db">Using DB libraries on Solaris etc.</a></h3>
The old <b>dbm</b> UNIX database has severe limitations when you
try to store lots of information. It breaks when the number of hash
-- Matthias AndreeHi! I'm the infamous .signature virus! Copy me into your ~/.signature to help me spread!
- Next message: cyberms10.hinet.net: "how to config postfix as an smtp gateway?"
- Previous message: Matthias Andree: "Re: man2html and postlink"
- Next in thread: Matthias Andree: "Re: man2html and postlink"
- Maybe reply: Matthias Andree: "Re: man2html and postlink"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This archive was generated by hypermail 2b27 : Mon Jan 03 2000 - 01:38:47 CST