"Errol U. Neal Jr." <[EMAIL PROTECTED]> said: > At 10:52 AM 9/23/2003, Chris Szilagyi wrote: > >Hello, > > > >I've got an issue with Qpopper 3.1.2, on Red Hat 7.1 (with sendmail and > >procmail). Basically, I have a problem whereby I'd like to tell Qpopper > >where to place the <user>.lock files. It seems the default is /var/mail/ and > >I'm having issues with user quotas, and would like to have it put the .lock > >files in a location like /var/lock/mail or something other than in the spool > >dir. I've read older posts that says this can be done but I haven't seen > >anything in the Qpopper 3.1.2 documentation on this. Can somebody please > >tell me how this can be done?? Thanks for all feedback... > > > >-- > >Chris > > > You need to rebuild the rpm or the source. Check the configure options. I >
I started to dig through the source since there doesn't appear to be a configure option to specify location of .lock files. In common/maillock.c, one of the revisions says: * 07/17/00 [rcg] * - Allow lock to proceed even if user is over quota. But the whole problem we are having is that Qpopper does NOT proceed if the user is over quota, and gives a quota error while trying to write the .lock file, in the log. Can anybody clue me in on the revision above, and what it is supposed to do? Is there supposed to be a feature of Qpopper that will allow it to continue if it cannot write the .lock file?? Thanks for all feedback. If I do happen to solve this issue I'll be sure to post what was done, as I would think this would be useful to those running Qpopper in a production environment like ours, where quotas are needed. Thanks, -- Chris
