This is the kind of answer needed! I know I'm not the only one who has been hit with the "OH NO! It downloaded everything again!!" problem. Being able to clean up the mess with telnet is beside the point ... it should be possible to have the mess never happen. But without something solid to work with -- on the Arachne end, and with the ISP where possible -- nothing much can be done to fix things. With my ISP and multiple mail servers, unless I can tell them the server they can't do a thing ... because using telnet the problem never occurs, [at least it never HAS occurred even when there is a Problem Message involved] and I think that is how they actually access a lot of the stuff right there in the office. Drat! I just remembered something! I had a problem message, I called up the techs because it was before I'd gotten a handle on how to use telnet, they "deleted" the message there ... and when I went to download again, the message was STILL there! And I didn't think to document it or get the name of the tech or anything, because I didn't know enough about what was going on to see that as very important. sheesh ... ==== On Sun, 09 Sep 2001 15:31:19 -0400, Glenn McCorkle wrote: > On Sat, 08 Sep 2001 20:01:15 -0400, L.D. Best wrote: > <snip> >> Fifth: All of that aside, regardless of how anything is stored anywhere >> on the POP3 server, I'd still like the POP3.log file generated to be a >> full capture, and not just a message [and message comand] log. Only >> that way can problems be pinpointed. > I'll look into the SRC code and get back to you on how difficult it > might be. -- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
