On 04/16/2012 01:15 PM, Eric Shubert wrote:
On 04/13/2012 07:20 PM, Casey Price wrote:
Eric,
Thanks for pointing this out. So while this give you the ability to
effectively "cc" every message sent/received by an individual user or
domain, it doesn't really appear to go above and beyond that. To be
honest, I really don't have any experience with archival solutions so
maybe my expectations are in the wrong place - however it seems like you
would need another component to be able to offer an archival solution,
doesn't it? Some form of management system for one - and then a way to
designate what you wanted archived.
For example, when I hear the word archive a few different things come to
mind:
1) Individuals or companies that need to keep an absolute record of
everything - TAPS is probably ideal for this (especially because it is
transparent to the user)
2) People that want to save certain things for a long period of time,
but don't need everything saved.
Right now I have some customers with mailboxes right around 2GB on a
server using Courier (I've installed Dovecot and got everything ready to
migrate, just reluctant to do so in the event that it screws up all of
the client subscriptions and causes mail to be re-downloaded). This
server has plenty of room to grow, but eventually people will get to the
point that either their mailboxes are so large that they become slow to
access, or I will end up with a very very full server (both of which are
likely to happen down the road some time from now, but it is something
I'd like to address before it becomes a problem).
So I suppose my true question here is, what are my best options to
consider when trying to build a system that needs to be robust and meet
the needs of the customer as technology changes?
Casey Price
I think your concerns about large mailboxes will become unfounded once
you get dovecot implemented. I've seen mailboxes in excess of 6G with no
problems.
When it comes to managing email, I don't think there's a "one size fits
all" solution. If you can define what your requirements are, I expect
that it wouldn't be very difficult to implement a solution.
That being said, I've not seen MailArchiva at all. It might make a nice
addition to QMT at some point.
Just scanning real quick and wanted to drop a note for the archives - if
you get into large mail stores (I'm talking >5TB of mail on the small
side), you'll be looking at some type of storage array to store the mail
on, and access using NFS or similar. In these cases, you'll want to use
the mbox format versus maildir. mbox's large file method is more
manageable by back end storage arrays versus maildir (NFS getattrs,
lookups, etc. are expensive in resources for the backend system/array).
Depending on what solution you use for your backend storage will
determine when/if you need to make that change.
And for those interested, I'm currently working on a 8 million user
Qmail installation, with >90TB of email stored. Performance is
interesting on this setup, and the smallest change affects exponentially.
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
