I wonder if binding to an outgoing IP can be forced on application =
level.
There is an option for sendmail which seems to do exactly this:
-
ClientPortOptions
This option is similar to the DaemonPortOptions but is 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 =
instead of
DaemonPortOptions.
.
DaemonPortOptions
This option can be used to customize the daemon's SMTP service. The =
default
value for the field 'Family' is 'inet' even if DaemonPortOptions is not
defined or value for the 'Family' is not specified in the =
DaemonPortOptions
setup.
Full story see http://docs.hp.com/en/5990-6693/ch01s01.html
-
Davide, is something similar possible for XMail ?
--Harald
> -Urspr=FCngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von CLEMENT Francis
> Gesendet: Dienstag, 19. April 2005 15:57
> An: 'xmail@xmailserver.org'
> Betreff: [xmail] Re: AW: Re: AW: Bind sending IP ?
>=20
>=20
>=20
>=20
> > -Message d'origine-
> > De : /dev/null [mailto:[EMAIL PROTECTED]
> > Envoy=3DE9 : mardi 19 avril 2005 12:00
> > =3DC0 : xmail@xmailserver.org
> > Objet : [xmail] Re: AW: Re: AW: Bind sending IP ?
> >=3D20
> >=3D20
> > Greetings,
> > Actually the only way to get around the AOL thing (and=3D20
> > others) is to be
> > able to *authorativly* answer for the IP to NAME matching. In=3D20
> > other words;
> > having a Name Service (Domain Name System) running that can answer =
=3D
> the
> > querries from AOL and anyone else trying to filter spam from=3D20
> > their mail
> > servers/ Customers. This is the only way to get past the problem you
> > originally mentioned you were having. Your "routing"=3D20
>=20
> Correct
>=20
> > situation stems from
> > the GW (gateway) IP. That is the lowest IP (1 in this case)=3D20
> > *must* be your
> > gateway in almost any situation. It is more of the way networking is
> > designed than an "OS" situation. It is all calculated=3D20
> > mathematically. Net
> > Blocks are created in such a way that you have "NET" and=3D20
> > "BCAST" numbers
> > and you will almost always need to use your Lowest number=3D20
> > "NET" as your
> > gateway. Because the Network Protocol is designed to=3D20
> > communicate in this
> > fashon, so looks there for that type of information. Hope=20
> that helps.
>=20
> False
>=20
> Networks Numbers assignements don't fix the ip to use on the gateway.
> I personnaly use a ip in the 'middle' of our ip block and this is =3D
> correct.
> I too use another 'middle' ip for my smtp server.
> I just have to create a good PTR entry for it to pass aol and other =
=3D
> rdns
> checks ...
> Use of the first or last ip available in a block (except=20
> broadcasts) is =3D
> just
> a 'convention'.
>=20
> Francis
>=20
>=20
>=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]
>=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]
