Sendmail -- What Did I Forget?
I've done a clean install of Slackware 64-bit 14.0 (fully patched) on a laptop. On all my systems, sendmail "just works;" i.e., I can
Code:
mailx -s "This is a Test Message" trona What the heck have I forgotten to turn on? /etc/rc.d looks like Code:
./ rc.autofs rc.inet1* rc.modules-3.2.45* rc.sendmail* rc.yp |
Check the log files of mail. Should be /var/log/mail.log. ls /var/log/mail.*. There should be four files.
|
A check of /var/log/maillog shows
Code:
Jul 3 10:29:56 pita sm-mta[16481]: r61KCwbf006996: to=<trona@pita.com>, delay=1+18:16:39, xdelay=00:00:00, mailer=esmtp, pri=9300454, relay=pita.com.com., dsn=4.0.0, stat=Deferred: Connection refused by pita.com.com. pita's entry in /etc/hosts is Code:
192.168.1.30 pita.com pita Cripes. |
I dunno much about sendmail but maybe it needs a FQDN? With a dot at the end. Okay lets check the hostnames and alike
PHP Code:
|
It looks normal to me:
Code:
-s, --short short host name Code:
for opt in s a i f d y So, I dunno. |
Hi tronayne,
I have a similar problem to yours so I think what I have found so far may help you pita.com.com is probably coming from $w macros, it is assigned at sendmail start from the gethostname() function to get the (local)host name You can try to run sendmail -bt -d8.8 to see how it is resolving the DNS: Code:
sendmail -bt -d8.8 I found the following book very helpful to understand how sendmail works: http://www.diablotin.com/librairie/n...il/ch31_10.htm adn the DNS stuff in: http://docstore.mik.ua/orelly/networ...il/ch21_02.htm Now, the problem I found is that when I send a mail to user [at] mydomain.com it tries to deliver to mydomain.com instead of the MX record which points to mail.mydomain.com I think it's the DNS setup which unfortunately is in another host so I cannot mess with that I don't know if something similar is happening to you. HTH |
After reading the maillog output again I see that the relay option is pita.com.com. Which concludes to me that spatior has some point with the dns settings. I can't check them from outside. Dont get a MX only massive NS records.
A short search for the $w macro states that it only gets assign on version 8. Not prior to this. dunno if your other machine have another version. Doubt it if all of them are slack 14. |
Thanks for the input -- here's the output of
Code:
sendmail -bt -d8.8 All my machines are fixed-IP, with identical /etc/hosts files; i.e., Code:
# For loopbacking. Code:
cat /etc/resolv.conf I'm not doing mailx trona@pita.com (which goes out to the world), I simply use mailx trona, which should be resolved (and is on every box but this one) to the local machine. And it ain't. WFT. Thanks for the input. |
Dunno if the output looks good. But I think that sendmail does not use your FQDN so it puts your domain (search in /etc/resolv.conf) at the end of the hostname. Coming from a little howto /etc/mail/genericsdomain should hold your FQDN. Do you have that one? What does it shown on (all) the machine(s)?
|
Nother thing. How did you configure your sendmail?
|
Have you updated the sendmail.cf or sendmail.mc file?
http://www.cyberciti.biz/tips/sendma...ions-from.html http://www.electrictoolbox.com/artic...ction-refused/ |
Actually, I never configure any of the sendmail files; the norm is that it "just works" on the individual server and with a mailto link from an internal web page. No kidding, I don't configure anything on any of these boxes.
So, maybe I'll look at the configuration files and see what's what but dang if I can figure out where this additional .com is coming from given that all four machines are identical Slackware 14.0 installations (other than 32-bit versus 64-bit) with all patches applied. Tiz a puzzlement. |
Hm that truly is weired. Maybe some packages did fiddle with your hosts config file or sendmail. Maybe a diff on the packages might show.
Also 32vs64 does not make a difference. But the one giving headache is the only 64bit? |
Yeah, I know that 32-bit and 64-bit are pretty much identical -- the one being a pain happens to be a 64-bit lap top (which is identical to a 64-bit desk top). There's not enough on it to make a difference (so I can just scrap it and reload Slackware and see what happens).
I mean I haven't got a clue -- never seen this before and these guys are kept identical with configuration files and patches, including the recent kernel patch on all. The two 32-bit data base servers have old Radeon cards but the 64-bit boxes have Intel graphics (and how that could make any difference I most certainly do not know). I think I'll just do a clean install and see what that does (if anything) to make a difference. It's just goofy. |
Hm. Does slackware has some options for labtop installs? I know in Debian theres an option for that. Also its more for energy saving and alike but maybe theres a silent com(on) give me more power. Just kidding. Long time ago I lost track of slack.
Maybe you can just copy the files of the desktop over to the labtop? At least that rules out any configurations. Also you would need to just host.conf and alike. Grub if installed also if you dont use the same uuid for the partitions. Could you backup the /etc directory and diff it after the installation? Maybe this will shed some light. |
All times are GMT -5. The time now is 03:48 AM. |