Spamd

[Matthew Seaman]

On 04/03/14 13:57, Jos Chrispijn wrote:
> 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?

Assuming 'spamd' here is part of spamassassin then it is a daemon
written in perl, and the command name will show up as perl in sockstat
listings.

In my experience, it is quite common for this daemon to end up running
under a different PID than the one recorded under /var/run -- so the
system initialization scripts 'sa-spamd' think it isn't running, and
then you get the fight over access to port 783 the OP saw.  Killing the
processes using port 783 and restarting spamd should work.

The situation is complicated by the /other/ spamd -- which is an OpenBSD
thing which works via pf to implement greylisting, teergrube and various
other anti-spam things.  Meaning the SpamAssassin 'sa-spamd' startup
script can't simply kill anything called spamd.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1029 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20140403/c3d98749/attachment.sig>