December 2017 - dovecot

Automatic Debian repository (Xi) updated
by Stephan Bosch 29 Dec '17

29 Dec '17

Hi, Now that we have a new Dovecot v2.3 release, I've created a new Xi builder that follows the git master branch to automatically produce Debian packages for the future Dovecot v2.4. The existing v2.3 repository now follows the master-2.3 branch, meaning that this will only follow developments/fixes ported to the v2.3 stable release series. This was already true for the v2.2 oldstable packages. All repositories now finally have the capability of updating version numbers automatically based on releases (as it used to be before we switched to git). This operates a little different than before though: the normal (alpha) repositories produce packages with a version that has an "~alpha" suffix. The base version represents the *next* release version, rather than the current as it was before. So, if the last Dovecot release was 2.3.0, Xi will release packages with version 2.3.1~alpha0, which is the version we're working towards. Another development is that the builders for v2.2 and v2.3 also follow the release-2.x.y branches once these are created. These branches are forked from the respective master-2.x branch once the first release candidate for a release is to be created, so that packages produced in this stream will follow those developments, including the actual release (and any small patch releases that may follow). Unlike the alpha packages, rc packages have a base version that matches the release version. Packages for the release branches are output to separate repository. While e.g. the repository for automatic packages for Debian stable is called "stable-auto", the release branch packages are published to a repository called "stable-rc-auto". The /etc/apt/sources.list line for that would look as follows: deb http://xi.dovecot.fi/debian/ stable-rc-auto/dovecot-2.3 main Keep in mind that, while the rc repositories will have a little more stability, these are still produced fully automatically without any regular human supervision. Using these for production systems is therefore not recommended. Also, since this is a new feature, these repositories are still to be considered experimental. IMPORTANT: Much of this work was prepared and tested earlier in the http://xi.dovecot.fi/debian.new repository. This repository is now shut down and will not be updated anymore. Therefore, all of you who have switched to that repository must switch back to the normal one. As you know, Dovecot now operates a repository with v2.3 packages for the community edition. Unlike Xi, the production of these packages is triggered manually and the resulting packages are suitable for production systems. Xi is still the repository to use if you wish to follow very recent developments (within the hour!) for testing purposes. Regards, Stephan.

1 0

Re: Random delivery
by Aki Tuomi 29 Dec '17

29 Dec '17

Not sure how this is random ... =) So you want it to deliver a the mail to first email1, next email to email2, next to email3, and next to email1. I am pretty sure you can do this better with postfix with transport that redirects it to one of these accounts in order. Aki > On December 29, 2017 at 2:09 AM Jorge Bastos <mysql.jorge(a)decimal.pt> wrote: > > > Howdy, > > > > Id like to achieve something that i dont know if its possible. > > > > I have account info(a)domain.tld and when an email is received, I want to > forward it to several accounts, always in this order: > > > > ð Email1(a)domain.tlf > > ð Email2(a)domain.tld > > ð Email3(a)domain.tld > > > > And when it reached email3(a)domain.tld it starts again with email1(a)domain.tld > > > > Would something like this be possible? >

1 0

doveconf -n not showing all changes
by Marc Weustink 29 Dec '17

29 Dec '17

Hi, Today I was testing the last dovecot release 2.3 from the dovecot repo on ubuntu 16.04. (I upgraded from 2.2.23) I cannot recall if I noticed it before, but doveconf -n not showing all changes. To be able to track my changes, I don't touch the config files provided in conf.d/ anymore, but I write them in local.conf (I did in the past so doveconf -n still shows something) I was testing the new submission service so I added to local.conf: protocols = imap pop3 lmtp sieve submission service submission-login { inet_listener submission { # test port = 588 } } submission_relay_host = 127.0.0.1 after restarting dovecot, submission works, mails get relayed. However doveconf -n shows: protocols = imap pop3 lmtp sieve This is very confusing. Marc

2 2

rename dirs at file system to strip .INBOX prefix?
by Voytek Eymont 29 Dec '17

29 Dec '17

looking at my personal email in /var/vmail/vmail1/dom.tld/voytek(a)dom.tld/Maildir I have some older dirs prefixed with .INBOX as so: .INBOX.Sent.2010.11 .INBOX.Sent.2010.12 around 30 or so, every other dir, .Sent or otherwise, doesn't have INBOX prefix can I just rename them from terminal to strip .INBOX from dir name..? and, if I do, what else I need to do or is that a bad idea, if so, how to get rid of old '.INBOX' prefixes? thanks, -- Voytek

1 0

Random delivery
by Jorge Bastos 29 Dec '17

29 Dec '17

