On Monday 05 August 2002 02:30 pm, Shane Kerr wrote: > > What is the reason you have a maxmail limit at all? If the purpose is > to limit the ability of users to consume server resources, then it > shouldn't matter whether the mail is deleted or not. Likewise, if you > are charging users based on number of mail messages, then it shouldn't > matter either. > > What is the rationale behind wanting this option?
It is not an option *I* want, the maxmail limit is already coded into dbmail. I am curious why it would start bouncing mail if the user logged in with pop3, downloaded his email, his email client then told the server to delete his mail, but dbmail-maintenance has not been run, so he hits his maxmail limit later that day and can't recieve emails. My employers would like to make sure that their pop3 users are not filling INBOXes with mail and not deleting it. If someone wants to use IMAP functions, then they should be signed up with IMAP service. Pop3 service shouldn't require more than 10MB of email storage, with the way that dbmail is working now, a user could recieve 11MB of mail in a day, check email every hour, have the emails set for deletion, and still get bounces for being over the limit. As far as he knows he doesn't have a single email message on the server. To me this is not the way that the system should work, at least not for pop3 users. Correct me if I am wrong. Thank you for your time. -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services ------------------------------------------ Today is the tomorrow you worried about yesterday.
