- dovecot - dovecot.org

systemd also listening on imaps port
by Kai Schaetzl 20 Aug '18

20 Aug '18

I noticed that most of the time with dovecot 2.3 I get this output, showing systemd listening on the port as well: lsof -i TCP:993 systemd 1 root 38u IPv4 3388360574 0t0 TCP *:imaps (LISTEN) systemd 1 root 41u IPv6 3388360575 0t0 TCP *:imaps (LISTEN) dovecot 11607 root 5u IPv4 3388360574 0t0 TCP *:imaps (LISTEN) dovecot 11607 root 6r IPv6 3388360575 0t0 TCP *:imaps (LISTEN) Sometimes I don't get the extra systemd lines, but I can't reproduce it now. It's only for port 143 and 993. Other ports show only two dovecot processes. Operation seems to be normal. Is this how it is supposed to be with dovecot 2.3? This is Ubuntu 16.04.

2 2

Re: creation of ssl-parameters fails
by Kai Schaetzl 20 Aug '18

20 Aug '18

Aki Tuomi wrote on Sun, 19 Aug 2018 18:21:31 +0300: > Just generate new parameters on some machine with good entropy source. So, if it fails to transform (although bigger) the machine hasn't enough entropy (because it's quite new?)? I'm generating now on the original machine from last year which is still going on while a second run on one of the machines where it failed to transform is already finished. So, that would indicate it has less entropy? Can I re-use the ssl-parameters.dat for several machines or should I create a new one for each? For the time being I just copied the dh.pem over, to get going, but I guess this should only be a temporary workaround? Thanks! Kai

3 6

imapsieve: Change message flags on COPY
by Leandro Lucarella 20 Aug '18

20 Aug '18

Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one can really change flags in IMAP without having to create a new (modified) message, I guess this is an exception? 3.8. The "setflag", "deleteflag", and "removeflag" Actions Implementations of IMAP events in Sieve MUST also support the imap4flags extension [RFC5232], and the actions associated with it are all applicable to any case that falls under IMAP events in Sieve. It is worth noting also that the "hasflag" test that is defined in the imap4flags extension might be particularly useful in scripts triggered by flag changes ("hasflag" will see the new, changed flags). The flag changes behave as though a client had made the change. As explained above, in order to avoid script loops, flag changes that are made as a result of a script that was itself invoked because of flag changes SHOULD NOT result in another script invocation. In any case, implementations MUST take steps to avoid such loops. https://tools.ietf.org/html/rfc6785 Should changing flags just work for imapsieve? I even tried to use fileinto to explicitly save a new message (as far as I understand if I use fileinto the implicit keep should be cancelled, so the original message should be flagged as \Deleted (this is another hint that changing flags in immutable messages should be fine), and a new message should be created with the changed flags. But this is not happening, after moving the message I see unseen message still not flagged with \Seen. This is my imapsieve script: ---------------------------- require ["variables", "imap4flags", "fileinto", "vnd.dovecot.imapsieve", "vnd.dovecot.environment", "vnd.dovecot.execute", "vnd.dovecot.debug"]; if header :matches "Subject" "*" { set "subject" "${1}"; } if header :matches "From" "*" { set "from" "${1}"; } if environment :matches "imap.mailbox" "*" { set "dst" "${1}"; } debug_log "IMAPSIEVE TEST ---------------------"; debug_log "subject:${subject}"; debug_log "from:${from}"; debug_log "dst:${dst}"; debug_log "END IMAPSIEVE TEST -----------------"; if string :is "${dst}" ["Archive", "Trash", "Spam", "Sent"] { debug_log "Moved to ${dst}, marking as read: '${subject}' <${from>"; setflag "\\Seen"; fileinto "${dst}"; } ---------------------------- This is the log: Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: Archive: Mailbox opened because: UID MOVE Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: Mailbox INBOX: Opened mail UID=13304 because: copying Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: imapsieve: mailbox Archive: MOVE event Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: imapsieve: Matched static mailbox rule [1] Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: file storage: Using Sieve script path: /home/luca/sieve/imapsieve.sieve Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: file script: Opened script `imapsieve' from `/home/luca/sieve/imapsieve.sieve' Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Opening script 1 of 1 from `/home/luca/sieve/imapsieve.sieve' Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Loading script /home/luca/sieve/imapsieve.sieve Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Script binary /home/luca/sieve/imapsieve.svbin successfully loaded Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: binary save: not saving binary /home/luca/sieve/imapsieve.svbin, because it is already stored Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Executing script from `/home/luca/sieve/imapsieve.svbin' Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 11: DEBUG: IMAPSIEVE TEST --------------------- Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 12: DEBUG: subject:Ihr DHL Paket wurde zugestellt. Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 13: DEBUG: from:DHL Paket <noreply(a)dhl.de> Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 16: DEBUG: dst:Archive Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 17: DEBUG: END IMAPSIEVE TEST ----------------- Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 23: DEBUG: Moved to Archive, marking as read: 'Ihr DHL Paket wurde zugestellt.' <DHL Paket <noreply(a)dhl.de>> Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: Archive: Mailbox opened because: lib-lda delivery Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: left message in mailbox 'Archive' The last line looks weird, it seems like the message is not being copied, right? I tried adding a stop; too, as suggested in this thread https://www.dovecot.org/list/dovecot/2017-April/107658.html, but the effect is the same, the message in Archive is still not flagged as \Seen. So the main question here is if changing IMAP flags in imapsieve scripts shouldn't just work, without even having to use fileinto, and if not, why isn't even using fileinto working? PS: Please Cc me, I'm not in the list. Thanks! -- Leandro Lucarella (Luca) https://llucax.com

