Re: [Mailmanager-users] MailManager 1.1rc5 gets slower as more email gets received

[Andrew V. <an...@lo...>]

The reason we went through the pain of changing MailManager over to  
using a relational database was precisely because the old  
architecture couldn't handle large volumes of email - which was a  
fairly crucial flaw!

We are planning on getting MailManager 2.0.5 out Friday 16 December.  
There are quite a few MySQL bug fixes in that release.

A

On 13 Dec 2005, at 16:03, John David wrote:

> Ron, we are in the same boat.  The additional installation and  
> administration of Postgre for just one program is not something we  
> can easily undertake right now.  Every other app used by our  
> servers is based on MySQL.  I tried migration too, (which failed)  
> and figured I could bite the bullet and convince everyone at our  
> organization to start fresh with no email data, if MySQL just  
> worked ok -- but it appears that the problems preventing migration  
> are the same ones preventing MySQL from importing Unicode  
> characters from international emails, etc.
>
> Our company sends and receives design files and other attachments  
> that are generally 1 to 5 MB in size, which doesn't account for all  
> of our email traffic, but in terms of overall storage, it is a  
> large proportion of the total correspondence.  This might warrant a  
> more frequent purging of archived messages, but at least it would  
> be using MySQL rather than a Data.fs file to store all this  
> information more efficiently.
>
> Maybe in the future a script could be used to strip the MIME  
> attachments from the messages, (since we usually keep the design  
> files on a separate fileserver once they are received).  That way  
> we would retain a record of the text of the message at the very  
> least.  Not high on our priority list, though -- right now we just  
> want MM running stable with our large volume of email!
>