June 2019 - dovecot - dovecot.org

Exclude dovecot-uidlist files from a Maildir backup ?
by David Pottage 25 Jun '19

25 Jun '19

Hi, I am using restic to backup my email (stored in dovecot Maildir format) to Amazon S3 As each message is a separate file on disk, and those files don't change after the email has been delivered and read by the user, the incremental backup each day is fairly efficient as it only stored new mails. However, the dovecot-uidlist files change frequently, and are often quite large. The restic backup program detects the file has changed and uploads a new version, but is not smart enough to detect that only a few lines have changed, so it uploads a fresh copy of the entire file to remote storage. I have done some test backups and have noticed, that if I exclude those files from the backup, it completes much faster and uploads far less. Would this be a reasonable policy? My backup is mainly there against unlikely but severe events such as complete hard drive failure, so if I ever had to use it, I would not mind wating for my email client to re-download all my emails. -- David Pottage

1 0

Dovecot LDA error - Invalid -f parameter: Invalid character in path
by Bruno de Paula Larini 25 Jun '19

25 Jun '19

Hi list. I'm using dovecot as postfix's LDA. The version is 2.3.6. Last week some spammer set the envelope's FROM to "foo@bar@domain.com" (with two @). While trying to deliver (as this one didn't hit the spamassassin's score), dovecot said the following: Jun 21 02:35:58 mymailserver postfix/pipe[29736]: ADA268195E: to=<user@mydomain>, relay=dovecot, delay=0.08, delays=0.03/0.02/0/0.04, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal: Invalid -f parameter: Invalid character in path ) Which caused postfix to put it on the bounce list, but the spammer's destiny don't really exist. I could successfully mimic the spammer using telnet and putting two @ in "mail from" address. I don't think this should be an expected behaviour, right? Or is this some config based error? Thanks!

2 1

Authentication against multiple mysql databases
by Graham S. Jarvis 24 Jun '19

24 Jun '19

Hello, I have setup authorisation against a mysql database. I'd now like to do (additional) authentication against another mysql database. i.e. I have two databases with usernames and passwords and I'd like allow all the users from both databases to be able to login to IMAP. Can I simply extend 10-auth.conf in conf.d with additional !include files - like auth-sql.db1.conf.ext auth-sql.db2.conf.ext and associated filed etc. Or do I have to create a new database and set up a view onto the other two databases / tables? Any ideas? Thanks, -Graham-

1 0

Re: Mail migration problem
by Germán Herrera 24 Jun '19

24 Jun '19

