The solution I plan to deploy will be two fold, first I will use the dot lock method to effectively keep Qpopper and Postfix from accessing the mail file while I am working with it. I also plan to stroke the .username.pop file and update the timestamp. I plan to do this because I use the last accessed time stamp of the .pop file to determine what dormant accounts I can delete.
As I imagine it, this strategy should effectively keep Qpopper/Postfix and my webmail system from inadvertantly corrupting a user's inbox. On the downside, if a user logins in through webmail, while a Qpopper session is active, my understanding is that there will not be any messages in the mbox file until the session completes. My understanding could be flawed here, since I haven't been able to actually witness this process (it happens to quickly for me to catch it with an ls). And I am still not 100% sure where these temporary files are stored.
As for Qpopper, I have it compiled with --enable-standalone, but *NOT* with --enable-server-mode. So the issue of Qpopper finding a different mbox file when it goes to write doesn't concern me.
Anyone spot any issues with this implementation?
My code was partially based on nwebmail.sourceforge.net, so feel free to look at that code to get an idea of what I am talking about.
-- L~
http://www.nerdshack.com
Clifton Royston wrote:
On Wed, Jun 30, 2004 at 01:51:27PM -0400, Daniel Senie wrote:
At 01:06 PM 6/30/2004, Chuck Yerkes wrote:
Quoting Ladar Levison ([EMAIL PROTECTED]):The best of the webmail systems I've found is Squirrelmail. It uses IMAP. Mailboxes to get corrupted from time to time when sendmail, qpopper and squirrelmail are all going at the mailboxes. I'd really like to find a fix for this too.
I have a question that stems from my desire to integrate a Webmail
system with my already up and running Qpopper 4.0.5 installation.
"a webmail"...
Basically my concern is in regards to the Webmail system, and QpopperCan the webmail not access the data THROUGH qpopper? Which would mitigate
cooperating nicely if both access the mbox file at the same time. I want
to make sure someone doesn't log in through the webmail system, and
Qpopper at the same time. Based on my reading of the source code
all the issues.
Is this with UW-IMAP?
In that case, it's the issue I mentioned above. You need to get the UW client library and qpopper to lock against each other, and those are the patches I never got into P4 for qpopper.
If you are interested, I will be happy to dig up and send you the latest version of the patches I had working, for you to try out.
If you were able to get them polished up and submitted towards the future qpopper mainstream as a build-time option, I would be tremendously happy.
-- Clifton
