Re: Anyone having dial-up problem with sendmail 8.11.0 ? (FIXED)

2000-09-12 Thread Gerhard Sittig

On Tue, Sep 12, 2000 at 16:19 +0200, Philippe CASIDY wrote:
 
 I am proud to say that I solved my problem. But not proud at
 all of the solution.
 
 During the merge performed by mergemaster it replaces (well, I
 told him to) the entries for the localhost.
 Instead of
 127.0.0.1 localhost greatoak.home
 I had
 127.0.0.1 localhost myname.my.domain
 not exactly this but this is the idea.

It's generally considered a Bad Idea(TM) anyway to have any other
name assigned to 127.x.x.x but localhost.  Just don't do so and
assign a "real" address to your NIF and name your machine
appropriately.  Even if you don't get official IPs from ARIN and
friends, RFC1918 has plenty of them for your toying ...


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" [EMAIL PROTECTED]
-- 
 If you don't understand or are scared by any of the above
 ask your parents or an adult to help you.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Anyone having dial-up problem with sendmail 8.11.0 ? (FIXED)

2000-09-12 Thread Peter Radcliffe

Gerhard Sittig [EMAIL PROTECTED] probably said:
  127.0.0.1 localhost greatoak.home
  I had
  127.0.0.1 localhost myname.my.domain
  not exactly this but this is the idea.
 
 It's generally considered a Bad Idea(TM) anyway to have any other
 name assigned to 127.x.x.x but localhost.  Just don't do so and
 assign a "real" address to your NIF and name your machine
 appropriately.  Even if you don't get official IPs from ARIN and
 friends, RFC1918 has plenty of them for your toying ...

That isn't entirely true.

As long as the first entry on the line is "localhost", everything will
still work as expected.

On any mobile machine I have that may or may not have real (or RFC
private) addresses to use at any given time I put an entry for the
name of the machine on the localhost line so it can resolve it's own
name when not connected. I also dislike fully qualified node names, so
just use the short form.

On a laptop that may connect to someone's internal RFC private network
and use DHCP you can't rely on any address space being legitimate for
a "private" interface or name on a mobile machine.

P.

-- 
pir  [EMAIL PROTECTED][EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message