Comcast and mail header errors?

[Kevin D. Clark]

Cole Tuininga writes:

> On Thu, 2006-03-23 at 08:12 -0500, Ben Scott wrote:
>> On 3/23/06, Cole Tuininga <colet at code-energy.com> wrote:
>> > The problem is that the application has no control which interface it
>> > uses when opening a socket to a remote system.
>> 
>> "man bind(2)"
>
> Right - this is for *listening* sockets.  Sending an email out requires
> the server to make a connection to a remote server - it doesn't use that
> same socket.

The use of bind() is not limited to passive sockets, i.e. sockets that
have been modified with listen().

bind() can also be used on active sockets, sockets that you might want
to use to initiate communications with some other server.


I'm not even certain that I am disagreeing with Cole here.  If
sendmail has a setting to allow the admin to cause it to bind to a
certain protocol address when it initiates connections to remote
servers, then bind() is the workhorse here.  But Cole might be
claiming that the setting that is being discussed here doesn't do
this.

Regards,

--kevin
-- 
GnuPG ID: B280F24E                     And the madness of the crowd
alumni.unh.edu!kdc                     Is an epileptic fit
                                       -- Tom Waits