#1  
Old 10th May 2011, 03:46
Davano Davano is offline
Junior Member
 
Join Date: May 2011
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default iRedMail

Hallo all,

i have installed a iRedMail server on openSuse 11.4.
I followed this guide http://www.howtoforge.com/iredmail-0...-opensuse-11.3

Now when i restart the services i get the following from the terminal:
Code:
Shutting down syslog services                                        done
Starting syslog services                                             done
Syntax OK
Shutting down httpd2 (waiting for all children to terminate)         done
Starting httpd2 (prefork)                                            done
Shutting down mail service (Postfix)                                 done
Starting mail service (Postfix)                                      done
Restarting service MySQL 
Shutting down service MySQL                                          done
Starting service MySQL                                               done
Shutting down ldap-server                                            done
Starting ldap-server                                                 done
Shutting down policyd                                                done
Starting policyd                                                     done
Stopping dovecot                                                     done
Starting dovecot Fatal: execv(/usr/lib/dovecot/managesieve) failed: Permission denied
Error: managesieve dump-capability process returned 84
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
startproc:  exit status of parent of /usr/sbin/dovecot: 89
                                                                     failed
Shutting down virus-scanner (amavisd-new): Daemon [23632] terminated by SIGTERM
                                                                     done
Starting virus-scanner (amavisd-new):                                done
Shutting down Clam AntiVirus daemon                                  done
Starting Clam AntiVirus daemon                                       done
Shutting down Clam AntiVirus database update daemon                  done
Starting Clam AntiVirus database update daemon                       done
Shutting down CRON daemon                                            done
Starting CRON daemon                                                 done
Stopping iredapd ...
Starting iredapd ...
Loading firewall rules                                               done
linux-nws1:/home/iRedMail-0.7.1 #
And when i test i cant log in to the webmail accounts.
If i try to log in i get this massage:
Code:
Connection to IMAP server failed
All the other services work and i can log in to them.
I also just restarted Linux and restarted the services then the output looked like this:

Code:
Shutting down syslog services                                        done
Starting syslog services                                             done
Syntax OK
Shutting down httpd2 (waiting for all children to terminate)         done
Starting httpd2 (prefork)                                            done
Shutting down mail service (Postfix)                                 done
Starting mail service (Postfix)                                      done
Restarting service MySQL 
Shutting down service MySQL                                          done
Starting service MySQL                                               done
Shutting down ldap-server                                            done
Starting ldap-server                                                 done
Shutting down policyd                                                done
Starting policyd                                                     done
Stopping dovecot                                                     done
Starting dovecot                                                     done
Shutting down virus-scanner (amavisd-new): Fatal: execv(/usr/lib/dovecot/managesieve) failed: Permission denied
Error: managesieve dump-capability process returned 84
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
Daemon [2487] terminated by SIGTERM
                                                                     done
Starting virus-scanner (amavisd-new):                                done
Shutting down Clam AntiVirus daemon                                  done
Starting Clam AntiVirus daemon                                       done
Shutting down Clam AntiVirus database update daemon                  done
Starting Clam AntiVirus database update daemon                       done
Shutting down CRON daemon                                            done
Starting CRON daemon                                                 done
Stopping iredapd ...
Starting iredapd ...
Loading firewall rules                                               done
Now my question is how do i fix this.
greets Davano
Reply With Quote
Sponsored Links
  #2  
Old 11th May 2011, 01:39
CopalFreak CopalFreak is offline
Junior Member
 
Join Date: May 2011
Posts: 19
Thanks: 2
Thanked 0 Times in 0 Posts
Default

Hiya Davano!

I am by no means an expert, but people here are trying to help me out so I thought I would reciprocate..at least I can try..
(I'll try NOT to be wrong, but no promises.. hehe)

Looks like 2 errors
1) Fatal: execv(/usr/lib/dovecot/managesieve) failed: Permission denied
try running
ls -l /usr/lib/dovecot/managesieve
(I think dovecot might need to be owner and have +x permissions..but get the "ls -l" results first..)

2) Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
can you post your /etc/dovecot/dovecot.conf ?
Reply With Quote
  #3  
Old 11th May 2011, 02:48
Davano Davano is offline
Junior Member
 
Join Date: May 2011
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thx for the reply,

if it turns out to be wrong it no problem

thanks for helping.

when i do i have this output:
ls -dl /usr/lib/dovecot/managesieve
Code:
ls -dl /usr/lib/dovecot/managesieve
-rwxr-xr-x 1 root root 1007416 Feb 22 19:04 /usr/lib/dovecot/managesieve
And this is my /etc/dovecot/dovecot.conf:
Code:
#
# File generated by iRedMail (2011.05.10.20.22.15):
#
# Version:  0.7.0
# Project:  http://www.iredmail.org/
#
# Community: http://www.iredmail.org/forum/
#

# Provided services.
protocols =  pop3 pop3s imap imaps managesieve

# Listen addresses. for Dovecot-1.1.x.
# ipv4: *
# ipv6: [::]
#listen = *, [::]
listen = *

# mail uid/gid.
mail_uid = 1001
mail_gid = 1000
first_valid_uid = 1001
last_valid_uid = 1001

#
# Debug options.
#
#mail_debug = yes
#auth_verbose = yes
#auth_debug = yes
#auth_debug_passwords = yes

#
# Log file.
#
#log_timestamp = "%Y-%m-%d %H:%M:%S "
log_path = /var/log/dovecot.log

#login_processes_count = 3
#login_max_processes_count = 128
#login_max_connections = 256

# Maximum number of running mail processes. Default is 512.
# When this limit is reached, new users aren't allowed to log in.
#max_mail_processes = 512

# Set max process size in megabytes. Default is 256.
# Most of the memory goes to mmap()ing files, so it shouldn't harm
# much even if this limit is set pretty high.
#
# Note:
# Some user reported that if mailbox is too large (e.g. 80GB), dovecot
# will disconnect the client with error:
# "pool_system_malloc(100248): Out of memory".
mail_process_size = 1024

disable_plaintext_auth = no

# Performance Tuning. Reference:
#   http://wiki.dovecot.org/LoginProcess
#
# High-Security mode. Dovecot default setting.
#
# It works by using a new imap-login or pop3-login process for each
# incoming connection. Since the processes run in a highly restricted
# chroot, running each connection in a separate process means that in
# case there is a security hole in Dovecot's pre-authentication code
# or in the SSL library, the attacker can't see other users'
# connections and can't really do anything destructive.
login_process_per_connection=yes

#
# High-Performance mode.
#
# It works by using a number of long running login processes,
# each handling a number of connections. This loses much of
# the security benefits of the login process design, because
# in case of a security hole the attacker is now able to see
# other users logging in and steal their passwords.
#login_process_per_connection = no

# Default realm/domain to use if none was specified.
# This is used for both SASL realms and appending '@domain.ltd' to username in plaintext logins.
auth_default_realm = erik.nl

# ---- NFS storage ----
# Set to 'no' For NFSv2. Default is 'yes'.
#dotlock_use_excl = yes

#mail_nfs_storage = yes # v1.1+ only

# If indexes are on NFS.
#mail_nfs_index = yes # v1.1+ only
# ----

plugin {
    # Quota warning.
    #
    # You can find sample script from Dovecot wiki:
    # http://wiki.dovecot.org/Quota/1.1#head-03d8c4f6fb28e2e2f1cb63ec623810b45bec1734
    #
    # If user suddenly receives a huge mail and the quota jumps from
    # 85% to 95%, only the 95% script is executed.
    #
    quota_warning = storage=85%% /usr/local/bin/dovecot-quota-warning.sh 85
    quota_warning2 = storage=90%% /usr/local/bin/dovecot-quota-warning.sh 90
    quota_warning3 = storage=95%% /usr/local/bin/dovecot-quota-warning.sh 95
}

# SSL support.
ssl = yes
verbose_ssl = no
ssl_key_file = /etc/ssl/private/iRedMail.key
ssl_cert_file = /etc/ssl/certs/iRedMail_CA.pem
ssl_ca_file = /etc/ssl/certs/iRedMail_CA.pem
# Maildir format and location.
mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/

plugin {
    # Quota, stored in file 'maildirsize' under user mailbox.
    # Dict quota. Used to store realtime quota in SQL.
    quota = dict:user::proxy::quotadict
    # Quota rules. Reference: http://wiki.dovecot.org/Quota/1.1
    # The following limit names are supported:
    #   - storage: Quota limit in kilobytes, 0 means unlimited.
    #   - bytes: Quota limit in bytes, 0 means unlimited.
    #   - messages: Quota limit in number of messages, 0 means unlimited. This probably isn't very useful.
    #   - backend: Quota backend-specific limit configuration.
    #   - ignore: Don't include the specified mailbox in quota at all (v1.1.rc5+).
    quota_rule = *:storage=0
    #quota_rule2 = *:messages=0
    #quota_rule3 = Trash:storage=1G
    #quota_rule4 = Junk:ignore
}

dict {
    # NOTE: dict process currently runs as root, so this file will be owned as root.
    expire = db:/var/lib/dovecot/expire/expire.db
}

plugin {
    # ---- Expire plugin ----
    # Expire plugin. Mails are expunged from mailboxes after being there the
    # configurable time. The first expiration date for each mailbox is stored in
    # a dictionary so it can be quickly determined which mailboxes contain
    # expired mails. The actual expunging is done in a nightly cronjob, which
    # you must set up:
    #
    #   1   3   *   *   *   /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool
    #
    # Trash: 7 days
    # Trash's children directories: 7 days
    # Junk: 30 days
    expire = Trash 7 Trash/* 7 Junk 30
    expire_dict = proxy::expire

    # If you have a non-default path to auth-master, set also:
    auth_socket_path = /var/run/dovecot/auth-master
}

# Per-user sieve mail filter.
plugin {
    # For maildir format.
    sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve
}
# LDA: Local Deliver Agent
protocol lda {
    postmaster_address = root
    auth_socket_path = /var/run/dovecot/auth-master
    mail_plugins = quota sieve autocreate
    sieve_global_path = /var/vmail/sieve/dovecot.sieve
    log_path = /var/log/sieve.log
}

# IMAP configuration
protocol imap {
    mail_plugins = quota imap_quota autocreate

    imap_client_workarounds = tb-extra-mailbox-sep

    # number of connections per-user per-IP
    #mail_max_userip_connections = 10
}

# POP3 configuration
protocol pop3 {
    mail_plugins = quota
    pop3_uidl_format = %08Xu%08Xv
    pop3_client_workarounds = outlook-no-nuls oe-ns-eoh

    # number of connections per-user per-IP
    #mail_max_userip_connections = 10
}

auth default {
    mechanisms = plain login
    user = vmail
    passdb ldap {
        args = /etc/dovecot/dovecot-ldap.conf
    }
    userdb ldap {
        args = /etc/dovecot/dovecot-ldap.conf
    }
    socket listen {
        master {
            path = /var/run/dovecot/auth-master
            mode = 0666
            user = vmail
            group = vmail
        }
        client {
            path = /var/spool/postfix/dovecot-auth
            mode = 0666
            user = postfix
            group = postfix
        }
    }
}
plugin {
    autocreate = INBOX
    autocreate2 = Sent
    autocreate3 = Trash
    autocreate4 = Drafts
    autocreate5 = Junk

    autosubscribe = INBOX
    autosubscribe2 = Sent
    autosubscribe3 = Trash
    autosubscribe4 = Drafts
    autosubscribe5 = Junk
}
dict {
    # Dict quota. Used to store realtime quota in SQL.
    quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf
}
namespace private {
    separator = /
    prefix =
    #location defaults to mail_location.
    inbox = yes
}

namespace shared {
    separator = /
    prefix = Shared/%%u/
    location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u
    # this namespace should handle its own subscriptions or not.
    subscriptions = yes
    list = children
}

plugin {
    acl = vfile
    acl_shared_dict = proxy::acl
}
dict {
    acl = mysql:/etc/dovecot/dovecot-share-folder.conf
}
# ManageSieve service. http://wiki.dovecot.org/ManageSieve
protocol managesieve {
    # IP or host address where to listen in for connections.
    listen = 127.0.0.1:2000

    # Login executable location.
    #login_executable = /usr/local/libexec/dovecot/managesieve-login

    # ManageSieve executable location. See IMAP's mail_executable above for
    # examples how this could be changed.
    #mail_executable = /usr/local/libexec/dovecot/managesieve

    # Maximum ManageSieve command line length in bytes. This setting is
    # directly borrowed from IMAP. But, since long command lines are very
    # unlikely with ManageSieve, changing this will not be very useful.
    #managesieve_max_line_length = 65536

    # ManageSieve logout format string:
    #  %i - total number of bytes read from client
    #  %o - total number of bytes sent to client
    #managesieve_logout_format = bytes=%i/%o

    # If, for some inobvious reason, the sieve_storage remains unset, the
    # ManageSieve daemon uses the specification of the mail_location to find out
    # where to store the sieve files (see explaination in README.managesieve).
    # The example below, when uncommented, overrides any global mail_location
    # specification and stores all the scripts in '~/mail/sieve' if sieve_storage
    # is unset. However, you should always use the sieve_storage setting.
    # mail_location = mbox:~/mail

    # To fool ManageSieve clients that are focused on timesieved you can
    # specify the IMPLEMENTATION capability that the dovecot reports to clients
    # (default: "dovecot").
    #managesieve_implementation_string = dovecot
}

# sieve plugin. http://wiki.dovecot.org/LDA/Sieve
plugin {
    # If the user has no personal active script (i.e. if the file 
    # indicated in sieve= does not exist), use this one:
    #sieve_global_path = /var/vmail/sieve/dovecot.sieve

    # The include extension fetches the :global scripts from this 
    # directory.
    #sieve_global_dir = 

    # Path to a script file or a directory containing script files
    # that need to be executed before the user's script. If the path
    # points to a directory, all the Sieve scripts contained therein
    # (with the proper .sieve extension) are executed. The order of
    # execution is determined by the file names, using a normal 8bit
    # per-character comparison.
    #sieve_before = /var/vmail/sieve/dovecot.sieve

    # Identical to sieve_before, only the specified scripts are
    # executed after the user's script (only when keep is still in
    # effect!).
    #sieve_after = /var/vmail/sieve/dovecot.sieve

    # Location of the active script. When ManageSieve is used this is actually
    # a symlink pointing to the active script in the sieve storage directory.
    sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve

    # The path to the directory where the personal Sieve scripts are stored. For
    # ManageSieve this is where the uploaded scripts are stored.
    sieve_dir = /var/vmail/sieve/%Ld/%Ln/
}

Greets Davano
Reply With Quote
  #4  
Old 11th May 2011, 03:34
CopalFreak CopalFreak is offline
Junior Member
 
Join Date: May 2011
Posts: 19
Thanks: 2
Thanked 0 Times in 0 Posts
Default

try this
chown dovecot:dovecot /usr/lib/dovecot/managesieve

restart dovecot, watch the logs and see if any of the errors go away.

If the permission denied error goes away but it still shutdown down because of invalid configuration in dovecot.conf, let me know and will try to help from there.
Reply With Quote
  #5  
Old 11th May 2011, 16:31
Davano Davano is offline
Junior Member
 
Join Date: May 2011
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thx for the reply.

i did that but no luck.
Still have the same error.
But what is also weird there is nothing in the /var/log/dovecot.log

When i restart dovecot i have this:
Code:
erik:~ # ILoading modules from directory: /usr/lib/dovecot/modules/imap
IModule loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so
IModule loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so
IModule loaded: /usr/lib/dovecot/modules/imap/lib20_autocreate_plugin.so
IEffective uid=65534, gid=65533, home=/tmp
IQuota root: name=user backend=dict args=:proxy::quotadict
IQuota rule: root=user mailbox=* bytes=0 messages=0
IQuota warning: bytes=0 (85%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 85
IQuota warning: bytes=0 (90%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 90
IQuota warning: bytes=0 (95%) messages=0 command=/usr/local/bin/dovecot-quota-warning.sh 95
Fatal: execv(/usr/lib/dovecot/managesieve) failed: Permission denied
Error: managesieve dump-capability process returned 84
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
ANd this is my config file
Code:
#
# File generated by iRedMail (2011.05.11.09.53.14):
#
# Version:  0.7.0
# Project:  http://www.iredmail.org/
#
# Community: http://www.iredmail.org/forum/
#

# Provided services.
protocols =  pop3 pop3s imap imaps managesieve

# Listen addresses. for Dovecot-1.1.x.
# ipv4: *
# ipv6: [::]
#listen = *, [::]
listen = *

# mail uid/gid.
mail_uid = 1001
mail_gid = 1000
first_valid_uid = 1001
last_valid_uid = 1001

#Debug options.

mail_debug = yes
auth_verbose = yes
auth_debug = yes
auth_debug_passwords = yes


#Log file.

log_timestamp = "%Y-%m-%d %H:%M:%S "
log_path = /var/log/dovecot.log

login_processes_count = 3
login_max_processes_count = 128
login_max_connections = 256

# Maximum number of running mail processes. Default is 512.
# When this limit is reached, new users aren't allowed to log in.
#max_mail_processes = 512

# Set max process size in megabytes. Default is 256.
# Most of the memory goes to mmap()ing files, so it shouldn't harm
# much even if this limit is set pretty high.
#
# Note:
# Some user reported that if mailbox is too large (e.g. 80GB), dovecot
# will disconnect the client with error:
# "pool_system_malloc(100248): Out of memory".
mail_process_size = 1024

disable_plaintext_auth = no

# Performance Tuning. Reference:
#   http://wiki.dovecot.org/LoginProcess
#
# High-Security mode. Dovecot default setting.
#
# It works by using a new imap-login or pop3-login process for each
# incoming connection. Since the processes run in a highly restricted
# chroot, running each connection in a separate process means that in
# case there is a security hole in Dovecot's pre-authentication code
# or in the SSL library, the attacker can't see other users'
# connections and can't really do anything destructive.
login_process_per_connection=yes

#
# High-Performance mode.
#
# It works by using a number of long running login processes,
# each handling a number of connections. This loses much of
# the security benefits of the login process design, because
# in case of a security hole the attacker is now able to see
# other users logging in and steal their passwords.
#login_process_per_connection = no

# Default realm/domain to use if none was specified.
# This is used for both SASL realms and appending '@domain.ltd' to username in plaintext logins.
auth_default_realm = erik.nl

# ---- NFS storage ----
# Set to 'no' For NFSv2. Default is 'yes'.
#dotlock_use_excl = yes

#mail_nfs_storage = yes # v1.1+ only

# If indexes are on NFS.
#mail_nfs_index = yes # v1.1+ only
# ----

plugin {
    # Quota warning.
    #
    # You can find sample script from Dovecot wiki:
    # http://wiki.dovecot.org/Quota/1.1#head-03d8c4f6fb28e2e2f1cb63ec623810b45bec1734
    #
    # If user suddenly receives a huge mail and the quota jumps from
    # 85% to 95%, only the 95% script is executed.
    #
    quota_warning = storage=85%% /usr/local/bin/dovecot-quota-warning.sh 85
    quota_warning2 = storage=90%% /usr/local/bin/dovecot-quota-warning.sh 90
    quota_warning3 = storage=95%% /usr/local/bin/dovecot-quota-warning.sh 95
}

# SSL support.
ssl = yes
verbose_ssl = no
ssl_key_file = /etc/ssl/private/iRedMail.key
ssl_cert_file = /etc/ssl/certs/iRedMail_CA.pem
ssl_ca_file = /etc/ssl/certs/iRedMail_CA.pem
# Maildir format and location.
mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/

plugin {
    # Quota, stored in file 'maildirsize' under user mailbox.
    # Dict quota. Used to store realtime quota in SQL.
    quota = dict:user::proxy::quotadict
    # Quota rules. Reference: http://wiki.dovecot.org/Quota/1.1
    # The following limit names are supported:
    #   - storage: Quota limit in kilobytes, 0 means unlimited.
    #   - bytes: Quota limit in bytes, 0 means unlimited.
    #   - messages: Quota limit in number of messages, 0 means unlimited. This probably isn't very useful.
    #   - backend: Quota backend-specific limit configuration.
    #   - ignore: Don't include the specified mailbox in quota at all (v1.1.rc5+).
    quota_rule = *:storage=0
    #quota_rule2 = *:messages=0
    #quota_rule3 = Trash:storage=1G
    #quota_rule4 = Junk:ignore
}

dict {
    # NOTE: dict process currently runs as root, so this file will be owned as root.
    expire = db:/var/lib/dovecot/expire/expire.db
}

plugin {
    # ---- Expire plugin ----
    # Expire plugin. Mails are expunged from mailboxes after being there the
    # configurable time. The first expiration date for each mailbox is stored in
    # a dictionary so it can be quickly determined which mailboxes contain
    # expired mails. The actual expunging is done in a nightly cronjob, which
    # you must set up:
    #
    #   1   3   *   *   *   /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool
    #
    # Trash: 7 days
    # Trash's children directories: 7 days
    # Junk: 30 days
    expire = Trash 7 Trash/* 7 Junk 30
    expire_dict = proxy::expire

    # If you have a non-default path to auth-master, set also:
    auth_socket_path = /var/run/dovecot/auth-master
}

# Per-user sieve mail filter.
plugin {
    # For maildir format.
    sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve
}
# LDA: Local Deliver Agent
protocol lda {
    postmaster_address = root
    auth_socket_path = /var/run/dovecot/auth-master
    mail_plugins = quota sieve autocreate
    sieve_global_path = /var/vmail/sieve/dovecot.sieve
    log_path = /var/log/sieve.log
}

# IMAP configuration
protocol imap {
    mail_plugins = quota imap_quota autocreate

    imap_client_workarounds = tb-extra-mailbox-sep

    # number of connections per-user per-IP
    #mail_max_userip_connections = 10
}

# POP3 configuration
protocol pop3 {
    mail_plugins = quota
    pop3_uidl_format = %08Xu%08Xv
    pop3_client_workarounds = outlook-no-nuls oe-ns-eoh

    # number of connections per-user per-IP
    #mail_max_userip_connections = 10
}

auth default {
    mechanisms = plain login
    user = vmail
    passdb ldap {
        args = /etc/dovecot/dovecot-ldap.conf
    }
    userdb ldap {
        args = /etc/dovecot/dovecot-ldap.conf
    }
    socket listen {
        master {
            path = /var/run/dovecot/auth-master
            mode = 0666
            user = vmail
            group = vmail
        }
        client {
            path = /var/spool/postfix/dovecot-auth
            mode = 0666
            user = postfix
            group = postfix
        }
    }
}
plugin {
    autocreate = INBOX
    autocreate2 = Sent
    autocreate3 = Trash
    autocreate4 = Drafts
    autocreate5 = Junk

    autosubscribe = INBOX
    autosubscribe2 = Sent
    autosubscribe3 = Trash
    autosubscribe4 = Drafts
    autosubscribe5 = Junk
}
dict {
    # Dict quota. Used to store realtime quota in SQL.
    quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf
}
namespace private {
    separator = /
    prefix =
    #location defaults to mail_location.
    inbox = yes
}

namespace shared {
    separator = /
    prefix = Shared/%%u/
    location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u
    # this namespace should handle its own subscriptions or not.
    subscriptions = yes
    list = children
}

plugin {
    acl = vfile
    acl_shared_dict = proxy::acl
}
dict {
    acl = mysql:/etc/dovecot/dovecot-share-folder.conf
}
# ManageSieve service. http://wiki.dovecot.org/ManageSieve
protocol managesieve {
    # IP or host address where to listen in for connections.
    listen = 127.0.0.1:2000

    # Login executable location.
    #login_executable = /usr/local/libexec/dovecot/managesieve-login

    # ManageSieve executable location. See IMAP's mail_executable above for
    # examples how this could be changed.
    #mail_executable = /usr/local/libexec/dovecot/managesieve

    # Maximum ManageSieve command line length in bytes. This setting is
    # directly borrowed from IMAP. But, since long command lines are very
    # unlikely with ManageSieve, changing this will not be very useful.
    #managesieve_max_line_length = 65536

    # ManageSieve logout format string:
    #  %i - total number of bytes read from client
    #  %o - total number of bytes sent to client
    #managesieve_logout_format = bytes=%i/%o

    # If, for some inobvious reason, the sieve_storage remains unset, the
    # ManageSieve daemon uses the specification of the mail_location to find out
    # where to store the sieve files (see explaination in README.managesieve).
    # The example below, when uncommented, overrides any global mail_location
    # specification and stores all the scripts in '~/mail/sieve' if sieve_storage
    # is unset. However, you should always use the sieve_storage setting.
    # mail_location = mbox:~/mail

    # To fool ManageSieve clients that are focused on timesieved you can
    # specify the IMPLEMENTATION capability that the dovecot reports to clients
    # (default: "dovecot").
    #managesieve_implementation_string = dovecot
}

# sieve plugin. http://wiki.dovecot.org/LDA/Sieve
plugin {
    # If the user has no personal active script (i.e. if the file 
    # indicated in sieve= does not exist), use this one:
    #sieve_global_path = /var/vmail/sieve/dovecot.sieve

    # The include extension fetches the :global scripts from this 
    # directory.
    #sieve_global_dir = 

    # Path to a script file or a directory containing script files
    # that need to be executed before the user's script. If the path
    # points to a directory, all the Sieve scripts contained therein
    # (with the proper .sieve extension) are executed. The order of
    # execution is determined by the file names, using a normal 8bit
    # per-character comparison.
    #sieve_before = /var/vmail/sieve/dovecot.sieve

    # Identical to sieve_before, only the specified scripts are
    # executed after the user's script (only when keep is still in
    # effect!).
    #sieve_after = /var/vmail/sieve/dovecot.sieve

    # Location of the active script. When ManageSieve is used this is actually
    # a symlink pointing to the active script in the sieve storage directory.
    sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve

    # The path to the directory where the personal Sieve scripts are stored. For
    # ManageSieve this is where the uploaded scripts are stored.
    sieve_dir = /var/vmail/sieve/%Ld/%Ln/
}
Greets Davano

Last edited by Davano; 11th May 2011 at 16:37.
Reply With Quote
  #6  
Old 13th May 2011, 00:35
CopalFreak CopalFreak is offline
Junior Member
 
Join Date: May 2011
Posts: 19
Thanks: 2
Thanked 0 Times in 0 Posts
Default

Are 1001 and 1000 your dovecot user and group?
Reply With Quote
  #7  
Old 13th May 2011, 21:51
Davano Davano is offline
Junior Member
 
Join Date: May 2011
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thx for the reply.

GroupID 1001 is iredadmin and GroupID 1000 is vmail.



greets Davano
Reply With Quote
  #8  
Old 13th May 2011, 23:09
CopalFreak CopalFreak is offline
Junior Member
 
Join Date: May 2011
Posts: 19
Thanks: 2
Thanked 0 Times in 0 Posts
Default

try this one maybe?
chown iredadmin:vmail /usr/lib/dovecot/managesieve
(assuming iredadmin is a member of the vmail group)
If that doesn't work, you might try o set it to whatever permissions managesieve might need.
Because of that error, it sure seems like it's something related. (if there is a log-level or something to get extra details out of the logs, you might turn that one as well)
Reply With Quote
  #9  
Old 13th May 2011, 23:43
Davano Davano is offline
Junior Member
 
Join Date: May 2011
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thx for the reply.

Ow sorry made a type:
Here a screen from the users and groups.
IRedadmin is not a member of the vmail group.
But can change that.
Will try out what you suggested, and will let you no if it worked.
I already did change the permissions on managesieve to 777 but no luck.


Greets Davano
Attached Images
  
Reply With Quote
  #10  
Old 17th May 2011, 08:20
CopalFreak CopalFreak is offline
Junior Member
 
Join Date: May 2011
Posts: 19
Thanks: 2
Thanked 0 Times in 0 Posts
 
Default

Davano,
I suspect it's not a good idea to leave the permissions on managesieve as 777, so you might want to research the appropriate setting on that one. (adding it to group 'vmail' could make it vulnerable to various security risks depending on what else vmail has access to.

By the way, did adding IRedadmin to vmail group get rid of that permission error?
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ISPConfig 3 with iRedMail???? Mr.Paradigm General 2 6th October 2010 17:14
iRedMail - phpLDAPadmin how to snarf77 HOWTO-Related Questions 2 17th September 2010 15:56
Some errors after using iRedMail to setup mail server DaaX HOWTO-Related Questions 1 21st January 2010 15:27
iRedMail nima0102 Installation/Configuration 1 13th October 2009 15:04
iRedMail: Build A Full-Featured Mail Server With LDAP, Postfix, RoundCube, Dovecot, C bentman78 HOWTO-Related Questions 12 1st May 2009 20:15


All times are GMT +2. The time now is 05:28.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.