- dovecot - dovecot.org

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