So, replace courier-IMAP from "Other packages compatible with
vpopmail" on the Inter7's website.

;D

On Fri, Mar 13, 2009 at 2:59 PM, Remo Mattei <r...@italy1.com> wrote:
> Btw this file does not come with the tar file
>
> cp /var/src/tar/dovecot-1.1.11.sysv /etc/init.d/dovecot
>
> Remo
>
>
>> From: Rick Widmer <vch...@developersdesk.com>
>> Reply-To: <vchkpw@inter7.com>
>> Date: Fri, 13 Mar 2009 11:31:24 -0600
>> To: <vchkpw@inter7.com>
>> Subject: Re: [vchkpw] Courier support
>>
>> This may be the new toaster page for dovecot and the supporting files
>> you need to install it.   It seems to work for both SuSE and Debian
>> installations.  I've sent the Debian support files, so unless you are
>> working with a United Linux based distribution (like SuSE) you should be
>> good to go.
>>
>>
>> ===========================================================================
>>
>> Dovecot IMAP
>>
>> Dovecot will supply IMAP/SIMAP access.
>>
>> Info: http://www.dovecot.org/
>>
>> Install:
>>
>>      cd /var/src
>>      tar -xzf tar/dovecot-1.1.11.tar.gz
>>      cd dovecot-1.1.11
>>
>>      ./configure --with-vpopmail --without-pop3d \
>>      --without-passwd --without-pam \
>>      --without-passwd-file --without-shadow \
>>      --without-checkpassword --without-deliver
>>
>>      make
>>      make install
>>
>>
>> Setup SSL certificate
>>
>>      cd doc
>>
>>      Edit the file dovecot-openssl.cnf and customize it for your site.
>> Your answers here should be nearly the same as the ones for the qmail
>> certificate except for the fact that this is used by the imap server and
>> the previous certificate is used by the mail server.
>>
>>
>> Create SSL certificate:
>>
>>      mkdir -p /etc/ssl/certs
>>      chmod 755 /etc/ssl/certs
>>      mkdir -p /etc/ssl/private
>>      chmod 700 /etc/ssl/private
>>      chmod 700 mkcert.sh
>>      ./mkcert.sh
>>
>>
>> Configure:
>>
>>      cd /usr/local/etc
>>      cp dovecot-example.conf dovecot.conf
>>      patch -p0 < /var/src/tar/dovecot-1.1.11-conf.patch
>>
>>
>> Setup run files for non SuSE systems
>>
>>      cp /var/src/tar/dovecot-1.1.11.sysv /etc/init.d/dovecot
>>      chmod 755 /etc/init.d/dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc0.d/K30dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc1.d/K30dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc2.d/S80dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc3.d/S80dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc4.d/S80dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc5.d/S80dovecot
>>      ln -s /etc/init.d/dovecot /etc/rc.d/rc6.d/K30dovecot
>>      ln -s /etc/init.d/dovecot /usr/bin/dovecotctl
>>
>>      # Start Dovecot IMAP server
>>      dovecotctl start
>>
>>
>> ===========================================================================
>>
>>
>>
>> dovecot-1.1.11-conf.patch
>> ===========================================================================
>> --- dovecot-example.conf 2008-10-27 13:57:52.000000000 -0600
>> +++ dovecot.conf 2008-10-27 14:19:09.000000000 -0600
>> @@ -344,8 +344,8 @@
>>   # to make sure that users can't log in as daemons or other system users.
>>   # Note that denying root logins is hardcoded to dovecot binary and can't
>>   # be done even if first_valid_uid is set to 0.
>> -#first_valid_uid = 500
>> -#last_valid_uid = 0
>> +first_valid_uid = 89
>> +last_valid_uid  = 89
>>
>>   # Valid GID range for users, defaults to non-root/wheel. Users having
>>   # non-valid GID as primary group ID aren't allowed to log in. If user
>> @@ -700,7 +700,7 @@
>>   # Authentication cache size in kilobytes. 0 means it's disabled.
>>   # Note that bsdauth, PAM and vpopmail require cache_key to be set for
>> caching
>>   # to be used.
>> -#auth_cache_size = 0
>> +auth_cache_size = 1024
>>   # Time to live in seconds for cached data. After this many seconds the
>> cached
>>   # record is no longer used, *except* if the main database lookup returns
>>   # internal failure. We also try to handle password changes
>> automatically: If
>> @@ -825,7 +825,7 @@
>>     # database (passwd usually), you can use static userdb.
>>     # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM
>>     # authentication to actually work. <doc/wiki/PasswordDatabase.PAM.txt>
>> -  passdb pam {
>> +#  passdb pam {
>>       # [session=yes] [setcred=yes] [failure_show_msg=yes]
>>       # [cache_key=<key>] [<service name>]
>>       #
>> @@ -854,7 +854,7 @@
>>       #   args = session=yes %Ls
>>       #   args = cache_key=%u dovecot
>>       #args = dovecot
>> -  }
>> +#  }
>>
>>     # System users (NSS, /etc/passwd, or similiar)
>>     # In many systems nowadays this uses Name Service Switch, which is
>> @@ -908,12 +908,12 @@
>>     #}
>>
>>     # vpopmail authentication <doc/wiki/AuthDatabase.VPopMail.txt>
>> -  #passdb vpopmail {
>> +  passdb vpopmail {
>>       # [cache_key=<key>] - See cache_key in PAM for explanation..
>>       # [quota_template=<template>] - %q expands to Maildir++ quota
>>       #   (eg. quota_template=quota_rule=*:backend=%q)
>>       #args =
>> -  #}
>> +  }
>>
>>     #
>>     # User database specifies where mails are located and what
>> user/group IDs
>> @@ -925,14 +925,14 @@
>>     # System users (NSS, /etc/passwd, or similiar). In many systems
>> nowadays this
>>     # uses Name Service Switch, which is configured in /etc/nsswitch.conf.
>>     # <doc/wiki/AuthDatabase.Passwd.txt>
>> -  userdb passwd {
>> +#  userdb passwd {
>>       # [blocking=yes] - By default the lookups are done in the main
>> dovecot-auth
>>       # process. This setting causes the lookups to be done in auth worker
>>       # proceses. Useful with remote NSS lookups that may block.
>>       # NOTE: Be sure to use this setting with nss_ldap or users might get
>>       # logged in as each others!
>>       #args =
>> -  }
>> +#  }
>>
>>     # passwd-like file with specified location
>>     # <doc/wiki/AuthDatabase.PasswdFile.txt>
>> @@ -971,8 +971,8 @@
>>     #}
>>
>>     # vpopmail <doc/wiki/AuthDatabase.VPopMail.txt>
>> -  #userdb vpopmail {
>> -  #}
>> +  userdb vpopmail {
>> +  }
>>
>>     # "prefetch" user database means that the passdb already provided the
>>     # needed information and there's no need to do a separate userdb lookup.
>> ===========================================================================
>>
>>
>> dovecot-1.1.11.sysv
>> ===========================================================================
>> #! /bin/sh
>>
>> DAEMON=/usr/local/sbin/dovecot
>>
>> test -x $DAEMON || exit 1
>> set -e
>>
>> base_dir=`$DAEMON -a|grep '^base_dir: '|sed 's/^base_dir: //'`
>> pidfile=$base_dir/master.pid
>>
>> if test -f $pidfile; then
>>    running=yes
>> else
>>    running=no
>> fi
>>
>> case "$1" in
>>    start)
>>      echo -n "Starting Dovecot"
>>      $DAEMON
>>      echo "."
>>      ;;
>>    stop)
>>      if test $running = yes; then
>>        echo "Stopping Dovecot"
>>        kill `cat $pidfile`
>>        echo "."
>>      else
>>        echo "Dovecot is already stopped."
>>      fi
>>      ;;
>>    reload)
>>      if test $running = yes; then
>>        echo -n "Reloading Dovecot configuration"
>>        kill -HUP `cat $pidfile`
>>        echo "."
>>      else
>>        echo "Dovecot isn't running."
>>      fi
>>      ;;
>>    restart|force-reload)
>>      echo -n "Restarting Dovecot"
>>      if test $running = yes; then
>>        kill `cat $pidfile`
>>        sleep 1
>>      fi
>>      $DAEMON
>>      echo "."
>>      ;;
>>    *)
>>      echo "Usage: /etc/init.d/dovecot
>> {start|stop|reload|restart|force-reload}" >&2
>>      exit 1
>>      ;;
>> esac
>>
>> exit 0
>> ===========================================================================
>>
>>
>>
>>
>>
>>
>
>
> 
>
>
--
[ ]'s
Aledr - Alexandre
"OpenSource Solutions for SmallBusiness Problems"

!DSPAM:49bbc5e432688994597163!

Reply via email to