From owner-freebsd-ports@FreeBSD.ORG Thu Apr 3 12:57:16 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DA43747 for ; Thu, 3 Apr 2014 12:57:16 +0000 (UTC) Received: from thetys.cloudzeeland.nl (webrz.xs4all.nl [83.161.133.58]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "cloudzeeland.nl", Issuer "PositiveSSL CA 2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B6AD9C5 for ; Thu, 3 Apr 2014 12:57:15 +0000 (UTC) Received: from thetys.cloudzeeland.nl (thetys.cloudzeeland.nl [10.10.10.31]) by thetys.cloudzeeland.nl (Postfix) with ESMTP id 2D49C164459A; Thu, 3 Apr 2014 14:55:42 +0200 (CEST) Received: from [10.10.10.70] (iMacJ.cloudzeeland.nl [10.10.10.70]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by thetys.cloudzeeland.nl (Postfix) with ESMTPSA id 08860164457D; Thu, 3 Apr 2014 14:55:42 +0200 (CEST) Message-ID: <533D5AA9.4000904@webrz.net> Date: Thu, 03 Apr 2014 14:57:13 +0200 From: Jos Chrispijn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "Sergey V. Dyatko" , FreeBSD Ports ML Subject: Re: Spamd References: <533D1366.7030607@webrz.net> <20140403110103.0b51d9fc@laptop.minsk.domain> In-Reply-To: <20140403110103.0b51d9fc@laptop.minsk.domain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on thetys.cloudzeeland.nl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 12:57:16 -0000 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