[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#119693: marked as done (ITP: popa3d -- Tiny and secure POP3 daemon)



Your message dated Fri, 21 Dec 2001 15:07:18 -0500
with message-id <E16HVws-00061z-00@auric.debian.org>
and subject line Bug#119693: fixed in popa3d 0.5-7
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Nov 2001 11:37:19 +0000
>From eloy@allegro.pl Thu Nov 15 05:37:19 2001
Return-path: <eloy@allegro.pl>
Received: from piecyk.allegro.pl [212.126.18.163] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 164Kpa-0000dp-00; Thu, 15 Nov 2001 05:37:18 -0600
Received: from lws244.allegro.pl (eloy@[192.168.88.244])
	by piecyk.allegro.pl (8.11.6/8.11.0) with ESMTP id fAFBaiX03663
	for <submit@bugs.debian.org>; Thu, 15 Nov 2001 12:36:44 +0100 (CET)
	(envelope-from eloy@allegro.pl)
Subject: ITP: popa3d - tiny & secure pop3 daemon
From: Krzysztof Krzyzaniak <eloy@allegro.pl>
To: submit@bugs.debian.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.99.0 (Preview Release)
Date: 15 Nov 2001 12:36:17 +0100
Message-Id: <1005824178.2000.0.camel@strzyga>
Mime-Version: 1.0
Delivered-To: submit@bugs.debian.org

Package: wnpp
Severity: wishlist

Package: popa3d
Version: 0.5
Upstream Author: Solar Designer <solar@openwall.com>
URL: http://www.openwall.com/popa3d/
License: BSD-like
Description: tiny and secure pop3 daemon

There're lots of different POP3 servers -- with different feature
sets, performance, and reliability.  However, as far as I know, before
I started the work on popa3d, there had been only one with security as
one of its primary design goals: qmail-pop3d.  Unfortunately, it would
only work with qmail, and only with its new maildir format.  While
both qmail and maildirs do indeed have some advantages, a lot of
people continue running other MTAs, and/or use the older mailbox
format, for various reasons.  Many of them need a POP3 server.


	The design goals.

Well, the goals themselves are obvious; they're probably the same for
most other POP3 servers as well.  It's their priority that differs.
For popa3d, the goals are:

1. Security (to the extent that is possible with POP3 at all, of
course).
2. Reliability (again, as limited by the mailbox format and the
protocol).
3. RFC compliance (slightly relaxed to work with real-world POP3
clients).
4. Performance (limited by the more important goals, above).

Obviously, just like the comments indicate, none of the goals can be met
completely, and balanced decisions need to be made.

  eloy
-- 
* QXL Poland Sp. z o.o.
* Krzysztof 'eloy' Krzyzaniak 
* <eloy@allegro.pl>, ICQ: 30855662



---------------------------------------
Received: (at 119693-close) by bugs.debian.org; 21 Dec 2001 20:08:27 +0000
>From troup@auric.debian.org Fri Dec 21 14:08:27 2001
Return-path: <troup@auric.debian.org>
Received: from auric.debian.org [206.246.226.45] (mail)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16HVxz-00051l-00; Fri, 21 Dec 2001 14:08:27 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
	id 16HVws-00061z-00; Fri, 21 Dec 2001 15:07:18 -0500
From: Krzysztof Krzyzaniak (eloy) <eloy@debian.org>
To: 119693-close@bugs.debian.org
X-Katie: $Revision: 1.66 $
Subject: Bug#119693: fixed in popa3d 0.5-7
Message-Id: <E16HVws-00061z-00@auric.debian.org>
Sender: James Troup <troup@auric.debian.org>
Date: Fri, 21 Dec 2001 15:07:18 -0500
Delivered-To: 119693-close@bugs.debian.org

We believe that the bug you reported is fixed in the latest version of
popa3d, which has been installed in the Debian FTP archive:

popa3d_0.5-7.diff.gz
  to pool/main/p/popa3d/popa3d_0.5-7.diff.gz
popa3d_0.5-7.dsc
  to pool/main/p/popa3d/popa3d_0.5-7.dsc
popa3d_0.5-7_mips.deb
  to pool/main/p/popa3d/popa3d_0.5-7_mips.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 119693@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Krzysztof Krzyzaniak (eloy) <eloy@debian.org> (supplier of updated popa3d package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 20 Dec 2001 22:07:56 +0100
Source: popa3d
Binary: popa3d
Architecture: source mips
Version: 0.5-7
Distribution: unstable
Urgency: low
Maintainer: Krzysztof Krzyzaniak (eloy) <eloy@debian.org>
Changed-By: Krzysztof Krzyzaniak (eloy) <eloy@debian.org>
Description: 
 popa3d     - A tiny POP3 daemon, designed with security as the primary goal
Closes: 119693 125979 125980
Changes: 
 popa3d (0.5-7) unstable; urgency=low
 .
   * ITP request closed (closes: #119693)
   * Spurius files (test.sh & patch.diff) removed (closes: #125979)
   * Creations & removal of popa3d user & group has changed (thanks to
     Gergely Nagy <algernon@debian.org> for suggestion; closes: #125980)
Files: 
 a66694ae7cb52fd0d6201dba690dfa30 641 mail extra popa3d_0.5-7.dsc
 7e92b55c46aa4c2b7e8492d9c2de99ee 2778 mail extra popa3d_0.5-7.diff.gz
 d3b7e1c65ca81bd1f4cc9278950d345d 23396 mail extra popa3d_0.5-7_mips.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Dalsze informacje znajduj± siê na http://www.gnupg.org/

iD8DBQE8Il01+NMfSd6w7DERAnoPAJ4sXWLeVpOOmMsvc2qbJQeWizxePgCgicLS
Ikfb8q38tXjBmO3FNJR1XQA=
=NgdQ
-----END PGP SIGNATURE-----



Reply to: