December 2017 - dovecot

Sieve can't move messages in a public namespace
by Paolo 02 Jan '18

02 Jan '18

Hello, my dovecot version is 2.1.17 I've configured some public namespaces (config attached). When a mail arrives at a certain mail address, that mail is handled by dovecot lmtp server and a sieve script is executed that shuold move the message in one of the namespaces. This is the script: require "fileinto"; if header :contains "From" "example(a)example.com" { fileinto :create "Cond-UFF_FORNITORI/CONTABILITA/Inviata"; } else { fileinto :create "Cond-UFF_FORNITORI/CONTABILITA/Ricevuta"; } The problem is that the sieve script fails with the error: sieve: info: started log at Jun 27 12:42:28. error: msgid=<c9154db4-ff68-52a3-2639-11f09f225f68(a)fcr.re.it>: failed to store into mailbox 'Cond-UFF_FORNITORI/CONTABILITA/Ricevuta': Mailbox doesn't exist: Cond-UFF_FORNITORI/CONTABILITA/Ricevuta. I double checked config, dovecot documentation, sieve documentation, ACL, filesystem paths, filesystem permissions, etc. etc. I'm pretty sure it's all right. So why isn't sieve working? Thanks if you bother to answer & Cheers Paolo

4 6

dovecot-submission SMTP send error with Thunderbird (BODY=8BITMIME)
by Reuben Farrelly 02 Jan '18

02 Jan '18

Hi, With latest 2.3 -git (and 2.3.0 release), I'm running into this error with Thunderbird: "An error occurred while sending mail. The mail server responded: 5.5.4 Unsupported mail BODY type. Please verify that your email address is correct in your account settings and try again." This is fatal and means Thunderbird cannot use the submission service - fortunately I can revert back to a native Postfix service which works. Here's a tcpdump of the conversation: thunderstorm /etc/dovecot/conf.d # tcpdump -A port 587 dropped privs to tcpdump tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 14:12:19.975982 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [S], seq 572328223, win 64800, options [mss 1440,nop,wscale 8,nop,nop,sackOK], length 0 `._.. .? .D.1...E.....>. .D.1..........#...K". ........ .w.............. 14:12:19.976022 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [S.], seq 3954361671, ack 572328224, win 28800, options [mss 1440,nop,nop,sackOK,nop,wscale 7], length 0 `.c|. .@ .D.1..........# .D.1...E.....>..K.....G". ..p.:4.............. 14:12:19.976158 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [.], ack 1, win 8235, length 0 `._....? .D.1...E.....>. .D.1..........#...K". ...HP. +. .. 14:12:19.983409 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 1:43, ack 1, win 225, length 42 `.c|.>.@ .D.1..........# .D.1...E.....>..K.....H". P...:R..220 thunderstorm.reub.net Dovecot ready. 14:12:19.992790 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [P.], seq 1:54, ack 43, win 8234, length 53 `._..I.? .D.1...E.....>. .D.1..........#...K". ...rP. *.H..EHLO [IPv6:2001:44b8:31d4:1311:45ec:e191:8093:3e9d] 14:12:19.992828 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [.], ack 54, win 225, length 0 `.c|...@ .D.1..........# .D.1...E.....>..K.....r". UP...:(.. 14:12:19.993027 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 43:200, ack 54, win 225, length 157 `.c|...@ .D.1..........# .D.1...E.....>..K.....r". UP...:...250-thunderstorm.reub.net 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING 14:12:20.015953 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [P.], seq 54:91, ack 200, win 8234, length 37 `._..9.? .D.1...E.....>. .D.1..........#...K". U....P. *....AUTH PLAIN xxxx 14:12:20.035676 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 200:222, ack 91, win 225, length 22 `.c|.*.@ .D.1..........# .D.1...E.....>..K......". zP...:>..235 2.7.0 Logged in. 14:12:20.036642 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [P.], seq 91:143, ack 222, win 8234, length 52 `._..H.? .D.1...E.....>. .D.1..........#...K". z...%P. *....MAIL FROM:<xxx(a)reub.net> BODY=8BITMIME SIZE=444 14:12:20.036826 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 222:260, ack 143, win 225, length 38 `.c|.:.@ .D.1..........# .D.1...E.....>..K.....%". .P...:N..555 5.5.4 Unsupported mail BODY type 14:12:20.089196 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [.], ack 260, win 8233, length 0 `._....? .D.1...E.....>. .D.1..........#...K". ....KP. ).... Curiously enabling rawlog doesn't capture this error, which is why I used tcpdump above. The logs from it like this: thunderstorm /run/dovecot/rawlogs # cat 20171219-141149.5633.1.in 1513653109.109030 220 thunderstorm.reub.net ESMTP Postfix (3.3-20171028) 1513653109.109266 250-thunderstorm.reub.net 1513653109.109266 250-PIPELINING 1513653109.109266 250-SIZE 40960000 1513653109.109266 250-VRFY 1513653109.109266 250-ETRN 1513653109.109266 250-STARTTLS 1513653109.109266 250-ENHANCEDSTATUSCODES 1513653109.109266 250-8BITMIME 1513653109.109266 250-DSN 1513653109.109266 250 SMTPUTF8 1513653130.973720 221 2.0.0 Bye thunderstorm /run/dovecot/rawlogs # cat 20171219-141149.5633.1.out 1513653109.109087 EHLO thunderstorm.reub.net 1513653130.973351 QUIT 1513653130.973829 QUIT thunderstorm /run/dovecot/rawlogs # This with: # Write protocol logs for relay connection to this directory for debugging #submission_relay_rawlog_dir = submission_relay_rawlog_dir = /run/dovecot/rawlogs/ Is this a separate but unrelated problem with rawlog support in this the submission? I would have expected it to capture the full conversation log including any protocol errors and failures like this. Reuben

3 5

Re: Random delivery
by Joseph Tam 01 Jan '18

01 Jan '18

"Jorge Bastos" <mysql.jorge(a)decimal.pt> writes: > I?d like to achieve something that i don?t know if it?s possible. It's almost always possible; it really depends on how much work you want to do. > 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 Others have suggested a postfix method. You can also pipe it to a script that will select a destination to forward to alias "info(a)domain.tld" to "|/my/selector|script". This will work both in Postfix, sendmail, and probably most other MTAs. If you actually want randomization (rather than sequential round-robin), you can simplify because you won't need to record the last delivery. Use /dev/urandom or unix time() mod 3 to select forwarding address. Joseph Tam <jtam.home(a)gmail.com>

3 2

Re: Random delivery
by Andreas Born 31 Dec '17

31 Dec '17

Jorge Bastos wrote: > 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? If you use the sql driver for userdb lookups, you could do this by means of your mysql lookup query. Just implement a counter and adapt the appropriate INBOX setting für the "mail" variable in the result set.

1 0

Adding Sieve to Roundcube
by ＠lbutlr 31 Dec '17

31 Dec '17

I'm planning on adding support for sieve to Roundcube here in the near future and am looking for any recommendations on read-mes on how to do this. I am planning on waiting until 2.3.0 hits Freebsd Ports -- No Sigs. Blame Apple.

5 6

Package repository now available
by aki.tuomi＠dovecot.fi 30 Dec '17

30 Dec '17

Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy

8 16

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