OK. I wasn't clear about this... We are using the bulletin database, and from readings that I had seen it seemed that popper continued to check the user's .popbull *each time* the user checked the mail. HOWEVER, upon further reading, more attention paid to said reading, and going to the actual source (GUIDE.pdf), popper only checks the popbull file the *first* time the user pops. So, I am barking up the wrong virutal tree here.
OK, to REphrase my question: Is there any way to tell popper -- when using the bulldb option -- to NOT give out a bulletin to a user. Can I manipulate the actual bulletin database in such a way (manually, that is) to get this outcome? Sorry I didn't fully explain the situation. It would have made more sense to people if I had given accurate information. Putting the number in the .popbull file to a large number does indeed work on a box that is not using the bulldb (I have another box I tried this on - it works as advertised). Thanks! Alex > > Is this an environment in which you can tell the users to > > lump it? > > Don't I wish!!! :) Unfortunately, it is an ISP situation > where users are paying for the service, and have the opinion > that they are the customer, and the customer is always right. :) > > > What about trying a smaller number in the .popbull > > file? In my setup, I have been able to prevent bulletins > > from, or even cause bulletins to, appear in users' mailboxes > > by manipulating the .popbull file just-so. > > > > One gotcha on this tactic, however, was file ownership and > > permissions. All of my .popbull files are owned by the user, > > GID of the user's default group, and chmod 740. > > OK, that sounds reasonable, I'll try a smaller number and > double check the file permissions. > > Thanks!! > > Alex > >
