Re: Webmail accessive Dovecot logins

2015-10-30 Thread Steffen Kaiser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, 29 Oct 2015, David Mehler wrote:


I've seen this issue before, running a imap/smtp/database server on
localhost and adding in a webmail interface, in this case Roundcube.

In my maillog I'm seeing accessive Dovecot connections and logouts
just from my own transaction of logging in, going to compose a
message, sending, and logging out.

I'm using Mysql as database backend and was wondering if there was
something I could do to cut down on the amount of connections needed?


:-) don't connect so often.

I guess with "from my own transaction" you mean a transaction in 
roundcube?


http://trac.roundcube.net/wiki/Howto_Config/Performance
"Use a caching IMAP proxy"

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBVjMb+3z1H7kL/d9rAQIf7wgAuX4CLKqlScNUhbIdVLGHWjkJbdEsGlds
TYvNvgMSzV/ga2yCZvXBQuSJgsAmPcw0u5r8cQ/giOg6RD8JNhDarCzW0EVsjcoh
NwKv/WuRpMS5dOw5F3WWgtJnP55upulYN4EvmYilxuO9XGsVYdzmR/TlXae/Urw9
n31YLVrMkE7DzSm5JSUhUBOKT+u3yCLdQ7MYzDeH9G1Tt6el3ZOZSOWRhgwSngTz
cwuPM84Q6kxifxdMibfMF8CwX2RwBbigstheQaJQH6l6vypvyjT7WMO3XRKxkBfZ
MIQCoI6nv1iYArN3Cdlt25IfZEucTvzRRaYD86LtA9z3H4X+YXy8FA==
=bbSN
-END PGP SIGNATURE-


IMAP COPY creates invalid index data with zlib and mail_log plugins enabled but zlib_save off

2015-10-30 Thread Robert L Mathews
I've noticed that maildir IMAP COPY commands can generate invalid
dovecot.index entries when all seven of the following are true:

- The zlib plugin is enabled;
- The zlib_save/zlib_save_level options are NOT enabled;
- The source message being copied is compressed;
- The mail_log plugin is logging "copy" events;
- The mail_log_fields setting includes at least one message header;
- The destination mailbox folder has an index file that is recording the
logged headers;
- The source mailbox folder does NOT have an index file recording the
logged headers.

In this situation, copying a message results in an index entry in the
destination that has all the headers blank, like this:

RECORD: seq=5, uid=182415, flags=0x08 (Seen)
 - ext 1 modseq:  3 (0300)
 - ext 2 cache :   2352 (3009)
 - cache offset=2352 size=120, prev_offset = 0
- hdr.FROM:
- hdr.MESSAGE-ID:
- hdr.SUBJECT:
- hdr.DATE:
- hdr.BCC:
- hdr.CC:
- hdr.CONTENT-TYPE:
- hdr.IN-REPLY-TO:
- hdr.NEWSGROUPS:
- hdr.PRIORITY:
- hdr.REFERENCES:
- hdr.REPLY-TO:
- hdr.TO:
- hdr.X-PRIORITY:

For these copies, the mail_log plugin records blank header data in the
log, too, like this (despite the message having a valid message-ID,
from, and subject):

Oct 29 21:11:42 wheezy dovecot: imap[31763]: user=<1...@example.com>
ip=192.168.0.4 session=RV/MmUojyADAqAAE copy from INBOX.Saved:
box=INBOX.Trash, uid=182412, msgid=, size=1357, vsize=1392, from=,
subject=, flags=(\Seen)

I've found this occurs in at least Dovecot 2.1.7, 2.2.13, and 2.2.18
(all packaged Debian versions).

Changing any of the seven things I mentioned above fixes it. I've tried
to find the code that causes this, but not yet been successful. My
theory is that when the mail_log plugin calls mail_get_first_header(),
and there's no index header record to read it from, it looks at the real
message on disk. Perhaps it somehow operates on a compressed copy of the
message although it expects uncompressed plaintext, so it doesn't find
any of the headers. The "missing" headers then get cached to the
destination index file as a side-effect.