Howdy, Id like to achieve something that i dont know if its possible. I have account info(a)domain.tld and when an email is received, I want to forward it to several accounts, always in this order: ð Email1(a)domain.tlf ð Email2(a)domain.tld ð Email3(a)domain.tld And when it reached email3(a)domain.tld it starts again with email1(a)domain.tld Would something like this be possible?

1 0

Ubuntu Auth Issues with new repository code..
by Howard Leadmon 28 Dec '17

28 Dec '17

Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. I followed the info on repo.dovecot.org, and first it started bitching about lmtp (dovecot: master: Fatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such file or directory), so I went back and installed the dovecot-lmtpd package and that seemed to fix that issue. Just FYI, I had dovecot-core, dovecot-imapd, and dovecot-pop3d installed on the system. OK, so now it started up, said it was 2.3.0 and I thought all was good, but now all authentication is failing. I turned on some of the logging debugging, and am seeing the below: dovecot: auth-worker(19578): Debug: pam(toss1,127.0.0.1,<IR3NJlZhFtZ/AAAB>): lookup service=dovecot dovecot: auth-worker(19578): Debug: pam(toss1,127.0.0.1,<IR3NJlZhFtZ/AAAB>): #1/1 style=1 msg=Password: dovecot: auth-worker(19578): pam(toss1,127.0.0.1,<IR3NJlZhFtZ/AAAB>): pam_authenticate() failed: System error dovecot: auth: Debug: client passdb out: FAIL#0111#011user=toss1 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 3 secs): user=<toss1>, method=PLAIN, rip=127.0.0.1, lip=127.0.1.1, session=<IR3NJlZhFtZ/AAAB> I took and compared my auth files like 10-auth.conf, and auth-system.conf.ext, and they are identical between the two versions, even though they were overwritten as part of the upgrade. If I just uninstall the 2.3.0 release, and install 2.2.22 back on the server, it all just starts working again. So for now I am back on 2.2, but was willing to give 2.3 a run if I can get it going. Any ideas as to what to look at to get this working, would be great. As stated above, this is Ubuntu Server 16.04.03, and I am also running Postfix and amavis-new, but don't think they should really impact me using dovecot for email over POP3 or IMAP.. --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com

5 6

2.3.0 upgrade from 2.2.x
by Fabian A. Santiago 28 Dec '17

28 Dec '17

Question; So after updating to 2.3.0 and following the recommended warnings / changes from running doveconf -n and then doing that same command > "a new conf file", and then renaming the conf files and restarting dovecot, I should be good to go with my old config updated to the new config spec? Just confirming. Thanks. What I mean is doing the -n to a new file hasn't changed or removed anything from my old config? Unless it was a changed or obsoleted option and in that case it would have warned me anyway, correct? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

2 2

Question about imap (expunge response)
by kjonca＠o2.pl 28 Dec '17

28 Dec '17

(This is not neccesarily about dovecot, but rather IMAP protocol) At https://drive.google.com/open?id=1j3oa5jYeSdiPbgaihq02K-u_vHbZLJZQ is fetchmail log from my sessinon with polish email provider "Wirtualna Polska" As you can se fetchmail logged "* 1 EXPUNGE" as a response to "STORE" command. According to https://tools.ietf.org/html/rfc3501#section-7.4.1 EXPUNGE must not be sent as response to STORE command. Am I right that their imap server is erroneous or am I missing something? KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Lonely men seek companionship. Lonely women sit at home and wait. They never meet.

2 2

Re: Renewing certificates
by Joseph Tam 28 Dec '17

28 Dec '17

Kenneth Porter <shiva(a)sewingwitch.com> writes: > Thanks. Some digging indicates that this is equivalent to doveadm reload. > Both paths ultimately send a SIGHUP to the server which initiates a full > reload of the configuration. > > I'll be combining this with a restart of sendmail. Alas, I don't see a way > to get it to reload its configuration. Should be the same way: send a SIGHUP signal to the parent process. http://etutorials.org/Server+Administration/Sendmail/Part+II+Administration… I'm not sure whether this will cause the sendmail worker processes to dump their cients, but if it did, SMTP is fault tolerant enough that delivery should be retried later. Joseph Tam <jtam.home(a)gmail.com>

1 0

Renewing certificates
by Kenneth Porter 27 Dec '17

27 Dec '17

I'm setting up certbot/letsencrypt to provide a certificate for dovecot and sendmail. Is it necessary to restart dovecot to load the new certificate, as shown in most examples I find in blogs? That seems rude to established connections. When does dovecot read the cert and key files? Once at startup or each time a connection requests SSL? Is there a preferred locking protocol when changing the two files to keep dovecot from reading one while the other is being replaced and getting a mismatched pair?

3 3