makemanidx   [plain text]


cat <<EOF
<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"



<title>Postfix Manual Pages </title>

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">



<h1><img src="postfix-logo.jpg" width="203" height="98" ALT="">Postfix
Manual Pages </h1>


<h2> Information for new Postfix users </h2>

<p> New Postfix users should first look at the following introductory
documents.  These introductions are hyperlinked to more advanced
documents and to UNIX-style manual pages. The UNIX-style manual
pages are intended for people who are already familiar with Postfix.


<li> <a href="OVERVIEW.html"> Postfix architecture overview </a>

<li> <a href="BASIC_CONFIGURATION_README.html"> Basic configuration

<li> <a href="DEBUG_README.html"> Trouble shooting </a>

<li> <a href="CONTENT_INSPECTION_README.html"> Content inspection

<li> <a href="SMTPD_ACCESS_README.html">Relay/access control overview

<li> <a href="DATABASE_README.html"> Lookup table overview </a>


<h2> Postfix manual page organization </h2>

<p> Each Postfix manual page is numbered after a section of the
UNIX manual: examples are mailq(1) or access(5). Unfortunately,
there is no single universal method to organize manual pages; each
UNIX flavor appears to be different. Postfix documentation assumes
the following convention:  </p>


<table cellpadding="0" cellspacing="0">

<tr><th> Section </th> <th> Topic </th> </tr>

<tr><td colspan="2"> <hr> </td> </tr>

<tr><td align="center"> 1 </td> <td> Commands </td> </tr>

<tr><td align="center"> 3 </td> <td> Library routines </td> </tr>

<tr><td align="center"> 5 </td> <td> File formats </td> </tr>

<tr><td align="center"> 8 </td> <td> Daemons </td> </tr>




srctoman "$@" | awk '

NR == 1,/SH "*SEE ALSO"*/ { next }

/^Other:$/ { print ul; exit }

/^[A-Z].*:$/ { print ul "<h2>", $0, "</h2>\n\n<ul>\n\n"; ul = "</ul>\n\n" }

/^[a-z][-a-z0-9_]+\(/ { print "<li>", $0, "\n" }

' | sed 's;: </h2>$; </h2>;'

cat <<EOF