Well, judging by the error message it appears like dovecot hasn't been compiled with support for maildir, which is strange because I don't see any way to disable in the compile-time options. Are you using the precompiled package from the distro or compiling dovecot by yourself? Could you share the output of "dovecot --build-options" and "dovecot --version"? Thanks! On 2019-06-21 17:17, Adam Raszkiewicz wrote: > Hi German, > > I have tried your way and getting the same error message: > > dsync(user(a)domain.com): Debug: Namespace inbox: type=private, prefix=, > sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes > location=maildir:~/Maildir > > dsync(user(a)domain.com): Error: User initialization failed: Namespace > '': Unknown mail storage driver maildir > > Thoughts? Missing dovecot library, something in the configuration? > > Thanks, > > Adam > > FROM: dovecot <dovecot-bounces(a)dovecot.org> on behalf of Germán Herrera > via dovecot <dovecot(a)dovecot.org> > ORGANIZATION: SES Sistemas Electrónicos S.A. > REPLY-TO: Germán Herrera <g.herrera(a)ses.com.ar> > DATE: Friday, June 21, 2019 at 3:10 PM > TO: Adam Raszkiewicz <araszkiewicz(a)medallies.com> > CC: "dovecot(a)dovecot.org" <dovecot(a)dovecot.org> > SUBJECT: Re: Mail migration problem > > Hi Adam > > Can you try: "doveadm sync -u <user> maildir:~/Maildir" > > My mailboxes are in sdbox (I have "mail_location = > sdbox:~/sdbox:ALT=/mnt/archive/%u/sdbox") and after running that > command I managed to successfully migrate the user mailbox to maildir. > Also that is the command I used to migrate all my user's maildirs to > sdbox some time ago. > > Regards > > --- > > Germán Herrera > Responsable de IT > Ingeniería > SES Sistemas Electrónicos S.A.| Espinosa 1045 (C1405AMM) | Buenos Aires > | Argentina > W: +54 11 54530000 | Email: g.herrera(a)ses.com.ar > > ------------------------- > > Denos su opinión aquí > > On 2019-06-21 11:58, Adam Raszkiewicz via dovecot wrote: > >> I'm trying to migrate mdbox to maildir based on >> https://wiki.dovecot.org/Migration/MailFormat >> >> * Modified dovecot.conf and set >> mail_location=maildir:/tmp/destination/mailboxes/ >> * Then I had run >> >> /mnt/testmail/bin/dsync -Dv -u user(a)domain.com mirror >> mdbox:/source/mailboxes/user@domain.com >> >> but that did nothing. Then I have >> >> * Modified dovecot.conf and set mail_location=mdbox:/source/mailboxes >> * Then I had run >> >> /mnt/testmail/bin/dsync -Dv -u user(a)domain.com mirror >> mdbox:/tmp/destination/mailboxes/user@domain.com >> >> that copied over user(a)domain.com mailbox from the source to the >> destination location. As that was working I have tried to run >> >> /mnt/testmail/bin/dsync -Dv -u user(a)domain.com mirror >> maildir:/tmp/destination/mailboxes/user@domain.com >> >> but that got an error: >> >> dsync(user(a)domain.com): Debug: Namespace inbox: type=private, prefix=, >> sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes >> location=maildir:/mnt/testmail/mailboxes >> >> dsync(user(a)domain.com): Error: User initialization failed: Namespace >> '': Unknown mail storage driver maildir >> >> First problem is that based on example #2 from above provided syntax >> in https://wiki.dovecot.org/Migration/MailFormat is incorrect or for >> some reason is not working for me as it should for example #1. >> >> Second issue is not recognizing maildir format - what about that? >> Docecot has some missing libraries? >> >> Thanks, >> >> Adam

2 2

Mail migration problem
by Adam Raszkiewicz 24 Jun '19

24 Jun '19

I’m trying to migrate mdbox to maildir based on https://wiki.dovecot.org/Migration/MailFormat * Modified dovecot.conf and set mail_location=maildir:/tmp/destination/mailboxes/ * Then I had run /mnt/testmail/bin/dsync -Dv -u user(a)domain.com<mailto:user@domain.com> mirror mdbox:/source/mailboxes/user@domain.com<mailto:/source/mailboxes/user@domain.com> but that did nothing. Then I have * Modified dovecot.conf and set mail_location=mdbox:/source/mailboxes * Then I had run /mnt/testmail/bin/dsync -Dv -u user(a)domain.com<mailto:user@domain.com> mirror mdbox:/tmp/destination/mailboxes/user@domain.com<mailto:/source/mailboxes/user@domain.com> that copied over user(a)domain.com<mailto:user@domain.com> mailbox from the source to the destination location. As that was working I have tried to run /mnt/testmail/bin/dsync -Dv -u user(a)domain.com<mailto:user@domain.com> mirror maildir:/tmp/destination/mailboxes/user@domain.com<mailto:/source/mailboxes/user@domain.com> but that got an error: dsync(user(a)domain.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/mnt/testmail/mailboxes dsync(user(a)domain.com): Error: User initialization failed: Namespace '': Unknown mail storage driver maildir First problem is that based on example #2 from above provided syntax in https://wiki.dovecot.org/Migration/MailFormat is incorrect or for some reason is not working for me as it should for example #1. Second issue is not recognizing maildir format – what about that? Docecot has some missing libraries? Thanks, Adam

3 2

quota-plugin + namespace with wildcards?
by Jost-Philip Matysik 24 Jun '19

24 Jun '19

