default settings for IMAP-connections too low

[Frater]

For a long time Plesk has ludicrously low default settings for its IMAP.
We don't even have that many domains on our server.....

Some people even wrote a tutorial to fix this:

http://kb.mediatemple.net/questions/259/How+can+I+raise+Courier-IMAP+connections+for+my+server?#dv

After installing Plesk I raised these values in /etc/courier-imap/imapd

A week ago we're all of a sudden getting complaints of customers that their mail isn't working.
It turned out that on May 2nd @ 4:13 AM Plesk updated this file and wrote these strange default values back in again.

How can I prevent this from happening in the future?

 

[EdwardDekker]

Hi,

You could add more instances to your courier-imapd config.
Than will there more resources free of your mailserver.

The configuration files can be found at:
/etc/courier-imap/pop3d
/etc/courier-imap/imapd

Adust the settings to:

MAXDAEMONS=128
MAXPERIP=256

Or double the value to 256 / 512 if necessary.

 

[Frater]

Thanks for your reply, but what I'm looking for is a change of the default settings of Plesk.
I already changed these values after I installed Plesk.

It turns out that Plesk can change these values at will on an update.
They did this last Tuesday morning.
These values are silly and they are there for more than 5 years.

I would like to know where those default values are stored.
Maybe they are somewhere in the database or they are hardcoded in some plesk-script.

Please, Parallels, change this!

 

[EdwardDekker]

I think that Parallels will not adjust these settings by them self.
For now it looks like that you have to edit some files to get the best results at your web server.

I hope for you that when Plesk 11 or Plesk 12 will come this feature could be build in into the mail settings.

 

[Frater]

I'm now monitoring the file /etc/courier-imap/imapd using Zabbix.
If that file changes I will get a warning...


If a client has a firm with 10 employees using IMAP and are behind a NAT-connection, they will not receive mail. And I'm not even talking about aggressive IMAP-clients....

 

[IgorG]

http://kb.parallels.com/en/113841

 

[Frater]

....again information I knew already!!!!

I changed these values months ago after setting up the server.

I want to know how I can prevent Plesk from changing them back to these ludicrously low values.
Plesk did this last week.

 

[IgorG]

Are you sure that you have not performed any upgrade for your Plesk during this period? What is version and MU you have?

 

[Frater]

Are you sure that you have not performed any upgrade for your Plesk during this period? What is version and MU you have?

I'm sure that it DID do an upgrade (I wrote this in the original post).

It did another upgrade yesterday, so this one wasn't the culprit

10.4.4 Update #29, laatste update op Mei 10, 2012 04:09 AM

My problem is exactly with this behaviour.
Plesk changes settings in a blunt way by blindly overwriting config files.
I don't know why Plesk had to touch that config file that night, but I'm convinced it had nothing to do with these specific settings. And I want to stress again that these settings are wrong for a real world environment.

The people writing these update-scripts should work with a bit more finesse.

Now I just want to know how I can prevent this from happening.
Does Plesk have a template file where this default config is stored?

In Zabbix I'm now monitoring that file to detect modification, I will at least be notified when it happens so I can revert the change before I'm getting complaints...

 

[Frater]

I still would like to get a reply on the OP.

I'm aware Plesk has a low default setting.
I'm aware I can change this by editing the file /etc/courier-imap/imapd

I became painfully aware that Plesk can change these values back to their original ones during an update.

It's the last thing I don't agree with.

 

[tkalfaoglu]

you are very right --- it uses rpm's, so why not leave the new conf files as .rpmnew ?