Mailinglist Archive: opensuse (2234 mails)

[rachel@xxxxxxxxxxxxxxxxxxxx (Rachel Greenham)]

Michael Hasenstein wrote:
> 
> On Wed, 1 Sep 1999, Rachel Greenham wrote:
> 
> > The default installation of sendmail is entirely non-functional, and I
> > have lost several important work-related emails as a result. It's
> > completely intolerant to the server straddling two networks (ie: is a
> > masquerading host for the rest of the house network), and has basically
> > been assuming everyone is a spammer and is rejecting everything. Our
> > attempts at fixing this only made it reject half of everything. We have
> > now deinstalled sendmail completely, I can't afford to lose more emails
> > like this, and we're picking up mail directly from our ISP using POP3.
> 
> Wasn't it you I had sent an email to regarding this very issue? If yes,
> why was there no response? 

If it was me, maybe there was no response because your reply got
rejected by sendmail. :-)

If it wasn't you, ignore this line.

But it probably wasn't me. The above, which I also sent to support@suse
was the first time I reported the error.

> Anyway, put all your _networks_ (you could also use the names, but that
> relies on a good DNS setup (incl. reverse mappings)) in /etc/mail/access
> and run either
>     SuSEconfig
> or
>     makemap hash /etc/mail/access.db </etc/mail/access

Ah, I'll look into that. Sendmail is back on our system, so that someone
else can use fetchmail, but listening on a nonstandard port so it
doesn't grab my mail from my ISP. :-)

> That's all! This process cannot be automated during installation - how are
> we supposed to find out what IPs are allowed? (CLient) IPs in
> /etc/mail/access are allowed to send any mail anywhere, mail for domains
> defined as local domains are accepted from anyone.

I think it could be one of the supplied configuration templates - we'd
be prepared to type in our own IP's and domains, it was just knowing
where to do so... Our setup is, I would have thought, a sensible one for
any installation where there's a private network connected to the
internet through a masquerading host, which is the way to go if you've
only got one real-world IP address.

> > Even more important: We upgraded our network card to a PCI NE2K clone to
> > a 3Com 3c905B-TX. Since that time, whenever we run YaST the machine
> > crashes completely. We've been able to set up and start the network card
> > manually and it all works fine, including coming up from a bootup, but
> > even with the network configuration being correct, now starting YaST
> > still causes a complete crash. Every time. As you can imagine, this is
> > extremely serious.
> 
> What about logfiles, e.g. /var/adm/messages?

I'll have a look. But I'm not hopeful: the machine stiffed, the write
cache was probably never flushed.

The crashing YaST problem is by far the more serious as far as I'm
concerned. I'm hoping we don't have to reinstall the whole machine to
fix it. By the way, a reminder, we *are* running the latest version of
YaST. :-) We're also running the standard SuSE kernel, unmodified from
installation.

Hmm. /var/adm/messages doesn't exist as a file or directory. Looking
further afield...

OK, there was nothing from yast in /var/log/messages - it just shows a
login and then a few minutes later the machine being powered up.
However, I noticed in /var/log/warn that before each crash was an error
from the ide-floppy module (we have an internal IDE ZIP drive which
we've so far made no attempt to configure since upgrading to 6.2, but
the device is being detected on startup):

ide-floppy: possible ide-floppy.c bug - Two request sense in serial were
issued

Following a hunch, we tried "insmod ide-floppy" and now have a crashed
computer! (Lucky I'm typing on my laptop.)

Now we've rebooted and we deleted ide-floppy.o completely, and now
everything is fine. yast is happy.

It's still a mystery as to why it only started happening after we
installed the new network card, it worked fine with the old one.


-- 
Rachel

--    
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx             
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/