2 4

creation of ssl-parameters fails
by Kai Schaetzl 19 Aug '18

19 Aug '18

I did that the last time one year ago, now on another machine with the same software (Ubuntu 16.04) it fails. openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem last command fails with 681+0 records in 681+0 records out 681 bytes copied, 0,00278343 s, 245 kB/s unable to load DH parameters 139858178938624:error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag:../crypto/asn1/tasn_dec.c:1129: 139858178938624:error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error:../crypto/asn1/tasn_dec.c:289:Type=DH ssl-parameters.dat is more than double the size as the one that worked. And that one I can still transform: 272+0 records in 272+0 records out 272 bytes copied, 0,00105017 s, 259 kB/s So, something with openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat must be wrong. But what? https://wiki.dovecot.org/SSL/DovecotConfiguration tells to use this command. Thanks! Kai

3 2

dovecot and postfix, help?
by Christy S 19 Aug '18

19 Aug '18

Hi all, First a disclaimer. I have played with linux off and on for years, but this is my first time trying to run a server completely on my own from start to finish, well it's on a vps, but still. I'm pretty techie, but a lot of this stuff is new to me, so I apologize for any *duh!* questions. That said, I've so far installed dovecot, postfix, wordpress, and related programs mostly successfully by following tutorials. I say mostly successfully, because I'm having a really hard time trying to get dovecot and postfix to behave together, and I'm about at the end of what I know how to find on google. If you're still with me and not groaning at yet another newbie asking wtf did I do wrong questions, thank you! My basic setup is running ubuntu 18 with up to date dovecot and postfix. Sasl is installed, and I'm using a custom domain with all records successfully pointing to the VPS. As I mentioned, I've been following tutorials. My goal is to have a mail server which can send and receive emails using this custom domain both from the shell and, much more often, from my primary computer using thunderbird. As there will likely only be two of us using this, I'm completely fine with the setup using mailboxes that actually have linux accounts. I'm also using maildir as the mailbox type. Furthermore, I want to make sure to use ssl on any mail connections.. Normal passwords but ssl being used. So, following one tutorial I set up postfix and dovecot, then went to test it. The result was that while on the shell, I could send email to my gmail account from the domain and receive it just fine. I could also send mail from my gmail account to the domain and receive it on the shel. I even managed to get imap to work, so I could receive domain emails in thunderbird, after playing around with tb's settings. However, if using tb I attempted to send an email using the custom domain, smtp failed to connect. I verified with my VPS provider that no, they do not block port 25, 465 or 587. I also verified that at&t, my home ISP, does not block outgoing smtp traffic, considering I am using google's for my gmail account. After hitting google again, I realized two things. One, for some reason port 25 never got opened on UFW, so I fixed that. Second, for some reason in all the stuff I did, postfix never got configured to use SSL. I found yet another tutorial, and ran through it to set up SSL with postfix. However, in doing this I had to change a path for sasl, only to find out later that doing that broke dovecot! Imap completely and utterly stopped behaving. Back to google again, and this time I found something a bit more up to date which explained how to interconnect postfix and dovecot. It goes through using mysql too, but I don't need that, so I skipped that part. Changed the sasl path back to what it should be, told dovecot and postfix to talk to each other and... Nope, still nothing. I saw a warning that I should not use different certificates for postfix and dovecot, so I told dovecot to look at the smtpd certificate that I made. Not sure if that's what's breaking this or something completely different, as I'm also brand new to the ssl certificate creation process. So, here's the current status of using thunderbird with my domain. mail sent from gmail to new domain, never comes back in thunderbird but doesn't bounce, either. Mail sent via thunderbird to gmail from domain, works, but shows up as from my gmail domain as well, which makes me think it's defaulting to the gmail account even though the domain's smtp info is set up. This could be because just before writing this message, I got the accept this certificate dialog over and over again for the domain and had to cancel out of it. One final point. I looked at /var/log/mail.log and, while at first I found an error in the path to one of the certificates, once I fixed that no error shows up. I restarted both postfix and dovecot, tried refreshing thunderbird and still no emails showed up. I see the connection in the log, but no errors. Anyone have ideas? Even maybe just point me in the right direction for what to check?

