- dovecot - dovecot.org

Dovecot Proxy LTMP client connect to TCP port 0
by Wido den Hollander 09 Apr '16

09 Apr '16

Hi, I am trying to set up a Dovecot proxy which proxies through POP3, IMAP and LTMP towards a different Dovecot machine. On the proxy machine I use a MySQL database as a userdb and passwdb backend and it returns the proper information as described here: http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy IMAP and POP3 works just fine, but with LMTP I run into a problem. On the 'proxy' machine Postfix is also running and it deliver locally to LTMP via Socket: virtual_transport = lmtp:unix:private/dovecot-lmtp Dovecot there is also configured to proxy LTMP: lmtp_proxy = yes service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } So far so good. A telnet to localhost 110 or 143 allows me to log in to the POP3/IMAP. When Postfix delivers the message locally to Dovecot through LTMP it tries to proxy it though. When doing so it tries to connect to TCP port 0 (zero). dovecot: lmtp(22580): Error: lmtp client: connect(mbox01.XXXX.nl, 0) failed: Connection refused I know I can return the 'port' field in the userdb query, but the same query is used for POP3, IMAP and LMTP. So that can't be hardcoded. I fixed it for now with a CASE statement in SQL: password_query = SELECT b.hostname AS host, NULL AS password, \ 'Y' AS nopassword, u.email AS destuser, 'Y' AS proxy, \ CASE '%s' WHEN 'lmtp' THEN 2525 WHEN 'pop3' THEN 110 WHEN 'imap' THEN 143 END AS port \ FROM User u, Backend b, Domain d \ WHERE u.domainID = d.domainID \ AND b.backendID = d.backendID \ AND u.email = '%u' %s is a variable containing the service Dovecot is trying to look up. This is however rather hacky. On my destination machine LMTP is listening on port 2525. Is there any way to tell the Dovecot LTMP client to connect to port 2525 by default? Thanks, Wido

1 1

fts_solr: Lookup failed: 400 Bad Request / GET null null
by Chris Laif 08 Apr '16

08 Apr '16

Hi, the log file shows suspicious entries as follows: Apr 3 09:14:49 xxx dovecot: imap(user@domain): Error: fts_solr: Lookup failed: 400 Bad Request The tomcat7 log shows for this request: 10.0.0.234 - - [03/Apr/2016:09:14:49 +0200] "GET null null" 400 - Dovecot is latest 2.2.23 with a pretty standard FTS config copied from the wiki: mail_plugins = " acl fts fts_solr" fts = solr fts_solr = break-imap-search url=http://10.0.0.123:8080/solr/ Unfortunately I do not know (yet) which client action produces these log lines. "GET null null" seems not to be a sensible request in any case. Anyone seeing the same effect? Chris

3 5

Intermittent IMAP Login failures - about 25% fail
by Mobile Phone 08 Apr '16

08 Apr '16

New server & just added three domains: now I see "dovecot: imap-login: Aborted login (auth failed, 1 attempts in 5 secs): user=<username.companyname>, method=PLAIN, rip=1.1.1.1, lip=99.99.99.99, TLS, session=<kw6Y2NYviQBex5Un>" Plus all Outlook users keep being bounced and finally get in. I am going to kill all the users soon... Not too many files open, nor bandwidth, nor load. Any light/help appreciated. root@brazil:/var/log# dovecot --version 2.2.9 root@brazil:/var/log# dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.19.0-58-generic x86_64 Ubuntu 14.04.4 LTS auth_debug_passwords = yes auth_mechanisms = plain login mail_location = maildir:~/Maildir 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 = } passdb { driver = pam } protocols = imap pop3 pop3 ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } Thanks

4 7

Permissions for new folders
by David Cigánek 08 Apr '16

08 Apr '16

