[REBOL] Re: Reading POP mail
From: holger:rebol at: 1-Oct-2001 17:44
On Tue, Oct 02, 2001 at 12:14:49AM +0100, Matt Burns wrote:
> I found the problem. For some reason, rebol on the server was trying to
> connect via APOP rather than vanilla POP, and because the account wasn't
> specified as APOP, login couldn't be verified.
> I found this using the trace/net function (and watching the output)
> At blooming last.
> Is APOP the default POP access method, or is there some specifier I can
> use to change this? I didn't set this up manually... Oh, well...
Prior to Core 2.5 APOP was not supported at all.
In Core 2.5 REBOL attempts APOP if the server signals that it supports
APOP (or that it at least knows how to correctly reject it) by putting
its date stamp into the login message. Unfortunately there are some
POP servers out there which signal that they support APOP but then
close the connection (instead of returning a proper error) when the
application attempts to use it :-(. Because of that...
... current versions of View, Command etc. (and future versions of
Core) no longer attempt to use APOP by itself. Instead you need to
enable it by settings system/schemes/pop/algorithms to 'apop.
Without that only regular pop is used.
It looks like you used different REBOL versions on different
machines, and your POP server is broken in that particular way...
To disable APOP in Core 2.5 put the following line into your user.r
or at the beginning of your script. You should check for system/product
and system/version so it does not get executed accidentially on
change pick find second get in system/schemes/pop/handler 'open 'if 3 true