Qpopper experts,
We are running qpopper 4.03 on aix 4.3.3 systems. I am in a quandary about
how to handle setting soft and hard quotas for incoming email for 1500
users and am open to different suggestions. We have set a 10mgb quota on
the mailbox files for each user in /var/spool/mail. If we have the temp
pop files located in /var/spool/mail, then they are unable to retrieve
exisiting email if they hit their quota limit. If we put the temp file in
another filesystem without a quota such as /var/spool/pop, then users can
still retrieve their email, but on occasion an incoming message comes in
while they are popping their email and if they have "leave on server" they
can exceed quota while retrieving. This results in the inability to write
the entire temp file back to /var/spool/mail. Hence, the temp file gets
stuck in the /var/spool/pop directory which has no quota and can grow very
large as new mail appends to it. We could set a quota on /var/spool/pop,
but even that wouldn't allow the ability to write back to /var/spool/mail
if new mail comes in. Any thoughts on this dilema?
Ideally, it would be nice if no new incoming email could get delivered
to /var/spool/mail while in the process of retrieving email (popping). But
this might be a bad idea if it actually gets rejected. Thoughts?
Second question, does qpopper increase the size of the mailbox file
slightly when popping by adding in any headers, etc?
Tim Tyler
Network Engineer - Beloit College
[EMAIL PROTECTED]
