# 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 = prlsrl.it

# 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/Sieveplugin { # 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/}

More or less it seems that it does not find a dovecot.pem certificates, in fact in some directory i've found a IredMail.pem certificates (I dont' know in which directory) but it is strange that the dovecot.conf does not contain the SSL configuration so where it tell to find the .pem certifactes.?And how I do to enable certificates also for Imaps, i wish to use only imaps not POP not IMAP and with a go daddy firmed certificates.