Yes and no. If the mailserver gets a message that is for a local user then the message should never get 'sent out' as it will be put straight into the pop 3 account. So it should never need to connect to itself.
So lets say the mail server is on 192.168.0.2. If it tries to connect to 192.168.0.2 it will work. If it tries to connect to 63.215.241.205 which is where your domain name points to, it probably wont work (i have no idea about the router you have, but i would guess not). Similarly outlook running on a machine on the internal network wont be able to connect to the name (mail.neticu.com). Outlook on external computers will be able to connect to mail.neticu.com provided you have port-forwarding (or whatever your router calls it) setup on the router. In order to get round this, set the pop3/smtp servers for the outlook account to 192.168.0.2 for computers on your network. Hope that helps explain the problem i think you're experiencing. Two other things i noticed were that you dont seem to have any mx records set up (unless they arnt listed in the portion of the no-ip settings you sent). You also have a lot of dns settings. You probably dont need all of these. As most routers act as dns servers, you can probably just use 192.168.0.1 as a single dns server. Daniel. -----Original Message----- From: Anonymous Professional [mailto:[EMAIL PROTECTED] Sent: 21 October 2004 17:55 To: [EMAIL PROTECTED] Subject: RE: James Usability Ques. Can you elaborate on a workaround configuration for this routing IP dilemma? Can mailserver's send mail to themselves inside a LAN? Find the music you love on MSN Music. Start downloading now! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
