sendmail problem

Ron Watson resqe1a0 at verizon.net
Wed May 10 16:26:15 UTC 2006



Mike.Kent at indystar.com wrote:
>
> Yes, you are correct, /etc/hosts does seem to be the key but what I've 
> run into is that changing the 127.0.0.1 line by making the hostname 
> fully qualified breaks other things on production servers. I'll 
> probably wind up using define(`confDOMAIN_NAME’, `xx.xx.xx')dnl to set 
> macro $j in sendmail.cf. That effectively bypasses the /etc/hosts issue.
>
>
>
> *Kostas Sfakiotakis <kostassf at cha.forthnet.gr>*
> Sent by: fedora-list-bounces at redhat.com
>
> 05/10/06 08:29 AM
> Please respond to
> kostassf at cha.forthnet.gr; Please respond to
> For users of Fedora Core releases <fedora-list at redhat.com>
>
>
> 	
> To
> 	For users of Fedora Core releases <fedora-list at redhat.com>
> cc
> 	
> Subject
> 	Re: sendmail problem
>
>
>
> 	
>
>
>
>
>
> Ron Watson wrote:
> >
> >
>
>
>
> > and by combining that with what you mentioned here about
> > no_masquerade_local being enabled,
> > perhaps he simply needs to get out of localhost and then all the
> > masquerade stuff will start to
> > take effect. It's been my experience that many of the older, legacy 
> Unix
> > programs are aware
> > that 127.0.0.1 is not a "normal" address, and modify their behavior
> > accordingly.
>
> Well in a sense 127.0.0.1 was never and will never be a "normal address"
> But 127.0.0.1 being the loopack address facilitates many things .
> It's the only network interface that all computers have .
> The DAEMON_OPTIONS i listed before need to refer to a standard point per
> default , that's why there was no reference to  LAN Addresses ( eg
> 10.0.0.0/8 ,
> 192.168.0.0/16,...) . Also if someone deletes the
>
> 127.0.0.1 localhost.localdomain localhost
>
> line  from /etc/hosts then many things will stop working with X Windows
> being one
> of them .
>
>
>
> Just trying to get  to the actual problem, rather than just fix
> symptoms. I was thinking
> > that maybe setting his  hostname correctly may be all he needs. Like 
> I said, I haven't changed
> > the sendmail config on my  system, but at least it knows who it is...
>
>
> I second your opinion on that . I have changed my hostname and i have
> sent mail even with PINE
> through the use of MASQUERADING . Although there stands a chance there
> is also another
> way to do it , i still believe that what you just proposed is the best
> thing to do .
>
>
> Kind Regards.
>   Kostas
>
> -- 
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
By "setting your hostname" I was speaking not of the sendmail config, 
but of the hostname(1) cmd.
For my own opinion, a good Rule of Thumb is: if you *need* to set 
127.0.0.1 to anything besides
localhost and localhost.localdomain, then you're doing something wrong. 
I see others suggesting
aliasing your host name to 127.0.0.1 here on the list, and I cringe 
every time I see it. If your system
is called ini-wf.indystar.com, then do a hostname command to set it to 
that. At the very least your
sendmail should stop trying to call itself localhost.


-- 
=== Ron Watson === rw at compukitty.com ===
  Nisi potestatam dabis, non habebunt.




More information about the fedora-list mailing list