On Tue, Nov 16, 2010 at 01:58:06PM -0500, Victor Duchovni wrote: > On Tue, Nov 16, 2010 at 06:50:02PM +0000, Chris G wrote: > > > So where is there a system sending this mail which appears to be > > 84.45.228.40? > > > > From what I can see in the logs the mail isn't going out to the outside > > world and coming back in, it's just going from 192.168.1.2 to 192.168.1.4. > > The best way forward is to accept that reality trumps theory, and that > clearly the traffic is addressed exactly as logged. > > You then need to look on the sending client, which almost certainly is > sending to the external IP address of the server, not the internal. This > likely hits the NAT box, which helpfully maps the destination address > to the server's internal address, and the source address of the client > to the external address of the NAT. This is by far the simplest and > most likely explanation. > > So now you need to fix the client's routing logic to not send to the > external IP, likely obtained from external DNS, and use a transport > table entry or relayhost that resolves to a local IP. > > For that, you'll need to know what software is doing all the work > on the client. > Er, it's Postfix isn't it? :-) Or have I misunderstood completely (quite likely!).
When I 'telnet mws.zbmc.eu 25' from the client it does connect to mws.zbmc.eu (192.168.1.4) and mws.zbmc.eu reports the connection to be coming from 192.168.1.2 which is dps.zbmc.eu. -- Chris Green
