I am guessing that the following is happening - Your computers are assigned private IP addresses by DHCP. (Private addresses can look like 10.x.x.x, 172.x.x.x, or 192.168.x.x.) These addresses are not valid on the Internet. In order for these computers to use the Internet, their network traffic is translated to look like it's coming from a valid address on the Internet by a Network Address Translator (NAT). The address they are being translated to is your static address.
Your James server is on the other side of the NAT. Since all of your computers' network traffic is being changed to look like it's coming from this one address, that's the way it appears to your James server. That's why telling it that anything from this address can be routed to external e-mail addresses works. The DNS and/or the domain the e-mail appears to come from has nothing to do with this. It is based purely on the address of the client connecting to the server, and can't be spoofed by appearing to come from an e-mail address in your domain. BTW - If you've removed "127.0.0.1" from the list of valid IP addresses, you'll want to put it back. James will need this for e-mail forwarding rules, etc. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
