Network/server latentancy and a poor MUA (OUTLOOK!) could cause a lot of
'could not connect to host' errors.
Funny thing is.. it's working. qmail-pop3 is secure (right?) and it
needs cleartext commands to log in, authenticate and pass mail.
It sure dosen't look broke to me.. why are we trying to fix it?
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Mon, 15 May 2000, David L. Nicol wrote:
>
> How about a really short time-out? Automated POP3 clients
> waste no time typing at the prompt -- Mark could analyze the
> delay his MUAs have between connection and sending auth commands;
> and patch pop3d accordingly. Or he could patch pop3 to require
> (not just accept) encrypted authentications, maybe in addition to
> the timing thing.
>
>
>
>
>
>
> Paul Farber wrote:
> >
> > I think the original poster is just 'scared' because the POP3 protocol
> > uses cleartext command (telnet, perl script, python) could connect up and
> > get mail.
> >
> > Thinking that telneting to 110 and giving the same commands at a console
> > is somehow 'hacking' a system.
> >
> > It will blow thier mind when they telnet to port 25 and can actually SEND
> > mail!
> >
> > Paul Farber
> > Farber Technology
> > [EMAIL PROTECTED]
> > Ph 570-628-5303
> > Fax 570-628-5545
> >
> > On Mon, 15 May 2000, Aaron L. Meehan wrote:
> > > It's difficult to answer a nonsensical question.
> > > Aaron
> > > > At 05/14/2000 05:48 AM Sunday, Mark Lo wrote:
> > > > > I would like to disable telnet to port 110, but still
> > > > >let my user to retrive mail via mail client at port 110?? (using
> > > > >tcpserver)
>
>
>
>
> --
> David Nicol 816.235.1187 [EMAIL PROTECTED]
> drawn to the speed and performance
>