The copied maildir message itself is fine, by the way. It's an
identical, still-compressed copy of the original message. And deleting
the destination "dovecot.index*" files that contain the bad data causes
Dovecot to rebuild the index with the correct header data.

It's unusual to use the zlib plugin without the
zlib_save/zlib_save_level options enabled, of course. That's probably
why (as far as I can tell) there have been no reports of this before. I
noticed it only because I was testing a small amount of manual mail
compression before deploying it for all mail.

Here's the "doveconf -n" of a system in the "has the problem" state:

# 2.2.18: /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.8 (0c4ae064f307+)
# OS: Linux 3.2.0-4-686-pae i686 Debian stretch/sid
auth_mechanisms = plain login
auth_username_format =
auth_verbose = yes
auth_verbose_passwords = sha1
default_vsz_limit = 1 G
disable_plaintext_auth = no
lda_mailbox_autosubscribe = yes
listen = *
log_timestamp = "%Y-%m-%d %H:%M:%S "
login_log_format_elements = user=<%u> pid=[%{mail_pid}] method=%m rip=%r
lip=%l %c
mail_fsync = never
mail_location = maildir:~/
mail_log_prefix = "%s[%{pid}]: user=<%u> ip=%{rip} session=%{session} "
mail_max_userip_connections = 100
mail_plugins = mail_log notify zlib
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex
imap4flags copy include variables body enotify environment mailbox date
index ihave duplicate spamtest spamtestplus
namespace {
  inbox = yes
  location =
  prefix = INBOX.
  separator = .
  type = private
}
namespace {
  hidden = yes
  inbox = no
  list = no
  location =
  prefix =
  separator = .
  type = private
}
passdb {
  args = /etc/dovecot/dovecot.users
  driver = passwd-file
}
plugin {
  fts = lucene
  fts_lucene = whitespace_chars=@.
  mail_log_events = copy delete undelete expunge mailbox_delete
mailbox_rename flag_change save mailbox_create
  mail_log_fields = vsize size flags box uid box msgid size flags vsize
from subject
  sieve = %h/mailbox.sieve
  sieve_after = %h/../../domain-after.sieve
  sieve_before = %h/../../domain-before.sieve
  sieve_dir = %h/sieve
  sieve_extensions = -reject +spamtest +spamtestplus
  sieve_global_dir = %h/../../sieve-global-include-scripts
  sieve_spamtest_max_value = 7
  sieve_spamtest_status_header = X-Spam-Level
  sieve_spamtest_status_type = strlen
}
protocols = pop3 imap lmtp sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
}
service imap-login {
  process_min_avail = 8
  service_count = 0
}
service imap {
  process_limit = 2000
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
   

Re: Webmail accessive Dovecot logins

2015-10-30 Thread Joseph Tam


"A. Schulze"  writes:


David Mehler:


Second question, in the doveconf -n there's reference to my ssl_cipher
am I  using current tls ciphers that support pfs?



ssl_cipher_list = ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL


some non pfs cipher would be still active. check yourself:
# openssl ciphers -v 'ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL' | grep -v DH


You'll want the 'E' variation (ephemeral) of the DH algorithms, and
preferably, the ECDHE variety as they are faster and supported on more
browsers.  The pattern to search for (or exclude) is "DHE"

openssl ciphers -v {cipher-specs} | grep DHE

If the OP wants preferentially use PFS ciphers (but keep the other
ciphers around for very old browsers),  maybe something like

ssl_cipher_list = ECDH:ALL:!LOW:!SSLv2:!EXP:!aNULL
ssl_prefer_server_ciphers = yes


finally you could use the service provided by ssllabs.com to scan your host.


I second this recommendation, if you can work out the port issue.  Maybe using
a ncat | ncat pipe.

Joseph Tam 


Re: Dovecot frequently full-text reindexes the whole maildir

2015-10-30 Thread vitalif
Thanks, after rewriting anti-spam scripts to doveadm and changing the 
search engine to fts-lucene fulltext indexing started to work reliably 
(fts-squat has constantly corrupted its index files, but lucene is 
working OK).


Now I have another small question: 'doveadm expunge' (even with -v) does 
not print any errors, but always returns exit code 68 in my case. What 
does it mean? I would like to get zero exit code in case of success...



Hi,

I'm not an expert, but am doing something similar (moving messages and
training the spam filter).

