I'm afraid that on a busy server, iRedAPD may establish too many SQL connections to SQL server (and close them immediately when request finished), this causes it reaches max connection set in PGSQL server. The questions are:
*) Is your mail server busy? process how many emails per-day?
*) What's the max connection number set in PGSQL server?
Thanks for your reply Zhang. Im really sorry that i havent seen your post until now. This could have save me a lot of work.
I think that your right. After I updated my iredap daemon like 7t3chguy sugested I keep checking my iredap.log and it keep doing the same:
2015-04-09 11:34:40 ERROR Error while creating Amavisd database connection: FATAL: remaining connection slots are reserved for non-replication superuser connections
2015-04-09 11:34:44 ERROR Error while creating Amavisd database connection: FATAL: remaining connection slots are reserved for non-replication superuser connections
I think check that this only happens when a mail was sent from a mail list (Mailman). So I figure out the same thing that you told here (iRedAPD may establish too many SQL connections to SQL server). So I check the max connection set in PGSQL server and it was of only 100. I replace it for 200 (the number that I use on my other IredMail, wich works great).
Lets see if this solves the problem for good.
Thanks to both of you by your time.
And by the way IredMail rocks.
Greetings from Cuba