...and postpone for fetchmail 6.4.
svn path=/branches/BRANCH_6-3/; revision=5296
fetchmail 6.3.10 (not yet released):
-# INCOMPATIBLE BUGFIXES
-* Use PS_PROTOCOL (4) rather than PS_SYNTAX (5) exit status when a pre- or
- post-connect command fails.
-
# BUGFIXES
* Fix misuse of canonical autoconf target as _TARGET when it should have been
_HOST. Report and patch courtesy of Diego E. "Flameeyes" Pettenò.
<simpkins@cisco.com> around Nov 2nd)?
6.4:
+- use PS_PROTOCOL for pre-/post-connect command failures - 6.3 uses
+ PS_SYNTAX, and that's not necessarily the case. At least if the
+ command terminates with a signal, we should report PS_PROTOCOL.
- revisit maximum allowed rcfile permissions, fix inconsistency
(silently allowing g+x).
- make UID code more efficient, parsing is O(n^2), should be no worse
else
report(stderr,
GT_("pre-connection command failed with status %d\n"), WEXITSTATUS(err));
- err = PS_PROTOCOL;
+ err = PS_SYNTAX;
goto closeUp;
}
else
report(stderr, GT_("post-connection command failed with status %d\n"), WEXITSTATUS(tmperr));
if (err == PS_SUCCESS)
- err = PS_PROTOCOL;
+ err = PS_SYNTAX;
}
set_timeout(0); /* cancel any pending alarm */
standard input attached to a terminal and could not prompt for a
missing password.
.IP 4
-Some sort of fatal protocol error was detected. Since 6.3.10, this
-includes non-zero exit status or signal-triggered termination of a pre-
-or post-connect command.
+Some sort of fatal protocol error was detected.
.IP 5
There was a syntax error in the arguments to
-.IR fetchmail .
-Up to and including 6.3.9, this was also used if the pre- or
-post-connect command failed.
+\fIfetchmail\fP, or a pre- or post-connect command failed.
.IP 6
The run control file had bad permissions.
.IP 7