Hi, I have a problem with permissions for newly created folders in Dovecot. Everything worked fine until few days ago, when i did a little change in userdb lookup - but i don't know why it is causing problems. Server uses following directory structure: index - /data/mail/index mail - /data/mail/mail alt - /data/mail/archive all 3 on separate volumes, for performance reasons. Up until few days, i used following: # doveadm user dave(a)example.com field value user dave(a)example.com uid 13726 gid 1004 home /data/mail/mail/003/3726/da/dave mail mdbox:~/mbox/:DIRNAME=.00f-dbox-Mails:INDEX=/data/mail/stub/index/data/mail/mail/003/3726/da/dave:ALT=/data/mail/stub/archive/data/mail/mail/003/3726/da/dave config is quite simple: mail_location = mdbox:~/mbox/:DIRNAME=.00f-dbox-Mails:INDEX=/data/mail/stub/index%h:ALT=/data/mail/stub/archive%h passdb { driver = sql args = /data/mail/sql/dovecot-sql.conf.ext } userdb { driver = static args = gid=vmail } from SQL i get those fileds username domain password userdb_home userdb_uid userdb_quota_rule userdb_quota_over_flag For nicer paths, i created a symlinks /data/mail/stub/index/data/mail -> /data/mail/index /data/mail/stub/archive/data/mail -> /data/mail/archive so path /data/mail/stub/index/data/mail/mail/003/3726/da/dave is in fact in /data/mail/index/003/3726/da/dave In that setup, everything worked fine, but i didn't like those simlinks, so i altered the SQL query to return all paths in userdb_mail filed: # doveadm user dave(a)example.com field value user dave(a)example.com uid 13726 gid 1004 home /data/mail/mail/003/3726/da/dave mail mdbox:~/mbox/:DIRNAME=.00f-dbox-Mails:INDEX=/data/mail/index/003/3726/da/dave:ALT=/data/mail/archive/003/3726/da/dave So everything is in fact the same but little nicer. But since then, newly created directories doesn't get the same permissions like parent folder as day should (2770), but instead they are created with 2700: # stat -c "%a (%A)" /data/mail/mail/ 2770 (drwxrws---) # stat -c "%a (%A)" /data/mail/mail/003 2700 (drwx--S---) I need to have there 2770 perms, especialy because when other user like this is created: user dave(a)example.com uid 13999 gid 1004 home /data/mail/mail/003/3999/da/dave Dovecot is unable to create directory /data/mail/mail/003/3999, because it doesn't have write permissions for group on /data/mail/mail/003. I can't find any reason for this behavior - is it something in Dovecot or am I doing something wrong? Thank you, David Dovecot version: 2.2.21 # doveconf -n # 2.2.21 (5345f22): /usr/local/dovecot/2.2.21/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.12 (c1c0a23) # OS: Linux 3.10.0-327.4.5.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_master_user_separator = xxxxxx dict { sieve_movespam = mysql:/data/mail/sql/dovecot-movespam-sql.conf.ext sieve_redirect = mysql:/data/mail/sql/dovecot-redirects-sql.conf.ext } mail_location = mdbox:~/mbox/:DIRNAME=.00f-dbox-Mails:INDEX=/data/mail/stub/index%h:ALT=/data/mail/stub/archive%h mail_plugins = " quota notify replication" 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 mime foreverypart extracttext mdbox_rotate_size = 15 M passdb { args = xxxxxx driver = passwd-file master = yes pass = yes skip = authenticated } passdb { args = /data/mail/sql/dovecot-sql.conf.ext driver = sql } passdb { args = /data/mail/sql/dovecot-catchall-sql.conf.ext driver = sql } plugin { mail_replica = tcp:xxx:xxx quota = dict:user-quota::file:~/user_quota.dat quota2 = dict:domain-quota:%d:file:~/../../domain_quota.dat quota2_over_flag_value = 1 quota2_over_script = quota-warning domain %d %n@%d %i missmatch2 quota2_rule = *:bytes=500M quota2_rule2 = Trash:bytes=+5%% quota2_warning = bytes=90%% quota-warning domain %d %n@%d %i warn 90 quota2_warning2 = bytes=100%% quota-warning domain %d %n@%d %i over 100 quota2_warning3 = -bytes=100%% quota-warning domain %d %n@%d %i under 100 quota_grace = 5%% quota_over_flag_value = 1 quota_over_script = quota-warning user %n %n@%d %i missmatch1 quota_rule = *:bytes=0 quota_rule2 = Trash:bytes=+5%% quota_warning = bytes=90%% quota-warning user %n %n@%d %i warn 90 quota_warning2 = bytes=100%% quota-warning user %n %n@%d %i over 100 quota_warning3 = -bytes=100%% quota-warning user %n %n@%d %i under 100 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = dict:proxy::sieve_movespam;name=sieve_movespam;bindir=~ sieve_before2 = dict:proxy::sieve_redirect;name=sieve_before;bindir=~ sieve_max_actions = 500 sieve_max_redirects = 500 sieve_redirect_envelope_from = recipient } pop3_no_flag_updates = yes protocols = imap pop3 lmtp sieve replication_dsync_parameters = -1 -d -N -l 30 -U replication_max_conns = 5 service aggregator { fifo_listener replication-notify-fifo { group = vmail mode = 0660 user = vmail } unix_listener replication-notify { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service doveadm { inet_listener { port = xxxx } } service imap-login { client_limit = 10000 inet_listener imap { port = 143 } process_min_avail = 50 service_count = 0 vsz_limit = 256 M } service imap { client_limit = 1 process_limit = 20000 vsz_limit = 1 G } service lmtp { inet_listener lmtp { port = 2525 } } service pop3-login { inet_listener pop3 { port = 110 } } service quota-warning { executable = script /data/mail/scripts/quota-actions.sh unix_listener quota-warning { mode = 0666 } user = root } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = no ssl_client_ca_file = /etc/pki/tls/cert.pem syslog_facility = local5 userdb { args = gid=vmail driver = static } userdb { args = /data/mail/sql/dovecot-sql.conf.ext driver = sql override_fields = gid=vmail } protocol imap { mail_max_userip_connections = 1000 mail_plugins = " quota notify replication imap_quota" } protocol lmtp { mail_plugins = " quota notify replication sieve" } protocol lda { mail_plugins = " quota notify replication sieve" }

1 0

Broken pipe with own dict server. Timing issue?
by martijn.list 08 Apr '16

08 Apr '16

Hi, I have created my own dict server (proxy:[<dict path>]:<destination dict>) to access a proprietary database. The dict server basically creates a listing socket on a separate thread and then waits for incoming requests with accept(handle, NULL, 0). When a request comes in (i.e., when accept returns the accepted socket fd), the request is handed over to a handler thread (from a thread pool). The handler thread then read from the input. The issue that I have is that if the read is done too fast after the accept, Dovecot reports a broken pipe: dovecot: auth-worker(19904): Error: write(/usr/share/test-server/tmp/test-dict) failed: Broken pipe This happens for almost all processes that try to access the dict server. However If I add some sort of delay between the accept call and read (for example a sleep), everything works. No broken pipe even after testing with a large number of parallel requests for a long time. Somehow it looks like if the first read is done too fast, it takes a long time to read the data. During this time it looks like all other Dovecot processes are no longer able to connect and report the broken pipe. With the artificial delay, everything works ok and I can see that multiple incoming request are handled by multiple threads so it looks like Dovecot uses multiple auth worker processes. If however one connection hangs on the read it looks like no Dovecot proccess is able to connect Any idea what might be causing the broken pipe in relation to timing of the read? Kind regards, Martijn

2 2

Own implementation of a dict server. Is dict lookup multi threaded or single threaded?
by martijn.list 08 Apr '16

08 Apr '16

Hi, I have created my own dict server (proxy:[<dict path>]:<destination dict>) to access a proprietary database. What happens if the dict server lookup is slow? for example because the lookup process takes some time? Does Dovecot access the dict proxy from multiple threads or is this a single threaded process? Kind regards, Martijn Brinkers

2 1

ETOOMANYREFS related errors
by Luis Ugalde 07 Apr '16

07 Apr '16

Hi, I'm starting to see, on a pretty standard Debian Jessie installation, some error messages that are apparently related to the ETOOMANYREFS errno. Firstly, the mail log shows this: dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice And then the login process fails: dovecot: pop3-login: Internal login failure (pid=34388 id=1) (internal failure, 1 successful auths): user=<username>, method=PLAIN, rip=rip, lip=lip, session=<session> Is this something that Dovecot should be able to handle, or is it strictly Debian/libc/MySillyMistake related? #uname -a Linux server 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux #dovecot --version 2.2.13 #dpkg -l | grep -E 'dovecot-core|libc6|linux-image' ii dovecot-core 1:2.2.13-12~deb8u1 amd64 ii libc6:amd64 2.19-18+deb8u3 amd64 ii libc6-i386 2.19-18+deb8u3 amd64 ii linux-image-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u3 amd64 Best Regards, Luis

