<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12-10-11 12:57 AM, Adam Thompson
wrote:<br>
</div>
<blockquote cite="mid:004401cda775$5a037280$0e0a5780$@athompso.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1"><br>
<p class="MsoNormal">to /etc/postfix/client_access (and
remembering to run postmap on it) eventually convinces Postfix
to let this message in. (But typically not immediately, which
I still don’t understand. Ideas?) Only one of those lines
should be necessary, but I’ve never figured out which one :-).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
The following reference provides an explanation:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://www.postfix.org/DATABASE_README.html">http://www.postfix.org/DATABASE_README.html</a>
<br>
<br>
Process dependent ... I generally reload and/or restart, depending
on what is being changed. :-)<br>
<br>
Dan.<br>
<br>
-------------------------------------------------------------------
snippet below ------------------------------------<br>
Maintaining Postfix lookup table files<br>
<br>
When you make changes to a database while the mail system is
running, it would be desirable if Postfix avoids reading information
while that information is being changed. It would also be nice if
you can change a database without having to execute "postfix
reload", in order to force Postfix to use the new information. Each
time you do "postfix reload" Postfix loses a lot of performance.<br>
<br>
If you change a network database such as LDAP, NIS or SQL, there is
no need to execute "postfix reload". The LDAP, NIS or SQL server
takes care of read/write access conflicts and gives the new data to
Postfix once that data is available.<br>
<br>
If you change a regexp: or pcre: file then Postfix may or may not
pick up the file changes immediately. This is because a Postfix
process reads the entire file into memory once and never examines
the file again.<br>
<br>
If the file is used by a short-running process such as smtpd(8),
cleanup(8) or local(8), there is no need to execute "postfix reload"
after making a change.<br>
<br>
If the file is being used by a long-running process such as
trivial-rewrite(8) on a busy server it may be necessary to execute
"postfix reload".<br>
<br>
If you change a local file based database such as DBM or Berkeley
DB, there is no need to execute "postfix reload". Postfix uses file
locking to avoid read/write access conflicts, and whenever a Postfix
daemon process notices that a file has changed it will terminate
before handling the next client request, so that a new process can
initialize with the new database.<br>
</body>
</html>