Spamd

[Jos Chrispijn]

Sergey V. Dyatko:
> use `sockstat -l4 -p783` instead. It show you what user-command-pid 
> listen that port

I killed process 1402 and started Spamd. That did the trick, thanks!

I am very curious:

a. why Perl occupied that port.
Tried to retrieve this information from logfiles in /var/log but no 
success. May that be an inward traffic issue on port 783 that triggered 
Perl and kept it occupied for Spamd?

b. Is it unsafe or possible to let spamd use another port if 783 is 
occupied. May that be a security risk?

T|hanks for your help,
Jos Chrispijn