bin/64036: Linux application Sophos Mailmonitor not opening TCP port

Kris Kennaway kris at obsecurity.org
Fri Mar 26 22:50:25 PST 2004


The following reply was made to PR bin/64036; it has been noted by GNATS.

From: Kris Kennaway <kris at obsecurity.org>
To: Scott Aitken <freebsd-emulation at two-fifths.com>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: bin/64036: Linux application Sophos Mailmonitor not opening TCP port
Date: Fri, 26 Mar 2004 22:40:53 -0800

 --IS0zKkzwUGydFO0o
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 On Wed, Mar 10, 2004 at 03:31:43AM -0800, Scott Aitken wrote:
 
 > FreeBSD freebsd-01.two-fifths.com 5.2.1-RELEASE-p1 FreeBSD 5.2.1-RELEASE-p1 #1: Wed Mar  3 14:13:53 GMT 2004     root at freebsd-01.two-fifths.com:/usr/obj/usr/src/sys/OLDCARD  i386
 > >Description:
 > The Linux binaries from Sophos Mailmonitor do not open a TCP port as expected.  The application executes and runs as a daemon, but should open a port (in this case 25) in order to process mail for viruses, but it doesn't.  It does not give any errors.  I have the Linux version of Sophos Anti-virus installed as a prerequisite for Mailmonitor.
 > >How-To-Repeat:
 > Install Sophos SAV and Mailmonitor (Linux versions), start the Mailmonitor daemon ./mmsmtpd -start
 > netstat -a shows no port opened.
 
 Can you install the linux_kdump port and use it to trace what the
 daemon is doing?  It's difficult to guess what is going wrong without
 further information.
 
 Kris
 
 --IS0zKkzwUGydFO0o
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFAZSH0Wry0BWjoQKURAmmaAKCWyb/UE6ypCrn7kLQ/JjgQJ0WqyQCffLZH
 fU+2Ux1omnaRdbEpBV7EhI0=
 =RMBm
 -----END PGP SIGNATURE-----
 
 --IS0zKkzwUGydFO0o--


More information about the freebsd-bugs mailing list