1

Topic: Error with iRedMail-0.7.3-rc1

Centos 6

Stopping Dovecot Imap:                                     [FAILED]
Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /root/iRedMail-0.7.3-rc1/config line 2: Expecting '='
doveconf: Error: managesieve-login: dump-capability process returned 89
doveconf: Fatal: Error in configuration file /root/iRedMail-0.7.3-rc1/config line 2: Expecting '='
                                                           [FAILED]
Shutting down amavisd: The amavisd daemon is apparently not running, no PID file /var/run/amavisd/amavisd.pid
                                                           [FAILED]

2

Re: Error with iRedMail-0.7.3-rc1

May i know when it shows these errors?
Also, can you show me output of command 'dovecot -n'?

3

Re: Error with iRedMail-0.7.3-rc1

May i know when it shows these errors?

during installation

Also, can you show me output of command 'dovecot -n'?

# 2.0.13: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-71.29.1.el6.x86_64 x86_64 CentOS Linux release 6.0 (Final)
auth_mechanisms = PLAIN LOGIN
dict {
  expire = db:/var/lib/dovecot/expire/expire.db
  quotadict = mysql:/etc/dovecot/used-quota.conf
}
disable_plaintext_auth = no
last_valid_uid = 500
listen = *
log_path = /var/log/dovecot.log
mail_gid = 500
mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/
mail_uid = 500
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character vacati                                                                                                                                                              on subaddress comparator-i;ascii-numeric relational regex imap4flags copy includ                                                                                                                                                              e variables body enotify environment mailbox date
passdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
plugin {
  auth_socket_path = /var/run/dovecot/auth-master
  autocreate = INBOX
  autocreate2 = Sent
  autocreate3 = Trash
  autocreate4 = Drafts
  autocreate5 = Junk
  autosubscribe = INBOX
  autosubscribe2 = Sent
  autosubscribe3 = Trash
  autosubscribe4 = Drafts
  autosubscribe5 = Junk
  expire = Trash 7 Trash/* 7 Junk 30
  expire_dict = proxy::expire
  quota = dict:user::proxy::quotadict
  quota_rule = *:storage=1G
  quota_warning = storage=85%% quota-warning 85 %u
  quota_warning2 = storage=90%% quota-warning 90 %u
  quota_warning3 = storage=95%% quota-warning 95 %u
  sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve
  sieve_global_path = /var/vmail/sieve/dovecot.sieve
}
protocols = pop3 imap sieve
service auth {
  unix_listener /var/spool/postfix/dovecot-auth {
    group = postfix
    mode = 0666
    user = postfix
  }
  unix_listener auth-master {
    group = vmail
    mode = 0666
    user = vmail
  }
}
service dict {
  unix_listener dict {
    group = vmail
    mode = 0660
    user = vmail
  }
}
service quota-warning {
  executable = script /usr/local/bin/dovecot-quota-warning.sh
  unix_listener quota-warning {
    group = vmail
    mode = 0660
    user = vmail
  }
}
ssl_cert = </etc/pki/tls/certs/iRedMail_CA.pem
ssl_key = </etc/pki/tls/private/iRedMail.key
userdb {
  args = /etc/dovecot/dovecot-mysql.conf
  driver = sql
}
protocol lda {
  auth_socket_path = /var/run/dovecot/auth-master
  lda_mailbox_autocreate = yes
  log_path = /var/log/sieve.log
  mail_plugins = quota sieve autocreate
  postmaster_address = root
}
protocol imap {
  imap_client_workarounds = tb-extra-mailbox-sep
  mail_plugins = quota imap_quota autocreate
}
protocol pop3 {
  mail_plugins = quota
  pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
  pop3_uidl_format = %08Xu%08Xv

4

Re: Error with iRedMail-0.7.3-rc1

I didn't get same error message before, and dovecot config file looks fine.
No idea why it happened.

Does Dovecot service work well? e.g. Login to webmail.

5

Re: Error with iRedMail-0.7.3-rc1

works fine!

6

Re: Error with iRedMail-0.7.3-rc1

busby wrote:

works fine!

Still no idea about why it happened. Sorry.