aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2010-07-14 17:44:55 +0300
committerSergey Poznyakoff <gray@gnu.org.ua>2010-07-14 18:46:38 +0300
commitc1b73cf4f3b0a99a2de76691e973652b3a5fb2e3 (patch)
treec00c8047869571ccdf545c78731933e154d3c5fa
parentc319e8349325f4d9d2136d7bfa385bc7bce2f648 (diff)
downloadmailfromd-c1b73cf4f3b0a99a2de76691e973652b3a5fb2e3.tar.gz
mailfromd-c1b73cf4f3b0a99a2de76691e973652b3a5fb2e3.tar.bz2
Minor changes
* NEWS: Reword some passages. * etc/Makefile.am (EXTRA_DIST): Add sendmail-8.14.3.connect.diff
-rw-r--r--NEWS90
-rw-r--r--etc/Makefile.am2
2 files changed, 51 insertions, 41 deletions
diff --git a/NEWS b/NEWS
index d957322b..ac9f77b9 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-Mailfromd NEWS -- history of user-visible changes. 2010-06-13
+Mailfromd NEWS -- history of user-visible changes. 2010-07-14
Copyright (C) 2005, 2006, 2007, 2008, 2009, 2010 Sergey Poznyakoff
See the end of file for copying conditions.
@@ -27,25 +27,28 @@ the milter requests, and Callout servers, which run callout
(or sender verification) SMTP sessions and update the cache
database accordingly.
-When a callout server is enabled, the sender verification functions
+When a callout server is enabled, sender verification functions
work the following way. First, the usual sender verification is
-performed using a set of so-called `soft' timeout values. If
-this verification yields a definite answer, that answer is entered
-into the cache database and returned to the calling procedure as
+performed with a set of so-called `soft' timeout values. If
+this verification yields a definite answer, that answer is stored
+in the cache database and returned to the calling procedure as
usual. In that regard, this release works exactly as its predecessors
did. If, however, the verification is aborted due to a timeout,
-the calling procedure is returned a e_temp_failure exception, and
+the caller procedure is returned an e_temp_failure exception, and
the session is scheduled for processing by a callout server. The
latter processes the request using a set of `hard' timeouts,
-which are normally much longer than `soft' ones and have the values
-required by RFC 2822 (see below, for a detailed description). Thus,
-this callout session is run independently of the milter session that
-initiated it. The milter session will return a temporary error to
-the sender, which will force it to retry the connection later. In
-the meantime, the callout server will finish the requested sender
+which are normally much longer than `soft' ones (their default values
+are those required by RFC 2822; see below for a detailed description).
+This callout session runs independently of the milter session that
+initiated it. The milter session returns a temporary error to
+the sender, urging it to retry the connection later. In the meantime,
+the callout server has a chance to finish the requested sender
verification and store its result in the cache database. When the
-sender retries the delivery, the milter server will obtain the cached
-result from the database.
+sender retries the delivery, the milter server will obtain the already
+cached result from the database. If the callout server has not
+finished the request by the time the sender retries the connection,
+the latter is again returned a temporary error, and the process
+continues until the callout is finished.
Milter servers are declared using the following configuration
statement:
@@ -64,7 +67,7 @@ server <type: milter | callout> {
<acl-statement>
}
-If type is `callout', the server block statement may also contain the
+If the type is `callout', the `server' block statement may also contain the
following sub-statement:
default <arg: boolean>;
@@ -81,18 +84,18 @@ statement:
* Timeout control for callout SMTP sessions
-Callout SMTP sessions, initiated by polling functions, are controlled
+Callout SMTP sessions initiated by polling functions, are controlled
by two sets of timeouts: `soft' and `hard'. Soft timeouts are used
by the mailfromd milter servers. Hard timeouts are used by callout
servers. When a soft timeout is exceeded, the calling procedure is
-delivered a e_temp_failure exception and the session is scheduled for
+delivered an e_temp_failure exception and the session is scheduled for
processing by a callout server. The latter re-runs the session using
hard timeouts. If a hard timeout is exceeded, the address is marked
-as not_found and is entered into the cache database with that status.
+as `not_found' and is stored in the cache database with that status.
Normally, soft timeouts are set to shorter values, suitable for use
in MFL scripts. Hard timeouts are set to large values, as requested
-by RFC2822, which guarantee obtaining of a definite answer (see below
+by RFC2822, which guarantee obtaining a definite answer (see below
for the default values).
Individual timeouts may be set in the configuration file, using the
@@ -127,7 +130,7 @@ The default timeout settings are:
rset I/O 5m
quit I/O 2m
-the entries marked with I/O, unless set explicitly by a
+The entries marked with I/O, unless set explicitly by a
corresponding `smtp-timeout soft' entry, are set to the
value of I/O timeout (see the `io-timeout' configuration
statement and the `--timeout' command line option), which
@@ -194,7 +197,7 @@ recovery.
If open call is used to start external program (i.e. its argument
begins with a `|' or `|&'), the standard error of the program is
-closed before starting it. Special constructs are provided for
+closed prior to starting it. Special constructs are provided for
redirecting it to an output file or syslog:
- "|2>null: COMMAND"
@@ -216,23 +219,23 @@ is assumed.
** Message Modifications and Accept.
-Calling `accept' causes any modifications to the
-message (applied by, e.g., header_add and the like) to be ignored.
-This is due to requirements of the Milter protocol.
+Calling `accept' undoes any modifications to the message applied by,
+e.g., header_add and the like. This is due to requirements of the
+Milter protocol.
-Previously it would be hard to diagnose and would cause some false bug
-reports. Now, calling `accept' after any modifications to the message
+This behavior caused several false bug reports in the past. Starting
+with this version, calling `accept' after any modifications to the message
results in the following warning message:
RUNTIME WARNING near /etc/mailfromd.mf:36: `accept' causes previous
message modification commands to be ignored; call mmq_purge() prior
to `accept', to suppress this warning
-It is only warning, the `accept' action itself is, of course, honored.
+It is only a warning, the `accept' action itself is, of course, honored.
If you see this diagnostics in your log, do the following:
- - if it was intended, call mmq_purge, as suggested (see below for the
- description of this function);
+ - if the behavior was intended, call mmq_purge, as suggested (see
+ below for a description of this function);
- if it was not, read the manual, subsection `4.12.1.8 Message
Modification Queue', for information on how to handle it.
FIXME: section number is subject to change.
@@ -257,15 +260,22 @@ for 1.5 seconds, use:
string dequote(string email)
-The function `dequote' removes surrounding angle brackets from its
-argument and returns the resuting string. If there are no angle
-brackets, or if they are unbalanced, returns unchanged argument.
+The function `dequote' removes angle brackets surrounding its
+argument and returns the resulting string. If there are no angle
+brackets, or if they are unbalanced, it returns unchanged argument.
*** debug_spec
-The `debug_spec' function takes an optional numeric argument, which
-sets the minimum debugging level. The function returns only those debug
-specifications whose level is greater than or equal to the minimum.
+string debug_spec([string modnames[, number minlevel]])
+
+Returns the current debugging level specification. Optional parameters
+supply conditions for abridging the amount of information returned.
+
+The `minlevel' parameters instructs the function to return only those
+specifications that have the level part greater than or equal to the
+given value. The `modnames' parameter (a comma-separated list of
+module name parts) selects only those specification that match the
+supplied module names.
*** mmq_purge
@@ -282,21 +292,21 @@ version of the package.
* smap
-The smap utility has been removed. Please, use the smapd daemon
-which provides much more power and flexibility. See
-http://puszcza.gnu.org.ua/projects/smap, for additional information,
+The smap utility has been removed. A new project was established
+that provides and largely expands its functionality. See
+http://smap.software.gnu.org.ua, for additional information,
including links to file downloads.
* Version output for alpha versions.
-Starting from this release, all alpha versions will output
+Starting from this release, all alpha versions output
additional information when invoked with the `--version' option.
The new output looks like this:
mailfromd (mailfromd) 6.0.91 [release-6.0-17-ga3fa5da]
where the string between brackets is the recent GIT tag (see also
-the description of `__git__' constant, above). If this release
+the description of `__git__' constant above). If this release
contains some uncommitted changes, the suffix `-dirty' is appended
to it.
diff --git a/etc/Makefile.am b/etc/Makefile.am
index e9f541fd..306c721d 100644
--- a/etc/Makefile.am
+++ b/etc/Makefile.am
@@ -14,7 +14,7 @@
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
-EXTRA_DIST = mailfromd.mf rc.in sendmail-8.13.7.connect.diff
+EXTRA_DIST = mailfromd.mf rc.in sendmail-8.13.7.connect.diff sendmail-8.14.3.connect.diff
noinst_SCRIPTS = rc.mailfromd
DEFAULT_PIDFILE = $(DEFAULT_STATE_DIR)/mailfromd.pid

Return to:

Send suggestions and report system problems to the System administrator.