From owner-freebsd-questions@FreeBSD.ORG Mon Aug 15 17:39:21 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 991E6106564A for ; Mon, 15 Aug 2011 17:39:21 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout029.mac.com (asmtpout029.mac.com [17.148.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id 819608FC12 for ; Mon, 15 Aug 2011 17:39:21 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp029.mac.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LPZ00LABD1DBN30@asmtp029.mac.com> for freebsd-questions@freebsd.org; Mon, 15 Aug 2011 10:39:14 -0700 (PDT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813,1.0.211,0.0.0000 definitions=2011-08-15_05:2011-08-15, 2011-08-15, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1108150185 From: Chuck Swiger In-reply-to: Date: Mon, 15 Aug 2011 10:39:13 -0700 Message-id: References: To: alexus X-Mailer: Apple Mail (2.1084) X-Mailman-Approved-At: Mon, 15 Aug 2011 17:49:29 +0000 Cc: freebsd-questions@freebsd.org Subject: Re: looking for a spammer/virii/malware .... on my system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2011 17:39:21 -0000 On Aug 15, 2011, at 10:05 AM, alexus wrote: > what else can I do to find it on my system who's trying to connect to > remote webmail.west.cox.net ? Monitor your network for SMTP traffic: tcpdump -nA -s 0 port 25 If malware is sending out spam, you'll see it and can then use lsof or whatever to identify the specific user/process. Regards, -- -Chuck