From owner-freebsd-ports Sun Aug 13 08:01:25 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id IAA26225 for ports-outgoing; Sun, 13 Aug 1995 08:01:25 -0700 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id IAA26201 ; Sun, 13 Aug 1995 08:00:52 -0700 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id PAA01516 ; Sun, 13 Aug 1995 15:55:28 +0100 X-Message: This is a dial-up site. Quick responses to e-mails should not be relied upon. Thanks! To: "Jordan K. Hubbard" cc: markm@freebsd.org, ports@freebsd.org Subject: Re: All is not well with the MH port.. In-reply-to: Your message of "Sat, 12 Aug 1995 19:02:59 PDT." <199508130202.TAA12027@time.cdrom.com> Date: Sun, 13 Aug 1995 15:55:25 +0100 Message-ID: <1511.808325725@palmer.demon.co.uk> From: Gary Palmer Sender: ports-owner@freebsd.org Precedence: bulk In message <199508130202.TAA12027@time.cdrom.com>, "Jordan K. Hubbard" writes: >Even with pop, it doesn't look like -rpop works properly; it technically shoul >d >authenticate via your .rhosts, but does not. I have popper built to allow >such authentication, for what it's worth, but without a working apop or >rpop it's impossible to have "unattended operation" with inc - something >that's necessary if you want to use MH+pop with a front-end like mh-e >or xmh (since there's no opportunity to type a password). >Any other MH enthusiasts out there who might like to work with me on >trying to fix this mess? :-) I'll help where possible. I've already looked quickly at some of the issues, and it seems that the supplied FreeBSD config file is non-ideal. We should probably have ``options POPSERVICE='"pop3'"'' in there also, as you have to delve into /etc/services otherwise... Gary