- dovecot - dovecot.org

Workaround for rcpt suffix
by Robban 10 May '16

10 May '16

Hi all! I'm stuck again, let me start with explaining my setup. The PassDB and UserDB is LDAP (FreeIPA) and I'm using ldap mail attribute to search after the recipient so one user can have multiple mail aliases. So far so good. Next is to have an catchall(a)domain.tld, that is done via an static userdb backend (I know you are strongly against catchall adresses), and they are delivered to public folders (${mail_location}/domain.tld). I also use address extension so sort a mail to correct folder (+ sign). Now I need to fix so mail to <mail attr>-sievetest is handled by the user assigned to <mail attr>, is this somehow possible? //Robban

2 1

resorting emails by date order after move/copy to sub folder ?
by voytek＠sbt.net.au 10 May '16

10 May '16

I have just used Squirrel web client to re organize some old emails to subfolders. that worked OK, EXCEPT, all these emails are now in order that I have moved them rather than original date, is that some 'simple' way to re-sort them back by original date ? thanks for any pointers, sorry for dumb question Voytek

2 2

more info about deleting users
by Matteo Gaito Test Account 09 May '16

09 May '16

Hi, i've search a lot in order to find a way to delete account by dovecot but i found only this way http://dovecot.org/list/dovecot/2011-November/079273.html It's possible today delete a maildir remotely with doveadm or with dovecot api? Thanks Matteo

6 8

Panic: file doveadm-mail.c: line 417 (doveadm_mail_single_user): assertion failed: (cctx->username != NULL)
by Daniel van Ham Colchete 07 May '16

07 May '16

Hello everyone! So, I'm trying to move away from a few older servers into new ones but I can't get dsync to work this time (the 2013 migration went perfectly). This is what I get: root@dovecot:/# dsync sync -u user(a)domain.org.br tcp:XXXX:12345 Panic: file doveadm-mail.c: line 417 (doveadm_mail_single_user): assertion failed: (cctx->username != NULL) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x85dee) [0x7f500d3cddee] -> /usr/lib/dovecot/libdovecot.so.0(+0x85e68) [0x7f500d3cde68] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f500d3725be] -> dsync(+0x28d50) [0x55dcb11bad50] -> dsync(+0x28ded) [0x55dcb11baded] -> dsync(doveadm_mail_try_run+0x219) [0x55dcb11bb779] -> dsync(main+0x441) [0x55dcb11aba91] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f500cfbeb45] -> dsync(+0x19c06) [0x55dcb11abc06] Aborted (core dumped) root@dovecot:/# doveconf -N is here: http://pastebin.ca/3594094 doveadm user '*" will list all the users correctly doveadm user user(a)domain.org.br will show all the user info correctly. Thank you very much! Best, Daniel Colchete

1 0

Is there a way to override Sieve's "not sending notification for auto-submitted message" behavior?
by deoren 07 May '16

07 May '16

Goal: 1) Setup a Google Calendar entry for a biweekly task 2) Configure the email notification schedule 3) When the email notification from Google arrives have Sieve send a notification to an alias I have setup for my cell provider's email to text messaging gateway 4) Receive text message I know there are other products which likely handle this better, but I'm specifically attempting to replicate old behavior by getting text message reminders when a specific Google Calendar event occurs. The problem I'm having is that Sieve is attempting to help by NOT sending a notification for emails that it finds are automatically generated. I didn't found a lot of information when I searched for additional details, but I didn't find an earlier message thread on this list that led me to believe that the default behavior is likely chosen as some sort of safety net to prevent common issues from occurring. What I would like to do is override this behavior at some level (per rule, per user, system-wide, whatever) to allow for Sieve notifications when emails matching a specific pattern are detected regardless of whether they are auto-generated or not. I already found mention in the documentation[1] that the editheader extension refuses to remove the Auto-Submitted header, so setting up a per user or global rule to do just that wouldn't help. I also haven't come upon a way to simply modify the value for the Auto-Submitted header, so that doesn't look to work in this situation either. Does anyone know of a way to accomplish this? Thanks in advance for your help! [1] http://wiki2.dovecot.org/Pigeonhole/Sieve/Extensions/Editheader

2 5

Re: Cannot connect to Dovecot IMAP or POP
by Joseph Tam 06 May '16

06 May '16

C. Andrews Lavarre writes: > Presumably, as Joseph shows with his nc call, imap calls are to ServerName mail.privustech.com. No, nc is just a dumb tool -- it knows nothing about IMAP or SSL. You didn't even get to the SSL handshake. Your problem has nothing to do with the interaction of client and server -- it's strictly a server problem. > ssl = required > ssl_cert = </etc/apache2/ssl.crt/mail.privustech.com_start.crt > ssl_key = </etc/apache2/ssl.key/mailprivustech.key > ssl_ca = </etc/apache2/ssl.crt/mailprivustech_root_bundle.crt ssl_ca is not analogous to Apache's SSLCertificateChainFile. I believe "ssl_ca" is used to validate clients (i.e. mutual authentication). You ought to concatenate your intermediate CA chain certificates and your public key into ssl_cert. See http://wiki2.dovecot.org/SSL/DovecotConfiguration Also, anything enlinghtening in the logs when ssl_verbose turned on? Joseph Tam <jtam.home(a)gmail.com>

1 0

Dovecot/Rainloop 2.0.13-1_129.el5
by Chris Smith 05 May '16

05 May '16

