On Friday 25 December 2009, Rony wrote:
Arun Khan wrote:
On Friday 25 December 2009, Linux wrote:
For other problem, I think you will need a machine with valid name, which should have forward and reverse DNS entries.
+1. I wanted to jump in when Rony mentioned there is no domain name for this client.
@Rony, you need a valid domain name on the 'Net and a sub-domain served by an internal DNS server that resolves A and PTR records.
I generally do this as "intra.example.com" for the internal LAN sub domain.
The customer has his own website and it is also enabled with POP/SMTP. Since that smtp needs to be authenticated with the email_id as username and a password, I thought of using that as credentials to relay messages to that server to then forward them to the world. Do I still need a domain setting? How does Thunderbird or Outlook Express forward mails from machines with only a hostname?
IMO, the proper way to do it:
1. define an LAN sub domain e.g. intra.example.com where example.com is your external domain.
2. define DNS A/PTR tables, yes this means running DNS for your sub domain.
3. give each host and meaningful name e.g. main- honcho.intra.example.com, email.intra.example.com (smtp/pop3/imap server)
4. All your email clients would point to your internal smtp server "email.intra.example.com" (postfix) for outgoing email.
5. Mail filtering would be done by postfix rules.