[Dovecot] Fresh Dovecot Install

[John Schettino]

I tried that, didn't work for me and I was too lazy to figure out why -
the symlink worked however.
On Tue, 2005-04-26 at 12:53, Robert Cooper wrote:
> Or, just edit the /etc/init.d script to call dovecot in 
> /usr/local/sbin/....save making the symlink....
> 
> John Schettino wrote:
> > Yep - I did a source install *after* installing the Fedora Core 2
> > version (.99something) via yum.
> > 
> > You may have better luck doing that if you can find an RPM for dovecot
> > for RH9 - then all you'll need to do is make a symlink from
> > /usr/sbin/dovecot (move aside the RPM version first) to
> > /usr/local/sbin/dovecot (your built-from-source version) after you make
> > install dovecot from source, and the service scripts for the Redhat
> > dovecot build will (probably) work.
> > 
> > On Tue, 2005-04-26 at 12:34, Jakob Curdes wrote:
> > 
> >>>I get nothing when I:
> >>>
> >>>rpm -qa | grep dovecot
> >>>ps aux | grep dovecot
> >>>service dovecot status
> >>>
> >>> 
> >>>
> >>
> >>I suppose you are expecting that after doing a "make install", the 
> >>application already runs, like you are used from rpm installs ?
> >>That will not be the case. I am not even sure if the dovecot install 
> >>process places a start/stop script in /etc/init.d. Often you have to do 
> >>many things on your own after a source install, like adapting or 
> >>creating a start/stop script or copying and modifying a sample 
> >>configuration file. That's what Mark pointed out : you should probably 
> >>at least go through the provided configuration file and then you can try 
> >>and start dovecot by hand and observer the relevant logfiles, depending 
> >>on your dsitribution. If you find that all works well, you can use the 
> >>start/stop mechanism to integrate dovecot startup into your system 
> >>startup. Sorry, but when compiling source packages you have to "RTFM" 
> >>and adapt the explanations to your configuration.
> >>
> >>If you configured dovecot and started it and it fails to run, start it 
> >>from the command line and watch out for fatal errors on STDOUT or in the 
> >>logs. Most probably the ports are in use by another pop/imap program.
> >>
> >>Hope this helps,
> >>Jakob Curdes
> >>
> > 
> >