Has anyone else been experiencing an increase in POP3 aborts with
Arachne error message screen since switching to 1.6x ??
I continue to have problems with it, even after switching to 1.61 and
cable access [mail server is, of course, the same].
I don't want to bug my ISP again if it may be a problem with Arachne.
These aborts are *not* a matter of "dropped carrier" or lost connection.
In every case the QUIT command has gone to mail server -- whether the
QUIT originated with Arachne or elsewhere I cannot tell. I know that
the QUIT command gets to mail server, because when I restart download
from server, it is with next message and not first. i.e. the mail
server deleted the messages already downloaded. And that happens *only*
when session ends with QUIT.
It could be a problem with mailserver having to "bail out" if
overloaded? Or a bug in server software? Or is it a problem in
Arachne? That's why I'm trying to figure out before contacting ISP.
[Dumb bunny I have to deal with doesn't know Linux, doesn't know how
mail server is supposed to work, and doesn't think DOS could possibly
work so every problem I report is all *my* fault for being a DOSasauer.]
l.d.
-- Arachne V1.61, NON-COMMERCIAL copy, http://arachne.cz/