2 3

lmtp_rcpt_check_quota = yes silently blocks mail if quota check fails
by Tom Sommer 07 Apr '16

07 Apr '16

I have a user which has a quota-check that fails with 'Internal error', if I enable lmtp_rcpt_check_quota, the mail is silently tempfailed. Actually it looks like lmtp_rcpt_check_quota=yes suppresses normal Info/Error logging, even on Director. The MTA just gets " 451 4.3.0 <xxxx(a)xxx.xxx> Temporary internal error (in reply to end of DATA command)" from the director, but nothing is logged with lmtp_rcpt_check_quota=yes, anywhere. -- Tom

1 0

doveadm sync -1 -R
by Lukas Kolbe 07 Apr '16

07 Apr '16

Hi, I’m migrating an old Zarafa-installation to a dovecot using mdbox and sis on Debian Jessie. To copy over the emails, I use doveadm backup on the new box - or more precisely: vmail# doveadm -v -o imapc_user=$user -o imapc_password=$pass -o imapc_host=$host -o imapc_features=rfc822.size -o imapc_port=993 -o mailbox_list_index=no -o imapc_ssl_verify=no backup -R -x "Public folders*" -x "Public folders/*" -u $user imapc: For each invoke of doveadm backup -R, the local (new) mailbox gets wiped and all mails are retransferred - so far, so good. I’d like to use "doveadm sync -1“ as per the manpage to keep the downtime short, however sync doesn’t like the -R option: sync: invalid option -- 'R' doveadm sync [-u <user>|-A] [-S <socket_path>] [-1fPU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x <exclude>] [-s <state>] -d|<dest> If I understand it correctly, without -R it would mean that doveadm sync would incorporate the changes from the local dovecot-mailbox into the remote imapc:-Mailbox, which is the opposite of what I want. Dovecot version is current head as of yesterday. Is what I’m trying to do even possible with doveadm sync? Kind regards, Lukas

2 2

[help]enotify "mail to" run fine edit via managesieve 0.4.4 complied failed
by wuwei 07 Apr '16

07 Apr '16

hi all edit via vi editor to change dovecot.sieve and enotify works fine.but when I telnet 4190 port via managesieve to edit it with the same code,the managesieve said "NO "Error in MANAGESIEVE command CHECKSCRIPT: "", find many topic in wiki and maillist but not solved. need you help!thanks!!dovecot version 2.2.15,pigonhole version 0.4.4 here are more infos below: *managesieve cmds:* "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate vacation-seconds" "NOTIFY" "mailto" "SASL" "PLAIN LOGIN" "VERSION" "1.0" OK "Dovecot ready." listscripts NO "Error in MANAGESIEVE command received by server." AUTHENTICATE "PLAIN" "AGFuZ196aGFAdG9tLmNvbQAxMTExMTE=" OK "Logged in." listscripts "blackwhitelist" "rulefilter" ACTIVE OK "Listscripts completed." getscript "rulefilter" {471} require ["reject","fileinto","imap4flags","vacation","regex","encoded-character","include","copy","enotify","variables"]; if header :matches "Subject" "*" { set "Subject" "${1}"; } if header :matches "From" "*" { set "From" "${1}"; } if header :matches "Message-ID" "*" { set "msg_id" "${1}"; } if header :matches "To" "*" { set "To" "${1}"; } if header :matches "Date" "*" { set "Date" "${1}"; } notify "mailto:wuweiwwd@tom.com"; OK "Getscript completed." checkscript {471} require ["reject","fileinto","imap4flags","vacation","regex","encoded-character","include","copy","enotify","variables"]; if header :matches "Subject" "*" { set "Subject" "${1}"; } if header :matches "From" "*" { set "From" "${1}"; } if header :matches "Message-ID" "*" { set "msg_id" "${1}"; } if header :matches "To" "*" { set "To" "${1}"; } if header :matches "Date" "*" { set "Date" "${1}"; } notify "mailto:wuweiwwd@tom.com"; *NO "Error in MANAGESIEVE command CHECKSCRIPT: "* BYE "Disconnected for inactivity" Connection closed by foreign host. *sieve code:* require ["reject","fileinto","imap4flags","vacation","regex","encoded-character","include","copy","enotify","variables"]; if header :matches "Subject" "*" { set "Subject" "${1}"; } if header :matches "From" "*" { set "From" "${1}"; } if header :matches "Message-ID" "*" { set "msg_id" "${1}"; } if header :matches "To" "*" { set "To" "${1}"; } if header :matches "Date" "*" { set "Date" "${1}"; } notify "mailto:wuweiwwd@tom.com"; *dovecot.conf ./dovecot -n* # 2.2.15: /home/mail/dovecot/etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=80960 } is lower than required under max. load (300000) doveconf: Warning: service anvil { client_limit=60000 } is lower than required under max. load (240003) # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_cache_negative_ttl = 1 days auth_cache_size = 1000 k auth_cache_ttl = 1 days auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login debug_log_path = /home/mail/dovecot/logs/dovecot.log default_client_limit = 60000 default_internal_user = vmail default_login_user = dovecotauth default_process_limit = 60000 disable_plaintext_auth = no first_valid_gid = 1007 first_valid_uid = 1007 imapc_features = rfc822.size fetch-headers imapc_host = 172.24.173.212 imapc_password = tom123VipIMAP587 imapc_user = %u info_log_path = /home/mail/dovecot/logs/dovecot.log log_path = /home/mail/dovecot/logs/dovecot.log mail_debug = yes mail_fsync = never mail_plugins = fts fts_lucene mail_log notify quota zlib mail_prefetch_count = 20 maildir_very_dirty_syncs = 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 ihave duplicate vacation-seconds namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Junk E-mail" { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { args = /home/mail/dovecot/etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { args = /home/mail/dovecot/bin/CheckPassword driver = checkpassword } plugin { fts = lucene fts_lucene = whitespace_chars=@. mail_debug = yes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append mail_log_fields = uid box msgid size quota = dict:%u::redis:host=127.0.0.1:prefix=user_quota/ quota_rule2 = Trash:storage=+80%% quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = storage=70%% quota-warning 70 %u quota_warning4 = storage=60%% quota-warning 60 %u sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +vacation-seconds sieve_max_redirects = 10 sieve_redirect_envelope_from = orig_recipient sieve_vacation_default_period = 0 sieve_vacation_max_period = 0 sieve_vacation_min_period = 0 welcome_letter_path = /home/mail/dovecot/etc/welcome welcome_letter_url = http://202.108.252.162:8080/domainmail zlib_save = gz zlib_save_level = 6 } pop3_fast_size_lookups = yes pop3_no_flag_updates = yes postmaster_address = postmastar@%d protocols = imap pop3 sieve lmtp service auth-worker { user = dovecotauth } service auth { client_limit = 80960 unix_listener /home/mail/postfix/var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } service_count = 0 vsz_limit = 256 M } service imap { executable = imap postlogin process_limit = 60240 } service lmtp { inet_listener { port = 11000 } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 vsz_limit = 256 M } service managesieve { process_limit = 80960 } service pop { executable = imap postlogin process_limit = 60240 } service pop3-login { inet_listener pop3 { port = 110 } service_count = 0 vsz_limit = 256 M } service postlogin { executable = script-login -d rawlog -b -t } service quota-warning { executable = script /home/mail/dovecot/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = no submission_host = 172.24.140.52:26 userdb { driver = prefetch } userdb { args = /home/mail/dovecot/etc/dovecot/dovecot-dict-auth.conf.ext driver = dict } protocol imap { imap_logout_format = bytes=%i/%o mail_plugins = fts fts_lucene mail_log notify quota zlib imap_quota imap_zlib } protocol pop3 { pop3_logout_format = bytes=%i/%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lmtp { mail_plugins = fts fts_lucene mail_log notify quota zlib quota sieve } protocol sieve { mail_max_userip_connections = 1000 mail_plugins = fts fts_lucene mail_log notify quota zlib quota managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 10 managesieve_max_line_length = 65536 } -- View this message in context: http://dovecot.2317879.n4.nabble.com/help-enotify-mail-to-run-fine-edit-via… Sent from the Dovecot mailing list archive at Nabble.com.

