- dovecot - dovecot.org

dovecot-openssl-common.c and [-Wincompatible-pointer-types]
by Rupert Gallagher 18 Mar '19

18 Mar '19

Warnings from clang 7.0 when compiling dovecot-openssl-common.c from dovecot 2.3.5 with openssl 1.1.1a. This is dovecot's configuration: > config_options="--prefix=$prefix \ > --sysconfdir=$prefix/etc \ > --datarootdir=$prefix/share \ > --mandir=$man \ > --docdir=$doc \ > --with-docs \ > --with-ssl=openssl --with-ssldir=$prefix/etc \ > --with-sodium \ > --with-libiconv-prefix=/opt/libiconv \ > \ > --with-bzlib=no \ > --with-gssapi=no \ > --with-ldap=no \ > --with-lucene=no \ > --with-lz4=no \ > --with-lzma=no \ > --with-pam=no \ > --with-solr=no \ > --with-sql=no \ > --with-vpopmail=no \ > --with-zlib=no \ > \ > --enable-dependency-tracking"; Note on passing: --with-ssldir=$prefix/etc is ignored by the configurator, as it forces $prefix/etc/dovecot.

1 0

Dovecot logrotation - old journal files are still in use (second attempt)
by Denis V Razumovskiy 18 Mar '19

18 Mar '19

Hi all Sorry, it is the second attempt due to wrong format of the first message. In my Dovecot there are 3 files of logging (debug, info and .log) While executing logrotation, the new files are created, but the previos ones, namely dovecot.*.1 are still in use by the process Here is the logger process in memory: root 19140 0.0 0.0 4140 1576 ? S Mar12 0:06 dovecot/log Here the files it uses after the daily logrotation had happened: # lsof -p19140 |grep log ... log 19140 root 33w REG 9,3 811 417675 /var/log/dovecot.log.1 log 19140 root 34w REG 9,3 2842123 417681 /var/log/dovecot.info.1 log 19140 root 35w REG 9,3 14853918 417683 /var/log/dovecot.debug.1 ... After the manual issue 'doveadm log reopen` command the files are changed to # lsof -p19140 |grep dovecot\\\. ... log 19140 root 33w REG 9,3 0 417651 /var/log/dovecot.log log 19140 root 34w REG 9,3 121374 417690 /var/log/dovecot.info log 19140 root 35w REG 9,3 916153 417691 /var/log/dovecot.debug as it is expected to be. I use the logrotate config for dovecot instance: /var/log/dovecot.log /var/log/dovecot.info /var/log/dovecot.debug { daily rotate 14 missingok notifempty compress delaycompress sharedscripts postrotate doveadm log reopen chmod 666 /var/log/dovecot.log chmod 666 /var/log/dovecot.info chmod 666 /var/log/dovecot.debug endscript } At the same time, dovecot itself still uses previous logs: # lsof |grep var\/log\/dovecot\. dovecot 19138 root 8w REG 9,3 12962 417613 /var/log/dovecot.log.1 (deleted) dovecot 19138 root 9w REG 9,3 4097250 416836 /var/log/dovecot.info.1 (deleted) dovecot 19138 root 10w REG 9,3 23816347 417603 /var/log/dovecot.debug.1 (deleted) What can be the root of the issue? I use Dovecot as LDA for Postfix with system users, mbox mail format. System Slackware 12.0 x86, Postfix 2.4.5, Dovecot 2.2.36. Interconnect Postfix-Dovecot has been made via `mailbox_command = ...' Dovecot was compiled from sources Logging configuration (file conf.d/10-logging.conf) contains the following: log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.info debug_log_path = /var/log/dovecot.debug auth_verbose = yes auth_verbose_passwords = yes auth_debug = yes mail_debug = yes verbose_ssl = yes plugin { } Could the fact, that Postfix require Dovecot logs to be accessible someway, result in such a weird behavior? To allow other processes to access Dovecot logs I had to chmod 0666 all the current logs while integrating Dovecot into Postfix delivery (please see `chmod' commands in the logrotate config above) Please ignore my previos post https://dovecot.org/pipermail/dovecot/2019-March/115075.html Thank you Denis Razoumovskiy

2 1

child-wait.c and [-Wnull-pointer-arithmetic]
by Rupert Gallagher 18 Mar '19

18 Mar '19

Attached warnings from clang 7.0 when compiling child-wait.c from dovecot 2.3.5: "arithmetic on a null pointer treated as a cast from integer to pointer is a GNU extension [-Wnull-pointer-arithmetic]".

2 2

LDAP users issue
by Anushka Bandara 18 Mar '19

18 Mar '19

Hi Team, I have enabled LDAP authentication with webmail client and it works successfully. But I found an error with LDAP user's mail. Email is not loaded when I log with an LDAP user. Login phase is successful and mail box is the issue. I created a mail user without including LDAP and that user works fine. Issue comes only with LDAP users. *Anushka Bandara* Research Engineer Lanka Software Foundation +94715846018

3 4

Upgrade from 2.1.17 2.2.36
by lty 18 Mar '19

18 Mar '19

v2.1.1 v2.2.36 The screenshot is the result returned by imap. I don't want to want dovecot to return time, can I close it?

2 1

`Spam' folder creation for multiple users
by Marek Kozlowski 17 Mar '19

17 Mar '19

:-) I've just added pigeonhole and a simple sieve script: ------------------------------------------------- require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spam"; } ------------------------------------------------- If a user has this folder (`Spam') it works fine. If they haven't it results in an error. 1. Can I modify the script to create this folder if the need arise? 2. If not - what's the most recommended way of adding this folder for all users (~1000)? Thanks! Best regards, Marek

3 2

