On Tue, Nov 16, 2010 at 01:13:48PM -0500, Victor Duchovni wrote: > On Tue, Nov 16, 2010 at 06:06:27PM +0000, Chris G wrote: > > > On Tue, Nov 16, 2010 at 12:34:38PM -0500, Wietse Venema wrote: > > > Chris G: > > > > Yes, I realise that "It connects from 84.45.228.40" but I can find no > > > > reason at all *why* the postfix server process on mws.zbmc.eu thinks > > > > that the connection is from 84.45.228.40. > > > > > > Because the operating system kernel said so when Postfix asked. > > > > Is the issue at the client end or the server end? > > Neither, there is no issue. The connection came from the reported IP > address. The issue is almost certainly just confusion on your part. > Even if I am confused I still want to fix the problem. Either one of my systems is reporting itself as 84.45.228.40 or another one thinks it is receiving mail from that IP address. I want to send mail locally on my LAN with any involvement of 84.45.228.40.
> > I.e. is it the postfix/sendmail > > The Postfix "sendmail" utility does not engage in any network > communications. It just adds a file to the Postfix "maildrop" queue. > > It sounds like you have both Postfix and Sendmail on the same systems, > and perhaps confused about which MTA is handling which mail. > When I say 'sendmail' I just mean the postfix executable of that name which is used by mutt (amoung others) to send mail from the system. I have enver had 'real' sendmail installed on these systems. > > The question is how do I overcome it, what system calls does Postfix use > > to get the hostname and why do they differ from what I see when I issue > > the command 'hostname'? > > Wrong question. The right question is: > > - Now that I know that the traffic is coming from the reported > IP address, how do I identify the sending client and either > allow it to send from that IP or reconfigure it to use a different > IP address. > I'm pretty sure I know the client, it's dps.zbmc.eu, and I want to "reconfigure it to use a different IP address.". I think that's the question I'm looking for an answer to. -- Chris Green
