But when I send an email from gmail.com to the domain I created in Postfix using ISP Config, I can receive the email successfully.

It only seems to be a problem while sending the email out of my LAN network.

I've an ADSL router and it is configured to allow connections on the following ports:

80,81,443,pop3,pop3s,imap,imaps

I did not install Firewall that comes in FC4 and I disabled SELINUX just as told to in Falko's instructions.

Is there anything else I need to do with regards to postconf configuration which would help my postfix send emails from AUthorised users like the ones created of ISP Config to send emails to others like @hotmail.com, yahoo.com, gmail.com etc etc.,

And logged into my hotmail as well as gmail to check the emails and no luck

I modified the /etc/resolv.conf to the nameservers of my DNS provider zoneedit.com and then restarted named and network and then tried sending emails to @hotmail and @gmail and still no luck

I again modified the /etc/resolv.conf to the DNS of my ISP (Which i called and got from my ISP E7even.com) and then restarted named and network. And then tried sending emails to @hotmail.com as well as to @gmail.com but still no luck.

I can see that from the logs it looks like it has correctly detected @hotmail.com as well as @gmail.com but I could not understand why i still did not receive any emails into both hotmail and gmail. Or log does not show of any trace of bounce back (Mailerdaemon) message.

Any help is greatly appreciated.

Also if you know how I can suppress this following error shown in the above log /var/log/maillog

And logged into my hotmail as well as gmail to check the emails and no luck

I modified the /etc/resolv.conf to the nameservers of my DNS provider zoneedit.com and then restarted named and network and then tried sending emails to @hotmail and @gmail and still no luck

I again modified the /etc/resolv.conf to the DNS of my ISP (Which i called and got from my ISP E7even.com) and then restarted named and network. And then tried sending emails to @hotmail.com as well as to @gmail.com but still no luck.

I can see that from the logs it looks like it has correctly detected @hotmail.com as well as @gmail.com but I could not understand why i still did not receive any emails into both hotmail and gmail. Or log does not show of any trace of bounce back (Mailerdaemon) message.

Any help is greatly appreciated.

Click to expand...

Your domain name resolution is now ok. The mails seem to have been sent, but I can think of 2 reasons why they didn't arrive in your mailboxes:

1) You're sending from your home network, so you most probably have a dynamic IP address. Most freemail providers like Gmail and Hotmail block emails from dynamic IP addresses.
2) You're sending from the domain example.com, and it's possible that Gmail and Hotmail see that you aren't example.com and therefore block your emails.

nandhu said:

Also if you know how I can suppress this following error shown in the above log /var/log/maillog

Your domain name resolution is now ok. The mails seem to have been sent, but I can think of 2 reasons why they didn't arrive in your mailboxes:

1) You're sending from your home network, so you most probably have a dynamic IP address. Most freemail providers like Gmail and Hotmail block emails from dynamic IP addresses.
2) You're sending from the domain example.com, and it's possible that Gmail and Hotmail see that you aren't example.com and therefore block your emails.

Try to

Code:

chmod 1777 /var/spool/mail

Click to expand...

Hi Falko,

1) About 6 months before I use to have qmailtoaster installed on my Redhat 9 and then I could send emails to just about any domain. I do not know whether recently gmail or hotmail have blocked messages coming from dynamic ip address!!!

3) I've tried chmod 1777 /var/spool/mail but I read in redhat bug tracking that it is an unsecure lock mechanism that Iumap is using and that they do not recommend it. so they are not accepting it as a bug but said try and fix your MTA. ??!!

Then I'd switch off the firewall and re-configure it step for step until the domain resolving doesn't work anymore. If you are at this step, then you know it was the last firewall rule you added. Remove that rule, and you should be fine.