Charlie Whisker wrote:
>
> I am familiar with both unix and solaris systems.
> I can appreciate that you wrote a piece of software
> but where do you get off insulting people or is that
> just one of the benefits of having your own mailing
> list.

If you fell you're "insulted", then this is bad for
*you*. Many people out there will say you just the
same as Wietse said about your "unfamiliarity" with
solaris, based on question(s) you ask. Yes, first
one (that started this thread) wasn't trivial, but
second, about what to do with non-working nslookup,
is simple for almost any who has real experience
with a system -- that question should even not
exist at all for such a people, as them knows what
to do. Well, not that strong, but still -- truss
(or strace or whatether) is a *great* tool for
debugging such problems. Your problem has nothing
to do with postfix -- your system not working
properly (besides your claims that you knows it),
but still Wietse provided useful points to solve
it, but you said he "insulted" you. And note that
Wietse NOT said "you're unfamiliar", he said "you
appear to be unfamiliar" (appear to he at least, and
for me you're unfamiliar too). This wasn't an
"insultion", that was a statement based on context.
You're incorrect in the above statement. And again,
I personally want no "insultions" for someone else --
I just look to a situation and see, and made conclusions...

Regards,
 Michael.

> --- Wietse Venema <wietseporcupine.org> wrote:
> > nslookup depends on *OTHER* files on the system in
> > order to work.
> > I bet that someone broke some file permissions.
> >
> > "truss nslookup" will show what files it wants to
> > open. However,
> > you appear to be unfamiliar with UNIX systems. The
> > truss output
> > will show a lot of file open attempts that fail even
> > on a normally
> > configured system.
> >
> > I suggest that you find someone who is more familiar
> > with Solaris.
> >
> > Wietse
> >
> > Charlie Whisker:
> > > Interestingly enough after a "su - postfix", if I
> > try
> > > to run nslookup as user postfix nslookup will hang
> > > with the following:
> > >
> > > $ nslookup
> > > *** Can't find server name for address 127.0.0.1:
> > No
> > > response from server
> > > *** Default servers are not available
> > >
> > > So the unprivlidged user postfix can acess
> > > /usr/sbin/nslookup since the attempt to run this
> > > command didn't produce a "file not found" error.
> > >
> > > Any ideas?
> > > Paul
> > >
> > >
> > > --- Wietse Venema <wietseporcupine.org> wrote:
> > > > Try your DNS tests as a REALLY unprivileged
> > user.
> > > >
> > > > The Postfix SMTP client runs as user postfix and
> > > > therefore does
> > > > not have the all-powerful privileges that you
> > may
> > > > have.
> > > >
> > > > Wietse
> > > >
> > > > Charlie Whisker:
> > > > > Hello, I have just installed
> > > > > Postfix(postfix-20010228-pl03) on solaris 7.
> > The
> > > > > environment is not chrooted. My DNS server
> > works
> > > > fine
> > > > > with dig, host etc. Yet I have mail stuck in
> > the
> > > > > deferred queue. Running mailq shows many of
> > these
> > > > > entries:
> > > > >
> > > > > (Name service error for sonymusic.com: Host
> > not
> > > > found,
> > > > > try again)
> > > > >
> > > > >
> > > > > Now I can look up the MX records for the above
> > > > domain
> > > > > just fine from this machine. I can do a:
> > > > >
> > > > > I looked at the FAQ and it only makes mention
> > of
> > > > this
> > > > > problem in chroot environments that are
> > missing
> > > > files.
> > > > > This is not the case here though. Can someone
> > shed
> > > > > some light on this and possible causes.
> > > > > Thanks
> > > > > Paul
> > > > >
> > > > >
[]
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]