Operating System - HP-UX
1833885 Members
1853 Online
110063 Solutions
New Discussion

when telneting to sendmail I get...

 
David McDowell
New Member

when telneting to sendmail I get...

When I telnet to sendmail on port 25, my response is as follows: 220 localhost.localdomain ESMTP Sendmail 8.11.6/8.11.6; Tue, 21 Jan 2003 10:49:1
6 -0500

I cannot figure out why I continue to get localhost.localdomain instead of host.domain.com. I also get localhost.localdomain as the HELO in my email headers. Any ideas? I've racked my brain on this one. I have DNS setup for this domain and an MX record. Sending and recieving of emails works perfectly between this sendmail and an exchange server which is in another domain, both internal to my network.
Thanks in advance!!
~~ "Kindness in another's trouble, courage in your own." ~~ Princess Diana
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: when telneting to sendmail I get...

in /etc/mail/sendmail.cf

Change

# #Dj$w.Foo.COM #
# to #
# Dj$w.hp.com #
#

where hp.com is your actual domain name.

or DJhp.com

If $w is being set as localhost

The real solution is to change you hostname to fully qualified domainname.

/etc/rc.config.d/netconf

change hostname to hostname.hp.com

Where hp.com is your genuine domain name.

Good Luck.

P
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
David McDowell
New Member

Re: when telneting to sendmail I get...

I have been taught not to edit sendmail.cf directly, that it is best to edit sendmail.mc and use m4 to apply changes to the .cf file. Do you know how I can avoid editing the .cf directly? Thanks.
~~ "Kindness in another's trouble, courage in your own." ~~ Princess Diana
David McDowell
New Member

Re: when telneting to sendmail I get...

OK, setting hostname to FQDN actually solved that part of the issue! When I telnet to port 25, I now get: 220 host.domain.com ESMTP Sendmail 8.11.6/8.11.6; Tue, 21 Jan 2003 11:31:
24 -0500
Thanks!

Now to continue that, in my latest email header, when using PINE on the local server, I get this:

Microsoft Mail Internet Headers Version 2.0
Received: from host.domain.com ([12.1.244.148]) by host1.domain2.com with Microsoft SMTPSVC(5.0.2195.4905);
Tue, 21 Jan 2003 11:29:08 -0500
Received: from localhost (user@localhost)
by user.domain.com (8.11.6/8.11.6) with ESMTP id h0LGS0i01052;
Tue, 21 Jan 2003 11:28:00 -0500
Date: Tue, 21 Jan 2003 11:28:00 -0500 (EST)
From: user@domain.com
To: user1@domain2.com
Subject: test1 headers for correct helo
Message-ID:
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Return-Path: user@domain.com
X-OriginalArrivalTime: 21 Jan 2003 16:29:08.0926 (UTC) FILETIME=[3925ADE0:01C2C16A]

Specifically my question is the line:
Received: from localhost (user@localhost)

Is this a PINE configuration or am I still missing something in my sendmail config?

Thanks! Making great progress with this forum, wish I would have joined sooner!

David
~~ "Kindness in another's trouble, courage in your own." ~~ Princess Diana
W.C. Epperson
Trusted Contributor

Re: when telneting to sendmail I get...

The "Received: from localhost" header is normal for an MUA (mail user agent, e.g. PINE) running on the same machine as the MTA (mail transport agent, e.g. sendmail). The MUA connects to the MTA via the 127.0.0.1 psuedo-interface, and the headers are written accordingly. On most DNS servers, there's an inverse arpa zone set up for network 127.0.0 in /etc/named.boot:
directory /etc/named.data ; running directory for named

primary 0.0.127.IN-ADDR.ARPA db.127.0.0And a zone entry mapping 127.0.0.1 to "localhost":

You could change the name "localhost" by altering the contents of the db.127 PTR record, but that would be atypical.
"I have great faith in fools; self-confidence, my friends call it." --Poe
Christopher Caldwell
Honored Contributor

Re: when telneting to sendmail I get...

By default, when sendmail starts, stock sendmail (no mods to HP's sendmail.cf) probes network interfaces.

The first IP that's found on the first interface gets looked up according to the settings in resolv.conf. The result becomes the setting of the $j macro.

The rest of the IPs on the interfaces are looked up and become class w. (We'll accept mail for domains in class w).

If sendmail can't resolve your host name, set the $j macro in sendmail.cf (Dj$w.Foo.COM)

If you don't want sendmail looking for interfaces that are available, look at DaemonPort Options and DontProbeInterfaces.

BTW, you'll want a correctly functioning DNS to take advantage of the anti-spam features of sendmail.