2 2

What is dovecot.socket and do i need it?
by Hamy 07 Apr '16

07 Apr '16

Helloafter rebooting the server, i keep getting these errors in mail.err : Apr 7 06:08:09 main dovecot: master: Error: systemd listens on port 143, but it's not configured in Dovecot. Closing. Apr 7 06:08:09 main dovecot: master: Error: systemd listens on port 993, but it's not configured in Dovecot. Closing. Apr 7 06:08:09 main dovecot: master: Error: systemd listens on port 993, but it's not configured in Dovecot. Closing. And then dovecot refuses any connection. the problem is solved if i do a manual restart of dovecot.service. After some search, i found 2 different solutions, one suggesting disabling dovecot.socket completely, the other one adjusting its settings: https://sowhatisthesolution.wordpress.com/2015/04/27/upgrading-dovecot-debi… I also found an old thread in the mailing list that might be relevant: http://dovecot.org/list/dovecot/2012-March/134376.html The errors indeed seem to go away if i disable dovecot.socket . I would be grateful is someone could help me understand the role of dovecot.socket , and why that error happens and what is the right way to solve it? PS: I am using Ubuntu server 15.10 and dovecot package v2.2.18 Best Regards,

1 0

RE: State for dsync not working
by Simon Pierre Desrosiers 07 Apr '16

07 Apr '16

