On Tue, 2002-07-30 at 12:02, daniel wrote:
| Why didn't you just install Redhat's pop3 server rpm (actually it's the
| imap rpm). It the UW pop3 package and would have saved you the trouble of
| building it and perhaps not including something needed?
'cause i'm "practicing" for a linux build on a machine that won't be big
enough for a redhat install. besides, i want to learn how to do things from
source and not be dependant of pre-made packages. it breeds problems just
like this one where i don't know what kind of authorisation my machine is
using and should use for pop3.
What constitutes "not big enough"? Before you spend too much time on
this project, you should probably realize that the time you're going to
put into getting sendmail and IMAP on this small machine is going to
cost you more than the system requirements of Red Hat Linux.
I'd also suggest that you re-examine your assertion that pre-made
packages breed problems "like this one". While true from a point of
view, the whole picture is bigger than that. Building an OS (or even
just the services on one) from source requires a great deal of
understanding about how the system functions, and how *everything* is
supposed to work together. A good system engineer knows more than how
to make things work: he knows how to make things work *right*.
I don't mean to discourage you from learning... I just think you're not
starting in the right place. Get Red Hat's src.rpm for the imap
package, and read the spec file. Read the patches. Understand what
they've had to change to make imap work properly on Linux, and how they
go about their build process.