- dovecot - dovecot.org

Dovecot top stats
by Kilburn Abrahams 15 Oct '15

15 Oct '15

Hi, I have being try to track down top email users to sometime. When I do a network traffic check I can see there is about 15 times more email traffic pulled from mail server than sent. The problem I am trying to track down is which users are the culprit. I have enabled doevcot stats and I can do a doveadm stats dump user but I get a 0 for disk_input, disk_output, read_bytes and write_bytes. I do get mail_read_bytes numbers but I am not sure these numbers are correct. I there a top utility that works well so I can see email traffic from users mailboxes. The doveadm top does not work well. I also tried the perl scripts and that does not do a much better job. Thanks Kilburn

2 2

Re: iterate users with passwd-file passdb?
by Joseph Tam 15 Oct '15

15 Oct '15

Eric Abrahamsen writes: > Simply: Is it possible to iterate over users if I'm using the > passwd-file passdb driver? Do I need a SQL-based driver if I want to > iterate? What do you mean by "iterate"? If you mean whether you can look up a password entry in a multi-entry file, then yes, definitely. If you mean to sequentially go through it and do a first/last/best match, probably not. Joseph Tam <jtam.home(a)gmail.com>

4 4

Emails with sender MISSING_MAILBOX@missing_domain
by grupo correo 15 Oct '15

15 Oct '15

Hello, we are working in the migration from courier-imap to dovecot 2.2.10-4.el7_0.1.x86_64. Some emails that send a internal application show as sender "MISSING_MAILBOX@missing_domain", i use like email client Horde using dovecot like server. But if i open that email with Horde and courier-imap i can see the correct email sender. I think that the email of the sender is no correct or not accomplish some RFC. Can anyone help me to understand this? Thank you

3 2

Re: Problems sync with mail client MAC and dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64
by grupo correo 14 Oct '15

14 Oct '15

> > On 2015-10-13 09:20, grupo correo wrote: > > Hello, > > > > i have installed Centos 7.1.1503 with Dovecot 2.2.10-4.el7_0.1. With > > Thunderbird all works fine, but when i configure the email client of > > Mac > > (Yosemite) with IMAP i can see a error in the log and the client not > > see > > the emails: > > > > Oct 9 14:31:34 localhost dovecot: imap(xxxxxxx@xxxxxxx): Fatal: > > master: > > service(imap): child 18639 killed with signal 11 (core dumps disabled) > > Do you have more logs? > > Have you enabled mail_debug = yes to get more verbose logs? > > > > > I have read the instructions of http://www.dovecot.org/bugreport.html, > > but > > core file is not writing. > > > > Does anyone have this issues? I think that can be a problem in the > > configuration > > Please share your doveconf -n output. > > > Best regards > > regards > christian > Attached the doveconf -n Yes i have mail_debug = yes into file conf.d/10-logging.conf I paste the rest of log: Oct 13 21:27:17 localhost dovecot: imap: Debug: Loading modules from directory: /usr/lib64/dovecot Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib02_imap_acl_plugin.so Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Effective uid=56396, gid=55000, home=/VMAIL/xxxxxxxxxxxxxx Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Quota root: name=User quota backend=maildir args= Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Quota grace: root=User quota bytes=0 (10%) Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=children, subscriptions=yes location=maildir:~/Maildir Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: maildir++: root=/VMAIL/xxxxxxxxxxxxxx/Maildir, index=, indexpvt=, control=, inbox=/VMAIL/xxxxxxxxxxxxxx/Maildir, alt= Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: initializing backend with data: vfile Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: acl username = xxxxxxxxxxxxxx Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: owner = 1 Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl vfile: Global ACL directory: (none) Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Fatal: master: service(imap): child 2464 killed with signal 11 (core dumps disabled)

2 1

Thanks for Dovecot
by Steve Litt 14 Oct '15

14 Oct '15

Hi all, Thanks for making Dovecot. I just transitioned from Debian Wheezy to Void Linux. It was fairly easy to get Dovecot working on my Void box, and having Dovecot makes all of my email activities easier by doing one thing and doing it right. Thank you for such great software. SteveT

6 5

Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed
by Akash 14 Oct '15

14 Oct '15

