- dovecot - dovecot.org

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 25 Oct '15

25 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 25 Oct '15

25 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