Carbonio Server Sto...
 
Notifications
Clear all

Carbonio Server Stopped Delivering Emails

6 Posts
2 Users
0 Reactions
377 Views
(@salah)
New Member
Joined: 9 months ago
Posts: 7
Topic starter  

I installed Carbonio CE 25.0, and it work.

Recently, it stopped delivering emails; emails stuck in Queue and not delivered to destination, not locally on server, not to external servers (such as Gmail).

With command:

/opt/zextras/common/sbin/postqueue -p

yield error:

(connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

or:

(delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

How to fix it?


   
Quote
(@sharif)
Honorable Member Admin
Joined: 4 years ago
Posts: 965
 

@salah

Let us know some more details:

  1. What OS you are using?
  2. Status of following commands: systemctl list-units carbonio*
  3. Any possible log on /var/log/carbonio.log

   
ReplyQuote
(@salah)
New Member
Joined: 9 months ago
Posts: 7
Topic starter  

OS : ubuntu 24.04

Carbonio CE : 25.0

 

I solved problem by:

1- reboot server

2- started some carbonio services manually after reboot

3- modified cloud.ini configuration file to not restore defaults on /etc/hosts file after reboot

4- added server public IP address and FQDN to /etc/hosts file

then normal email service restored.

I don't understand what caused service blocking at first, because it happened suddenly ?


   
ReplyQuote
(@sharif)
Honorable Member Admin
Joined: 4 years ago
Posts: 965
 

@salah 

/etc/hosts is a very critical configuration in Carbonio CE scenario. When /etc/hosts loses the FQDN to IP mapping, Amavis (like many other sysrtem components) fails to resolve its own hostname at startup (it reads $myhostname which depends on proper FQDN resolution). And With Amavis down, Postfix cannot deliver to 27.0.0.1:10024, so all mail queues up.

As you have resolved the issue, for future I would suggest you to disable cloud-init's /etc/hosts management. It would avoid unnecessary issues after each reboot.

 


   
ReplyQuote
(@salah)
New Member
Joined: 9 months ago
Posts: 7
Topic starter  

I did.

The server is a cloud server, and I excluded /etc/hosts file from cloud.ini service intervention.

 

But what I want to understand what caused email accounts to become in-accessable in first place, that it happened suddenly.

users were able to reach login page online, but suddenly cannot login their credentials on.

Is there a log file to check to get clue what happened?


   
ReplyQuote
(@sharif)
Honorable Member Admin
Joined: 4 years ago
Posts: 965
 

@salah 

Try looking at following logs:

/opt/zextras/log/mailbox.log

/opt/zextras/log/nginx.error.log (upstream issues),

 


   
ReplyQuote