Your message dated Fri, 2 May 2008 09:33:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Pkg-citadel-devel] Bug#478996: citadel-server: Began
listening on
has caused the Debian Bug report #478996,
regarding citadel-server: Began listening on 10 ports by default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
478996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478996
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: citadel-server
Version: 7.35-1
Severity: normal
I can't recall which package auto-installed citadel, but I was quite unhappy to
note that, without any prompting, it immediately began listening on 10 ports.
frodo-the-cat:~# netstat -tap | grep citserver
tcp 0 0 *:imaps *:* LISTEN
23138/citserver
tcp 0 0 *:pop3s *:* LISTEN
23138/citserver
tcp 0 0 *:2020 *:* LISTEN
23138/citserver
tcp 0 0 *:xmpp-client *:* LISTEN
23138/citserver
tcp 0 0 *:submission *:* LISTEN
23138/citserver
tcp 0 0 *:pop3 *:* LISTEN
23138/citserver
tcp 0 0 *:imap2 *:* LISTEN
23138/citserver
tcp 0 0 *:ssmtp *:* LISTEN
23138/citserver
tcp 0 0 *:citadel *:* LISTEN
23138/citserver
tcp 0 0 *:smtp *:* LISTEN
23138/citserver
I am not intimately familiar with Debian package policies, but shouldn't good
sense alone dictate that a package not listen on *any* ports unless specifically
configured to do so?
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=locale: Cannot set LC_CTYPE to
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages citadel-server depends on:
ii adduser 3.107 add and remove users and groups
ii citadel-common 7.35-1 complete and feature-rich groupwar
ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libcitadel1 1.09-1 Citadel toolbox
ii libdb4.6 4.6.21-7 Berkeley v4.6 Database Libraries [
ii libexpat1 1.95.8-4 XML parsing C library - runtime li
ii libical0 0.31-1 iCalendar library implementation i
ii libldap-2.4-2 2.4.7-6.2 OpenLDAP libraries
ii libncurses5 5.6+20080419-2 Shared libraries for terminal hand
ii libpam0g 0.99.7.1-6 Pluggable Authentication Modules l
ii libsieve2-1 2.2.6-1 a library for parsing, sorting and
ii libssl0.9.8 0.9.8g-8 SSL shared libraries
ii openssl 0.9.8g-8 Secure Socket Layer (SSL) binary a
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages citadel-server recommends:
ii db4.6-util 4.6.21-7 Berkeley v4.6 Database Utilities
ii shared-mime-info 0.23-5 FreeDesktop.org shared MIME databa
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_COLLATE = "C",
LANG = "en_US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
* citadel/Administrator: Administrator
* citadel/ServerIPAddress: 0.0.0.0
* citadel/LoginType: false
citadel/Installnote:
--- End Message ---
--- Begin Message ---
> I can't recall which package auto-installed citadel, but I was quite unhappy
> to
Probably a package that depended on mail-transport-agent while you had
none installed.
> note that, without any prompting, it immediately began listening on 10 ports.
That's its job.
> I am not intimately familiar with Debian package policies, but shouldn't good
> sense alone dictate that a package not listen on *any* ports unless
> specifically
> configured to do so?
No, it's the other way round. If a server package is installed policy
and common sense dictate that this server is fully functional. However,
it cannot do so if it does not open any port. It's your choice to not
install/deinstall it to get those ports closes. But if you do install
it, you'd expect it to work afterwards, don't you?
Anyway, this is not a bug, therefore I close it.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
--- End Message ---
