December 2019 - dovecot

spamsieve question
by Gerben Wierda 31 Dec '19

31 Dec '19

My new dovecot covers spam/ham training through the standard Spam_train and Notspam_train mailboxes. When a message is copied (I’m using macOS/iOS standard Apple clients) it triggers the spam/ham learning by rspamd. So far so good. When I move a message to Spam_train I’d like it to be removed immediately after learning. When I move a message to Notspam_train, I’d like it to move back where it came from after having been piped The first is I think doable, but how? Is the second doable? Gerben Wierda Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

1 0

Problem with big number of pop3-login [1 pre-login]
by Григорий Семенов 30 Dec '19

30 Dec '19

Dear all, I have recently migrated from my old Debian 8 (jessie) system to a new VM with fresh Debian 10 (buster) installation. Previous dovecot version was 2.2.13 and now I have 2.3.4.1. Dovecot was setup from Debian packages. Mostly, it is working, but one problem is just frustrating me. The number of some pop3-login processes are getting higher and higher until they reach my login_max_processes_count option which is equal 1000. From ps aux it looks like this: dovecot 55067 0.0 0.0 8192 6340 ? S 00:09 0:00 dovecot/pop3-login [1 pre-login] dovecot 55344 0.0 0.0 8192 6388 ? S 00:35 0:00 dovecot/pop3-login [1 pre-login] dovecot 55351 0.0 0.0 8192 6268 ? S 00:35 0:00 dovecot/pop3-login [1 pre-login] dovecot 55354 0.0 0.0 8192 6388 ? S 00:35 0:00 dovecot/pop3-login [1 pre-login] dovecot 55594 0.0 0.0 8192 6280 ? S 00:36 0:00 dovecot/pop3-login [1 pre-login] dovecot 56822 0.0 0.0 8192 6300 ? S 00:36 0:00 dovecot/pop3-login [1 pre-login] dovecot 56996 0.0 0.0 8192 6268 ? S 00:36 0:00 dovecot/pop3-login [1 pre-login] … Once it reaches the login_max_processes_count value my users start to complain to no new mail is arriving. Restart resolves the problem just for some time, until it will come to a limit next time (sometimes it take 1 day, sometimes 1 hour). In my old system I had nothing like that, but I guess it could be done something wrong during migration. I don’t know if it is significant but instead of real users I deal with only one third-party application which utilizeses 5 simultaneous tcp connections to check mailboxes via SSL\TLS. My dovecot is not public, and there is nothing else besides these 5 connections. Currently, in a config I have this: service pop3-login { process_min_avail = 4 process_limit = 4 client_limit = 100 service_count = 100 Please friends give me a way how to handle the situation. Might it be a bug? ========= Regards, Greg Semenov

1 0

Re: Issue running Dovecot in Docker Container
by Naveen Reddy 30 Dec '19

30 Dec '19

I'm not using internal logging. I'm running the docker with the logging to the host. I have used the same options you have specified. The problem is that the below processes are not running inside docker container whereas the standalone dovecot is running these processes(meaning without container) dovecot-Dovecot/auth dovecot-Dovecot/ssl-params dovecot-Director/lmtp dovecot-Director/ssl-params dovecot-Director/imap-login director Thanks & Regards, Naveen On Mon, Dec 30, 2019 at 3:16 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > If you are running your container as root. You will not have the issues > I encountered. Dovecot is dropping to the 'dovecot' and 'dovenull'(?) > when needed, this is fine. > > PS. I would not recommend using internal logging, use something like > this to log to the host or remote syslog. > docker run -v /dev/log:/dev/log -it dovecot-proxy > > > -----Original Message----- > Subject: Re: Issue running Dovecot in Docker Container > > Hi Marc, > > I can see the processes are running as a root in container environment. > Do you think that still have issues ? > Here is the processes running inside container: > > bash-4.2# ps -ef > UID PID PPID C STIME TTY TIME CMD > root 1 0 0 Dec27 ? 00:00:00 /bin/bash /bootstrap.sh > root 7 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F -c > /etc/dovecot/director.conf > root 8 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F > root 9 1 0 Dec27 ? 00:00:00 sleep 36000d > dovecot 10 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/anvil > dovecot 14 7 0 Dec27 ? 00:00:00 dovecot-Director/anvil > root 267 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/log > root 269 8 0 Dec27 ? 00:00:08 dovecot-Dovecot/config > root 281 7 0 Dec27 ? 00:00:00 dovecot-Director/log > root 283 7 0 Dec27 ? 00:00:00 dovecot-Director/config > > > > > Thanks & Regards, > Naveen > > > > On Mon, Dec 30, 2019 at 2:56 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> > wrote: > > > > I have noticed several issues with dovecot, trying to run it > without > root. Which is preferable in any container environment. Maybe you > would > like me to document these somewhere? So at some point they can be > applied. > > > -----Original Message----- > From: Naveen Reddy [mailto:naveenreddy99@gmail.com] > Sent: 30 December 2019 09:02 > To: Aki Tuomi > Cc: dovecot(a)dovecot.org > Subject: Re: Issue running Dovecot in Docker Container > > Hi, I can see those values correctly with the doveconf -nc > command. > Here > is the part of output: > > bash-4.2# doveconf -nc /etc/dovecot/director.conf # 2.2.36 > (1f10bfa63): > /etc/dovecot/director.conf # OS: Linux > 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # > Hostname: > 69b492645b56 auth_debug = yes auth_default_realm = > xxxxxxxxxxxxxxxx > > auth_verbose = yes base_dir = /var/run/dovecot_director > debug_log_path = > $log_path director_mail_servers = xxxxxxxxxxxxxxxxxx > director_servers = > xxxxxxxxxxxxxxxxxxxx disable_plaintext_auth = no first_valid_uid = > 1000 > hostname = xxxxxxxxxxxxxxxxxxxx info_log_path = $log_path > instance_name > = Director lmtp_proxy = yes log_path = /dovecot.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l > mpid=%e %c > home=%h > > Thanks & Regards, > Naveen > > > > On Fri, Dec 27, 2019 at 10:08 PM Aki Tuomi > <aki.tuomi(a)open-xchange.com> > wrote: > > > > Can you check with `doveconf -nc /path/to/director.conf` > that the > values are actually set correctly? > > Aki > > On 27/12/2019 15:34 Naveen Reddy > <naveenreddy99(a)gmail.com> > wrote: > > > > The conf.d files are not included. I have added > !include > conf.d/*.conf to director.conf and reloaded the dovecot and > director > services. > > conf.d/10-logging also has the following lines: > > log_path = /dovecot.log > info_log_path = $log_path > debug_log_path = $log_path > > > The /dovecot.log file still shows empty. Nothing > is being > logged to that file. > > > Thanks & Regards, > Naveen > > > > On Thu, Dec 26, 2019 at 10:52 PM Aki Tuomi < > aki.tuomi(a)open-xchange.com> wrote: > > > > Do you have !include or !try_include in > director.conf? > The conf.d files are not included otherwise. > > Aki > > On 26/12/2019 11:27 Naveen Reddy < > naveenreddy99(a)gmail.com> wrote: > > > I have tried these in the > 10-logging.conf but no > luck. There is nothing logged to the file. > > bash-4.2# ps -ef > UID PID PPID C STIME TTY > > TIME CMD > root 1 0 0 Dec23 ? > > 00:00:00 > /bin/bash /bootstrap.sh > root 8 1 0 Dec23 ? > > 00:00:00 > sleep 36000d > root 15681 0 0 08:51 > pts/1 > 00:00:00 bash > root 16340 0 0 09:19 ? > > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/director.conf > dovecot 16341 16340 0 09:19 ? > > 00:00:00 > dovecot-Director/anvil > root 16342 16340 0 09:19 ? > > 00:00:00 > dovecot-Director/log > root 16344 16340 0 09:19 ? > > 00:00:00 > dovecot-Director/config > root 16390 0 0 09:22 ? > > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf > dovecot 16391 16390 0 09:22 ? > > 00:00:00 > dovecot-Dovecot/anvil > root 16392 16390 0 09:22 ? > > 00:00:00 > dovecot-Dovecot/log > root 16394 16390 0 09:22 ? > > 00:00:00 > dovecot-Dovecot/config > root 16406 15681 0 09:22 > pts/1 > 00:00:00 ps > -ef > > > The below processes are not > starting as well. > > dovecot-Dovecot/auth > dovecot-Dovecot/ssl-params > dovecot-Director/lmtp > dovecot-Director/ssl-params > dovecot-Director/imap-login > director > > Thanks & Regards, > Naveen > > > > On Tue, Dec 24, 2019 at 10:54 PM > Aki Tuomi < > aki.tuomi(a)open-xchange.com> wrote: > > > > > > On 24/12/2019 > 12:33 > Naveen Reddy < > naveenreddy99(a)gmail.com> wrote: > > > Hello, > > We need help with > an issue that we are > running into when we are trying to run Dovecot in Docker > container. > > Also how do we > enable debugging for > dovecot. Logs doesn't show any info about the issue. > > Below processes > are > not running when a > Director service is started: > > > dovecot-Dovecot/auth > > dovecot-Dovecot/ssl-params > > dovecot-Director/lmtp > > dovecot-Director/ssl-params > > dovecot-Director/imap-login director > > Here is the > version > that I'm running and > including the dovecot -n output below: > > bash-4.2# dovecot > --version > 2.2.36 > > > bash-4.2# dovecot > -n > # 2.2.36 (xxxxx): > /etc/dovecot/dovecot.conf > # OS: Linux > 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) > # Hostname: XXXXXXX > auth_debug = yes > auth_default_realm > = xxxxxxxxxxxx > auth_verbose = yes > > disable_plaintext_auth = no > dotlock_use_excl = > no > hostname = > xxxxxxxxxxxxxxxx > instance_name = > Dovecot > > login_log_format_elements = user=<%u> > method=%m rip=%r lip=%l mpid=%e %c home=% domain=%d > mail_debug = yes > mail_fsync = always > mail_gid = imapd > mail_home = > /xxxxxxxxxxx/%d/%n > mail_location = > dbox:~/ > mail_uid = imapd > mmap_disable = yes > passdb { > args = > /etc/dovecot/lookups/ldap-pass.conf > driver = ldap > } > passdb { > args = > /etc/dovecot/lookups/xxxx.conf > driver = ldap > } > plugin { > stats_refresh = > 30 secs > stats_track_cmds > = yes > } > protocols = imap > lmtp > service auth { > client_limit = > 4096 > unix_listener > auth-userdb { > mode = 0777 > } > } > service imap-login > { > chroot = login > client_limit = 0 > > drop_priv_before_exec = no > executable = > imap-login > extra_groups = > group = > idle_kill = 0 > inet_listener > imap { > address = > port = 1144 > ssl = no > } > inet_listener > imaps { > address = > port = 994 > ssl = yes > } > privileged_group > = > process_limit = 0 > > process_min_avail > = 0 > protocol = imap > service_count = > 50 > type = login > user = > $default_login_user > vsz_limit = > 18446744073709551615 B > } > service imap { > service_count = > 50 > } > service lmtp { > executable = > lmtp > -L > inet_listener > lmtp { > address = > port = 10025 > } > } > service stats { > fifo_listener > stats-mail { > mode = 0600 > user = imapd > } > } > ssl_cert = > </xxxxxxx/cert/dovecot.pem > ssl_cipher_list = > XXXXXX > ssl_key = # > hidden, use -P to show it > ssl_protocols = > XXXXX > userdb { > args = > /etc/dovecot/lookups/ldap-user.conf > driver = ldap > } > userdb { > args = > /etc/dovecot/lookups/xxxxxxx.conf > driver = ldap > } > > > Thanks & Regards, > Naveen > > > > Try setting > > log_path=/dovecot.log > info_log_path=$log_path > debug_log_path=$log_path > --- > Aki Tuomi > > > --- > Aki Tuomi > > > --- > Aki Tuomi > > > > > >

3 4

Re: Issue running Dovecot in Docker Container
by Naveen Reddy 30 Dec '19

30 Dec '19

Hi Marc, I can see the processes are running as a root in container environment. Do you think that still have issues ? Here is the processes running inside container: bash-4.2# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 Dec27 ? 00:00:00 /bin/bash /bootstrap.sh root 7 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F -c /etc/dovecot/director.conf root 8 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F root 9 1 0 Dec27 ? 00:00:00 sleep 36000d dovecot 10 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/anvil dovecot 14 7 0 Dec27 ? 00:00:00 dovecot-Director/anvil root 267 8 0 Dec27 ? 00:00:00 dovecot-Dovecot/log root 269 8 0 Dec27 ? 00:00:08 dovecot-Dovecot/config root 281 7 0 Dec27 ? 00:00:00 dovecot-Director/log root 283 7 0 Dec27 ? 00:00:00 dovecot-Director/config Thanks & Regards, Naveen On Mon, Dec 30, 2019 at 2:56 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > I have noticed several issues with dovecot, trying to run it without > root. Which is preferable in any container environment. Maybe you would > like me to document these somewhere? So at some point they can be > applied. > > > -----Original Message----- > From: Naveen Reddy [mailto:naveenreddy99@gmail.com] > Sent: 30 December 2019 09:02 > To: Aki Tuomi > Cc: dovecot(a)dovecot.org > Subject: Re: Issue running Dovecot in Docker Container > > Hi, I can see those values correctly with the doveconf -nc command. Here > is the part of output: > > bash-4.2# doveconf -nc /etc/dovecot/director.conf # 2.2.36 (1f10bfa63): > /etc/dovecot/director.conf # OS: Linux 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # Hostname: > 69b492645b56 auth_debug = yes auth_default_realm = xxxxxxxxxxxxxxxx > auth_verbose = yes base_dir = /var/run/dovecot_director debug_log_path = > $log_path director_mail_servers = xxxxxxxxxxxxxxxxxx director_servers = > xxxxxxxxxxxxxxxxxxxx disable_plaintext_auth = no first_valid_uid = 1000 > hostname = xxxxxxxxxxxxxxxxxxxx info_log_path = $log_path instance_name > = Director lmtp_proxy = yes log_path = /dovecot.log > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c > home=%h > > Thanks & Regards, > Naveen > > > > On Fri, Dec 27, 2019 at 10:08 PM Aki Tuomi <aki.tuomi(a)open-xchange.com> > wrote: > > > > Can you check with `doveconf -nc /path/to/director.conf` that the > values are actually set correctly? > > Aki > > On 27/12/2019 15:34 Naveen Reddy <naveenreddy99(a)gmail.com> > > wrote: > > > > The conf.d files are not included. I have added !include > conf.d/*.conf to director.conf and reloaded the dovecot and director > services. > > conf.d/10-logging also has the following lines: > > log_path = /dovecot.log > info_log_path = $log_path > debug_log_path = $log_path > > > The /dovecot.log file still shows empty. Nothing is being > logged to that file. > > > Thanks & Regards, > Naveen > > > > On Thu, Dec 26, 2019 at 10:52 PM Aki Tuomi < > aki.tuomi(a)open-xchange.com> wrote: > > > > Do you have !include or !try_include in > director.conf? > The conf.d files are not included otherwise. > > Aki > > On 26/12/2019 11:27 Naveen Reddy < > naveenreddy99(a)gmail.com> wrote: > > > I have tried these in the 10-logging.conf > but no > luck. There is nothing logged to the file. > > bash-4.2# ps -ef > UID PID PPID C STIME TTY > TIME CMD > root 1 0 0 Dec23 ? > 00:00:00 > /bin/bash /bootstrap.sh > root 8 1 0 Dec23 ? > 00:00:00 > sleep 36000d > root 15681 0 0 08:51 pts/1 > 00:00:00 bash > root 16340 0 0 09:19 ? > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/director.conf > dovecot 16341 16340 0 09:19 ? > 00:00:00 > dovecot-Director/anvil > root 16342 16340 0 09:19 ? > 00:00:00 > dovecot-Director/log > root 16344 16340 0 09:19 ? > 00:00:00 > dovecot-Director/config > root 16390 0 0 09:22 ? > 00:00:00 > /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf > dovecot 16391 16390 0 09:22 ? > 00:00:00 > dovecot-Dovecot/anvil > root 16392 16390 0 09:22 ? > 00:00:00 > dovecot-Dovecot/log > root 16394 16390 0 09:22 ? > 00:00:00 > dovecot-Dovecot/config > root 16406 15681 0 09:22 pts/1 > 00:00:00 ps > -ef > > > The below processes are not starting as > well. > > dovecot-Dovecot/auth > dovecot-Dovecot/ssl-params > dovecot-Director/lmtp > dovecot-Director/ssl-params > dovecot-Director/imap-login director > > Thanks & Regards, > Naveen > > > > On Tue, Dec 24, 2019 at 10:54 PM Aki Tuomi > < > aki.tuomi(a)open-xchange.com> wrote: > > > > > > On 24/12/2019 12:33 Naveen > Reddy < > naveenreddy99(a)gmail.com> wrote: > > > Hello, > > We need help with an issue > that we are > running into when we are trying to run Dovecot in Docker container. > Also how do we enable > debugging for > dovecot. Logs doesn't show any info about the issue. > > Below processes are not > running when a > Director service is started: > > dovecot-Dovecot/auth > dovecot-Dovecot/ssl-params > dovecot-Director/lmtp > dovecot-Director/ssl-params > > dovecot-Director/imap-login director > > Here is the version that > I'm running and > including the dovecot -n output below: > > bash-4.2# dovecot --version > 2.2.36 > > > bash-4.2# dovecot -n > # 2.2.36 (xxxxx): > /etc/dovecot/dovecot.conf > # OS: Linux > 4.1.12-112.14.11.el7uek.x86_64 > x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) > # Hostname: XXXXXXX > auth_debug = yes > auth_default_realm = > xxxxxxxxxxxx > auth_verbose = yes > disable_plaintext_auth = no > dotlock_use_excl = no > hostname = xxxxxxxxxxxxxxxx > instance_name = Dovecot > login_log_format_elements > = user=<%u> > method=%m rip=%r lip=%l mpid=%e %c home=% domain=%d > mail_debug = yes > mail_fsync = always > mail_gid = imapd > mail_home = > /xxxxxxxxxxx/%d/%n > mail_location = dbox:~/ > mail_uid = imapd > mmap_disable = yes > passdb { > args = > /etc/dovecot/lookups/ldap-pass.conf > driver = ldap > } > passdb { > args = > /etc/dovecot/lookups/xxxx.conf > driver = ldap > } > plugin { > stats_refresh = 30 secs > stats_track_cmds = yes > } > protocols = imap lmtp > service auth { > client_limit = 4096 > unix_listener > auth-userdb { > mode = 0777 > } > } > service imap-login { > chroot = login > client_limit = 0 > drop_priv_before_exec = > no > executable = imap-login > extra_groups = > group = > idle_kill = 0 > inet_listener imap { > address = > port = 1144 > ssl = no > } > inet_listener imaps { > address = > port = 994 > ssl = yes > } > privileged_group = > process_limit = 0 > process_min_avail = 0 > protocol = imap > service_count = 50 > type = login > user = > $default_login_user > vsz_limit = > 18446744073709551615 B > } > service imap { > service_count = 50 > } > service lmtp { > executable = lmtp -L > inet_listener lmtp { > address = > port = 10025 > } > } > service stats { > fifo_listener stats-mail > { > mode = 0600 > user = imapd > } > } > ssl_cert = > </xxxxxxx/cert/dovecot.pem > ssl_cipher_list = XXXXXX > ssl_key = # hidden, use > -P to show it > ssl_protocols = XXXXX > userdb { > args = > /etc/dovecot/lookups/ldap-user.conf > driver = ldap > } > userdb { > args = > /etc/dovecot/lookups/xxxxxxx.conf > driver = ldap > } > > > Thanks & Regards, > Naveen > > > > Try setting > > log_path=/dovecot.log > info_log_path=$log_path > debug_log_path=$log_path > --- > Aki Tuomi > > > --- > Aki Tuomi > > > --- > Aki Tuomi > > >

2 1

Issue running Dovecot in Docker Container
by Naveen Reddy 30 Dec '19

30 Dec '19

Hello, We need help with an issue that we are running into when we are trying to run Dovecot in Docker container. Also how do we enable debugging for dovecot. Logs doesn't show any info about the issue. Below processes are not running when a Director service is started: dovecot-Dovecot/auth dovecot-Dovecot/ssl-params dovecot-Director/lmtp dovecot-Director/ssl-params dovecot-Director/imap-login director Here is the version that I'm running and including the dovecot -n output below: bash-4.2# dovecot --version 2.2.36 bash-4.2# dovecot -n # 2.2.36 (xxxxx): /etc/dovecot/dovecot.conf # OS: Linux 4.1.12-112.14.11.el7uek.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # Hostname: XXXXXXX auth_debug = yes auth_default_realm = xxxxxxxxxxxx auth_verbose = yes disable_plaintext_auth = no dotlock_use_excl = no hostname = xxxxxxxxxxxxxxxx instance_name = Dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c home=% domain=%d mail_debug = yes mail_fsync = always mail_gid = imapd mail_home = /xxxxxxxxxxx/%d/%n mail_location = dbox:~/ mail_uid = imapd mmap_disable = yes passdb { args = /etc/dovecot/lookups/ldap-pass.conf driver = ldap } passdb { args = /etc/dovecot/lookups/xxxx.conf driver = ldap } plugin { stats_refresh = 30 secs stats_track_cmds = yes } protocols = imap lmtp service auth { client_limit = 4096 unix_listener auth-userdb { mode = 0777 } } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 1144 ssl = no } inet_listener imaps { address = port = 994 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 50 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap { service_count = 50 } service lmtp { executable = lmtp -L inet_listener lmtp { address = port = 10025 } } service stats { fifo_listener stats-mail { mode = 0600 user = imapd } } ssl_cert = </xxxxxxx/cert/dovecot.pem ssl_cipher_list = XXXXXX ssl_key = # hidden, use -P to show it ssl_protocols = XXXXX userdb { args = /etc/dovecot/lookups/ldap-user.conf driver = ldap } userdb { args = /etc/dovecot/lookups/xxxxxxx.conf driver = ldap } Thanks & Regards, Naveen

3 7

Dovecot Postfix MySQL Authentication Issues
by jason hirsh 29 Dec '19

29 Dec '19

I aim using mysql 5.7.28 Postfix 3.4,8 Dovecot 2.3.9.2 It began a whole and I was using the Purple Hat Organiation installation guide which was loaded with minor errors Now dead in water

1 0

Dovecot Postfix MySQL Authentication Issues
by jason hirsh 29 Dec '19

29 Dec '19

I am I a situation where I have to wipe my remote server and reinstall, Its been a while since I built a server and I am not as sharp as I use to be I am running FreeBSD 12.1. well at least the server is... I am getting constant authentication errors like Dec 28 22:10:18 triggerfish dovecot[21809]: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=<jason(a)example.com>, method=PLAIN, rip=73.150.178.106, lip=x.x.x.x, TLS, session=<QFSvEM+aA8lJlrJq> Dec 28 22:10:19 triggerfish dovecot[21809]: imap-login: Aborted login (client didn't finish SASL auth, waited 4 secs): user=<>, method=LOGIN, rip=73.150.178.106, lip=x.x.x.x, TLS, session=<FNjXEM+aBMlJlrJq> Dec 28 22:10:19 triggerfish dovecot[21809]: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=73.150.178.106, lip=x,x,x,x, TLS: Connection closed, session=<pNccEc+aBslJlrJq> Dec 28 22:10:24 triggerfish dovecot[21809]: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=<jason(a)example.com>, method=LOGIN, rip=73.150.178.106, lip=x,x,x,x, TLS, session=<hukLEc+aBclJlrJq> results of postconf -n are broken_sasl_auth_clients = yes command_directory = /usr/local/sbin compatibility_level = 2 daemon_directory = /usr/local/libexec/postfix data_directory = /var/db/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 dovecot_destination_recipient_limit = 1 html_directory = /usr/local/share/doc/postfix inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/local/bin/mailq manpage_directory = /usr/local/man message_size_limit = 25600000 meta_directory = /usr/local/libexec/postfix mydestination = localhost mydomain = example.com myhostname = mail.example.com mynetworks_style = host newaliases_path = /usr/local/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/local/share/doc/postfix relay_recipient_maps = mysql:/usr/local/etc/postfix/mysql-virtual-mailbox-maps.cf sample_directory = /usr/local/etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = maildrop shlib_directory = /usr/local/lib/postfix smtp_tls_note_starttls_offer = yes smtp_use_tls = yes smtpd_delay_reject = yes smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_unknown_hostname, reject_non_fqdn_hostname, reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, permit smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unauth_destination, reject_unauth_pipelining, reject_rbl_client bl.spamcop.net, reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client zen.spamhaus.org, reject_rbl_client dnsbl.sorbs.net, reject_rbl_client rhsbl.sorbs.net, reject_rbl_client db.wpbl.info, reject_rbl_client cbl.abuseat.org, reject_rbl_client proxies.blackholes.wirehub.net, reject_rbl_client query.bondedsender.org permit smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_sender_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_sender, reject_unknown_sender_domain, reject_unlisted_sender, permit smtpd_tls_auth_only = yes smtpd_tls_cert_file = /usr/local/etc/ssl/more/server.crt smtpd_tls_key_file = /usr/local/etc/ssl/more/server.key smtpd_tls_loglevel = 0 smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes soft_bounce = no tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/usr/local/etc/postfix/mysql-virtual-alias-maps.cf virtual_mailbox_domains = mysql:/usr/local/etc/postfix/mysql-virtual-domains-maps.cf virtual_mailbox_limit = 51200000 virtual_mailbox_maps = mysql:/usr/local/etc/postfix/mysql-virtual-mailbox-maps.cf virtual_transport = lmtp:unix:private/dovecot-lmtp Not sure if I need to post main.cf. I have been beating my head against the screen for a week and thought I'd try here. Probably some stupid typo or stupid action on my part. Feel free to slap me around

2 1

Using "doveadm pw" as unpriviledged user
by Ralf Jung 29 Dec '19

29 Dec '19

Hi all, Some time ago, I wrote a small CGI script to let users change their IMAP password. The script runs as www-data user and uses "doveadm pw" to check if a password hash matches a password. Unfortunately, this means that I have to make large parts of my dovecot config world-readable, as otherwise I get errors like this: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-auth.conf line 123: Couldn't open include file /etc/dovecot/conf.d/auth-sql.conf.ext: Permission denied I understand doveadm also does plenty of things that interact with the running dovecot instance and thus need access to the config, but for generating hashes or comparing hashes with passwords, it should not be necessary to read the dovecot config. This shouldn't require a properly setup dovecot on this machine at all, in fact. I'd prefer to make the config not world-readable, and indeed the Debian packaging sometimes makes those files not-world-readable on upgrades, breaking my setup. Is there any way to call "doveadm pw" as a users that cannot read the dovecot config on the current machine? This happens with the following versions of the dovecot debian package: 1:2.3.4.1-5+deb10u1~bpo9+1, 1:2.3.4.1-5+deb10u1 Thanks! Ralf PS: Please keep me in Cc, as I am not subscribed to the list.

1 0

Packages missing from repo
by Jon Geerars 29 Dec '19

29 Dec '19

Hi, Since a couple of weeks the Dovecot packages for Debian Jessie and Ubuntu Trusty have disappeared from the repo. According to https://repo.dovecot.org/ they should be in https://repo.dovecot.org/ce-2.3-latest/debian/jessie and https://repo.dovecot.org/ce-2.3-latest/ubuntu/trusty, but that leads to a 404. Where can I find them? Jon

2 3

Dovecot proxy: authentication best practices
by William Edwards 28 Dec '19

28 Dec '19

Hi! I have a few questions regarding Dovecot proxy: 1. 1.1 If I understand correctly, setting 'nopassword' in the proxy passdb file, authentication is completely up to the destination host. Setting 'nopassword' in no way means the proxy becomes an open relay. Is this correct? 1.2 Are there any security implications when using 'nopassword' on the proxy? 2. 2.1 I would like to avoid having to store all users in a passdb file on the proxy. I would much rather specify a domain for which Dovecot proxy will route all users to a specific host. Is there a way to let Dovecot proxy route to a destination host based on domain, so individual users don't have to be specified in the proxy passdb? 2.2 Is it correct that userdb does not have any effect on proxying and it can be left out of the config? Source: https://dovecot.org/pipermail/dovecot/2013-October/093138.html (point 2) Met vriendelijke groeten, William Edwards T. 040 - 711 44 96 E. wedwards(a)cyberfusion.nl

2 2