No one will answer, so I will provide my own answer for posterity. The -s flag does not accept a file, but a string. So a correct for loop would be the following : for user in $userlist ; do state=$(cat "/Users/_dovecot/.bin/syncStates/syncstate$user" ) doveadm sync -u $user -s $state tcp:xxx.xxx.xxx.xxx > "/Users/_dovecot/.bin/syncStates/syncstate$user" done Hope it helps someone. > > ------------------------------ > > Message: 3 > Date: Fri, 25 Mar 2016 19:26:11 -0400 > From: Simon Pierre Desrosiers <simonpie(a)cs.mcgill.ca> > To: dovecot(a)dovecot.org > Subject: State for dsync not working. > Message-ID: <CAF2F45A-3F6A-4540-8C32-6551C6F27F7C(a)cs.mcgill.ca> > Content-Type: text/plain; charset=us-ascii > > Hello, > > Since replication does not seem to work on Mac OSX, I will run doveadm sync by hand every few minutes. > > In order to improve efficiency, I would like to use state. I have tried a few ways, but I always get the following error > doveadm(user): Error: Saved sync state is invalid, falling back to full sync: Invalid base64 data > KBtMOd0181bQ/wAAoQsxE90181YBAAAAAQAAAAAAAAAAAAAAAAAAABtI+mg= > > > Here is the code I use to sync : > for user in $userlist ; do > doveadm sync -u $user -s "/Users/_dovecot/.bin/syncStates/syncstate$user" tcp:xxx.xxx.xxx.xxx > "/Users/_dovecot/.bin/syncStates/syncstate$user" > done > > Any idea on how I can correct the encoding error ? > > Thank you > > ------------------------------ > > Message: 4 > Date: Sat, 26 Mar 2016 13:30:03 +1000 > From: Noel Butler <noel.butler(a)ausics.net> > To: dovecot(a)dovecot.org > Subject: Re: NetApp NFS vs. ZFS and NFS for Maildir > Message-ID: <79e7f44d74014b5c83d370d74e02205b(a)ausics.net> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > It seems its troll time again on this list, ohh maybe its Harry in > disguise... So I will play along, for today anyway :) > > > On 19/03/2016 18:11, Stephan von Krawczynski wrote: >> On Sat, 19 Mar 2016 17:37:04 +1000 >> Noel Butler <noel.butler(a)ausics.net> wrote: >> >>> On 14/03/2016 18:49, Stephan von Krawczynski wrote: >>>> >>>>> >>>>> and you've never seen these cause problems with FS? then you must be >>>>> a >>>>> newbie, in over 25 years I've seen it happen several times - yes even >>>>> after an apparent controlled shutdown. >>>> >>>> Maybe you're doing something wrong then. because in my last 21 years >>>> working >>>> exactly in this business I've not seen a single deadly fs-crash because >>>> of a >>>> power-outage. Not one. And we had of course several, all backed by UPS. >>> >>> Consider yourself lucky, Most network admins whove been around large >>> busy ISP DC's have seen this in their lifetime, to not have seen one >>> is >>> rare, go buy yourself a lotto ticket :) >>> >>>> >>>> If your servers get drowned with water during a fire your fs is >>>> probably the >>>> least of your worries. You don't really plan to re-enable servers with >>>> water- or fire-damage, do you? That's probably why there shouldn't be a >>>> fireman pouring water in the first place. >>> >>> This shows you dont understand structural engineering, the fire does >>> not >>> have to be on your floor, it can be far away as two or so levels >>> above, >>> with the high pressure water used - equating to a shitload of water, >>> there are ducts, shafts, other risers and so on that with a shit-tone >>> of >>> water can easily penetrate fireblocks of floors below - dont take my >>> work, go ask a fireman, or maybe watch the nightly news sometime >>> (building fire - many levels water affected blah blah blah)... so >>> keeping those boxes on via UPS's is asking for lots of charcoaled >>> boards >>> and fried drives. IOW, total stupidity. >>> >>> Should those machines be depowered as required by our building codes, >>> well, might take a few days of drying out but at least they will power >>> back up without error - yes, done it in risk assessments. >> > >> Obviously you must work for people that have not the slightest idea >> about >> using hardware in a correct way and don't know when the time has come >> to throw > >> it away. Man, there is no way to let a drowned box survive. It is not >> back to > > Wow, how long did you allege to have been in network/sys admin? 20 > years? Really? I think you made a typo and and it should have read 20 > minutes, ya know I have refrained from posting no here for a long time > (apart from fact I rarely read the list), and I was not going to feed > the trolls, but sometimes the smart mouthed know nothing, need to bitch > slap upside the head so thats why I am devoting about 60 seconds to you. > > Of course there is, networks dont throw away many hundreds of servers > valued $7K to $10K, nor $100K+ storage systems, or $40K routers, LB's or > switches, just because they got drenched - with power isolated. > > >> normal when it is dry. If you don't get that I am pretty happy to be no >> customer. This can only be an idea born in the sick mind of a >> controller who > > You will never be a customer _or_employee_ of mine, trust me on that > one! > >> didn't want to pay insurance in the first place. We are talking about >> serious > > Got nothing to with insurance, it might take 2 days to dry out and get > back up and running, it will take an awful lot longer to get offsite > backups and restore every last one of them. > > I hope your employer reads this list, because he/she should be seeing > alarm bells from your comments. > >> corrosion effects here let alone that you have a hard time even >> knowning when > > yep, you sure did fail basic engineering > >> your boxes are really dry. Your fireman on the other hand seem to be >> stuck in >> the 80ths. Today there are solar panels almost everywhere _which you >> cannot >> turn off_. > > Wow, you really are clutching the fantasy straws arnt you, perhaps your > country lacks modernisation, I can go to the side of my house and > isolate the panels with a flick of a switch, strangely enough and I > guess in your eyes horrifyingly called "solar isolator" that stops the > panels providing power to my electrical circuits, yes, there might be > power from panels to it, but thats not going to affect my power circuits > or equipment > > > > -- > If you have the urge to reply to all rather than reply to list, you best > first read http://members.ausics.net/qwerty/ > > > ------------------------------ > > Message: 5 > Date: Sat, 26 Mar 2016 13:34:34 +1000 > From: Noel Butler <noel.butler(a)ausics.net> > To: dovecot(a)dovecot.org > Subject: Re: Email hosting provider > Message-ID: <2b1abc9c94e3f1322753d7547cb991e4(a)ausics.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 21/03/2016 17:06, Andre Rodier wrote: >> Hello, >> >> Sorry if I am off topic a little. >> >> I am looking for an email host provider that supports dovecot, sieve >> and manage sieve. Ideally with the roundcube webmail and managesieve >> plugin >> >> Better if it is in Europe or switzerland. I don't mind paying a little. >> >> Thanks, >> Andr?. > > Hi Andre, > > see www.webhostingtalk.com > > There are a number of reliable and reasonable priced hosts in Germany > (best place if you value your privacy) and Netherlands. > > > -- > If you have the urge to reply to all rather than reply to list, you best > first read http://members.ausics.net/qwerty/ > > > ------------------------------ > > Message: 6 > Date: Sat, 26 Mar 2016 10:52:33 +0530 > From: Joy <pj.netfilter(a)gmail.com> > To: Joseph Tam <jtam.home(a)gmail.com> > Cc: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: IMAP Idle > Message-ID: > <CALM64LbXF_Nw+7STyxHMnjLNujEcTsc5mEXMA8DXaZuNX4pvpA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I am ok if connection is closed automatically after 30 min if client is not > responding but connection is not being closed even after 2 days. > > > On Sat, Mar 26, 2016 at 2:52 AM, Joseph Tam <jtam.home(a)gmail.com> wrote: > >> Joy <pj.netfilter(a)gmail.com> wrote: >> >> We have implement imap idle in web mail built by us to have >>> push mail feature. IMAP idle working perfectly with browser notification >>> and we are happy with it but having one issue with users who close the >>> browser directly and never logout in that case there are number of idle >>> connection which are not in use and users are unable to login once IP wise >>> connection limit is reached. >>> >>> Dovecot is not closing connection which are not in use, is there any >>> setting available which can help me to resolve this issue. >>> >> >> I had much the same situation where a user signed up with a roaming >> wireless carrier that assigned a new IP to the client whenever it got >> passed from one access point to another. Good fun when this person >> took a bus ride through the city, leaving orphaned connections in >> its wake. >> >> The IDLE disconnection timeout is hardwired in the Dovecot code >> >> http://wiki.dovecot.org/Timeouts >> >> It's set to the RFC minimum of 30min. You'll have to recompile Dovecot >> to lower this to a non-RFC compliant value. I'm not sure how this this >> will affect clients, but 30min seems to be overly generous. >> >> Joseph Tam <jtam.home(a)gmail.com> >> > > > ------------------------------ > > Message: 7 > Date: Sat, 26 Mar 2016 08:04:33 +0100 > From: Stephan von Krawczynski <skraw(a)ithnet.com> > To: dovecot(a)dovecot.org > Subject: Re: Email hosting provider > Message-ID: <20160326080433.07fcf216.skraw(a)ithnet.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Sat, 26 Mar 2016 13:34:34 +1000 > Noel Butler <noel.butler(a)ausics.net> wrote: > >> On 21/03/2016 17:06, Andre Rodier wrote: >>> Hello, >>> >>> Sorry if I am off topic a little. >>> >>> I am looking for an email host provider that supports dovecot, sieve >>> and manage sieve. Ideally with the roundcube webmail and managesieve >>> plugin >>> >>> Better if it is in Europe or switzerland. I don't mind paying a little. >>> >>> Thanks, >>> Andr?. >> >> Hi Andre, >> >> see www.webhostingtalk.com >> >> There are a number of reliable and reasonable priced hosts in Germany >> (best place if you value your privacy) and Netherlands. > > You mean "best place if you have no idea of the german laws and whats really > going on" ... > > -- > Regards, > Stephan > > > ------------------------------ > > Message: 8 > Date: Sat, 26 Mar 2016 10:48:47 +0000 > From: michael crane <mick.crane(a)gmail.com> > To: dovecot(a)dovecot.org > Subject: mailbox prefix > Message-ID: > <CACJbxCQ5by9eXKtAMfJ7aa1C2hCkmph=LbyUqn2yv6w=0hVseQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > dovecot version 2.2.13 > > hello, > I try to make a new server just for me after having old one working for > ages with Dovecot, Fetchmail, Squirrelmail, Procmail > making new one with above plus Postfix using Maildir structure. > I am having a bit of trouble understanding exactly what the namespace and > prefix are. > Is the "private/" prefix an internal thing with Dovecot ? Or is it supposed > to be a real directory ? > I'm not quite sure how to properly address the INBOX in Procmail, > Squirrelmail, Postfix config. > > > for example am I supposed to say inbox is ".private/.INBOX" > > > > cheers > > zemlik > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 155, Issue 45 > ****************************************

