On 07/22/2010 11:27 PM Roderick A. Anderson wrote:> Read what I could find on possible upgrade issues and saw only one that
> might be a problem. I don't think it will but figured it was worth
> checking.
>
> Anything jump out at the more experienced users?
>
>
> dovecot -n (edited to protect the guilty. ie. me) attached.
>
> # 1.1.11: /etc/dovecot.conf
> # OS: Linux 2.6.22.19-vs2.3.0.34.1 i686 CentOS release 5.2 (Final)
> log_path: /var/log/dovecot/dovecot.log
> info_log_path: /var/log/dovecot/dovecot-info.log
> protocols: imap imaps
> listen: *:143
> ssl_listen: *:993
> login_dir: /var/run/dovecot/login
> login_executable: /usr/libexec/dovecot/imap-login
> login_greeting_capability: yes
> valid_chroot_dirs: /var/mail
> first_valid_uid: 5000
> last_valid_uid: 5000
> first_valid_gid: 5000
> last_valid_gid: 5000
> mail_access_groups: mail
> mail_location: maildir:~/Maildir
> mail_debug: yes
> maildir_copy_preserve_filename: yes
> imap_client_workarounds: outlook-idle
> auth default:
> mechanisms: plain login CRAM-MD5
> default_realm: example.com
> master_user_separator: *
> verbose: yes
> debug: yes
> debug_passwords: yes
> passdb:
> driver: passwd-file
> args: /var/mail/vhosts/%d/passwd.masterusers
> pass: yes
> master: yes
> passdb:
> driver: passwd-file
> args: username_format=%n /var/mail/vhosts/%d/passwd
> userdb:
> driver: passwd-file
> args: username_format=%n /var/mail/vhosts/%d/passwd
> socket:
> type: listen
> master:
> path: /var/run/dovecot/auth-master
> mode: 432
> user: vmail
> socket:
> type: listen
> client:
> path: /var/spool/postfix/private/auth
> mode: 432
> user: postfix
> plugin:
> sieve: /var/mail/vhosts/%d/%n/dovecot.sieve
>
Information about upgrading from 1.1.x to 1.2.x is available at:
http://wiki.dovecot.org/Upgrading/1.2
If you go a specific question ask it. So you will get an actual answer.
Regards,
Pascal
--
The trapper recommends today:
http://kopfkrebs.de/mitarbeiter/mitarbeiter_der_woche.html