POPIMAPDaemon Dead

Hi UJay Thank you for connecting with the Sophos community team, You may check the warren.log, csc.log, and applg.log to get the clue. Please validate below old thread steps if any log lines matches.

https://community.sophos.com/sophos-xg-firewall/f/discussions/98766/upgrade-from-17-mr1-to-mr2-breaks-imappop-daemon

I would also suggest opening a support case to work on the same to have the next investigation.

Hi Vishal

I have already open a support case and they are working on it but so far no positive outcome. 

BR

Uditha

Did you get any feedback on the problem? Well, this error happened to me too.

I still haven't got a proper solution from them. One of the support personnel collected logs and went off but so far no resolution. I have downgraded it to previous firmware version and it helps to run without that error. 

The support personnel told me that this issue has reported by a few others too. May be you should also create a support request. Then SOPHOS engineers will wake up from the hibernation to develop a resolution.  

I am disappointed about the lethargic support response they have

Here is the solution I found in the link below.

(+) POPIMAPDEAMON is dead after updating to SFOS 19 - Discussions - Sophos Firewall - Sophos Community

The solution was to do the following steps.

1. Chang the CA settings

• Login to your Sophos XG
• Go to Certificates
• Go to Certificate authorities
• Click on edit by the CA called Default
• Set here state, company and mail
• Save

2. Regenerat the ApplianceCertificate

• Go to Certificates
• Click on the gear behind ApplianceCertificate
• Accept the popup message

3. Start the warren service

• Start an SSH connection
• Open the advanced shell
• service warren:start -dsnosync

After that the service is running without any problems.

The solution was to do the following steps.

1. Chang the CA settings

• Login to your Sophos XG
• Go to Certificates
• Go to Certificate authorities
• Click on edit by the CA called Default
• Set here state, company and mail
• Save

2. Regenerat the ApplianceCertificate

• Go to Certificates
• Click on the gear behind ApplianceCertificate
• Accept the popup message

3. Start the warren service

• Start an SSH connection
• Open the advanced shell
• service warren:start -dsnosync

After that the service is running without any problems.

I tried just following these mentioned steps and they failed.

Then I reversed the firmware to version 18 and executed said steps. Thereafter i moved back to firmware version 19. This time, i was able to get the POPIMAPDaemon back onto working status. 

Hello UJay,

Also ensure to: 

>> Navigate to Certificates >> Certificate Authorities >> Default >> Fill in the blank Certificate details appropriately.

>> Start the service again.  "service warren:start -ds nosync"