1 0

"Lost" e-mail after alternate partition offline
by Daniel van Ham Colchete 07 Apr '16

07 Apr '16

Hey guys! I've got a problem here and I wish you could help me. A drive failed here and went offline for some time. This was a alternate storage drive so it took a while (hours) for us to notice. There was a problem with DRBD also, so it didn't move to the redundancy, it just went offline. I was able to recover all the files there, but a few of my users still don't see their old e-mails, the ones that are supposed to be on the alternate storage. >From what I could troubleshoot here file are there, vmail user can access them, so it's not a permission issue, but a doveadm dump on the index file of each mail folder, won't show the e-mail at the alternate storage drive. So, they are there (at the filesystem), but they aren't (from a imap client). Is there a way to rebuild the dovecot.index file, re-adding everything back to each folder? Best, Daniel Colchete

2 1

namespace...mailbox doesn't exist
by Eric 06 Apr '16

06 Apr '16

Hello list, I have a namespace called 'projects' which when clicked in Thunderbird (nonexistent in eM Client) yields the following error: "The current operation on 'projects' did not succeed. The mail server for account user(a)domain.tld responded: mailbox doesn't exist: projects.projects (0.00 + 0.00 secs)." The namespace is configure as follows: # Shared namespace 'projects' namespace { location = maildir:/home/vpopmail/domains/domain.tld/shared/projects prefix = projects. separator = . type = public } This is the log: 1: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Effective uid=89, gid=89, home=/home/vpopmail/domains/domain.tld/postmaster 2: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Quota root: name=ignore=Trash backend=maildir args= 3: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Quota rule: root=ignore=Trash mailbox=? bytes=0 messages=0 4: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Quota grace: root=ignore=Trash bytes=0 (10%) 5: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Namespace : type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location= 6: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: mdbox: access(/home/vpopmail/domains/domain.tld/postmaster/mdbox, rwx): failed: No such file or directory 7: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: mdbox: couldn't find root dir 8: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: sdbox: access(/home/vpopmail/domains/domain.tld/postmaster/sdbox, rwx): failed: No such file or directory 9: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: sdbox: couldn't find root dir 10: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: maildir: root exists (/home/vpopmail/domains/domain.tld/postmaster/Maildir) 11: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: maildir++: root=/home/vpopmail/domains/domain.tld/postmaster/Maildir, index=, indexpvt=, control=, inbox=/home/vpopmail/domains/domain.tld/postmaster/Maildir, alt= 12: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: Namespace : type=public, prefix=projects., sep=., inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:/home/vpopmail/domains/domain.tld/shared/projects 13: Apr 04 20:00:30 imap(postmaster(a)domain.tld): Debug: maildir++: root=/home/vpopmail/domains/domain.tld/shared/projects, index=, indexpvt=, control=, inbox=, alt= This did not happen with other versions of dovecot (I think) but just started happening with the upgrade. While it is not a serious problem and I can live with it, what would be causing it in the new dovecot iteration (2.2.23) ? And, could it be that I'm missing the necessary setting to mitigate this? Please let me know if any additional information is necessary. I'm thinking that the problem lies in lines 6/7 and 8/9 where Dovecot is looking for mdbox/sdbox. Eric

3 5

Migrating from Olde server to Dovecot
by Hendrik Velloen 06 Apr '16

06 Apr '16

