From owner-freebsd-questions Tue Jun 6 10:18:31 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail2.wmptl.com (mail2.wmptl.com [216.221.73.131]) by hub.freebsd.org (Postfix) with ESMTP id 03C6737B69B for ; Tue, 6 Jun 2000 10:18:19 -0700 (PDT) (envelope-from webmaster@wmptl.com) Received: from wmptl.com ([10.0.0.168]) by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id NAA51499; Tue, 6 Jun 2000 13:27:30 -0400 (EDT) (envelope-from webmaster@wmptl.com) Message-ID: <393D3211.15CBF133@wmptl.com> Date: Tue, 06 Jun 2000 13:17:05 -0400 From: Nathan Vidican Reply-To: webmaster@wmptl.com X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: keith@mail.telestream.com Cc: questions@freebsd.org Subject: Re: Popper errors. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG keith@mail.telestream.com wrote: > > After setting up a mail server with about 500 accounts on > it Some of the pop logs are curious. I've never seen these errors before > and would like some hints as to what to look at to resolve the issue. I > initialy thought it was just that there were to many pop requests over the > default allowable access time so I put the following into inetd.conf > > pop3 stream tcp nowait.60 root /usr/local/libexec/popper > popper > > That didn't seem to be the issue since I still get the errors. There are > two types of errors occuring. Not on all accounts mind you, just seems to > be a random thing. Here are the two errors. > > rervega@[209-128-77-041.bayarea.net]: -ERR POP EOF received > visitor1@[209-128-77-058.bayarea.net]: -ERR POP timeout > > Machine: FreeBSD 4.0-stable > Sendmail: 8.10.0 fresh source install > popper: popper installed from ports > Using these FEATURES in my m4 builds > FEATURE(`use_cw_file')dnl > FEATURE(`virtusertable', `hash -o /etc/mail/sendmail.domains.db')dnl > FEATURE(`access_db', `hash -o /etc/mail/sendmail.access.db')dnl > > Keith > > ================================= > Keith W. > > At the helm > ================================= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message I had similar errors when using popper, also some noted security holes with popper. We switched over to using cucipop instead, it runs as standalone, (no more need for inetd round' here), and has yet to give me any trouble(s). It's in the ports collection, all you need to do is envoke '/usr/local/libexec/cucipop -Y' on startup, and it works great. -- Nathan Vidican webmaster@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message