Hi, Mailing list archives suggest that this problem has been fixed in the older versions itself but I am getting the error still while trying to doveadm index a large folder of emails. Sometimes it throws error after 30000, something 40000, the latest it gave up after 111000. But it just never completes. 111000/322080doveadm: /home/stephan/packages/wheezy/i386/clucene-core-2.3.3.4/src/core/CLucene/index/DocumentsWriter.cpp:210: std::string lucene::index::DocumentsWriter::closeDocStore(): Assertion `numDocsInStore*8 == directory->fileLength( (docStoreSegment + "." + IndexFileNames::FIELDS_INDEX_EXTENSION).c_str() )' failed. Aborted I am using dovecot 2:2.2.19-1~auto+7& libclucene-core1:i386 2.3.3.4-4 from debian wheezy backports. Please advice. -Akash

3 2

Re: iterate users with passwd-file passdb?
by Joseph Tam 14 Oct '15

14 Oct '15

Eric Abrahamsen <eric(a)ericabrahamsen.net> writes: >>> Simply: Is it possible to iterate over users if I'm using the >>> passwd-file passdb driver? Do I need a SQL-based driver if I want to >>> iterate? >> >> What do you mean by "iterate"? If you mean whether you can look up a >> password entry in a multi-entry file, then yes, definitely. If you >> mean to sequentially go through it and do a first/last/best match, >> probably not. > > Basically I just mean the -A argument to the doveadm commands. For > example, iterate through all the users and run sa-learn on each user's > learn/spam folder. If it's got to be SQL, it won't kill me... Ah. Yes, you can use -A and iterate through users, subject to any constraints such as first_valid_uid, last_valid_uid, etc. Joseph Tam <jtam.home(a)gmail.com>

1 0

Dovecot - Postfix with HAproxy
by Michael JOIGNY 13 Oct '15

13 Oct '15

Hi Everyone, I wouldlike to set up a postfix-dovecot with HA using HAproxy but im facing issues. I've followed this documentation : http://wiki2.dovecot.org/HAProxy (pour dovecot) http://blog.haproxy.com/2012/06/30/efficient-smtp-relay-infrastructure-with… (pour postfix) Package's version : dovecot : 2:2.2.19 (>= 2.2.19 pour proxy protocol) haproxy : 1.5.14 postfix : 2.11.2-1 (>2.10 pour postscreen) A part of my configuration : ##HAPROXY #postfix listen smtp bind mail.xx.xx:465 balance roundrobin timeout client 1m timeout connect 5s no option http-server-close mode tcp option smtpchk option tcplog server tst tst.xxx:10465 send-proxy server tst2 tst2.xxx:10465 send-proxy server tst3 tst3.xxx:10465 send-proxy #dovecot listen imap bind mail.xxx.xx:993 timeout client 1m no option http-server-close balance leastconn stick store-request src stick-table type ip size 200k expire 30m mode tcp option tcplog server tst tst.xxx:10993 send-proxy-v2 server tst2tst2.xxx:10993 send-proxy-v2 server tst3 tst3.xxx:10993 send-proxy-v2 ##POSTFIX postix main.cf #Haproxy proxy protocol postscreen_upstream_proxy_protocol = haproxy postfix master.cf #haproxy 10465 inet n – n – 1 postscreen smtpd pass – – n – – smtpd S ##DOVECOT # 2.2.19 (719e7f8fd70b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 # OS: Linux 2.6.32-41-pve x86_64 Debian 7.9 simfs auth_debug = yes auth_verbose = yes disable_plaintext_auth = no *haproxy_timeout = 5 secs** **haproxy_trusted_networks = x.x.x.x* log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/mailbox/%d/%n mail_max_userip_connections = 0 mail_privileged_group = mail 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 = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /mailbox/globalsieverc } protocols = sieve pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0660 user = mailboxes } unix_listener auth-userdb { group = mail mode = 0666 user = dovecot } user = root } service imap-login { inet_listener imap { port = 0 } inet_listener imap_haproxy { haproxy = yes port = 10993 } inet_listener imaps { address = * port = 993 } process_limit = 450 } service pop3-login { inet_listener pop3 { address = * port = 110 } process_limit = 180 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/star.key userdb { args = uid=5000 gid=5000 home=/mailbox/%d/%n/ allow_all_users=yes driver = static } protocol imap { imap_client_workarounds = } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol sieve { mail_location = maildir:/mailbox } protocol lda { auth_socket_path = /var/run/dovecot/auth-master hostname = xxx.yyy.com log_path = /var/log/dovecot/deliver.log mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins = sieve postmaster_address = postmaster(a)xxx.yyy rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s sendmail_path = /usr/sbin/sendmail } With my mail client : With an IMAP connection, logs below, i don't understand why my login is empty ... dovecot: imap-login: Disconnected: Too many invalid commands (no auth attempts in 0 secs): *user=<>*, rip=mon_ip_publique, lip=ip_publique_haproxy, session= xxx With a SMTP connection, logs below, i have a timeout. postfix/postscreen[16654]: CONNECT from [my public ip]:49942 to [my haproxy public ip]:465 postfix/postscreen[16654]: PREGREET 166 after 0 from [mon ip publique]:49942: \22\3\1\161\1\157\3\3+0E\b\213\131\177\173>\r/\213\177i\223k”FjA#\144\145\153\vP\\\155HL\190 If someone could help me, thanks. Kind regards. --

2 1

Dualstack IPv4/IPv6 setup with directors
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) But connecting the the neighbor director gives: Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid input: ME 149.x.y.96 9090 Oct 13 21:23:29 director1 dovecot: director: Error: director(149.x.y.97:9090/out): connect() failed: Connection refused Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): ip->family != my_ip->family Oct 13 21:23:29 director1 dovecot: director: Error: Remote director thinks it's someone else (connected to 2001:x:y:f33::5:1:9090, remote says it's 149.x.y.96:9090) I assume it's because the director uses only one (IPv4 OR IPv6) address for it's own identity, right? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Storage Design (Regligious War, Whatever)
by Kelsey Cummings 13 Oct '15

13 Oct '15

We've been running dovecot director setup using MAILDIR++ spools on NFS served by 4 (aging) Netapp clustered filers and are considering modernizing our storage. There's nothing particularly wrong with the existing storage except the age, density and power consumption don't compare well when against new systems. Refreshing the Netapps is an option but they come at a substantial cost. The last time we were looking one of the recommended hot DIY setups was Linux NFS backed by XFS on N mirrors but this predated the availability of stable ZFS in FreeBSD or Linux as well as products like FreeNAS. A FreeBSD NFS/ZFS filer on commodity hardware with zil/l2arc on a PCIe SSD seems like an attractive, affordable and easily scaled out solution which also would allow us to leverage compression at the filesystem layer. Does anyone have any experience running ZFS spool storage? If so, how do you handle DR/HA for spool storage? Thoughts on how this might compare to using DRBD? Any pitfalls to watch out for or general pointers? Suggestions on pool configuration? -K

1 0