I configured Dovecot on our mail server under Centos 5.3 (I think) some while ago now (about 2 years) and, to the best of my knowledge,it had been working correctly all that time. However, one of the team wanted to use webmail while away from base and found that, although he could receive emails OK, he was unable to reply or send fresh emails. When he pressed Send he got a message “Authentication failed" in a pop-up box. He assured me that sending mail had been working and I was certain that I had tested that aspect when I was setting Dovecot up, at least for local mail. I tried to send email from my Dovecot account and had the same problem. Our MTA is sendmail and that is not configured to authenticate on outgoing mail, The configuration for sendmail hasn’t changed at least since the last update in 16 March 2015 (sendmail 8.13.8-10.el5_11). Dovecot uses php-5.5.5 in this set up. The relevant entry in /var/log/maillog when I attempt to send an email from Dovecot is: May 5 16:34:29 firewall dovecot: auth: Debug: auth client connected (pid=13001) May 5 16:34:29 firewall dovecot: auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=51861 resp=AGNocmlzADB1dFkwdUcwNDkh May 5 16:34:29 firewall dovecot: auth: Debug: pam(chris,127.0.0.1): lookup service=dovecot May 5 16:34:29 firewall dovecot: auth: Debug: pam(chris,127.0.0.1): #1/1 style=1 msg=Password: May 5 16:34:29 firewall dovecot: auth: Debug: client out: OK 1 user=chris May 5 16:34:29 firewall dovecot: auth: Debug: master in: REQUEST 2607546369 13001 1 0bcf2e3a108cd9cd18eaff4b7de9c428 May 5 16:34:29 firewall dovecot: auth: Debug: passwd(chris,127.0.0.1): lookup May 5 16:34:29 firewall dovecot: auth: Debug: master out: USER 2607546369 chris system_groups_user=chris uid=514 gid=100 home=/home/chris May 5 16:34:29 firewall dovecot: imap-login: Login: user=<chris>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=13002, secured May 5 16:34:29 firewall dovecot: imap(chris): Disconnected: Logged out bytes=11/334 May 5 16:34:29 firewall sendmail[13003]: u45FYTtd013003: localhost.localdomain [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA The webmail server and our mail server are the same system. The firewall is open for port 143. It is only send from Dovecot that fails authentication, all other outgoing mail is sent correctly. Does anyone have any idea where else I can look for clues as to why there is this behaviour? Suplementary question: what does the “Sign me” check box on the webmail log in page do? Many thanks. Chris

3 2

Long delays when deleting a message in inbox
by Yves Goergen 05 May '16

05 May '16

Hi, Since recently, there's a long delay when deleting any message from my inbox folder. This affects deleting and moving messages, but only the inbox of a single mailbox. The delay is a few seconds. Other operations work instantly. The server is Ubuntu 14.04 running Dovecot version "1:2.2.9-1ubuntu2". The filesystem is local ext4. My MUA is Thunderbird on Windows, latest version, connecting with IMAP. What could be the cause for this extreme delay? Yves Goergen http://unclassified.software

3 4

Re: Cannot connect to Dovecot IMAP or POP
by Joseph Tam 05 May '16

05 May '16

> 2. openssl s_client -connect mail.privustech.com:xxx > a. xxx=25, 110, 143 all return > error:140770FC You need to add the "-starttls protocol" parameter, otherwise "openssl s_client" thinks your using SSL, not STARTTLS i.e. openssl s_client -starttls pop3 -connect mail.privustech.com:110 openssl s_client -starttls imap -connect mail.privustech.com:143 But even if you do that, you get the same error because it can't start the TLS session: $ nc mail.privustech.com 143 * OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED AUTH=CRAM-MD5] privustech.com IMAP4rev1 2007e.404 at Wed, 4 May 2016 22:26:36 -0400 (EDT) x STARTTLS x NO Server certificate not installed So there you go, dovecot can't get at your server certificate. You can start the search of your problem from there. The configuration verbose_ssl = yes will help to log the problem. > ssl_dh_parameters_length = 2048 Probably not related to your problem, but this will cause wildly variable dovecot initialization times, as temp key generation of this length can result in a lot of candidate primailty testing. Joseph Tam <jtam.home(a)gmail.com>

2 1

Changing Password Schemes
by Carl A Jeptha 03 May '16

03 May '16

Good Day, I have been following this tutorial without much luck - http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes#CA-26af2b83a43b810052… It is obvious to me that I am not following the instructions correctly and need to be shown what I am misunderstanding. I have an old postfix + dovecot + Roundcube mailserver (mail.domain.Tld). Server clock is loosing time and adjusting it causes dovecot to kill itself, we cannot install more memory, bigger hard-drives, etc. I have built a new server box (mail2.domain.Tld) With Postfix + dovecot + Roundcube. This server is functioning, with a client's new domain, and my personal domain. it's password system is SHA512-CRYPT. I have imported the users from the old server over to the new server. I have created a new column "plain_pass" for the plain passwords. I will be using imapsync to transfer the mail folders from the one server to the other, but will not proceed until I fix this issue. # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 4.2.0-35-generic x86_64 Ubuntu 15.10 ext4 auth_mechanisms = plain login first_valid_gid = 8 first_valid_uid = 150 last_valid_gid = 8 last_valid_uid = 150 listen = * mail_gid = mail mail_location = maildir:/var/vmail/%d/%n mail_uid = vmail 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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota_grace = 10%% quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } postmaster_address = postmaster(a)airnet.ca protocols = imap pop3 lmtp lmtp pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service imap { executable = imap imap-postlogin } 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 } ssl_cert = </etc/ssl/certs/ssl-cert-snakeoil.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/ssl-cert-snakeoil.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } -- ------------ You have a good day now, en mag jou môre ook so wees, Carl A Jeptha

9 35