It's a default setting by the server's hoster in order to assign = different addresses to different domains.
--Harald > -----Urspr=FCngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im Auftrag von Bill Healy > Gesendet: Mittwoch, 20. April 2005 15:45 > An: 'xmail@xmailserver.org' > Betreff: [xmail] Re: AW: Re: AW: Bind sending IP ? >=20 >=20 > What is your reason for having multiple IP addresses on one NIC card? >=20 > Bill >=20 >=20 > >---------- > >From: Harald Schneider[SMTP:[EMAIL PROTECTED] > >Sent: Tuesday, April 19, 2005 2:13 PM > >To: xmail@xmailserver.org > >Subject: [xmail] AW: Re: AW: Bind sending IP ? > > > >I see .. thanks for clarification! > > > >--Harald > > > >> -----Urspr=3DFCngliche Nachricht----- > >> Von: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] Im Auftrag von=20 > S=3DF6nke Ruempler > >> Gesendet: Dienstag, 19. April 2005 22:59 > >> An: xmail@xmailserver.org > >> Betreff: [xmail] Re: AW: Bind sending IP ? > >>=3D20 > >>=3D20 > >> Hi Harald, > >>=3D20 > >> On Tuesday, April 19, 2005 7:17 PM [GMT+1=3D3DCET], > >> Harald Schneider <[EMAIL PROTECTED]> wrote: > >>=3D20 > >> > I wonder if binding to an outgoing IP can be forced on=20 > application =3D > >=3D3D > >> > level. > >> > There is an option for sendmail which seems to do exactly this: > >> > > >> > --------- > >> > ClientPortOptions > >> > > >> > This option is similar to the DaemonPortOptions but is=3D20 > >> meant only for > >> > __outgoing__ connections. > >> > > >> > The steps to set this option are same as those for the > >> > DaemonPortOptions except that the option name ClientPortOptions > >> > should be specified =3D3D instead of > >> > DaemonPortOptions. > >> ^^^^ > >>=3D20 > >> It's the outgoing Ports, _NOT_ the IP! > >>=3D20 > >> I know that on linux the systems handles this with it's=3D20 > >> routing table. An=3D20 > >> application cannot bind to an outgoing IP! > >>=3D20 > >> Don't believe route command - just do a: > >>=3D20 > >> # ip route > >>=3D20 > >> and additionally a: > >>=3D20 > >> # ip addr > >>=3D20 > >> and you can see exactly what is going on - here example of my=3D20 > >> local nets: > >>=3D20 > >> # ip route > >> 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.1 > >> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.1 > >> ^^^^^^^^^^^^^^^ > >>=3D20 > >> From manpage: > >>=3D20 > >>=3D20 > >> src ADDRESS > >> the source address to prefer when sending to=3D20 > >> the destinations=3D20 > >> covered by the route prefix. > >>=3D20 > >>=3D20 > >> - > >> To unsubscribe from this list: send the line "unsubscribe xmail" in > >> the body of a message to [EMAIL PROTECTED] > >> For general help: send the line "help" in the body of a message to > >> [EMAIL PROTECTED] > >>=3D20 > > > >- > >To unsubscribe from this list: send the line "unsubscribe xmail" in > >the body of a message to [EMAIL PROTECTED] > >For general help: send the line "help" in the body of a message to > >[EMAIL PROTECTED] > > > > > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] >=20 - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
