take a look at the dbmail list
my conversations with paul and a optimized transition for dbmail3 resolved a lot of bugs the last weeks, most fixes are even not included in 3.0.1 branch
currently high recommended is this snapshot fixing at least a lot of memory-leaks to prevent imapd cosume > 1 GB RAM after a few hours, fixes POP3 in most cases (timeout AND login_timeout to 1800 is a workaround for troubles with Outlook2003 over slow connections with hughe attachments), so dbmail in Fedora in the RC version can be called as unusable for any production server
i would strongly recommend to update the package since it was way to soon to include dbmail3 RC in stable releases (i holded back 2.2 in our infrastructure to prevent from a migration disaster) and started testing/debugging after 3.0.0 final - even than it was a hard work the last weeks to make it really fine
WOULD YOU PLEASE UPDATE THE PACKAGE FOR FEDORA USERS OR CONSIDER THE NEXT TIME NOT INCLUDE RELEASE CANDIDATES?
i have no problem because i was able to hold back 2.2 fro F15 and rolled out 3.0.2 after test some minutes ago - but you are shipping a broken package to all other users
-------- Original-Nachricht --------
Betreff: [Dbmail] DBMail 3.0.2 released
Datum: Sun, 11 Mar 2012 17:01:23 +0100
Von: Paul J Stevens <firstname.lastname@example.org>
Antwort an: DBMail mailinglist <email@example.com>
An: DBMail mailinglist <firstname.lastname@example.org>, DBMAIL Developers Mailinglist <email@example.com>
-----BEGIN PGP SIGNED MESSAGE-----
I'm pleased to announce DBMail version 3.0.2, the latest in the new
This is a bugfix only release, focussed mainly at addressing improved
IMAP compliance and reducing memory leakage. It also includes a small
but important fix in the POP3 code (bug #951).
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
can someone here explain why the hell are RELEASE CANDIDATES are puseh to fedora GA releases and after that ignored for fixes/updates?
dbmail-3.0.2-2.el6 has been submitted as an update for Fedora EPEL 6.
dbmail-3.0.2-1.fc15 has been submitted as an update for Fedora 15.
dbmail-3.0.2-1.fc16 has been submitted as an update for Fedora 16.
dbmail-3.0.2-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dbmail-3.0.2-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
I'm running a fully up-to-date F15. I updated dbmail on March 21. I am now getting error messages about the dbmail database being obsolete, and asking me to run a script to convert it. The database is an sqlite3 database, and it thinks I am running a pre 2 database. I've looked for a conversion script and can't find it. I haven't done a lot of "coming up to speed" on what is going on here. I think I'm going to downgrade the dbmail package to see if that fixes the problem temporarily, at least. Thanks for any help you can provide.
you missed my link to the dbmail list-archive and there you find
a messagw from me showing a full migration, but this is for
mysql and not sqlite - who is really using sqlite as mailserver
i do not know the fedora dbamil3 package well because it does not bother me after all the work i did for dbmail3 to get it stable with my own ones and the migration himself was a one-shot-thing
so i do not know if the fedora-maintainer missed some pieces and i fear upstream is also testing sqlite not as well as you expect
Thanks for the response Harald. I'm using it as mail storage, and I didn't set it so I presume it was the default. I had thought of moving to postgres or mysql as a solution when I first saw the configuration. Maybe I still will, but the default seems to serve my needs and it would take an investment to do it. Just like I'm still considering a move to dovecot, and have been for a while. Both of these make sense, but the benefit for the cost just doesn't seem to be there right now.
I posted back in order to give the full error message I'm getting.
Message from syslogd@fedora15 at Mar 22 03:20:28 ...
dbmail/maintenance: [0x1949060] EMERGENCY:[db] check_table_exists(+803): pre-2.0 database incompatible. You need to
the conversion script
I've downgraded now to the previous 3.0.0 and will see what happens. I'll also go look at the link Harald provided.
dbmail-3.0.2-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
dbmail-3.0.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
dbmail-3.0.2-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
dbmail-3.0.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.