To detect the existence of new messages looking directly at the
maildir can be a quick and dirty solution to get a trigger event.

But to move or delete I think you should use  'doveadm' to search for
all messages in your spam directory and get a list of all uids an
guids. Then you can call doveadm again to move vor delete the messages
by id.

Just look for "doveadm search/move/purge" in the dovecot wiki.
This should ensure that the indexes stay up to date.

Am 27. Oktober 2015 11:24:39 MEZ, schrieb vita...@yourcmc.ru:

Hi!

I'm using Dovecot 2.2.13 (Debian Jessie package 1:2.2.13-12~deb8u1) on
my personal mail server (the address I'm writing from is on this
server).

I use Maildirs, I have fts + fts_squat enabled, and I have a problem
with it for a long time - dovecot seems to not update the index always
"incrementally".

Yesterday I've finally made a test by telneting to imap port and
issuing
a search request. Dovecot started to reindex the mailbox. Full
reindexing has taken around 15-20 minutes.

After reindexing the fulltext searches were fast, just as they should
be. And they were fast yesterday even after some new emails arrived.

But I've tried to do a new search today and Dovecot started to reindex
the whole maildir again!

Why is it reindexing the whole maildir again? Could it be related to 
my


anti-spam scripts removing messages from SPAM imap folder? And if yes,
how to remove them correctly?



--
With best regards,
  Vitaliy Filippov


Re: updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve

2015-10-30 Thread Teemu Huovila


On 30.10.2015 12:18, Götz Reinicke - IT Koordinator wrote:
> Hi,
> 
> winter is coming and so I start to clean up some left overs of the year.
> 
> One thing is to use the yum.dovecot.fi repository.
> 
> After installing the current availabel dovecot and dovecot-ee-pigeonhole
> package and restarting dovecot I do get the error:
> 
> 
> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
> protocols: Unknown protocol: sieve
Could you please reply with the output of doveconf -n


> 
> 
> Is the sieve protocol an extra package? I thought in the 2.2. tree I
> dont have to do bigger config changes.
> 
> We run already 2.2.something from city-fan.org and the switch was also
> the idea of going to the most recent release.
> 
> 
>   Thanks for hints and feedback . Götz
> 


Initialization Failed:

2015-10-30 Thread brian

Hi dovecotters

I am trying to install dovecot on a mail server I am provisioning for 
myself in AWS.
I am following an ArsTechnica guide, and at some stage in the process 
the author recommends and provides instructions to configure Dovecot 
(http://arstechnica.com/information-technology/2014/03/taking-e-mail-back-part-2-arming-your-server-with-postfix-dovecot/4/) 



So, now I have it installed and configured (I believe the way suggested) 
but when I try to connect via IMAP I am getting an error.


If I try :
root@ip-10-0-0-244:~# telnet mail.myactualdomain.com 143
Trying 127.0.0.1...
Connected to mail.myactualdomain.com.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.

a1 LOGIN br...@myactualdomain.com plaintextpassword
* BYE Internal error occurred. Refer to server log for more information.
Connection closed by foreign host.
root@ip-10-0-0-244:~#

If I go to /var/log/syslog I can see the following lines:
Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap-login: Login: 
user=, method=PLAIN, rip=127.0.0.1, 
lip=127.0.0.1, mpid=16934, secured, session=
Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(br...@myactualdomain.com): 
Error: user br...@myactualdomain.com: Initialization failed: Namespace 
'': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail
Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(br...@myactualdomain.com): 
Error: Invalid user settings. Refer to server log for more information.


root@ip-10-0-0-244:~# dovecot --version
2.2.9

So, I don't know why it's giving me an error about :
Initialization failed: Namespace '': Unknown setting: 
/var/mail/vmail/myactualdomain.com/brian/mail


The location is there, with the permissions with I believe the correct 
permissions.

I'm a bit stuck as to where to even go from here.

Any help would be greatly appreciated.

Kind Regards
Brian



root@ip-10-0-0-244:~# dovecot -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-48-generic x86_64 Ubuntu 14.04.2 LTS
auth_mechanisms = plain login
auth_verbose = yes
mail_home = /var/mail/vmail/%d/%n
mail_location = maildir:~/Maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body enotify 
environment mailbox date ihave

namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
auto = subscribe
special_use = \Drafts
  }
  mailbox Junk {
auto = subscribe
special_use = \Junk
  }
  mailbox Sent {
auto = subscribe
special_use = \Sent
  }
  mailbox Trash {
auto = subscribe
special_use = \Trash
  }
  prefix =
}
passdb {
  args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db
  driver = passwd-file
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_after = /var/mail/vmail/sieve-after
  sieve_before = /var/mail/vmail/sieve-before
  sieve_dir = ~/sieve
}
protocols = imap sieve
service auth {
  unix_listener /var/spool/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
  }
}
ssl_cert = ssl_cipher_list = 
ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM

ssl_client_ca_dir = /etc/ssl/certs
ssl_key =  was automatically rejected:%n%r
}
protocol imap {
  imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
  mail_max_userip_connections = 10
}


Re: updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve

2015-10-30 Thread Götz Reinicke - IT Koordinator
Am 30.10.15 um 11:49 schrieb Teemu Huovila:
> 
> 
> On 30.10.2015 12:18, Götz Reinicke - IT Koordinator wrote:
>> Hi,
>>
>> winter is coming and so I start to clean up some left overs of the year.
>>
>> One thing is to use the yum.dovecot.fi repository.
>>
>> After installing the current availabel dovecot and dovecot-ee-pigeonhole
>> package and restarting dovecot I do get the error:
>>
>>
>> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
>> protocols: Unknown protocol: sieve
> Could you please reply with the output of doveconf -n


my guess: in the currently used rpms the "managesieve" libs are
included; for the official dovecot repo I do have to install the
dovecot-ee-managesieve.rpm too...


# 2.2.18.2 (866bffbafde7): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-371.6.1.el5xen x86_64 CentOS release 5.11 (Final)
auth_debug = yes
auth_master_user_separator = *
auth_mechanisms = plain login
auth_verbose = yes
default_client_limit = 4000
default_process_limit = 4000
disable_plaintext_auth = no
log_path = /var/log/dovecot.log
login_trusted_networks = 193.196.129.21
mail_debug = yes
mail_location = maildir:~/Maildir
mail_plugins = mail_log notify quota acl
mail_privileged_group = mail
mdbox_rotate_size = 10 M
namespace {
  list = children
  location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u
  prefix = shared/%%u/
  separator = /
  subscriptions = yes
  type = shared
}
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
  separator = /
}
passdb {
  args = /etc/dovecot/master-users
  driver = passwd-file
  master = yes
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  acl = vfile
  acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes
  quota = dict:User quota::noenforcing:file:%h/dovecot-quota
  quota_rule = *:storage=5G
  quota_rule2 = Trash:storage=+100M
  quota_warning = storage=95%% quota-warning 95 %u
  quota_warning2 = storage=80%% quota-warning 80 %u
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
postmaster_address = postmas...@filmakademie.de
protocols = imap pop3 lmtp sieve sieve
quota_full_tempfail = yes
service auth {
  unix_listener /var/spool/postfix/private/auth {
mode = 0666
  }
  unix_listener auth-userdb {
group = vmail
user = vmail
  }
  user = root
}
service imap-login {
  process_limit = 1024
  process_min_avail = 16
  service_count = 0
}
service imap {
  process_limit = 1024
}
service lmtp {
  inet_listener lmtp {
address = 127.0.0.1
port = 24
  }
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
  service_count = 1
}
service managesieve {
  process_limit = 1024
}
service pop3-login {
  process_limit = 1024
  process_min_avail = 16
  service_count = 0
}
service pop3 {
  process_limit = 1024
}
service quota-warning {
  executable = script /usr/local/bin/quota-warning.sh
  unix_listener quota-warning {
user = vmail
  }
  user = dovecot
}
ssl_ca = 

smime.p7s
Description: S/MIME Cryptographic Signature


Re: Webmail accessive Dovecot logins

2015-10-30 Thread A. Schulze


David Mehler:


Second question, in the doveconf -n there's reference to my ssl_cipher
am I  using current tls ciphers that support pfs?




ssl_cipher_list = ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL


some non pfs cipher would be still active. check yourself:
# openssl ciphers -v 'ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL' | grep -v DH

you disable the SSLv3 *cipher list* here. That's may be not the  
expected result.

The *cipher list* SSLv3 is also used by TLSv1+ *protocols*.
I suggest reading (again?)  
https://bettercrypto.org/static/applied-crypto-hardening.pdf



ssl_protocols = TLSv1 !SSLv3 !SSLv2
that disable SSLv2, SSLv3 but would also disable TLSv1.1 and TLSv1.2  
your ssl library may support otherwise.


better:
ssl_protocols = !SSLv3 !SSLv2

finally you could use the service provided by ssllabs.com to scan your host.
It's a little bit tricky. ssllabs allow only to scan on port 443
So you may configure your host for imaps ( not imap + STARTTLS ) on port 443
and use ssllabs.com. But that require you do not run a regular HTTPS  
webserver on the same host.


Andreas


Re: updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve

2015-10-30 Thread Teemu Huovila


On 30.10.2015 15:35, Götz Reinicke - IT Koordinator wrote:
> Am 30.10.15 um 11:49 schrieb Teemu Huovila:
>>
>>
>> On 30.10.2015 12:18, Götz Reinicke - IT Koordinator wrote:
>>> Hi,
>>>
>>> winter is coming and so I start to clean up some left overs of the year.
>>>
>>> One thing is to use the yum.dovecot.fi repository.
>>>
>>> After installing the current availabel dovecot and dovecot-ee-pigeonhole
>>> package and restarting dovecot I do get the error:
>>>
>>>
>>> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
>>> protocols: Unknown protocol: sieve
>> Could you please reply with the output of doveconf -n
> 
> 
> my guess: in the currently used rpms the "managesieve" libs are
> included; for the official dovecot repo I do have to install the
> dovecot-ee-managesieve.rpm too...
Yes, if you have "protocols = sieve .." then you need the managesieve package 
too. Also, to use sieve filtering, you need to load the sieve plugin in 
mail_plugins for lmtp or lda. Please refer to 
http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration
http://wiki2.dovecot.org/Pigeonhole/ManageSieve/Configuration

Teemu
 
> 
> # 2.2.18.2 (866bffbafde7): /etc/dovecot/dovecot.conf
> # OS: Linux 2.6.18-371.6.1.el5xen x86_64 CentOS release 5.11 (Final)
> auth_debug = yes
> auth_master_user_separator = *
> auth_mechanisms = plain login
> auth_verbose = yes
> default_client_limit = 4000
> default_process_limit = 4000
> disable_plaintext_auth = no
> log_path = /var/log/dovecot.log
> login_trusted_networks = 193.196.129.21
> mail_debug = yes
> mail_location = maildir:~/Maildir
> mail_plugins = mail_log notify quota acl
> mail_privileged_group = mail
> mdbox_rotate_size = 10 M
> namespace {
>   list = children
>   location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u
>   prefix = shared/%%u/
>   separator = /
>   subscriptions = yes
>   type = shared
> }
> namespace inbox {
>   inbox = yes
>   location =
>   mailbox Drafts {
> special_use = \Drafts
>   }
>   mailbox Junk {
> special_use = \Junk
>   }
>   mailbox Sent {
> special_use = \Sent
>   }
>   mailbox "Sent Messages" {
> special_use = \Sent
>   }
>   mailbox Trash {
> special_use = \Trash
>   }
>   prefix =
>   separator = /
> }
> passdb {
>   args = /etc/dovecot/master-users
>   driver = passwd-file
>   master = yes
> }
> passdb {
>   args = /etc/dovecot/dovecot-ldap.conf.ext
>   driver = ldap
> }
> plugin {
>   acl = vfile
>   acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes
>   quota = dict:User quota::noenforcing:file:%h/dovecot-quota
>   quota_rule = *:storage=5G
>   quota_rule2 = Trash:storage=+100M
>   quota_warning = storage=95%% quota-warning 95 %u
>   quota_warning2 = storage=80%% quota-warning 80 %u
>   sieve = ~/.dovecot.sieve
>   sieve_dir = ~/sieve
> }
> postmaster_address = postmas...@filmakademie.de
> protocols = imap pop3 lmtp sieve sieve
> quota_full_tempfail = yes
> service auth {
>   unix_listener /var/spool/postfix/private/auth {
> mode = 0666
>   }
>   unix_listener auth-userdb {
> group = vmail
> user = vmail
>   }
>   user = root
> }
> service imap-login {
>   process_limit = 1024
>   process_min_avail = 16
>   service_count = 0
> }
> service imap {
>   process_limit = 1024
> }
> service lmtp {
>   inet_listener lmtp {
> address = 127.0.0.1
> port = 24
>   }
> }
> service managesieve-login {
>   inet_listener sieve {
> port = 4190
>   }
>   service_count = 1
> }
> service managesieve {
>   process_limit = 1024
> }
> service pop3-login {
>   process_limit = 1024
>   process_min_avail = 16
>   service_count = 0
> }
> service pop3 {
>   process_limit = 1024
> }
> service quota-warning {
>   executable = script /usr/local/bin/quota-warning.sh
>   unix_listener quota-warning {
> user = vmail
>   }
>   user = dovecot
> }
> ssl_ca =  ssl_cert =  ssl_cipher_list =
> DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ALL:!LOW:!SSLv2:!EXP:!aNULL
> ssl_key =  ssl_prefer_server_ciphers = yes
> userdb {
>   args = /etc/dovecot/dovecot-ldap.conf.ext
>   driver = ldap
> }
> verbose_proctitle = yes
> doveconf: Error: protocols: Unknown protocol: sieve
> protocol lmtp {
>   info_log_path = /var/log/dovecot-lmtp.log
>   log_path = /var/log/dovecot-lmtp-errors.log
>   mail_plugins = mail_log notify quota acl sieve
> }
> protocol imap {
>   mail_max_userip_connections = 20
>   mail_plugins = mail_log notify quota acl imap_zlib imap_quota imap_acl
> }
> protocol pop3 {
>   mail_max_userip_connections = 20
> }
> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
> protocols: Unknown protocol: sieve
> 
> 


Re: updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve

2015-10-30 Thread Götz Reinicke - IT Koordinator
Am 30.10.15 um 15:44 schrieb Teemu Huovila:
> 
> 
> On 30.10.2015 15:35, Götz Reinicke - IT Koordinator wrote:
>> Am 30.10.15 um 11:49 schrieb Teemu Huovila:
>>>
>>>
>>> On 30.10.2015 12:18, Götz Reinicke - IT Koordinator wrote:
 Hi,

 winter is coming and so I start to clean up some left overs of the year.

 One thing is to use the yum.dovecot.fi repository.

 After installing the current availabel dovecot and dovecot-ee-pigeonhole
 package and restarting dovecot I do get the error:


 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
 protocols: Unknown protocol: sieve
>>> Could you please reply with the output of doveconf -n
>>
>>
>> my guess: in the currently used rpms the "managesieve" libs are
>> included; for the official dovecot repo I do have to install the
>> dovecot-ee-managesieve.rpm too...
> Yes, if you have "protocols = sieve .." then you need the managesieve package 
> too. Also, to use sieve filtering, you need to load the sieve plugin in 
> mail_plugins for lmtp or lda. Please refer to 
> http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration
> http://wiki2.dovecot.org/Pigeonhole/ManageSieve/Configuration

Hi,

currently sieve filtering is working (sieve plugin in mail_plugins for
lmtp is enabled) with the old repo packages; do I have to install an
other something-plugin.rpm from the dovecot repo?

Thanks & Regards . Götz

-- 
Götz Reinicke
IT-Koordinator

Tel. +49 7141 969 82420
E-Mail goetz.reini...@filmakademie.de

Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de

Eintragung Amtsgericht Stuttgart HRB 205016

Vorsitzender des Aufsichtsrats: Jürgen Walter MdL
Staatssekretär im Ministerium für Wissenschaft,
Forschung und Kunst Baden-Württemberg

Geschäftsführer: Prof. Thomas Schadt



smime.p7s
Description: S/MIME Cryptographic Signature


Re: updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve

2015-10-30 Thread Philon
Hi Götz,

for my debian repository at least I find these packages:
dovecot-ee-sieve - sieve filters support for Dovecot
dovecot-ee-managesieved - secure ManageSieve server for Dovecot

Could be that your third party yum package had these included in the default 
build.


Grüße aus Tübingen
Philon

> Am 30.10.2015 um 15:56 schrieb Götz Reinicke - IT Koordinator 
> :
> 
> Am 30.10.15 um 15:44 schrieb Teemu Huovila:
>> 
>> 
>> On 30.10.2015 15:35, Götz Reinicke - IT Koordinator wrote:
>>> Am 30.10.15 um 11:49 schrieb Teemu Huovila:
 
 
 On 30.10.2015 12:18, Götz Reinicke - IT Koordinator wrote:
> Hi,
> 
> winter is coming and so I start to clean up some left overs of the year.
> 
> One thing is to use the yum.dovecot.fi repository.
> 
> After installing the current availabel dovecot and dovecot-ee-pigeonhole
> package and restarting dovecot I do get the error:
> 
> 
> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
> protocols: Unknown protocol: sieve
 Could you please reply with the output of doveconf -n
>>> 
>>> 
>>> my guess: in the currently used rpms the "managesieve" libs are
>>> included; for the official dovecot repo I do have to install the
>>> dovecot-ee-managesieve.rpm too...
>> Yes, if you have "protocols = sieve .." then you need the managesieve 
>> package too. Also, to use sieve filtering, you need to load the sieve plugin 
>> in mail_plugins for lmtp or lda. Please refer to 
>> http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration
>> http://wiki2.dovecot.org/Pigeonhole/ManageSieve/Configuration
> 
> Hi,
> 
> currently sieve filtering is working (sieve plugin in mail_plugins for
> lmtp is enabled) with the old repo packages; do I have to install an
> other something-plugin.rpm from the dovecot repo?
> 
>   Thanks & Regards . Götz
> 
> -- 
> Götz Reinicke
> IT-Koordinator
> 
> Tel. +49 7141 969 82420
> E-Mail goetz.reini...@filmakademie.de 
> 
> Filmakademie Baden-Württemberg GmbH
> Akademiehof 10
> 71638 Ludwigsburg
> www.filmakademie.de 
> 
> Eintragung Amtsgericht Stuttgart HRB 205016
> 
> Vorsitzender des Aufsichtsrats: Jürgen Walter MdL
> Staatssekretär im Ministerium für Wissenschaft,
> Forschung und Kunst Baden-Württemberg
> 
> Geschäftsführer: Prof. Thomas Schadt


updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve

2015-10-30 Thread Götz Reinicke - IT Koordinator
Hi,

winter is coming and so I start to clean up some left overs of the year.

One thing is to use the yum.dovecot.fi repository.

After installing the current availabel dovecot and dovecot-ee-pigeonhole
package and restarting dovecot I do get the error:


doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
protocols: Unknown protocol: sieve


Is the sieve protocol an extra package? I thought in the 2.2. tree I
dont have to do bigger config changes.

We run already 2.2.something from city-fan.org and the switch was also
the idea of going to the most recent release.


Thanks for hints and feedback . Götz

-- 
Götz Reinicke
IT-Koordinator

Tel. +49 7141 969 82420
E-Mail goetz.reini...@filmakademie.de

Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de

Eintragung Amtsgericht Stuttgart HRB 205016

Vorsitzender des Aufsichtsrats: Jürgen Walter MdL
Staatssekretär im Ministerium für Wissenschaft,
Forschung und Kunst Baden-Württemberg

Geschäftsführer: Prof. Thomas Schadt



smime.p7s
Description: S/MIME Cryptographic Signature