This is Bugzilla
Bugzilla Version 2.22.7
View Bug Activity | Format For Printing | XML | Clone This Bug
groupware McServer imap doesn't delete .eml files from the serverfolder. Causing double messages to appear in the imap folder view in Scribe. Imap folder in Scribe shows the same amount of emails as emls in the folder, only all of them with content of an email stored in the folder that has not been deleted.
*** Bug 51 has been marked as a duplicate of this bug. ***
When you right click on the folder in Scribe and go "Properties" you should have a "Expunge" button and a number of deleted messages. If you hit "Expunge" it will delete the messages flagged for deletion. At this point the files should disappear off the server. Can you confirm that is the case? If so you should close this bug, as it is working as intended. This is simply how the IMAP protocol works.
Yes and no. you are right, the expunge action removes the eml. but some bugs do remain. after an expunge the eml is deleted, but the email remains in the imap folder of clients other then the one that deleted. viewing an other folder, and then back to the imap folder still shows the deleted email. (i tried this because it does work for displying new imap emails). only a reconnect will remove the email from the imap folder. allso the client that puts an email in the imap folder cannot delete this email untill after a reconnect. when clicking the delete button on a just copied email, the email is put in the trash folder, but it stillremains in the imap folder. (sometimes server crashes) in my opinion (without knowing the details of the code or protocol) there should be more information exchanges between client and server after every action. If i perform a reconnect after every action taken on the imap folder there are no problems. (except that another client cannot know that something has changed so is not aware that a reconnect is required) my 2 cents, exo
should i make some screen recordings?
Ok, I'll take these comments into consideration when I look at it next. I'm still digesting your comments about the POP server.
Some of these issues are actually problems in the Scribe codebase not on the server. But I've made a number of fixes there for not being able delete new messages and deleted messages coming back from the dead. For issue of other clients not getting notifications of deletes and new messages I will create a new bug as it's a separate issue.
I've made a new build of Scribe with some IMAP fixes here: http://www.memecode.com/temp/inscribe-win32.exe And you can grab groupware v0.81 from the main site.
scribe and server crash on expunge new scribe build, 0.81 win2k crash data scribe (note scribe folder is under server folder) ///////////////////////////////////////////////////////////////////// Unhandled Exception Code: c0000005 Description: EXCEPTION_ACCESS_VIOLATION Call stack: ------------------------------------------------------------------ 0048DB92: E:\Memecode Groupware\scribe2\Scribe.exe 1001AE25: E:\Memecode Groupware\scribe2\Lgi.dll Offset: 0x930 (GView::OnEvent) 77E12CA8: C:\WINNT\system32\USER32.DLL Offset: 0x444 (GetSysColor) 1001F98F: E:\Memecode Groupware\scribe2\Lgi.dll Offset: 0x191 (GDialog::DoModal) 0042DF15: E:\Memecode Groupware\scribe2\Scribe.exe ------------------------------------------------------------------ //////////////////////////////////////////// crash data server: //////////////////////////////////// Call stack: ------------------------------------------------------------------ 0041C189: E:\Memecode Groupware\McServer.exe ------------------------------------------------------------------ Unhandled Exception Code: 80000003 Description: EXCEPTION_BREAKPOINT Call stack: ------------------------------------------------------------------ ------------------------------------------------------------------ Unhandled Exception Code: 80000003 Description: EXCEPTION_BREAKPOINT Call stack: ------------------------------------------------------------------ ------------------------------------------------------------------ Unhandled Exception Code: 80000003 Description: EXCEPTION_BREAKPOINT Call stack: ------------------------------------------------------------------ ------------------------------------------------------------------ //////////////////////////////
I've moved the crashes to Bug #63. This should be fixed in the exo2 builds I sent you links for.
exo2 build still chraches, but ill move to the new bug number