Hi I am new to the mailing List, and was hoping to get some assistance migrating from an Old Cucipop + Sendmail server (running on a old Redhat v 7) to a new Dovecot setup. My new installation is Dovecot + Postfix. All is setup and working, however I want to trasnsfer the contents of the mailboxes from my old server to this new Dovecot setup. Please let me know what information will be required to transfer the mailboxes - I have tried a number of things, but with no luck. I think the correct method is the one below, but I am getting UIDL errors and AUTH errors and not sure if this is the right approach ---- PLEASE HELP dsync -u <DOVECOT_USER> mirror mbox:~/mail:INBOX=<MAIL_BOX_COPIED_FROM_OLD_SERVER> ~# dsync -u hendrikv(a)tcmvpn.co.za mirror mbox:~/mail:INBOX=/var/mail/User_mbox/hendrikv dsync(hendrikv(a)tcmvpn.co.za): Error: pop3c(196.26.136.162): AUTH PLAIN failed: -ERR Invalid command, try one of: USER name, PASS string, APOP name digest, QUIT dsync(hendrikv(a)tcmvpn.co.za): Error: pop3c: Disconnected from remote server dsync(hendrikv(a)tcmvpn.co.za): Error: pop3_migration: Couldn't sync mailbox POP3-MIGRATION-NS/INBOX: Internal error occurred. Refer to server log for more information. [2016-04-04 08:27:01] dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=ddbe5c71e58919cfe2a40905bced091d (UID=3054) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=64087a4c7bf960114cf17ba044047900 (UID=374) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=fd28baf9e91aedaf06c6e979ca76e96f (UID=2982) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=607087e611559d2df02c0684de87e10d (UID=991) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=c6a9aebd1f535f0cd82ed612a42bae77 (UID=1541) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=4c56ffcfb600c8b216b2f1603383dc13 (UID=1007) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=96ce5556fab323206f51deb03625be8a (UID=2357) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=cda74cb161321b7c99973cc65e80a591 (UID=1401) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=b735acf7ef69b39be157a97223878cdc (UID=642) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=6d9baedf21198be32152461f96737a1a (UID=481) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=19f36b934b74ce11f1eda95e32a0b112 (UID=1998) dsync(hendrikv(a)tcmvpn.co.za): Error: Exporting mailbox INBOX failed: Can't lookup pop3-uidl for UID=1: POP3 UIDLs couldn't be synce -- Kind Regards Hendrik

4 3

Internal quota calculation error (redis), double mail delivery
by Tom Sommer 06 Apr '16

06 Apr '16

Sometimes my redis connection times out, both for pop3, imap and lmtp. I have no idea why, when I do a "doveadm quota recalc -u" it works just fine? I'm thinking the connection is lost somehow and not retried? Apr 06 15:42:00 lmtp(xxx(a)xxx.com): Error: redis: Lookup timed out in 30.000 secs Apr 06 15:42:00 lmtp(xxx(a)xxx.com): Error: Internal quota calculation error Apr 06 15:42:00 lmtp(xxx(a)xxx.com): Error: Internal quota calculation error Apr 06 15:42:00 lmtp(xxx(a)xxx.com): Info: xxxx: msgid=<xxxx(a)xxxx.com>: saved mail to INBOX Apr 06 15:49:23 lmtp(xxx(a)xxx.com): Info: xxxx: msgid=<xxxx(a)xxxx.com>: saved mail to INBOX <-- Same mail This happens a lot, and it's really bad, because the mail is actually saved correctly, but the error is reported back to the Director, causing the delivery to be retried by the MTA - so the mail actually lands *twice* in the user's inbox. Thanks -- Tom

2 4

LMTP with alias addresses
by davide marchi 06 Apr '16

06 Apr '16

Hi, my problem is this: if i use lmtp for delivery and lookup for real_virtual_user(a)mydomain.com all function perfectly and mails are delivered correctly (quota and presence of user also) but if i send an email to real_alias_address(a)mydomain.com LMTP service (it's an alias containing several users) dosen't find user. How can i resolve this problem? for completeness my system users is based on vpopmail userdb

2 1

Session ID separator change
by Timo Sirainen 06 Apr '16

06 Apr '16

LMTP is a but troublesome in that a single LMTP session can do multiple RCPT TOs, so the same session will end up delivering mails to multiple different users. This is causing trouble with stats process, because each delivery is using the same session ID for multiple different users, which causes errors about session ID duplication in stats process. So we'll need to make the session IDs unique, while still keeping it clear enough that they're part of the same original LMTP session (which is also visible in th Received: headers). I'm now thinking that the first recipient's delivery will have the original normal session ID (e.g. "ME3ZHCi+A1dUDQAAvAUe3g"), while the following recipients will have :2, :3, etc suffix (e.g. "ME3ZHCi+A1dUDQAAvAUe3g:2"). If somebody cares about parsing the original session ID from logs, they can just cut off the session ID from the first ':' character (because indexer-worker also adds its own :suffix). So now I'm mainly wondering if ':' is a good character? Has somebody already changed mail_log_prefix in a way that these additional ':' chars might break their log parsers (e.g. mail_log_prefix=%u:%s%{session}:%r).

3 3

Unable to login with iPhone?
by Jason Pruim 06 Apr '16

06 Apr '16

Hey Everyone, So I have my dovecot install up and running! I can receive mail from the outside, still dealing with a small issue with sending email, but I think that's an issue off needing to setup a relay... Right now though... My biggest issue is it won't connect to my iPhone... I can login with mail on my computer, and through round cube for webmail... But it gets stuck on "verifying"... I tried addingcram-md5 and digest-md5 to the auth_mechanisms but that didn't work... Any idea what I'm missing? Here is my doveconf -n: [ec2-user@ip-172-31-28-46 postfix]$ doveconf -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 4.4.5-15.26.amzn1.x86_64 x86_64 ext4 auth_mechanisms = plain login cram-md5 digest-md5 mail_location = maildir:/var/vmail/%d/%n/Maildir 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 mbox_write_locks = fcntl namespace inbox { inbox = yes location = prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl = required ssl_cert = </etc/ssl/certs/mailserver.pem ssl_key = </etc/ssl/private/mailserver.pem ssl_protocols = !SSLv2 !SSLv3 userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } protocol lda { mail_plugins = " sieve" } [ec2-user@ip-172-31-28-46 postfix]$ If I try to telnet to port 993 from my local computer it connects, but won't let me login... Same on port 143... Any ideas? Thanks everyone for your help! I can't wait until I can actually help with the questions instead of just asking them!

3 2

dovecot squatter
by Gabriele Bulfon 05 Apr '16

05 Apr '16

Hi, on cyrus installations we have the squatter utility that can index full message bodies and headers incrementally, allowing to run the squatter from time to time to arrange for index changes. Is there anything similar in Dovecot? This is expecially useful for full searches in body message. Thanks for any help Gabriele ---------------------------------------------------------------------------------------- Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon

2 1

How to delete Dovecot users when using Single Instance Storage
by Jesus Cea 05 Apr '16

05 Apr '16

In case somebody find this useful: https://blog.jcea.es/posts/20160211-delete_users_dovecot.html -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

2 1

New feature: HTTP API
by aki.tuomi＠dovecot.fi 05 Apr '16

05 Apr '16

Hi all! We are bringing out HTTP API for doveadm-server in master HEAD. This feature is experimental, and can be expected to have bugs in it and might not always work. If you feel like trying it out though, you can enable it in your configuration file: doveadm_api_key = some-string service doveadm { inet_listener http { port = 8080 } } To use the API, you can go to http://host:8080/doveadm. GET request will print out possible commands, along with their parameters. If you have set API KEY, you need to include it in the request as X-API-Key header. This API has been designed to resemble JMAP API since we are planning to implement it in future version. The rule of thumb is that all the commands work as they would on cli, so the parameters are more or less the same. There are few exceptions, like 'field' parameter in some mail/mailbox commands. Commands are executed by POSTin JSON to /doveadm. The JSON format is [ ["command",{"parameter":"value"},"opaque identifier"], ["command",{"parameter":"value"},"opaque identifier"], ["command",{"parameter":"value"},"opaque identifier"], ... ] Be warned though that even if it supports multiple commands, some commands still use i_fatal to terminate the server if they are unhappy. This will mean you will lose the whole result set, and get no output, so at this point it is safest option to run only one command at a time. If you run into problems or discover issues, please report them in the usual manner to us. Kind regards, Aki Tuomi Dovecot Oy

2 3

Environment Variable Expansion
by Tim Evers 04 Apr '16

04 Apr '16

System: Debian Jessie I'm trying to put an environment variable in the sql config like: password_query = SELECT userid AS user, crypt AS password, maildir as userdb_home, 500 as userdb_uid, 500 as userdb_gid FROM local_account WHERE userid = '%u' and mbox_host = '%{env:CLUSTERNAME}' \ and ( ( imap_aktiv='1' and '%s'='imap' ) or ( pop_aktiv='1' and '%s'='pop3' ) or ( sieve_aktiv='1' and '%s'='sieve' ) ) \ and aktiv_abruf='1' My variable is %{env:CLUSTERNAME} CLUSTERNAME is set through /etc/default/dovecot. I tried setting the import_environment config variable to TZ CLUSTERNAME but that changed nothing. When I execute this through a login attempt, I see the following in the tcpflow output: SELECT userid AS user, crypt AS password, maildir as userdb_home, 508 as userdb_uid, 503 as userdb_gid FROM local_account WHERE userid = 'te' and mbox_host = 'env:CLUSTERNAME}' and ( ( imap_aktiv='1' and 'pop3'='imap' ) or ( pop_aktiv='1' and 'pop3'='pop3' ) or ( sieve_aktiv='1' and 'pop3'='sieve' ) ) and aktiv_abruf='1' So %{env:CLUSTERNAME} was parsed to env:CLUSTERNAME} which is not what the doc (http://wiki.dovecot.org/Variables) says, and it also seems like the parser somehow sees this as a short variable (removing %+{). Any hints what might be happening here / how I can make it work. Regards, Tim

