Don't try to drop our controlling TTY except when we are starting up a
daemon; this can cause UUCP jobs to hang waiting for carrier on a dialin
line (completely contrary to the intent). Many thanks

Don't try to drop our controlling TTY except when we are starting up a
daemon; this can cause UUCP jobs to hang waiting for carrier on a dialin
line (completely contrary to the intent). Many thanks to Keith Sklower
for pointing this one out. However, that damned parameter to disconnect()
has reappeared!

show more ...

Don't try to drop our controlling TTY except when we are starting up a
daemon; this can cause UUCP jobs to hang waiting for carrier on a dialin
line (completely contrary to the intent). Many thanks

Don't try to drop our controlling TTY except when we are starting up a
daemon; this can cause UUCP jobs to hang waiting for carrier on a dialin
line (completely contrary to the intent). Many thanks to Keith Sklower
for pointing this one out. However, that damned parameter to disconnect()
has reappeared!

show more ...

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA c

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA command; the problem
went away quite mysteriously, so I have no idea why it happened

show more ...

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA c

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA command; the problem
went away quite mysteriously, so I have no idea why it happened

show more ...

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA c

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA command; the problem
went away quite mysteriously, so I have no idea why it happened

show more ...

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA c

Ignore SIGPIPE early (in main rather than in deliver) so that rude hosts
that close the connection early don't cause us to die -- in particular,
CMU-CS-A (nee CMU-10A) was doing this after the DATA command; the problem
went away quite mysteriously, so I have no idea why it happened

show more ...

take EHOSTDOWN as a temporary failure; change the format of "deferred"
message to be consistent with other messages.

change format of deferred message to be consistent with other messages

take EHOSTDOWN as a temporary failure

fix botch that causes sendmail to core dump when there are large
numbers of requests

fix botch that causes sendmail to core dump when there are large
numbers of requests

add min and max

Detect an internal error that seems to be occuring

Detect an internal error that seems to be occuring

give more useful error messages (including the errno that caused
a temporary failure); reflect these messages out to mailq

give more useful error messages (including the errno that caused
a temporary failure); reflect these messages out to mailq

give more useful error messages (including the errno that caused
a temporary failure); reflect these messages out to mailq

give more useful error messages (including the errno that caused
a temporary failure); reflect these messages out to mailq

give more useful error messages (including the errno that caused
a temporary failure); reflect these messages out to mailq

add e_message field for eventual error message improvement

have canonname pass the address through ruleset four also

have canonname pass the address through ruleset four also

take ENETUNREACH (Network unreachable) as a transient error -- this
probably isn't usually right, but it seem safer in the long run....

take ENETUNREACH (Network unreachable) as a transient error -- this
probably isn't usually right, but it seem safer in the long run....

print "request" instead of "requests" if there is only one request