Juergen - I'll try it again in hosts.allow using your suggestions. My mind might be playing tricks on me, because I can't find any of the log entries. I think now the error messages I mentioned were from tcpdcheck on the command line, not log messages from sendmail. Although I'd be surprised if tcpdcheck could barf on /etc/hosts.* and sendmail wouldn't, it's worth a try. But it'll have to wait a bit while I try to earn a living. ;-) It's interesting that you mention ipv6, which this sendmail is also compiled with (different from SuSE 6.3). I haven't had a chance to look at my kernel modules setup yet, but noticed that the ipv6 module failed to load. I just commented it out of /etc/modules.conf because I don't need it. But there were also some error messages (I think again from tcpdcheck) that looked like it was trying to use ipv6. I know *nothing* about ipv6, but when I put a bad IP address in hosts.allow the error message looked like it was interpreting it as an ipv6 number. Sorry I can't be more specific, but will try to duplicate it later. I'm just wondering if there's something (e.g. resolver, tcp wrappers) that's defaulting to ipv6. That doesn't appear to be a primary part of my problems, but something doesn't seem quite right. I appreciate your time and will get back when I have more info. BTW, both sendmail's are stock from the SuSE cd. The old one (from SuSE 6.3) was sendmail-8.9.3-42, and the new one (from SuSE 7.0) is sendmail-8.10.2-24. I tried rebuilding sendmail on my own a while back, but had a problem with the installation and never had a chance to chase it down. That' s one of the reasons I went for the 7.0 upgrade, but will build 8.11 myself if necessary. I'll check the web/ftp sites again for more info. - Don On 27 Sep, juergen.braukmann@ruhr-west.de wrote:
D E Hammond wrote:
Hi,
this sounds odd. I cannot be of much more help, since I do not know more myself. I ran into trouble with sendmail from 7.0, fetchmail would d/l it, sendmail refused and literally teared my mail to pices. Fetchmail deleted on the server, so I lost a few messages. Tried sendmail from 6.4 and everything worked. Tried (without success) SuSE support, hinting me to a updated version of sendmail since the version won't work with IPV6. Then I learned to telnet to port 25 for a chat with the daemon. That worked again with the old sendmail, but not with the new. Then one idea struck: I disabled host.allow / deny and it worked. I tried to add the sendmail line to hosts.allow and it still worked. ;-) My complete hosts.allow looks like:
in.ftpd: LOCAL, .forty.two in.telnetd: LOCAL, .forty.two rplayd: LOCAL, .forty.two portmap: LOCAL, .forty.two in.rshd: LOCAL, .forty.two in.talkd: LOCAL, .forty.two popper: LOCAL, .forty.two sendmail: LOCAL, .forty.two rpc.nfsd: LOCAL, .forty.two rpc.mountd: LOCAL, .forty.two
apart from portmap there is nothing to obvious. Did you restart sendmail afterwards??
from my inetd.conf: # nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode # smtp stream tcp nowait root /usr/sbin/sendmail sendmail -bs # printer stream tcp nowait root /usr/sbin/tcpd /usr/bin/lpd -i # it's not active...
Which version of sendmail do you use? might be worth to get the update from the SuSE ftp server, since your problem might also be linked to the IPV6 issue.
root@marvin:/usr/local/bin > rpm -qi sendmail Name : sendmail Relocations: (not relocateable) Version : 8.11.0 Vendor: SuSE GmbH, Nuernberg, Germany Release : 0 Build Date: Wed Sep 6 01:17:17 2000 Install date: Fri Sep 22 11:16:40 2000 Build Host: snell.suse.de Group : Networking Source RPM: sendmail-8.11.0-0.src.rpm Size : 2278057 License: 1983 Eric P. Allman Packager : feedback@suse.de Summary : BSD sendmail Description : The "Unix System Administration Handbook" calls sendmail "The most complex and complete mail delivery system in common use..." . Ready-made configuration files are included for systems connected by TCP/IP (with or without a name server) and for systems using UUCP. 'procmail' is included as a local mail agent.
Authors: -------- Eric Allman
SuSE series: n root@marvin:/usr/local/bin >
Otherwise I am now clueless...
Juergen
On 26 Sep, juergen.braukmann@ruhr-west.de wrote:
[...] I discovered this later last week. Same seems to be true with the nfs server. I added the following lines to hosts.allow to find my peace:
sendmail: LOCAL, .forty.two rpc.nfsd: LOCAL, .forty.two rpc.mountd: LOCAL, .forty.two
As I just discovered I still got this problem with nfsd, since there was an "ALL:ALL" statement. Never the less, it works for sendmail. (Try to telnet to port 25 on localhost for verification)
Well I tried something like this and it complained that there was no sendmail entry in inetd.conf. It's commented out because sendmail runs as daemon, not from inetd. If it's uncommented in inetd.conf, it complains that it can't bind to the port because it's already in use (obviously). There must be a way to do this because, unless I'm missing something, what would be the point of compiling sendmail with the tcp wrappers library if the only way it could be used effectively is by running it through inetd? If it's running through inetd, rather than as daemon, sendmail wouldn't need to be compiled with the library, no?
But if the only way to get mail accepted is to use ALL as the service list, that's not much of a feature. What am I missing?
- Don
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq