If I may, let me add to my previous message (below) one additional piece of information. I cannot believe I'm saying this, but an Outlook XP client and qpopper 4.0.4 work just fine to delete such messages from the server. But my Eudora clients (5, for t he most part) are still exhibiting this problem:
>Hello. I've just upgraded from qpopper 2.5.3 to qpopper 4.0.4 (Solaris 7). I've been >away from qpopper for about 2 years (since I installed the earlier version). > >Here's the problem: if a user with a POP client (e.g. Eudora 5.1) has her client >configured to remove messages from the server on check, it deletes them just fine. > >However, if she has "leave messages on server" checked, but "delete after 3 days" >and/or "delete from server when emptied from trash," qpopper is not deleting the >messages from the server. Ever. They continue to sit in her spool file. The stats log >confi r >ms this. Am I doing something wrong? The install and make went fine: > >./configure --enable-uw-kludge (we have some IMAP users) >make > >Then, I copied the popper executable to our local binary directory. Here's the >"inetd.conf" entry: > >pop3 stream tcp nowait root /usr/local/etc/popper popper -R -s -t /var/log/maillog > >I could understand this behavior perhaps on the first check with the new qpopper >(reference the "old-uidl" business in the administrator's guide), but not on >subsequent ones. > >Can anyone offer any help? I can't have spool files growing forever, but we do need >to continue to provide the "leave on for X days" option from a client. TIA. Sean [EMAIL PROTECTED]
