teapop 0.3.3 has locking problems I'm unable to resolve. Note that today I also filed bug #10222 concerning a misspelling in the ebuild in the configure section. These problems occur regardless. $ telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Teapop [v0.3.3] - Teaspoon stirs around again <1036447966.18F81C8C@Llywellyn> USER [deleted] +OK Welcome, do you have any type of ID? PASS [deleted] -ERR Mailbox already locked. Connection closed by foreign host. ==> /var/log/messages <== Nov 4 17:12:52 fire-eyes teapop[30898]: Successful login for [deleted] [127.0.0.1] from localhost [127.0.0.1] Nov 4 17:12:52 fire-eyes teapop[30898]: Problems opening mailbox /home/[deleted]/mail in (errno = 21) # ls -l ~[deleted]/ | grep mail drwx------ 2 [deleted] [deleted] 152 Nov 1 00:43 mail -rw-r--r-- 1 [deleted] [deleted] 0 Nov 4 17:12 mail.lock It seems like teapop is expecting ~[deleted]/mail to be a single file? But it is a directory, created by pine I belive. http://www.toontown.org/teapop/faq.php#maillock mentions this problem. "The most common reason is that you have compiled Teapop with dotlocking method for locking mailboxes AND that the user does not have access to write files in the directory the mailbox resides in. To work around this, compile Teapop to use flock() instead: ./configure --enable-flock" Editing the ebuild script, by removing --enable-lock=flock,dotlock \ and replacing it with --enable-flock \ , then emerge -C teapop && emerge teapop has no effect on the problem. I also tried replacing --enable-homespool=mail \ with --enable-homespool=Mail \ , and created a symlink from ~[deleted]/Mail to /var/spool/mail/[deleted] . Same problem, and mail.lock is once again left in ~[deleted]/ (after being removed) . I've run out of ideas here, I'll be watching the bug.
teapop-0.3.5 has been added to portage with a couple of important fixes to the ebuild and the source has many fixes and changes.. Please test this new version. As a note, the ebuilds enable both flock and dotlocking...
please test this new version and let me know if you have the same problems or if things are resolved by this upgrade.
db fix
