Date: Tue, 8 Apr 1997 22:54:19 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Cliff Addy <fbsdlist@federation.addy.com> Cc: questions@FreeBSD.org Subject: Re: ipop3d, pine, and large mail files Message-ID: <Pine.BSF.3.96.970408224735.3224K-100000@localhost> In-Reply-To: <Pine.BSF.3.95q.970407161625.13430A-100000@federation.addy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Apr 1997, Cliff Addy wrote: > I'm having a problem with ipop3d and pine dealing with large mail files. > For example, I had a user named em111 and the /var/mail/em111 file was > around 15 megs. Both ipop3d and pine blew up for this user after chewing > up 200 megs of virtual memory. It really surprised me that ipop3d would > even be *trying* to read the entire file into RAM. This should be taken up with the UWash (or whomever) people, since it's in their software. (I know it sounds like "blame them!"...) I can corroborate this sort of problem to SunOS systems -- our Sun SPARCenter 1000 mailserver will choke pretty badly if the mailspool > 2mb or so. Thus, we have 1mb quotas on the /var/mail filesystem to prevent such abuses of the mail system. > Regardless, it seems on a system with 30 megs free RAM and 200 megs of > virtual that pine or pop3d should not need more memory than that. Is > there a misconfiguration here? I'm guessing it gets stuck in an endless loop. Generally, pop will copy messages from the mailspool to a temp file as they are sent. It may be overflowing that copy. You should mention this to UWash or whomever provided you with ipop3d. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970408224735.3224K-100000>