Undocumented change, it seems: sendmail in Slackware 9.1 was built
with tcp_wrappers, unlike previous releases. This means that if you
have "ALL: ALL" in /etc/hosts.deny and specifically allow services
in /etc/hosts.allow, after upgrading to Slackware 9.0 you may find
(like me) that sendmail does not work, and logs messages about
tcpwrappers rejections. You need to add a line like "sendmail: ALL"
to /etc/hosts.allow to get it working.

On Thu, 13 Nov 2003 02:01:54 GMT,
ljb <ljb220@mindspring.no-spam.com> wrote:
> Undocumented change, it seems: sendmail in Slackware 9.1 was built
> with tcp_wrappers, unlike previous releases.

Thanks for that. I didn't notice anything about tcp wrappers in the
SlackBuild files. Perhaps sendmail's Makefile autodetects tcp wrappers
now?

> You need to add a line like "sendmail: ALL"
> to /etc/hosts.allow to get it working.

I had the following in /etc/hosts.deny, so didn't notice the change.

ALL: ALL EXCEPT LOCAL

--
Mark Hill <usenet@mark.ukfsn.org> (Yahoo address not read)
GPG KeyID: 4A3B58AC

Mark Hill <mark_usenet@yahoo.co.uk> wrote:
> I had the following in /etc/hosts.deny, so didn't notice the change.
>
> ALL: ALL EXCEPT LOCAL

You stil won't be able to RECEIVE e-mail then (although, with a
commercial provider, you can FETCH it with POP cq IMAP).
But people with a real mail server will have to change their hosts.allow
for sendmail to still work as a e-mail receiver (accepting msgs).
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TWA **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

On Thu, 13 Nov 2003 12:06:37 +0000 (UTC),
Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote:
> Mark Hill <mark_usenet@yahoo.co.uk> wrote:
>>
>> ALL: ALL EXCEPT LOCAL
>
> You stil won't be able to RECEIVE e-mail then (although, with a
> commercial provider, you can FETCH it with POP cq IMAP).

Good point. The only thing that communicates with sendmail here is
fetchmail, so the above is fine for me.


--
Mark Hill <usenet@mark.ukfsn.org> (Yahoo address not read)
GPG KeyID: 4A3B58AC

Eef Hartman wrote:

> ... people with a real mail server will have to change their hosts.allow
> for sendmail to still work as a e-mail receiver (accepting msgs).

I would argue that people with a "real mail server" are likely to have
performed a local installation of Sendmail, rather than use the
distribution supplied version, and are also likely to have been using
TCP_Wrappers with sendmail for a number of years already ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems analyst / Postmaster Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

mark_usenet@yahoo.co.uk wrote:
> On Thu, 13 Nov 2003 02:01:54 GMT,
> ljb <ljb220@mindspring.no-spam.com> wrote:
>> Undocumented change, it seems: sendmail in Slackware 9.1 was built
>> with tcp_wrappers, unlike previous releases.
>
> Thanks for that. I didn't notice anything about tcp wrappers in the
> SlackBuild files. Perhaps sendmail's Makefile autodetects tcp wrappers
> now?

No, it's in the "site.config.m4" file which gets used when Sendmail is
built (I guess):
APPENDDEF(`confMAPDEF', `-DNEWDB -DSTARTTLS -DTCPWRAPPERS -DNIS -DMAP_REGEX')
APPENDDEF(`confLIBS', `-lnsl -lssl -lcrypto -lwrap -lm -ldb -lresolv')
I also think that this change came incidental to another change
in Sendmail configuration, perhaps TLS, and may not have been intentional.

On Fri, 14 Nov 2003 02:29:05 GMT,
ljb <ljb220@mindspring.no.spam.com> wrote:
> mark_usenet@yahoo.co.uk wrote:
>>
>> Perhaps sendmail's Makefile autodetects tcp wrappers now?
>
> No, it's in the "site.config.m4" file which gets used when Sendmail is
> built

Ah. I see. Thanks.


--
Mark Hill <usenet@mark.ukfsn.org> (Yahoo address not read)
GPG KeyID: 4A3B58AC