Resolved Does Plesk have it's own hidden version of poppassd running?

[Richard18]

12.5.30 #42 on Ubuntu 14.04, I don't have the poppassd package installed but poppassd still answers on port 106.

Any ideas why?

 

[IgorG]

What is output of command

# lsof -i tcp:106

?

 

[Richard18]

What is output of command

# lsof -i tcp:106

?

Thanks for the reply.

COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
xinetd  6289 root    6u  IPv6 440667      0t0  TCP *:poppassd (LISTEN)

 

[IgorG]

# cat /etc/xinetd.d/poppassd_psa
#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST AFTER YOU UPGRADE PARALLELS PLESK PANEL.
service poppassd
{
socket_type = stream
protocol = tcp
port = 106
wait = no
disable = no
user = root
instances = 1000
flags = KEEPALIVE IPv6
server = /usr/local/psa/admin/sbin/poppassd
}


# rpm -qf /usr/local/psa/admin/sbin/poppassd
psa-mail-driver-common-12.5.30-cos6.build1205150826.19.i686

As you can see poppassd is a part of psa-mail-driver-common Plesk package.

 

[Richard18]

Can it be disabled? We don't run any external facing mail services on the server, just need mail internally for things.

 

[IgorG]

disable = no

Just set it to "yes"

 

[Richard18]

Thanks, can I ignore "DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY"? The changes will be kept?

 

[IgorG]

Thanks, can I ignore "DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY"? The changes will be kept?

You can try at least. I think it may be overwritten if psa-mail-driver-common package will be updated in microupdate, or something else.

 

[Richard18]

Thanks for the help, I'll make the change and just keep a look out for it in the future.

 

[G J Piper]

You could also just block the incoming port 106 at the firewall. Then, if it does get re-enabled during an update it will be inconsequential.