Probably because xinetd works, by default, with tcp-wrappers, etc,
and in the old 6.x and prior setups, you had to add tcpd (the
tcp-wrappers executable) to the command to get hosts.allow to work.
On Tue, 5 Dec 2000 18:11:52 -0800, Steve Lee wrote:
>okay.
>i found out that it was something in the hosts.allow.
>interesting why it didn't work with the old allow?
>
>----- Original Message -----
>From: "Edward Marczak" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, December 05, 2000 4:11 PM
>Subject: Re: Redhat 7.0
>
>
>> On 12/4/00 10:11 PM, Steve Lee spake unto the assembled:
>>
>> > it was setup previously, working wonderfully.
>> > here is a snip of what happens when i telnet into port 143.
>> > Escape character is '^]'.
>> > * OK neptune.blitzen-priv.net IMAP4rev1 v12.264 server ready
>>
>> Well, that's only one part of it. Do that again, and then...
>>
>> 1 CAPABILITY
>> (some response)
>> 2 LOGIN name pass
>> (some response)
>>
>> What does that get you?
>>
>> > could it be a version problem with outlook?
>>
>> Doubt it.
>>
>> > i do have xinetd setup properly.
>>
>> I manually upgraded a 7.0 machine to IMAP-2000. I vaguely remember having
>> to add to the PAM settings.
>> --
>> Ed Marczak
>> [EMAIL PROTECTED]
>>
>>
>>
>> _______________________________________________
>> Redhat-list mailing list
>> [EMAIL PROTECTED]
>> https://listman.redhat.com/mailman/listinfo/redhat-list
>>
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
