problem is you have to provide a high available mysql cluster, to ensure all services running. when you run a single instance of mysql an the service crashes, the whole mailsystem is dead too...

Another advantage of the solution is, that is much easier to run the services on different machines as it is with hash tables

Hi!

Thank you for your interesting reply.

Hmm, I am working with an ISP and we are hosting x00(0) postboxes and aliases - based on Postfix/Cyrus/mysql.
The mysql-server is running on the same machine in these cases. We never encountered serious problems with that. Only luck?

Kind regards, Jens

Hi jmeyerdo

hope I didn't understand this wrong. I also would like to see a super duper open source control panel - tomorrow if possible...

my personal pros/contras:
- flatfiles/hashtables are independent: if mysql for any reason falls out (or has a small downtime) not everything is stopped. For clustered databases this is not a problem.
+ handling would be easier: the data don't have to be held on two (or three: userdb for courier) places.

BTW: AFAIK SysCP runs like this

/J

We never encountered serious problems with that. Only luck?

No not only luck. MySQL is a very stable application.
But I am not as courageous as you. And my mailservices are distributed on more than one server...

Yes, I know - "keep the reality".

But: The dovecot-change/configuration is one major step in this direction. IMHO this is more secure than changing hash-files regularly... But I understand the probably problems with mysql-errors also.

Kind regards,

Jens

This post was last modified: 10-24-2007 07:01 PM by jmeyerdo.

For me a solution where the admin can choose "hash files" or "db based" would be really great - and if more than one pop/imapserver is supported it's even better (I like dovecot very much). This would support the idea of freedom :-)
But it's a hard way to get there...

At least we could focus on such a target???

/J

i totaly agree with you joximu.

So, lets make the ispCP 2.0 version the real modular one I will spent my spare time, and my brain on this goal. And as i said to rats. I will code

perhaps i did something wrong, but after installing dovecot, all my Outlook Clients didn't work anymore.

First thing i've found: most Outlooks, especially Outlook Express don't send a full qualified domainname and therefore are not able to send mails. (Postfix problem)

Second: Outlook prior to Outlook 2007 need also a modification on the dovecot.conf ->

mechanisms = plain login digest-md5

plz post some logfiles... Whitout them we cant help you...

I don't need help anymore... i helped myself

The Problem with the full qualified domainname is posted elsewhere in the forum (postfix related).

The other problem, with the authentication belongs to dovecot and give the the solution in my first post:

mechanisms = plain login digest-md5

because in your HowTo you write only:

mechanisms = plain <- that doesn't work for my Outlook clients (Thunderbird works fine)