mirror of
https://github.com/vdukhovni/postfix
synced 2025-09-02 07:05:27 +00:00
postfix-2.0.0-20030105
This commit is contained in:
committed by
Viktor Dukhovni
parent
1eed3b4cde
commit
4268b309fa
@@ -26,7 +26,7 @@ Incompatible changes with Postfix snapshot 2.0.0-20030104
|
|||||||
=========================================================
|
=========================================================
|
||||||
|
|
||||||
This release adds the new proxymap service (table lookup via a
|
This release adds the new proxymap service (table lookup via a
|
||||||
proxy process) to the the master.cf file. If you get warnings about
|
proxy process) to the master.cf file. If you get warnings about
|
||||||
problems connecting to the proxymap service, then you did not
|
problems connecting to the proxymap service, then you did not
|
||||||
properly upgrade Postfix.
|
properly upgrade Postfix.
|
||||||
|
|
||||||
@@ -51,7 +51,7 @@ to automatically restart even on busy mail systems.
|
|||||||
Clients of multi-server daemons such as trivial-rewrite and the
|
Clients of multi-server daemons such as trivial-rewrite and the
|
||||||
new proxymap service now automatically disconnect after $ipc_ttl
|
new proxymap service now automatically disconnect after $ipc_ttl
|
||||||
seconds of activity (default: 1000s). This allows multi-server
|
seconds of activity (default: 1000s). This allows multi-server
|
||||||
daemons to automatically restart even on busy mail mail systems.
|
daemons to automatically restart even on busy mail systems.
|
||||||
|
|
||||||
Incompatible changes with Postfix snapshot 1.1.11-trace-20021119
|
Incompatible changes with Postfix snapshot 1.1.11-trace-20021119
|
||||||
================================================================
|
================================================================
|
||||||
|
@@ -188,7 +188,7 @@ mail_owner = postfix
|
|||||||
# the system passwd file in the chroot jail is just not practical.
|
# the system passwd file in the chroot jail is just not practical.
|
||||||
#
|
#
|
||||||
#local_recipient_maps = unix:passwd.byname $alias_maps
|
#local_recipient_maps = unix:passwd.byname $alias_maps
|
||||||
#local_recipient_maps = proxy:passwd.byname $alias_maps
|
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
|
||||||
#local_recipient_maps =
|
#local_recipient_maps =
|
||||||
|
|
||||||
# The unknown_local_recipient_reject_code specifies the SMTP server
|
# The unknown_local_recipient_reject_code specifies the SMTP server
|
||||||
|
@@ -39,7 +39,7 @@
|
|||||||
#
|
#
|
||||||
#local_recipient_maps =
|
#local_recipient_maps =
|
||||||
#local_recipient_maps = unix:passwd.byname $alias_maps
|
#local_recipient_maps = unix:passwd.byname $alias_maps
|
||||||
local_recipient_maps = proxy:passwd.byname $alias_maps
|
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
|
||||||
|
|
||||||
# The unknown_local_recipient_reject_code specifies the SMTP server
|
# The unknown_local_recipient_reject_code specifies the SMTP server
|
||||||
# response code when a recipient domain matches $mydestination or
|
# response code when a recipient domain matches $mydestination or
|
||||||
|
@@ -49,9 +49,10 @@ PROXYMAP(8) PROXYMAP(8)
|
|||||||
<i>type:mapname</i> and <i>flags</i> are the same as with the
|
<i>type:mapname</i> and <i>flags</i> are the same as with the
|
||||||
<b>PROXY</b><i>_</i><b>REQ</b><i>_</i><b>OPEN</b> request.
|
<b>PROXY</b><i>_</i><b>REQ</b><i>_</i><b>OPEN</b> request.
|
||||||
|
|
||||||
There is no close command. This does not seem to be useful
|
There is no close command, nor are tables implicitly
|
||||||
because tables are meant to be shared among client pro-
|
closed when a client disconnects. One of the purposes of
|
||||||
cesses.
|
the proxymap server is to share tables among multiple
|
||||||
|
client processes.
|
||||||
|
|
||||||
The request completion status code is one of:
|
The request completion status code is one of:
|
||||||
|
|
||||||
|
@@ -51,8 +51,9 @@ the lookup result value.
|
|||||||
The \fImaptype:mapname\fR and \fIflags\fR are the same
|
The \fImaptype:mapname\fR and \fIflags\fR are the same
|
||||||
as with the \fBPROXY_REQ_OPEN\fR request.
|
as with the \fBPROXY_REQ_OPEN\fR request.
|
||||||
.PP
|
.PP
|
||||||
There is no close command. This does not seem to be useful
|
There is no close command, nor are tables implicitly closed
|
||||||
because tables are meant to be shared among client processes.
|
when a client disconnects. One of the purposes of the proxymap
|
||||||
|
server is to share tables among multiple client processes.
|
||||||
|
|
||||||
The request completion status code is one of:
|
The request completion status code is one of:
|
||||||
.IP \fBPROXY_STAT_OK\fR
|
.IP \fBPROXY_STAT_OK\fR
|
||||||
|
@@ -115,7 +115,7 @@ static void clnt_stream_event(int unused_event, char *context)
|
|||||||
clnt_stream_close(clnt_stream);
|
clnt_stream_close(clnt_stream);
|
||||||
}
|
}
|
||||||
|
|
||||||
/* clnt_stream_ttl_event - server-initiated disconnect or client-side timeout */
|
/* clnt_stream_ttl_event - client-side expiration */
|
||||||
|
|
||||||
static void clnt_stream_ttl_event(int event, char *context)
|
static void clnt_stream_ttl_event(int event, char *context)
|
||||||
{
|
{
|
||||||
|
@@ -132,6 +132,7 @@ static const char *dict_proxy_lookup(DICT *dict, const char *key)
|
|||||||
case PROXY_STAT_OK:
|
case PROXY_STAT_OK:
|
||||||
return (STR(dict_proxy->result));
|
return (STR(dict_proxy->result));
|
||||||
case PROXY_STAT_NOKEY:
|
case PROXY_STAT_NOKEY:
|
||||||
|
dict_errno = 0;
|
||||||
return (0);
|
return (0);
|
||||||
case PROXY_STAT_RETRY:
|
case PROXY_STAT_RETRY:
|
||||||
dict_errno = DICT_ERR_RETRY;
|
dict_errno = DICT_ERR_RETRY;
|
||||||
|
@@ -20,7 +20,7 @@
|
|||||||
* Patches change the patchlevel and the release date. Snapshots change the
|
* Patches change the patchlevel and the release date. Snapshots change the
|
||||||
* release date only, unless they include the same bugfix as a patch release.
|
* release date only, unless they include the same bugfix as a patch release.
|
||||||
*/
|
*/
|
||||||
#define MAIL_RELEASE_DATE "20030104"
|
#define MAIL_RELEASE_DATE "20030105"
|
||||||
|
|
||||||
#define VAR_MAIL_VERSION "mail_version"
|
#define VAR_MAIL_VERSION "mail_version"
|
||||||
#define DEF_MAIL_VERSION "2.0.0-" MAIL_RELEASE_DATE
|
#define DEF_MAIL_VERSION "2.0.0-" MAIL_RELEASE_DATE
|
||||||
|
@@ -45,8 +45,9 @@
|
|||||||
/* The \fImaptype:mapname\fR and \fIflags\fR are the same
|
/* The \fImaptype:mapname\fR and \fIflags\fR are the same
|
||||||
/* as with the \fBPROXY_REQ_OPEN\fR request.
|
/* as with the \fBPROXY_REQ_OPEN\fR request.
|
||||||
/* .PP
|
/* .PP
|
||||||
/* There is no close command. This does not seem to be useful
|
/* There is no close command, nor are tables implicitly closed
|
||||||
/* because tables are meant to be shared among client processes.
|
/* when a client disconnects. One of the purposes of the proxymap
|
||||||
|
/* server is to share tables among multiple client processes.
|
||||||
/*
|
/*
|
||||||
/* The request completion status code is one of:
|
/* The request completion status code is one of:
|
||||||
/* .IP \fBPROXY_STAT_OK\fR
|
/* .IP \fBPROXY_STAT_OK\fR
|
||||||
|
Reference in New Issue
Block a user