Red Hat Bugzilla – Bug 76452
remote servers deny email from server with unroutable IP address
Last modified: 2007-04-18 12:47:51 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0rc3) Gecko/20020523 Description of problem: My server has an unroutable address and it uses a router/masquerader to connect to the Internet. When I try to send email to another server, it is rejected with the following error: Relaying denied. IP name possibly forged [10.0.0.2] Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. run mail -v carl@carltm.com Actual Results: Snippets from the output: >>> EHLO computer.carltm.com 250- carltm.com Hello computer.carltm.com [10.0.0.2] (may be forged), pleased to meet you >>> MAIL From:<root@computer.carltm.com> SIZE=53 250 2.1.0 <root@computer.carltm.com>... Sender ok >>> RCPT To:<carl@carltm.com> >>> DATA 550 5.7.1 <carl@carltm.com>... Relaying denied. IP name possibly forged [10.0.0.2] Expected Results: It should have said "Recipient ok" and accepted the message. I have already sent email from another server to verify that the remote server is not misconfigured. Additional info: Is there a way in the sendmail.cf I can either tell it not to send its IP address or give it the address of the router/masquerader?
I've solved the problem. Even though my host name resolves correctly through dns and the reverse lookup gives the right IP address, it is not enought to put the fully qualified domain name in /etc/mail/access. I had to include the IP address in /etc/mail/access. For anyone that's reading this, just include the IP address of your clients(s) in the file /etc/mail/access, run "makemap hash /etc/mail/access < /etc/mail/access", then "service sendmail restart".
Just an after-thought...if I'm logged into a host and sending mail, why is it making the connection through the network interface instead of the loopback device? In other words, why use computer.carltm.com instead of localhost? Early versions of Red Hat didn't have this issue.
I needed to reinstall the OS, and noticed that this problem did not happen. The only difference is that the first time I gave the computer a hostname during the installation. This time I didn't give it a hostname, so it used localhost.localdomain. When the computer came up, it got the correct hostname and IP address from the dhcp server, and when I run hostname it says computer.carltm.com, but now it sees email as coming from localhost.localdomain. It seems odd to me that assigning a hostname during installation would make any difference.
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED state for these products. However, we do want to make sure that nothing important slips through the cracks. If, in fact, these issues are not resolved in a current Fedora Core Release (such as Fedora Core 5), please open a new issues stating so. Thanks.