×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi David,
In sockets programming, that message "Transport endpoint is not
connected" refers to the act of trying to read/write to a socket that
hasn't yet been connected. The mnemonic for it is ENOTCONN.
I haven't seen it in conjunction with Sendmail, but I can only guess
that there's a Milter (like a spam filter, virus scanner or similar
tool) that's connected to the Sendmail server via an AF_UNIX socket, and
that Milter has gone down.
Are you getting this error on your own Sendmail server, or is it being
reported to you from a remote server? I'm guessing your MTA is
connecting to a remote MTA, and trying to send the message to the remote
MTA. The remote MTA is trying to run your message through some sort of
milter, but the milter is failing with that error message, so it sends
you back a "4xx x.x.x Transport endpoint is not connected." and your
log file therefore contains "Deferred: Transport endpoint is not connected"
But that's purely an educated guess.
David Gibbs wrote:
Anyone know what the sendmail status "Deferred: Transport endpoint is not connected" means?
I'm getting this a lot recently ... but I can't figure out exactly why.
When I manually flush the mail queue ... the messages that are in this state send correctly.
david
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