1 0

(no subject)
by Hendrik Velloen 04 Apr '16

04 Apr '16

Hi I am new to the mailing List, and was hoping to get some assistance migrating from an Old Cucipop + Sendmail server (running on a old Redhat v 7) to a new Dovecot setup. My new installation is Dovecot + Postfix. All is setup and working, however I want to trasnsfer the contents of the mailboxes from my old server to this new Dovecot setup. Please let me know what information will be required to transfer the mailboxes - I have tried a number of things, but with no luck. I think the correct method is the one below, but I am getting UIDL errors and AUTH errors and not sure if this is the right approach ---- PLEASE HELP dsync -u <DOVECOT_USER> mirror mbox:~/mail:INBOX=<MAIL_BOX_COPIED_FROM_OLD_SERVER> ~# dsync -u hendrikv(a)tcmvpn.co.za mirror mbox:~/mail:INBOX=/var/mail/User_mbox/hendrikv dsync(hendrikv(a)tcmvpn.co.za): Error: pop3c(196.26.136.162): AUTH PLAIN failed: -ERR Invalid command, try one of: USER name, PASS string, APOP name digest, QUIT dsync(hendrikv(a)tcmvpn.co.za): Error: pop3c: Disconnected from remote server dsync(hendrikv(a)tcmvpn.co.za): Error: pop3_migration: Couldn't sync mailbox POP3-MIGRATION-NS/INBOX: Internal error occurred. Refer to server log for more information. [2016-04-04 08:27:01] dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=ddbe5c71e58919cfe2a40905bced091d (UID=3054) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=64087a4c7bf960114cf17ba044047900 (UID=374) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=fd28baf9e91aedaf06c6e979ca76e96f (UID=2982) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=607087e611559d2df02c0684de87e10d (UID=991) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=c6a9aebd1f535f0cd82ed612a42bae77 (UID=1541) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=4c56ffcfb600c8b216b2f1603383dc13 (UID=1007) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=96ce5556fab323206f51deb03625be8a (UID=2357) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=cda74cb161321b7c99973cc65e80a591 (UID=1401) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=b735acf7ef69b39be157a97223878cdc (UID=642) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=6d9baedf21198be32152461f96737a1a (UID=481) dsync(hendrikv(a)tcmvpn.co.za): Error: Mailbox INBOX: Remote didn't send mail GUID=19f36b934b74ce11f1eda95e32a0b112 (UID=1998) dsync(hendrikv(a)tcmvpn.co.za): Error: Exporting mailbox INBOX failed: Can't lookup pop3-uidl for UID=1: POP3 UIDLs couldn't be synce -- Kind Regards Hendrik

1 0

How to make quota_status policy to apply to postfix virtual aliases as well?
by Hamy 04 Apr '16

04 Apr '16

HelloI am setting up a postfix+dovecot setup and using quota-status service to reject mails for full mailboxes on smtp session, according to this: https://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ This is working fine and without any apparent issues. however, Postfix doesn't seem to consult the policy when you're using virtual alias addresses. a virtual alias, is the one that you usually define with virtual_alias_maps . what happens is that Postfix only verifies there is a corresponding value for the given email address and blindly accept it. And it seems smtpd_recipient_restrictions , only applies to the original email address and postfix does not consult that after applying virtual alias. Does any one have any idea how to solve this? is there a setting that i'm missing? or is there a better way to setup email aliases that solve this issue? Best Regards,

1 0