Hi all! Is the quota-plugin (quota + quota-rule directives) supposed to function for namespaces that are generated dynamically for shared mailboxes? (namespace=shared/%u with %u expanded from userdb) 'Cause I cannot find anything in the wiki that suggests it can't be used that way, but it ain't a-workin'... :o( Thanks! Jost

1 0

last login user tracking
by David Mehler 22 Jun '19

22 Jun '19

Hello, I'm trying to get last login user tracking going, using Dovecot and mysql. I'm using: https://docs.iredmail.org/track.user.last.login.html and it is working, I am seeing an entry and it is updated, the problem is the last login value does not mean anything to me. I was wondering if it's possible to have the value be of a last login date and time, and also a remote ip would be helpful so I can see from where users are logging in from. Thanks. Dave.

4 4

Submission service and SMTP AUTH capability
by Germán Herrera 22 Jun '19

22 Jun '19

Hi Everyone! I've setup dovecot 2.3.2.1 on a Gentoo server. I want to configure the submission service in order to replace the corresponding part in Postfix (which is my SMTP server). I configured submission it with just a few options different of the default ones: submission_client_workarounds = whitespace-before-path submission_relay_host = 127.0.0.1 submission_relay_port = 10026 submission_relay_trusted = yes The issue I'm having is that the SMTP AUTH is enforced and performed correctly, but it doesn't get published on the server capaabilities when the connection doesn't come from localhost. This causes issues with some smtp clients which authenticate (python smtpclient). When I telnet the submission service from localhost I get: 220 (protected hostname) Dovecot ready. EHLO L 250-(protected hostname) 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING quit 221 2.0.0 Bye But when I do the same from another host other than the one running dovecot (telnetting the submission port): 220 (protected hostname) Dovecot ready. EHLO L 250-(protected hostname) 250-8BITMIME 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING quit 221 2.0.0 Bye As you can see, the AUTH capability is not there. Do you know what could be causing this issue? Your help is much appreciated! German

3 3

Listener indicated in logs
by jbwlists＠hilltopgroup.com 21 Jun '19

21 Jun '19

I'm looking for a way to indicate which listener a connection came in via in the logs. For instance, I have IMAPS connections coming in via 993 as well as 1993, and would like some way to differentiate in the logging. Is there a way to do this? Thanks in advance, Joseph

2 2

CentOS 7 SeLinux Problem?
by Günther J. Niederwimmer 21 Jun '19

21 Jun '19

Hello, I update my dovecot to the last Version, now I have this error in the audit Log. Can any tell me what I can do, without selinux disabled // SELinux hindert /usr/sbin/dovecot daran, mit getattr-Zugriff auf Datei /proc/ sys/fs/suid_dumpable zuzugreifen. ***** Plugin catchall (100. Wahrscheinlichkeit) schlägt vor ************** If you believe that dovecot should be allowed getattr access on the suid_dumpable file by default. Dann sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Ausführen allow this access for now by executing: # ausearch -c 'dovecot' --raw | audit2allow -M my-dovecot # semodule -i my-dovecot.pp zusätzliche Information: Quellkontext system_u:system_r:dovecot_t:s0 Zielkontext system_u:object_r:proc_security_t:s0 Zielobjekte /proc/sys/fs/suid_dumpable [ file ] Quelle dovecot Quellpfad /usr/sbin/dovecot Port <Unknown> Host <Unknown> RPM-Pakete der Quelle dovecot-2.3.6-2.x86_64 RPM-Pakete des Ziels Richtlinien-RPM selinux-policy-3.13.1-229.el7_6.12.noarch SELinux aktiviert True Richtlinientyp targeted Enforcing-Modus Enforcing Rechnername mx01.example.com Plattform Linux mx01.example.com 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 x86_64 Anzahl der Alarme 1 Zuerst gesehen 2019-06-21 06:15:28 CEST Zuletzt gesehen 2019-06-21 06:15:28 CEST Lokale ID 259a6386-ad49-4cdf-a21b-97f891c997aa Raw-Audit-Meldungen type=AVC msg=audit(1561090528.816:4135): avc: denied { getattr } for pid=28610 comm="dovecot" path="/proc/sys/fs/suid_dumpable" dev="proc" ino=39881 scontext=system_u:system_r:dovecot_t:s0 tcontext=system_u:object_r:proc_security_t:s0 tclass=file permissive=0 type=SYSCALL msg=audit(1561090528.816:4135): arch=x86_64 syscall=stat success=no exit=EACCES a0=556b5394906b a1=7fff567c8e40 a2=7fff567c8e40 a3=7fff567c87e0 items=0 ppid=1 pid=28610 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=dovecot exe=/usr/sbin/dovecot subj=system_u:system_r:dovecot_t:s0 key=(null) Hash: dovecot,dovecot_t,proc_security_t,file,getattr // when I create a separate my-dovecot.pp I have the same Error :-( -- mit freundliche Grüßen / best regards, Günther J. Niederwimmer

1 0