3 2

update to my first email
by Christy S 19 Aug '18

19 Aug '18

Alright so after checking logs, rebooting the vps because why not, and removing and re-adding the account in thunderbird... Now nothing is working other than sending mail from gmail to the domain. imap does not pick up the email and trying to send with the domain just plain fails, saying it can't connect to the server. Honestly, tempted to uninstall dovecot, sasl and postfix and start again, but I don't want to run into the same issues with conflicting tutorials. Does anyone know of a good source of how to do this that's fairly recent? I'll keep searching, but all of the outdated info is kind of frustrating. If anyone has replied to me I haven't gotten it yet, so I'm not ignoring anything you may have said. For now going to give this a break. I've been working on it literally all day! :) Christy

4 3

None
by Jarrad 18 Aug '18

18 Aug '18

1 0

Imap special-use with IOS 11
by Federico Bartolucci 17 Aug '18

17 Aug '18

Hello, has anyone experiened any issues with IMAP SPECIAL-USE extension with ios11? After the update to ios11 the Ios mail client seems to not recognize anymore the imap special-use, so that system folders (Sent, Trash etc..) are not authomatically recognized and set during the configuration. Regards Federico

2 1

"nologin" field set leads to internal failure
by postminion＠dicksinmyan.us 17 Aug '18

17 Aug '18

Hi, I've tried to use the "nologin" extra password-db field as specified here: https://wiki.dovecot.org/PasswordDatabase/ExtraFields/NoLogin Due to lack of exact documentation, I've tried to use `nologin`='y' for users that can't login, and setting `nologin`='n' for normal users. Apparently setting it to NULL for normal users would have been correct, as I've found out. Maybe write that on the above website. Anyway, login didn't work for a user with `nologin`='n' set. Trying to debug a normal user being unable to login, the log (mail.log) says: dovecot: imap-login: Disconnected (internal failure, 4 successful auths): user=<test(a)example.com>, method=PLAIN, rip=<ip6>, lip=<ip6>, TLS, session=<session> What I'm expecting it to say would be something like "user not allowed to login". I'm considering this a problem because of "Dovecot always logs a detailed error message if something goes wrong." as written here: https://wiki2.dovecot.org/Logging For the record, setting auth_debug=yes and mail_debug=yes gave the following line in the logs somewhere, from which I was able to figure out that NOLOGIN was the problem: dovecot: auth: Debug: client passdb out: OK#011<id>#011user=test(a)example.com#011nologin Thank you. dovecot -n output: --snip-- # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 auth_default_realm = example.com base_dir = ... listen = *,[v6] login_greeting = ... mail_home = .../%d/%n/ mail_location = maildir:~/mail/:INDEX=MEMORY mail_plugins = trees mail_temp_dir = ... namespace inbox { inbox = yes location = prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap lmtp recipient_delimiter = -+ service auth { unix_listener ... { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 0 } service_count = 1 } service lmtp { unix_listener ... { group = postfix mode = 0600 user = postfix } user = vmail } ssl = required ssl_cert = <... ssl_cipher_list = ... ssl_dh_parameters_length = 4096 ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } --snap--

1 0

imap-login: Error: BUG: Authentication server sent unknown id
by Tom Sommer 17 Aug '18

17 Aug '18

I randomly get these errors on my Director Aug 17 10:52:37 imap-login: Error: BUG: Authentication server sent unknown id 98448 Aug 17 10:52:37 imap-login: Warning: Auth connection closed with 2 pending requests (max 2 secs, pid=27036, Received broken input: FAIL 98448 user=user(a)example.com) Aug 17 10:52:37 auth: Warning: auth client 27036 disconnected with 1 pending requests: EOF 2.3.2.1 -- Tom

2 1