This is really like going back to basic.
DBmail's data model is not perfect the way it is right now. At
insertion time the data should be stored structured, this would make
any daemon for mail retrieval and storage faster than any filesystem
solution. We're not there yet since this will need quite a big code
change. Speed isn't the only big issue that DBmail is trying to solve.
Manageability, scalability and security are at least as important.
We have a site running dbmail with about 30.000 accounts and 12 Gbyte
of maildata. It's running smooth and there are never any complaints
from customers. We're also setting up a freemail site which uses dbmail
as its engine. For us this is the only way to really test dbmail in
high performance area's.
Speed hasn't been an issue for us since 1.0rc3 :)
Why do you want to store on the fs? (with all security and locking
problems involved?)
Best regards,
Eelco
On woensdag, maa 19, 2003, at 04:17 Europe/Amsterdam, Blake wrote:
Yeah, I dislike current IMAP servers exactly for the reasons you list
here. I think one file per message is the only reasonable mode of
operation. It would be best to tune the message store file system for
small inode size, and avoid the problem of large directories by
storing the messages in an /ab/cd/ef/gh type hierarchy. They would be
useless on their own, just a big soup of messages without the > database.
Ryan Butler wrote:
Flat files on large mailboxes are terrible performers. It might read
sequentially faster, but try removing a message from the middle of the
flat file...
Not to mention how inflexible it is.
There's patches to qpopper and uw-imapd that allow you to use a sql
auth
system with them. Maybe one of those would be better suited to what
yoour goal is. (Its what I ran previous to switching to dbmail)
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_________________________
E.J.A. van Beek
ICT Manager
IC&S
T: +31 30 2322878
F: +31 30 2322305
PGP-key:
www.ic-s.nl/keys/eelco.txt
