Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!Germany.EU.net!wizard.pn.com!news1.channel1.com!tick From: mcgovern@spoon.beta.com (Brian McGovern) Newsgroups: comp.os.386bsd.questions Subject: Re: Setting POP on FreeBSD Date: Thu, 12 Jan 95 21:46:35 GMT Organization: Channel 1 Communications Lines: 52 Distribution: world Message-ID: <3f47gu$3n7@news1.channel1.com> References: <3ed6l3$kpk@sundog.tiac.net> <3ed7tu$i4n@agate.berkeley.edu> <D22H5q.53L@indirect.com> <3eovvj$j8g@sundog.tiac.net> NNTP-Posting-Host: 199.165.180.34 To: jkh@violet.berkeley.edu X-Newsreader: News Xpress Version 1.0 Beta #2 I've seen exactly the same problem (or almost). My POPD will delete messages, but it makes the mailbox like 542MB (or some large size) without actually allocating the space on the disk. Either that, or, if I fiddle with some options, will exit with a zero return code (as checked by echo $? in bash). Popper will always do the later (ie - exit with a 0 return code) no matter how much I play with it. Perhaps, Jordan, you could share your MH config file, or better yet, uuencode your popd and ship it to us? *begs* I've been trying to get the popd with mh-6.8.3 (from the ports dir, with patches) working for weeks now, and I just keep running back and forth. Thanks, Brian rick@vox.trystero.com (Richard E. Nickle) wrote: >In article <D22H5q.53L@indirect.com>, Barnacle Wes <wes@indirect.com> wrote: >>Richard E. Nickle <rick@vox.trystero.com> reported: >>> POP doesn't know how to delete messages properly. I hacked on it for >>> some time and managed to fix some cases, but I haven't fixed them all >>> yet (I sorta gave up for the time being). >> >>Jordan K. Hubbard (jkh@violet.berkeley.edu) wrote: >>: Are you sure of this? Are you sure you're not using MH's POP support >>: without the -truncate flag to inc? I use pop almost every day and it >>: truncates the mailbox just fine! >> >> >>Telnet to the pop server manually, delete a message in the middle, and >>quit. Check the mailbox to see if the message has been deleted. (Ain't >>"chatty" protocols wunnerful?) It is always important to isolate client >>vs. server bugs in client-server systems. ;^) > >Hey, no, this is exactly how I found the problem. I don't have a POP >client for FreeBSD, so I was testing it with telnet, to make sure it >worked before my friend tried using a client from a DOS box. > >>I've been working with a recent version of popper on FreeBSD 1.1, and now >>with the "qpop" package for FreeBSD 2.0 from the CD-ROM, and have not >>encountered this problem at all. > >I still got it. > >Think I'll recompile it yet again, maybe I got another problem. I've >tried three versions (a pop3 I pulled from ftp.uu.net, the qpop from >the ports directory on FreeBSD, and the original (unpatched) qpop that >they ported. > > >-- >-- >Richard Nickle http://www.trystero.com/rick.html