MikroTik Users Contact List
by Kathleen Brown 17 Mar '19

17 Mar '19

Hello, Hope you're having a great day! I just wanted to know if you're looking to acquire MikroTik Users Contact List for your marketing efforts? Information Field: Names, Title, Email, Phone, Company Name, Company URL, Company physical address, SIC Code, Industry and Company Size (Revenue and Employee). Kindly review and let me know of your target interest so that I can get back to you with the exact counts and sample file. Do let me know if you have any questions for me. Regards, Kathleen Brown Database Executive If you do not wish to receive these emails. Please respond Exit.

2 1

lda: Unknown mail storage driver maildir
by Rob De Langhe 17 Mar '19

17 Mar '19

hi all, I have a successful (self-compiled from source code) Dovecot v2.2.16 setup active on my Solaris-10 server, with mails stored in user's $HOME/Maildir The mails are fetched from the ISP with "fetchmail", using a "cron" job fetchmail -f $HOME/etc/pop3.myisp where the file "$HOME/etc/pop3.myisp" contains set logfile fetchmail.log poll pop.myisp.be with proto POP3 user myIspmailLogin there with password myIspPwd is rob here nokeep mda "/programs-3.2/amd64/64/libexec/dovecot/deliver" Now I want to get it also running on a Debian server, with the same Dovecot version, and exactly the same config files, but here I get the following messages in "/var/log/mail.log" when launching a "fetchmail" attempt : Mar 17 14:36:20 apps_b dovecot: lda(rob): Debug: Effective uid=1000, gid=1000, home=/home/rob Mar 17 14:36:20 apps_b dovecot: lda(rob): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Mar 17 14:36:20 apps_b dovecot: lda(rob): Error: User initialization failed: Namespace '': Unknown mail storage driver maildir Mar 17 14:36:20 apps_b dovecot: lda(rob): Fatal: Invalid user settings. Refer to server log for more information. So it seems to be complaining about "maildir" storage driver ?! My config is: # /programs/3.4/x86_64/64/sbin/dovecot -n -c /usr/local/dovecot/dovecot.conf # 2.2.16: /usr/local/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.4 disable_plaintext_auth = no first_valid_gid = 1000 first_valid_uid = 1000 last_valid_gid = 1500 last_valid_uid = 2000 mail_debug = yes mail_location = maildir:~/Maildir namespace inbox { 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 = * driver = pam } postmaster_address = rob(a)mydomain.be ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd }

2 1

LMTP Proxy failure using master login via destuser field
by Dirk 17 Mar '19

17 Mar '19

Hi list, I set up dovecot as IMAP proxy using a master user to login into the backend and it works beautifully. 👍🏻 Next I set out to do LMTP proxying and I struggled (initially). I got the log message: Mar 17 11:23:44 mail postfix/lmtp[2665]: 99A3F219C8: to=<johnny(a)doe.com>, relay=10.15.1.2[10.15.1.2]:24, delay=5.1, delays=4.9/0.05/0.01/0.07, dsn=5.1.1, status=bounced (host 10.15.1.2[10.15.1.2] said: 550 5.1.1 <"johnny(a)doe.com*director"@mail.server.com> User doesn't exist: "johnny(a)doe.com*director"@mail.server.com (in reply to RCPT TO command)) My director's passdb setting looked like this: passdb { driver = sql args = /etc/dovecot/sql/my-passdb.conf result_success = continue-ok result_failure = return-fail result_internalfail = return-fail } # Add director master user credentials if above succeeded passdb { driver = static args = proxy=y starttls=any-cert \ destuser=%u*director(a)example.com \ pass=correcthorsebatterystaple \ nopassword=y skip = unauthenticated } In the end I found that setting the `master` field instead of `destuser` solves the issue. It looks like LMTP does not know how to handle the master user separator although set. I this known/wanted behavior? Maybe this is something to mention on the wiki page, it took a while to figure this out... Kind regards, Dirk Mit freundlichen Grüßen Dirk Weise DevOps Engineer -- bitloft GmbH | Schulstraße 2 | D-42551 Velbert www.bitloft.de | weise(a)bitloft.de Telefon: +49 2051 40514-32 Geschäftsführer: Robin Clemens, Franz-Josef Wieneke Amtsgericht Wuppertal HRB 17297 | USt-IDNr. DE121540053

1 0

testing dovecot LMTP with postfix/spamassassin
by Marek Kozlowski 17 Mar '19

17 Mar '19

:-) My postfix configuration is quite complex with a lot of special cases and rules. However I'd like to make an anti-spam configuration as simple and lightweight as possible (KISS). /etc/postfix/master.cf ------------------------------------------------------------------------ smtp inet n - n - - smtpd -o content_filter=spamassassin spamassassin unix - n n - - pipe user=nobody argv=/usr/bin/vendor_perl/spamc -e /usr/sbin/sendmail -oi -f ${sender} ${recipient} ------------------------------------------------------------------------ then the simplest sieve rule I can think of: ------------------------------------------------------------------------ require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spam"; } ------------------------------------------------------------------------ I'd like to make this rule active for only local deliveries via dovecot LMTP with sieve plugin and setting postfix `mailbox_transport' to dovecot LMTP. I believe it is so simple it should work (am I wrong?). But... It would be more convenient to do some tests before applying changes to a production environment config. The problem is: I have no separate testing environment with my strange configuration I'm able to test a spamassassin score for an e-mail manually. How about dovecot LMTP? Can I test local mail delivery by dovecot LMTP manually? I mean: to simulate "I'm the Postfix" and produce for some testing e-mail the same effect as postfix granting it via `local_transport' to dovecot? Best regards, Marek

4 6