>> Debug level is currently 5. Is there a higher debuglevel available? >> Would be great if the config file would tell me that 0 means almost no >> messages and (i don't know) 12 is _everything_ the daemon does. > > Afaik 5 is the max level. Using debug level 5 you should get pretty much > everything, i.e. most if not all imap protocol messages and all sql > queries. > Ok, good to know ;)
>> >> I will switch to a more recent dbmail version from CVS now, maybe it is >> fixed there. Any release schedule for dbmail 2? I may be able to >> contribute a GUI to it (the account management software i currently >> use). > > I don't know if there's a eta for 2.0. I for one wouldn't mind a 1.2 > release based on cvs as it now stands. At least then new users would > start with using something more stable, and with far fewer bugs than > 1.1. Most questions from 1.1 users concern matters already resolved in > cvs. > I'd vote for a 1.2 release too, as the cvs version does fix a lot (e.g. crypt-md5 and md5sum password lookups and moving messages). And please include the autocreation of INBOX patch sb. posted to the list in 1.2 if you release it ;) >> Oh, i see many messages in the syslog, but none of them say anything >> about a UPDATE or DELETE to the database or a imap cp/rm/mv command, >> that's why i have no idea what exactly keeps the messages from being >> moved... > > Mmm, I've just tried it and I see plenty of imap commands and sql > queries flying by. > > From what I understand moving basically involves: > > [ copy from old folder to tmpmessage(blk) ] > insert into tmpmessage ... select ... from message ... > insert into tmpmessageblk ... select ... from messagesblk ... > > [ copy from tmpmessage(blk) to new folder ] > insert into message ... select ... from tmpmessage ... > insert into messageblk ... select ... from tmpmessageblk ... > > [ clear out tmpmessage(blk) ] > I can see that stuff too now, but i did not when i used dbmail 1.1. Thanks for your help and information, dbmail now seems to work nice for me. Mike
