I am currently using Cyrus IMAPd, and been using it for a long time, the main reason being that I want an IMAP server with nice server-side filtering, which Cyrus provides via Sieve. Given that Sieve is integrated with Squirrelmail, all is good.
Or is it? Cyrus IMAPd is powerful, but it's a complete mess to upgrade, either when upgrading the software per se, or when upgrading the whole OS. There are just too many "moving parts", complicated by the fact that it interacts with SELinux. And so on. So I'm kind of starting to hate it.
But recently Freshmeat reminded me of DBMail:
And today I noticed that DBMail uses Sieve. Very nice!
Now, storing email in a database might be a controversial idea. I can definitely see at the same time some advantages, but also some disadvantages. However, for an IMAP server that essentially is used only by two people, I don't think the database per se can be a problem.
So, what I'm asking is:
Anybody here using DBMail? Any success stories? Horror stories? "Meh" stories? If I do end up using it, most likely I'll use ver 2.2.5 (available in the EPEL repo) with CentOS 5, probably with a MySQL backend (but I'm not sure yet, SQLite might be another option).
Florin Andrei wrote:
I am currently using Cyrus IMAPd, and been using it for a long time, the main reason being that I want an IMAP server with nice server-side filtering, which Cyrus provides via Sieve. Given that Sieve is integrated with Squirrelmail, all is good.
Or is it? Cyrus IMAPd is powerful, but it's a complete mess to upgrade, either when upgrading the software per se, or when upgrading the whole OS. There are just too many "moving parts", complicated by the fact that it interacts with SELinux. And so on. So I'm kind of starting to hate it.
But recently Freshmeat reminded me of DBMail:
And today I noticed that DBMail uses Sieve. Very nice!
Now, storing email in a database might be a controversial idea. I can definitely see at the same time some advantages, but also some disadvantages. However, for an IMAP server that essentially is used only by two people, I don't think the database per se can be a problem.
So, what I'm asking is:
Anybody here using DBMail? Any success stories? Horror stories? "Meh" stories? If I do end up using it, most likely I'll use ver 2.2.5 (available in the EPEL repo) with CentOS 5, probably with a MySQL backend (but I'm not sure yet, SQLite might be another option).
I used it quite some time ago, and it did work rather well. The most difficult time I had was getting the mail server integration working right. I suspect that it's probably come a long way since I used it (2 years now) and when I did use it it really gave me no problems.
A good web/other interface for administration would have been very useful, but what was there at the time was utter crap.
James A. Peltier wrote:
Florin Andrei wrote:
I am currently using Cyrus IMAPd, and been using it for a long time, the main reason being that I want an IMAP server with nice server-side filtering, which Cyrus provides via Sieve. Given that Sieve is integrated with Squirrelmail, all is good.
Or is it? Cyrus IMAPd is powerful, but it's a complete mess to upgrade, either when upgrading the software per se, or when upgrading the whole OS. There are just too many "moving parts", complicated by the fact that it interacts with SELinux. And so on. So I'm kind of starting to hate it.
But recently Freshmeat reminded me of DBMail:
And today I noticed that DBMail uses Sieve. Very nice!
Now, storing email in a database might be a controversial idea. I can definitely see at the same time some advantages, but also some disadvantages. However, for an IMAP server that essentially is used only by two people, I don't think the database per se can be a problem.
So, what I'm asking is:
Anybody here using DBMail? Any success stories? Horror stories? "Meh" stories? If I do end up using it, most likely I'll use ver 2.2.5 (available in the EPEL repo) with CentOS 5, probably with a MySQL backend (but I'm not sure yet, SQLite might be another option).
I used it quite some time ago, and it did work rather well. The most difficult time I had was getting the mail server integration working right. I suspect that it's probably come a long way since I used it (2 years now) and when I did use it it really gave me no problems.
A good web/other interface for administration would have been very useful, but what was there at the time was utter crap.
BTW: PostgreSQL backend.
Florin Andrei wrote:
I am currently using Cyrus IMAPd, and been using it for a long time, the main reason being that I want an IMAP server with nice server-side filtering, which Cyrus provides via Sieve. Given that Sieve is integrated with Squirrelmail, all is good.
have you tried Dovecot? it seems a lot simpler and easier to setup and manage than Cyrus. I believe it has optional database integration. Dovecot also supports Sieve, also, although I've never used this, http://wiki.dovecot.org/LDA/Sieve
Dovecot also is bundled with CentOS 4 and later, I dunno about CentOS 3.
Florin Andrei wrote: ...
And today I noticed that DBMail uses Sieve. Very nice!
...
What's the advantage of using sieve compared to procmail?
Mogens
On Sun, 04 Nov 2007 19:53:17 +0100 mouss mlist.only@free.fr wrote:
Mogens Kjaer wrote:
Florin Andrei wrote: ...
And today I noticed that DBMail uses Sieve. Very nice!
...
What's the advantage of using sieve compared to procmail?
syntax! procmail syntax resembles nothing else.
Sieve is a library, integrated into lmtpd, while procmail is a standalone process (and eats resources).
John R Pierce wrote:
Christopher Chan wrote:
Sieve is a library, integrated into lmtpd, while procmail is a standalone process (and eats resources).
I thought eating resources was a feature of procmail?
I didn't think procmail ate significantly more resources than any other delivery agent ?
procmail chews more memory and cpu processing power than any other delivery agent I know of. It chews more than maildrop does. It definitely chews more than the ld agents of sendmail, postfix and qmail.