|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: bind to specific interface...
From: Wietse Venema (wietse
porcupine.org)Date: Mon Feb 14 2000 - 10:24:15 CST
- Next message: Brad Knowles: "Re: Queue only + cache flushing?"
- Previous message: Wietse Venema: "Re: virtual table and masquerading"
- In reply to: Jürgen Fluk: "Re: bind to specific interface..."
- Next in thread: Jürgen Fluk: "Re: bind to specific interface..."
- Reply: Wietse Venema: "Re: bind to specific interface..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[J_rgen] Fluk:
> > One Postfix can receive mail for any number of IP addresses.
> >
> > > I would like to set
> > > inet_interfaces = <newIP> <oldIP>
> > > so it listens to both (does work) and would send out on any (the first)
> > > of them (does not work as both IPs are only aliases and smtp_connect
> > > does not bind).
> >
> > Why are you concerned about the source IP address used for sending
> > mail?
>
> Because that`s the address/name which shows up in the "Received:" headers
> and the one
> which one of the outside server will check for detecting relay access.
> Currently postfix uses the machine's "native" address (in a 192.168.
> network) and
> connections appear coming from my MASQuerading gateway. This is not what I
> want.
What TCP/IP stack binds to the wrong interface address when making
connections over the network?
Wietse
- Next message: Brad Knowles: "Re: Queue only + cache flushing?"
- Previous message: Wietse Venema: "Re: virtual table and masquerading"
- In reply to: Jürgen Fluk: "Re: bind to specific interface..."
- Next in thread: Jürgen Fluk: "Re: bind to specific interface..."
- Reply: Wietse Venema: "Re: bind to specific interface..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]