Again, thanks all who responded. I'm still interested in ideas. As for the plugin, I am loving that idea! So, on to my favorite editor and some C code. Quick question: are plugins only in 1.0?
It is going to be difficult, at best, to get my institution to let me run "non-production" code in our production environment.
Is dovecot-stable still around and, if so, is that considered production level? Does that have the plugin architecture in it? I have until March 5th so if 1.0 is out by then I'm good anyway ;).
Regards,
| Todd Piket | Email: todd@mtu.edu | | Programmer/Analyst | Phone: (906) 487-1720 | | Distributed Computing Services | | | Michigan Technological University | |
Timo Sirainen wrote:
On Wed, 2006-02-08 at 16:42 -0500, Todd Piket wrote:
The perfect scenario would be if Dovecot could check /var/mail/%u to see if there is new mail and if so, *attempt* to move it to ~/Maildir. If Dovecot gets an over quota message it can stop and just return "No new mail" to the client and allow the user to see existing mail, but do nothing more. This should happen every time the user "checks" for new mail such that an under quota scenario (user deletes Sent folder messages, for instance) results in mail from /var/mail/%u to be "delivered" to ~/Maildir.
Oh, and this could probably be done best using a plugin. You could check plugins/convert code as an example how to copy mails from one storage format to another at login. You could even hook into Dovecot's expunge operation so that immediately after expunging it tries to move more mails into INBOX. Doing it only while logging in isn't probably enough since IMAP connections can last a long time.
BTW. if you haven't already, you should also place Dovecot's indexes and maildir control dir to non-quota partition or things break.