Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
dbmail.org is a lean fast database-backed email store. It can replace maildir or other storage and has an imap daemon so you can access your email using any imap client (including many webmail packages) simply using imap. Lastly, qmail and other mta's can feed directly into dbmail instead of onto disk. dbmail is made for managing large numbers of users... check it out!
Created an attachment (id=12873) [details] dbmail-1.1.ebuild Simple to use. Edit the ebuild to use either mysql or postgres (the ebuild needs a little tweaking). It should work by default with postgres... Good luck! Some users are already using this with 10,000-20,000 users!
Created an attachment (id=20450) [details] dbmail-1.2.1.ebuild (updated ebuild) this is a bugfix version bump. I have installed and tested this ebuild.
Created an attachment (id=20451) [details] enhancement script for postgresql for dbmail (add to files/ subdir) This script is described in the 1.2.1.ebuild, and it is to be placed in the files/ dir as an optional script.
Updating summary of ebuild
Ebuild works fine if you version bump it to latest, 1.2.6. Would appreciate an add to portage.. migrating from courier due to maildirs heavy io loads in large folders.
Created an attachment (id=31141) [details] ebuild for dbmail 1.2.7b Now Postgres and mySQL are mutually exclusive (copied from nagios-core ebuild)
Created an attachment (id=31146) [details] Updated ebuild for dbmail 1.2.7b Updated dbmail 1.2.7b with init scripts for dbmail-pop3d and dbmail-imapd and new empty mysql initial database config
Created an attachment (id=31147) [details] dbmail-pop3d init script
Created an attachment (id=31148) [details] dbmail-imapd init script
Has anyone tried these ebuilds with later builds of dbmail, such as the 2.0 series? I'm interested in trying dbmail out on alpha.
The latest uploaded ebuild has worked fime for me up to 1.2.10 but there's an issue with the enewgroup and enewuser macros that I haven't dedicated time to fix. I will try 1.2.11 once I have fixed the ebuild. I have an ebuild for 2.0RC8 that compiles fine with ebuild dbmail-2.0_rc8.ebuild compile. I will upload it so you can give it a try. The ebuild has the same issue with enewgroup and enewuser that I will fix later. I have not tried with emerge, I will do it later.
Created an attachment (id=41784) [details] ebuild for dbmail 2.0RC8 ebuild dbmail-2.0_rc8.ebuild compile => successful emerge =dbmail-2.0_rc8 => haven't tried
Created an attachment (id=41785) [details] Updated ebuild for dbmail 1.2.10 emerge -u dbmail => successful and stable in production use.
Forgot to add myself to CC list.
Created an attachment (id=41952) [details] ebuild for dbmail-2.0.0 Proposed ebuild for DBMail 2.0, which was released on Oct. 14, 2004.
Created an attachment (id=42440) [details] ebuild for dbmail 1.2.11 Fixed enewgroup, enewuser (missing include eutils) Merged some small changes from the 2.0 ebuild
Is it any useful to put dbmail 2 in a separate slot?
Only if 1.x and 2.x are meant to be installed simultaneously in system, like f.e. GTK+
Nice, the ball is already rolling on this :-) I'm a developer of DBMail and a Gentoo user myself. I have a set of init scripts (slight updates to the ones I put in the contrib/ directory of the distribution) and an ebuild that I use myself. Looks like this ebuild is actually a bit more sophisticated, though -- I write lots of C, but not so many ebuild scripts ;-) What's the status in terms of getting this into the portage tree?
(From update of attachment 41784 [details]) As 2.0 is out, I guess ebuild for a RC is obsolete.
(From update of attachment 20450 [details]) Marking obsolete
Try modifying the ebuild in a way so if both mysql and postgresql USE flags are enabled, one of these will be prioritized, displaying a easy to spot message (maybe ewarn?) for the user.
(From update of attachment 41952 [details]) Adjusting attachment's mime type for easier viewing.
What is wrong with the current method for prohibiting the use of mysql and postgresql flags simultaneously? It's the same method used in net-analyzer/nagios-core ebuild.
It's not wrong, I just tried to offer an alternate way to handle this.
hi, with both mysql and postgres set in the general use flags in /etc/make.conf for postgres support I had to add: net-mail/dbmail -mysql postgres to /etc/portage/package.use to set the use flags just for dbmail I've recently put up an ebuild for dbmail-admin (web config tool) here http://bugs.gentoo.org/show_bug.cgi?id=73840 I think I'll have a look at the dbmail 2.0.0 ebuild next, there seem to be some problems starting the daemons at the moment
Created an attachment (id=45764) [details] dbmail-2.0.1.ebuild I've re-done the ebuild for 2.0.1, I think this should work now I've also revised the init.d scripts, added some conf.d files and added a patch for amd64 dbmail-amd64-gentoo.patch dbmail-startup-gentoo.patch files to be located in the files dir for dbmail
Created an attachment (id=45765) [details] dbmail-startup-gentoo.patch for 2.0.1
Created an attachment (id=45766) [details] dbmail-amd64-gentoo.patch for 2.0.1
DBMail 2.0.2 is out today. Whomever's been driving this bug, please update the ebuild. Whomever's in charge of getting ebuilds into Portage, Please Please Get This In Already!
Created an attachment (id=48551) [details] ebuild for dbmail-2.0.3 Here's one better :) dbmail-2.0.3 not that much of a difference to the ebuild other than removing the amd64 patch and altering the version number no difference in the way the database tables are laid out (the DB init scripts in /home/dbmail/sql are still the same) it looks as if a couple of extra options have been added to /etc/dbmail.conf I've also altered the maintenance message I've noticed that dbmail-maintenance has been replaced with dbmail-util when going from version 1 to version 2 e.g. crontab entry "0 3 * * * /usr/sbin/dbmail-util -cpdy >> /dev/null 2>&1" but would it be better to relocate the files in /home/dbmail across to /usr/share/dbmail instead?
A small comment: einfo "Please read /usr/share/doc/${P}/INSTALL " Should be: einfo "Please read /usr/share/doc/${P}/INSTALL.gz" Will give it a proper ride later.
Created an attachment (id=55725) [details] ebuild for dbmail-2.0.4 New ebuild for dbmail 2.0.4 also requires a couple of patches for amd64
Created an attachment (id=55726) [details] dbmail-2.0.4-01_quota.patch patch a amd64 bug
Created an attachment (id=55727) [details] dbmail-2.0.4-fPIC.patch fix a couple of fPIC errors during install for amd64
Created an attachment (id=55728) [details] ebuild for dbmail-2.1.0 (unstable) I didn't have to patch this one fo amd64 but gmime had to be added as a depend note this is classed as unstable
I'd just like to add an additional bump to putting this into the portage tree.
Created an attachment (id=61730) [details] DBMail 2.1.1 ebuild (unstable) Ebuild for DBMail 2.1.1. It has a new dependency to gmime compare to 2.0.1 ebuild. I have tested it compiles all the way to the end. Haven't run it yet.
It would be nice to have this in the portage so more people can test it out for Gentoo.
I have been using dbmail-1.2.11 since 2004-10-22 in production servers whthout any complain from customers other than occassional load peaks. I don't understand why is dbmail still out of portage tree.
Created an attachment (id=67162) [details] updated ebuild for new filenames in dbmail 2.1.2 updated the ebuild to include also some new README files doc files are now stored *.gz files
Created an attachment (id=67177) [details] Updated 2.0.6 ebuild This ebuild updates the location of the source file and has the quota patch already merged into the main source. There's now an untested script for MySQL setup. Some erratas in comments were fixed.
Created an attachment (id=67609) [details] dbmail-2.0.6-r1.ebuild Removed bloated dbmail-startup-gentoo.patch. By removing that patch the daemons don't need to run dbmail-util -a before starting so they start immediately instead of taking more than 20 minutes. Also, /etc/conf.d/dbmail entries in the patch are not needed since all needed configuration is already in /etc/dbmail.conf.
Created an attachment (id=67610) [details] dbmail-2.0.6-r2.ebuild Fixed init scripts install from contrib
You cannot specify both --with-mysql and --with-pgsql on the same build...
something like other ebuilds with /etc/portage/package.use mail-mta/dbmail -postgresql mysql
Created an attachment (id=70257) [details] dbmail-2.0.7.ebuild new version is out 2.0.7 the only difference from 2.0.6-r2 removed the fPic patch as this is no longer needed for amd64 with this version marked old crud obsolete startup scripts for gentoo are now included in the source tree which is good
This is now in the sunrise overlay. You can find it at: http://www.gentoo-sunrise.org/svn/reviewed/net-mail/dbmail/ all feature request, patches went here! regards Martin
ebuild for dbmail-2.1.6 is also in gentoo sunrise at http://www.gentoo-sunrise.org/svn/reviewed/net-mail/dbmail/ Martin
Created an attachment (id=93954) [details] dbmail-2.1.7.ebuild updated ebuild
2.1.7 requires glib2.6, but the ebuild does not require this, hence the ebuild only works if you (for some other reason) have glib2.6 installed. http://mailman.fastxs.net/pipermail/dbmail/2006-May/008940.html
Hey folks, What's happening with this? We just cut the DBMail 2.2 branch, and we're looking forward to distributions including DBMail soon. Let's begin by accepting an ebuild for DBMail 2.1.7, to be followed by 2.2.0 stable which has the same library requirements. If a maintainer is needed, let me know and I will gladly take on that role. Thanks, Aaron
Also, I'd like to bring attention to the fact that DBMail no longer has any mutually exclusive compile time options. You can very happily build a DBMail with any combination of mysql, postgresql, sqlite, sieve, ldap -- well, as long as you have at least one of the three databases ;-)
Aron, what if you configure dbmail and you have mysql and sqlite installed? Does it compile against 2 (or 3) DB libs? Dep on >=glib-2.6 is commited to sunrise. Martin
DBMail uses dl() to load modules which are linked against the different db's. At compile time, you can pick which modules to build (and thus which libraries will be linked against). At run time, the DBMail shim is dl() loaded, which pulls in the relevant database library, and gives useful error messages if it isn't found. This has also made binary packagers happy, because they can ship a fully-built DBMail and the user can select whichever database they have on their system from the dbmail.conf config file. Anyhow, I'd really like to get DBMail into Gentoo, and would appreciate if someone CC'd on this bug could give me a hand getting the ball rolling!
i have uploaded a new ebuild to sunrise. no db logic anymore, it uses whatever is installed, added ldap use flag, added sieve use flag (needs libsieve ebuild installed under mail-filter , see bug http://bugs.gentoo.org/show_bug.cgi?id=149770 . Perhaps libsieve should also added to sunrise? Martin
Ping for update to version 2.2.0rc1.
2.0.0_rc1 is in gentoo-sunrise. http://www.gentoo-sunrise.org/sunrise/browser/sunrise/net-mail/dbmail regards Martin
Ping for DBMail 2.2.0rc2. libSieve is now in Portage, at mail-filter/libsieve, so DBMail is now free and clear of non-Portage dependencies! :-) Martin, thanks very much for maintaining Sunrise. But how do I get DBMail into Portage proper!?
Bump for 2.2.0: 2006-11-15 DBMail 2.2.0 released!
Pavel, you beat me to it! ;-) I really do wish someone on the Gentoo side of things would reply to any of my bug posts and direct emails asking about how to get DBMail into Portage. C'mon. I'm being a squeeky wheel. Let's get some oil here! :-)
Ping for DBMail 2.2.1. I'm dismayed report that I sat in on the net-mail IRC channel a few days ago and was not responded to in any way about this bug.
*** Bug 155626 has been marked as a duplicate of this bug. ***
2.2.1 is in gentoo-sunrise. http://www.gentoo-sunrise.org/sunrise/browser/sunrise/net-mail/dbmail regards Martin
Martin has updated to DBMail 2.2.2 in Sunrise. I'd still like to see this in Portage. Hailing frequencies open to net-mail, come in please, net-mail! :-)
As i'm interested in using this on my own server i am considering maintaining this, but since i'm not part of the net-mail team i'll contact them first. will update this asap. regards
just an updae for interested parties... i've tried the sunrise builds and will start using this soon.. as soon as i'm satisfied it works ok (and won't delete my emails lol) i've emailed net-mail herd to see if they have any objections ;)
Added dbmail-2.2.4 to portage, based on ebuild from sunrise. Thanks everyone who contributed here (I see quite lot of people here), and thanks Aaron for the patience and incessant bugging. :) Thomas, feel free to take over maintainership or start co-maintaining when you're ready - I felt it's good to have this in the tree rather sooner than later.
thanks ;) sure will think about if i wanna take maintainership or co-maintain ;) (prolly best to co-maintain). i was just finishing the setup of my own server to test this sufficiently ;)
