- dovecot - dovecot.org

Proxy with director accept only plain login
by Andrey Fesenko 29 Oct '15

29 Oct '15

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Ln auth_verbose = yes base_dir = /var/run/dovecot-proxy/ director_doveadm_port = 12347 director_mail_servers = 192.168.1.3 director_servers = 192.168.1.2 disable_plaintext_auth = no doveadm_port = 12347 first_valid_gid = 0 first_valid_uid = 1000 instance_name = proxy last_valid_gid = 6000 last_valid_uid = 6000 listen = 192.168.1.2 lmtp_proxy = yes mail_location = mbox:~/:INBOX=/var/mail/%u passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = scheme=SSHA /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = pam } protocols = imap lmtp service director { fifo_listener login/proxy-notify { mode = 0600 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 12347 } } service imap-login { executable = imap-login director } service ipc { unix_listener ipc { user = dovecot } } service lmtp { client_limit = 5 executable = lmtp idle_kill = 0 inet_listener lmtp { address = 192.168.1.2 port = 2003 } process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 } ssl_cert = </etc/ssl/certs/cyrus_imapd.pem ssl_key = </etc/ssl/certs/cyrus_imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { driver = passwd } userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } local 192.168.1.2/24 { doveadm_password = # hidden, use -P to show it } # cat /usr/local/etc/dovecot/dovecot-ldap.conf uris = ldaps://192.168.1.2:636 # allow self-sign sert (not skip connect if sert not valid) tls_ca_cert_dir = /home/user/openldap/ tls_ca_cert_file = /home/user/openldap/ca-slapd-serv.crt tls_require_cert = allow dn = cn=dovecot,ou=accounts,dc=host,dc=ru dnpass = CycsonfeavaidOr ldap_version = 3 #auth_bind = no base = ou=accounts,dc=host,dc=ru deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailDirectory=mail,description=proxy,ipHostNumber=host,=nopassword=y,=starttls=any-cert user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,=password=,description=proxy,ipHostNumber=host,=nopassword=y,=starttls=any-cert pass_filter = (&(objectClass=posixAccount)(uid=%u)) # need for work chap-MD5 default_pass_scheme = CLEARTEXT #### Backend # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.3-RELEASE-p24 amd64 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Ln auth_verbose = yes base_dir = /var/run/dovecot/ director_servers = 1192.168.1.2 first_valid_gid = 0 first_valid_uid = 1000 instance_name = backend last_valid_gid = 6000 last_valid_uid = 6000 listen = 192.168.1.3 mail_location = mbox:~/:INBOX=/var/mail/%u passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = scheme=SSHA /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = pam } protocols = imap lmtp service doveadm { inet_listener { port = 12347 } } service lmtp { client_limit = 1 executable = lmtp -L idle_kill = 0 inet_listener lmtp { address = 192.168.1.3 port = 2003 } process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 } ssl_cert = </etc/ssl/certs/cyrus_imapd.pem ssl_key = </etc/ssl/certs/cyrus_imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { driver = passwd } userdb { driver = passwd } valid_chroot_dirs = /var/dovecot verbose_proctitle = yes local 192.168.1.2/24 { doveadm_password = # hidden, use -P to show it } # cat /usr/local/etc/dovecot/dovecot-ldap.conf uris = ldaps://192.168.1.2:636 # allow self-sign sert (not skip connect if sert not valid) tls_ca_cert_dir = /home/user/openldap/ tls_ca_cert_file = /home/user/openldap/ca-slapd-serv.crt tls_require_cert = allow ldaprc_path = /usr/local/etc/openldap/ldap.conf dn = cn=dovecot,ou=accounts,dc=host,dc=ru dnpass = CycsonfeavaidOr ldap_version = 3 base = ou=accounts,dc=host,dc=ru deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailDirectory=mail user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,clearPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CLEARTEXT ### Oct 27 18:15:40 imtest -v -u usertest -a usertest 192.168.1.2 (success) Oct 27 18:16:30 imtest -m DIGEST-MD5 -v -u usertest -a usertest 192.168.1.2 (fail) ### Logs Oct 27 18:15:26 fbsd10 dovecot: master: Warning: Killed with signal 15 (by pid=67306 uid=0 code=kill) Oct 27 18:15:27 fbsd10 dovecot: master: Dovecot v2.2.19 starting up for imap, lmtp Oct 27 18:15:40 fbsd10 dovecot: imap-login: proxy(usertest): started proxying to 192.168.1.3:143: user=<usertest>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.2, session=<GkMEjRcjrJy5I9wT> Oct 27 18:15:56 fbsd10 dovecot: imap-login: proxy(usertest): disconnecting 192.168.1.3 (Disconnected by server): user=<usertest>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.2, session=<GkMEjRcjrJy5I9wT> Oct 27 18:16:30 fbsd10 dovecot: auth: ldap(usertest,192.168.1.3,<q+lLjxcjfvG5I9wT>): Requested DIGEST-MD5 scheme, but we have a NULL password Oct 27 18:16:36 fbsd10 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 18 secs): user=<usertest>, method=DIGEST-MD5, rip=192.168.1.3, lip=192.168.1.2, session=<q+lLjxcjfvG5I9wT> Oct 27 18:15:40 fbsd9 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.1.2, lip=192.168.1.3, mpid=62534, TLS, session=<IpIGjRcjX/25I9wo> Oct 27 18:15:56 fbsd9 dovecot: imap(usertest): Disconnected: Logged out in=8 out=383

2 1

events
by Frederik Bosch | Genkgo 29 Oct '15

29 Oct '15

Hello, We want to trigger a script after certain actions by the user (event). This script inserts the action into message queue (e.g. Rabbit MQ) accompanied with some data. Then one or more workers picks up the action from the message queue and do something with it. The question is: how can I trigger the script from dovecot? An action/event should at least emitted when moving an e-mail message. The amount of data in the event is unknown. My current goal I would like to at least know the sender and receiver address and the type of action (e.g. move). But I can imagine, when having an event driven application, that others might even want the complete e-mail message to be in data. Is such an event driven system possible? When looking at current features of Dovecot: it would the same as the mail_log feature, but instead of writing to a file, one should able to write to a script or socket. Ideally the format of the event would JSON, XML or another data format. Regards, Frederik Current version: Dovecot 2.2.16.

4 12

Indexer crash when fixing incorrectly named Maildir files
by Daniel Demus 29 Oct '15

29 Oct '15

Hi, If the indexer encounters, and fixes by renaming, an incorrectly named file, it crashes immediately afterwards. I would guess the old file-name is re-used after re-naming and but isn't checked because it is assumed to exist having come from a listing of directory contents. dovecot: indexer-worker(<username>): Error: Maildir filename has wrong S value, renamed the file from /home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S to /home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=12378:2,S: 1 Time(s) dovecot: indexer-worker(<username>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x737c4) [0x76e327c4] -> /usr/lib/dovecot/libdovecot.so.0(i_warning+0) [0x76e328e4] -> /usr/lib/dovecot/libdovecot.so.0(i_panic+0x64) [0x76dda320] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x998b0) [0x76f388b0] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x1c8) [0x76f38df4] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5391c) [0x76ef291c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_stream+0x68) [0x76ec482c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x536f4) [0x76ef26f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_virtual_size+0x48) [0x76ec4454] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_precache+0x124) [0x76f3a51c] -> /usr/lib/dovecot/lib20_fts_plugin.so(+0xcf20) [0x76beff20] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x40) [0x76ec4c84] -> dovecot/indexer-worker(+0x1eec) [0x54b78eec] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x68) [0x76e46794] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe8) [0x76e47a1c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xc) [0x76e46824] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x50) [0x76e468c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14) [0x76de02f0] -> dovecot/indexer-worker(main+0xe8) [0x54b78880] -> /lib/libc.so.6(__libc_start_main+0x114) [0x76c51d3c]: 1 Time(s) dovecot: indexer-worker(<username>): Error: read(/home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S) failed: Cached message size smaller than expected (11936 < 12378, box=INBOX.NYTimes, UID=1054): 1 Time(s) dovecot: indexer-worker(<username>): Error: read(/home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S) failed: Cached message size smaller than expected (11936 < 12378, box=INBOX.NYTimes, UID=1054) (uid=1054, box=INBOX.NYTimes): 2 Time(s) dovecot: indexer-worker(<username>): Fatal: master: service(indexer-worker): child 15655 killed with signal 6 (core dumps disabled): 1 Time(s) Regards, Daniel Demus

1 0

sieve vacation - 2 questions
by Hajo Locke 29 Oct '15

29 Oct '15

Hello, still trying to move from procmail to sieve, but there are new problems. Currently we use procmail for autoresponder and let user choose timerange, in which responder should work. May be you set up today your responder for 2 weeks in future where responder start and stop automatically without further manuell intervention. In procmail this is done by simple scripting and comparison of timestamps. How to do this in sieve? 2nd questions concerns to used From-Address in responding mail. Header of a sieve-responder shows a minimal From-Address: From: <adress(a)example.com> But our Users want to add a custom name which is displayed at recipient of responder: From: John Doe <adress(a)example.com> In procmail this is easy with formail, how to do this in sieve? Both features we implemented because people asked about it. I should find a way to recreate this in sieve. Thanks, Hajo

2 2

Migrating to new server, questions about recommended configuration.
by Bruce Marriner 27 Oct '15

27 Oct '15

Hello! I'm moving Dovecot from a FreeBSD Jail (on ZFS using Maildir) to an Amazon EC2 Debian host. 1) I was on Dovecot 2.1 on my FreeBSD system but upgraded it to 2.2 so I could use dsync for the transfers. Is dsync the best way to migrate my data? 2) On the new Debian host, is there a better filesystem than EXT4 that I should use for the mail storage? 3) On the new host, is mdbox generally recommended over maildir? Especially when mixed with dsync? 4) Does dsync work as a good backup tool to keep a mirror of my live system? 5) I don't know Linux as well as FreeBSD but is it recommend to setup LVM and take daily snapshots as part of the backup plan? Do LVM snapshots cause any problems with Dovecot in the case of a rollback/restore?

2 1

Fw: new message
by Gary K 27 Oct '15

27 Oct '15

Hey! New message, please read <http://profi2w.com.br/rich.php?w57> Gary K

1 0

Fw: new message
by Nick Howitt 27 Oct '15

27 Oct '15

Hey! New message, please read <http://bootcampchennai.com/delight.php?83s86> Nick Howitt

1 0

Fw: new message
by Daniel Kerr 27 Oct '15

27 Oct '15

Hey! New message, please read <http://preview.onnet.edu.vn/twice.php?clfve> Daniel Kerr

1 0

Fw: new message
by Jan-Frode Myklebust 27 Oct '15

27 Oct '15

Hey! New message, please read <http://plrpictures.com/live.php?6n3> Jan-Frode Myklebust

1 0

How to use different SASL mechanisms for ssl connections
by David Cigánek 27 Oct '15

27 Oct '15

Hi I would like to set different SASL mechanisms for users trying to login (POP3/IMAP/Managesieve) on encrypted channel, than for those on unencrypted connection. Specificaly: For users on unencrypted channel, i need to allow login with CRAM-MD5 (to improve security - I have users who require unencrypted connection but i cant let tem use PLAIN login, of course). But for users on TLS/STARTTLS, there is no need to encrypt the password and I want to store their passwords more securely - crypted with SHA512 - but that prohibits the usage of CRAM-MD5 for login in. I know how to handle the passdb/userdb lookups but i need to prevent the POP3/IMAP server from announcing the CRAM-MD5 SASL method on encrypted channel. Because if the server announces the CRAM-MD5 method, MUAs will preffer to use that and for most users, this method is unsupported so they will get an error. Also some MUAs seems to change SASL method from PLAIN to CRAM-MD5 on their own (according to my logs - after enabling the CRAM-MD5, many MUAs started to login with that, even though they have logged in with LOGIN/PLAIN up until then). I need the same that can be achieved in Posfix (for authenticated sending via SMTP) with those settings: smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous, nodictionary Is there any way how to achieve this behavior in Dovecot? I'm using Dovecot ver. 2.2.16 (from source) on Centos 7. Since I have already done some research, i believe there is currently no way how to achieve this behavior. Now I'm looking at the source code here: src/login-common/sasl-server.c sasl_server_get_advertised_mechs() and I think it shouldn't be too hard for me to implement a little ad-hoc change to get this working. So I'd like to ask you if I'm on the righ way with that and if there is anyone out there who could help me with that, I would realy appreciate it. Thank you very much. David.

1 0

MAPI Properties?
by Mark Foley 27 Oct '15

27 Oct '15

I'm using Dovceot/IMAP on Linux and Outlook clients on WIN7 workstations. Mail on Linux is stored in Maildir format. I'm searching for where Outook keeps its information on color categories in IMAP. According to Diane Poremsky at slipstick.com, "Outlook stores it in the mapi properties of each message. If you use MFCMAPI to viuw the messages, you'll see the properties." MAPI is a Windows thing and the recommended MFCMAPI is for viewing these properties in Exchange. Not what I can use. Outlook must be storing these properties somewhere in the Dovecot/IMAP system as color categories can be set from Outlook. Can someone tell me where to look for these properties? THX - Mark

3 2

Can't access maildir with dovecot
by Julien Cubizolles 27 Oct '15

27 Oct '15

I'm a total newbie regarding imap servers. I'm trying to set up a Offlineimap/dovecot/Gnus system and Gnus complains that it cannot access the maildir... Here is my setup, put together by copying stuff from around the web without any prior knowledge of these tools... * Offlineimap is setup to use the $HOME/Maildir-free/, using --8<---------------cut here---------------start------------->8--- preauthtunnel = /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir-free --8<---------------cut here---------------end--------------->8--- in the local maildir part of ~/.offlineimaprc. * The Maildir-free maildir has been correctly (I think) populated with a single "General" folder. /home/wilk/Maildir-free: total used in directory 52 available 5502852 drwxrwxr-x 6 wilk wilk 4096 oct. 23 11:10 . drwx------ 240 wilk wilk 20480 oct. 23 15:06 .. drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 cur -rw-rw-r-- 1 wilk wilk 348 oct. 23 11:10 dovecot.index.log -rw-rw-r-- 1 wilk wilk 51 oct. 23 11:10 dovecot-uidlist -rw-rw-r-- 1 wilk wilk 8 oct. 23 11:09 dovecot-uidvalidity -r--r--r-- 1 wilk wilk 0 oct. 23 11:09 dovecot-uidvalidity.5629f967 drwx------ 6 wilk wilk 4096 oct. 23 11:16 General -rw-rw-r-- 1 wilk wilk 0 oct. 23 11:09 maildirfolder drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 new drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 tmp * dovecot is not setup to start as a server (no script in /etc/rc*.d/) and I didn't configure anything in any /etc/dovecot/ file (maybe I should have ?) * Gnus is supposed to access the maildir as an IMAP server through dovecot: I have: (nnimap "FreeOffline" (nnimap-stream shell) (nnimap-shell-program "/usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir-free") in gnus-secondary-select-methods * I try to access this maildir as follows /usr/lib/dovecot/imap -o mail_location=maildir:/home/wilk/Maildir-free/ * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE] Logged in as wilk * LIST "" * * LIST (\HasNoChildren) "." INBOX * OK List completed. As you can see, the "General" folder doesn't appear, and there is a mention of "INBOX" even though there is no folder under this name (but I guess that's a default for any IMAP system). Accordingly, Gnus only displays a INBOX folder when browsing the FreeOffline IMAP server, and complains that it contains no message. What's the correct way to setup dovecot? Thanks for your help. Julien.

2 4

2.2.18 initial setup permissions problem
by Forrest 27 Oct '15

27 Oct '15

I'm using Dovecot 2.2.18, compiled from source, on CentOS 6. I'm running into a permissions problem with my first rollout of Dovecot which has to do with directory permissions: Oct 23 14:34:51 mail dovecot: imap(username): Error: stat(/home/username/Maildir/tmp) failed: Permission denied (euid=596(<unknown>) egid=97(dovecot) missing +x perm: /home/username/Maildir, dir owned by 500:500 mode=0700) This being setup with the Dovecot wiki instructions. I may have misunderstood an initial setting. If I change permissions to my personal Maildir directory struct to be dovecot:dovecot it works fine, but this seems unusual. Dovecot is running as root: root 19176 0.0 0.1 2876 1096 ? Ss 14:28 0:00 /usr/local/sbin/dovecot dovecot 19178 0.0 0.0 2780 996 ? S 14:28 0:00 dovecot/anvil root 19179 0.0 0.1 2912 1144 ? S 14:28 0:00 dovecot/log root 19225 0.0 0.1 3544 1776 ? S 14:38 0:00 dovecot/config dovecot 19226 0.0 0.1 3332 1408 ? S 14:38 0:00 dovecot/auth root 19227 0.0 0.0 2776 916 ? S 14:38 0:00 dovecot/ssl-params I can't seem to figure this one out. Can someone point me in the right direction. Thanks.

2 3

Haproxy and Dovecot auth
by Giuseppe Civitella 26 Oct '15

26 Oct '15

Hi all, I'd like to use Haproxy to balance an auth service on a couple of Dovecot directors to have a redundant sasl service for my Postfix instances. While I configure the Postfixes to use, as smtpd_sasl_path, a direct connection to one of the directors I notice no errors. When I redirect the smtpd_sasl_path through an Haproxy balanced connection, I receive an error the first time I try to sen an email. The error is: SASL PLAIN authentication failed: Connection lost to authentication server If then I send more emails I receive no errors. If I do not send emails for a few minutes, the error appears again. The relevant Haproxy configuration is the following: listen auth *:12345 mode tcp balance source log global option tcplog option log-health-checks stick-table type ip size 200k expire 30m stick on src default-server inter 1000 fall 3 rise 1 server dovecot-director01 dovecot-director01:12345 check Do anyone have an idea about what it's missing? Thanks a lot Giuseppe -- Giuseppe Civitella gcivitella(a)entermail.it

2 1

Memory leak or misconfiguration: Repeated allocation of very large block
by Sebastian Wolfgarten 25 Oct '15

25 Oct '15

Dear all, I am using Dovecot 2.2.19 and I keep on getting the following warnings in my mail.log file on FreeBSD 10: Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated allocation of very large block (appr. size 20480): Oct 24 10:45:28 server1 dovecot: imap: Error: May lead to memory leak and poor performance. I am wondering whether this is a configuration issue (i.e. a mistake in my current config) or whether I am hitting a bug. What’s the best way of figuring this one out? I tried increasing the verbosity of the logs but it did not really provide me with further information. Any ideas? Here is my config: -- [root@server1 ~]# dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.1-RELEASE amd64 zfs auth_cache_size = 50 M auth_mechanisms = plain login default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_uid = 1008 last_valid_uid = 1008 login_greeting = Ready. mail_gid = 1008 mail_location = maildir:/var/mail/vdomains/%d/%n mail_max_keyword_length = 128 mail_max_userip_connections = 20 mail_uid = 1008 maildir_stat_dirs = yes 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 index ihave duplicate passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = sebastian(a)wolfgarten.com protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = vmail mode = 0666 user = vmail } user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 3 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 1024 vsz_limit = 512 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 } ssl_ca = </etc/postfix/ca.pem ssl_cert = </etc/postfix/server1.wolfgarten.com.crt.chain ssl_cipher_list = ALL:!LOW:!ADH:!SSLv2:SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:+HIGH:+MEDIUM ssl_key = </etc/postfix/server1.wolfgarten.com.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } protocol lda { mail_plugins = " sieve" } -- Many thanks. Best regards Sebastian

2 2

Notify plugin doesn't send mailbox_create notifications
by Lukas Mika 24 Oct '15

24 Oct '15

Hi there, I'm running dovecot 2.2.13 on my debian jessie server. When installing my own dovecot plugin, I noticed that there are no notifications coming from the notify plugin. I checked back with the mail_log plugin, but also this plugin doesn't log any notifications when a new mailbox is created; the mail is saved to the new inbox never the less. I ran dovecot 2.2.9 before on my Ubuntu Trusty (14.04) server, where with the same settings the plugins worked. Can you reproduce this issue and does anybody know a fix to this? Here are the relevant bits of my config: 20-lmtp.conf: protocol lmtp { mail_plugins). mail_plugins = $mail_plugins sieve mail_log notify } 10-logging.conf ... plugin { mail_log_events = mailbox_create mail_log_fields = uid box } ... Cheers

2 1

Question about dovecot replication
by Urban Loesch 24 Oct '15

24 Oct '15

Hi, last week I installed 2 servers with two dovecot nodes and replication in active/active mode located in different datacenters. Based on the howto from wiki "http://wiki2.dovecot.org/Replication" it works great. According to the wiki it is recomended to run "doveadm purge" on both systems continously, because "doveadm purge" will not be replicated by the replication service. No problem so far. But I have one doubt: is it also reccmended (for keeping maildata in sync) to run "doveadm replicator replicate '*'" continously on both nodes? Or is it enough on only one node? Or should I run "doveadm sync -A tcp:anotherhost.example.com" in regular intervalls? Perhaps once a day on both nodes? Thanks Urban Loesch

2 1

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://lawofattractionbible.com/considered.php?a> dovecot

1 0

important message
by fila＠pruda.com 24 Oct '15

24 Oct '15

Hello! New message, please read <http://t4tdeutsch.org/friend.php?r5> fila(a)pruda.com

1 0

important message
by Vojtech Kodera 24 Oct '15

24 Oct '15

Hello! New message, please read <http://vapeologypa.com/spirit.php?jj64p> Vojtech Kodera

1 0

important message
by Vojtech Kodera 24 Oct '15

24 Oct '15

Hello! New message, please read <http://iamakeupartistry.com/making.php?o> Vojtech Kodera

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://askdrrutherford.com/eat.php?w9f> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://netregistra.com/sat.php?yyl> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://humtvchannel.com/after.php?2e64> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://anisenterprise.com/leave.php?r34> dovecot

1 0