From owner-freebsd-questions@FreeBSD.ORG Sat Apr 26 19:58:21 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 441821065673 for ; Sat, 26 Apr 2008 19:58:21 +0000 (UTC) (envelope-from chris@chrismaness.com) Received: from nlpi101.prodigy.net (nlpi101.prodigy.net [207.115.36.117]) by mx1.freebsd.org (Postfix) with ESMTP id 0CF5D8FC14 for ; Sat, 26 Apr 2008 19:58:20 +0000 (UTC) (envelope-from chris@chrismaness.com) X-ORBL: [76.238.148.145] Received: from adsl-76-238-148-145.dsl.irvnca.sbcglobal.net (adsl-76-238-148-145.dsl.irvnca.sbcglobal.net [76.238.148.145]) by nlpi101.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id m3QJwIEW008199; Sat, 26 Apr 2008 14:58:19 -0500 Date: Sat, 26 Apr 2008 12:58:18 -0700 (PDT) From: Chris Maness X-X-Sender: chris@ns1.kq6up.org To: Jeffrey Goldberg In-Reply-To: <8B5240D5-EC66-468F-BE44-27BE9928F4E3@goldmark.org> Message-ID: References: <8B5240D5-EC66-468F-BE44-27BE9928F4E3@goldmark.org> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD List Subject: Re: Pine Corupting Inbox X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2008 19:58:21 -0000 On Sat, 26 Apr 2008, Jeffrey Goldberg wrote: > On Apr 21, 2008, at 12:53 PM, Chris Maness wrote: > >> I think that pine is corrupting my inbox, so that it is unreadable by >> UW-IMAPD. When using squirrelmail after using pine I see the headers, but >> squirrelmail is unable to open the e-mails. > > When you read your mail with (al)pine with it picking up mail directly from > /var/spool/mail, (al)pine will move the mail from /var/spool/mail into > mailbox folders in your home directory. > > Now normally, this puts the mail in a place where it can still be picked up > by uw-imap server. Indeed, under default configurations the uw-imap server > will perform pretty much the same action when it gets new mail out of > /var/spool/mail. So when everything is working right, even reading the mail > locally with pine shouldn't mess things up as they have for you. > >> I switched over to alpine since I do understand that pine is no longer >> supported. If other people have experienced this it would be nice to have >> at least a notice when it is installed. I have used pine for almost 10 >> years without this problem, but maybe this is an incompatability with a >> newer version of UW-IMAPD. > > Here is what I would do to start diagnosing my first guess at the problem: > > (1) Set up (or use) a clean vanilla user account, say fred. > (2) Send fred mail. > (3) log in as fred and have fred read mail with pine, with as close to a > default configuration as possible. > (4) See if fred can see his mail via squirrelmail. If so > (5) Look around ~/fred to find where pine put the mail. > (6) Compare the mail file locations for ~/fred and for you. > (7) If there are difference (which is what I'm expecting), then look through > your .pinerc > > Post back a report about how those steps go. If things break at step 4, then > still do step (5) and report that back here. > > Good luck. > > Cheers, > > -j > > > -- > Jeffrey Goldberg http://www.goldmark.org/jeff/ > I'll check it out. Alpine is doing the same thing. It worlks fine for a bit, an then no imap clients can access the mail. Only alpine can read the spool. I am not having any problems whith other users, I will have to try to test the spool with a fresh user like you suggested. I might use aliases to send mail to this account as well. Chris Maness (909) 223-9179