Hi, Paul.

PE> FM> It's ten past four on Sunday, so I thought I'd call and see how your
PE> FM> adaptive answer experiment works.

PE> Yeah, there was a reasonable turnout, ...

PE>   12 May 16:07:23.50   Received: 1/16841 Sent: 1/6080 Total: 2/22921 CPS:
PE> 440
PE> * 12 May 16:07:23.50   Seconds: 52  Tariff: 0  Fee: 0  System:
PE> 3:711/808{at}fidonet
PE> > 12 May 16:07:26.62   AT%L
PE> # 12 May 16:07:26.62   046
PE> # 12 May 16:07:26.62   OK
PE> # 12 May 16:07:26.62   RING
PE> : 12 May 16:07:27.71   Exit after receiving mail with errorlevel 70
PE> + 12 May 16:07:27.71   end, BinkleyTerm PE-OS/2 Ver. 4.02 -WATCOM C/32
PE> > 12 May 16:07:27.81   dropping DTR
PE> > 12 May 16:07:30.03   dropping DTR

PE> That could have been you.  Unfortunately you got one of those situations

Was me. The next call was 21 seconds later. 1 sec inter-attempt delay,
and I always get "CONNECT..." after 24 or 25 seconds - presumably your
end recognises it a few seconds earlier.

PE> where you managed to call just as I was picking up the phone to exit.

To exit? Dunno what you mean.

PE> Quite annoying.

Mmmm, but hardly a problem.

[chomp heaps of PE debug stuff]

PE> I know I said I was not going to implement it until Tuesday, but I
PE> should have thought it through more.  If there were no failed
PE> connects, then that means that no-one can report any problems.  And
PE> if no-one reports any problems, then there is no need to wait till
PE> Tuesday, there's not going to be any special information on Monday!
PE> So I am leaving it as adaptive answer.  BFN.  Paul.

Yeah, no obvious point in waiting except to get a larger sample of
callers. And I see "someone" has had trouble connecting - isolated that
one yet?

Regards, fIM.

 * * Memory is a thing we forget with.
@EOT:

---