- dovecot - dovecot.org

Re: Question about password field in passwd-file
by J Doe 08 Jul '18

08 Jul '18

> On Jul 7, 2018, at 2:12 AM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > you can add nopassword attribute to the end. See https://wiki.dovecot.org/PasswordDatabase/ExtraFields > > > --- > Aki Tuomi > Dovecot oy Hi Aki, Thank you for your reply. I have two questions regarding this: 1. Is the “nopassword” attribute the same as specifying a null password field by itself ? The documentation at [1] seems to suggest that having a null password AND specifying “nopassword” will allow someone to authenticate with _no_ password: “nopasword: if you want to allow all passwords, use an empty password and this field.” Farther down, the page seems to indicate that the “nologin” attribute is what I am looking for: “nologin: User isn’t actually allowed to log in even if the password matches . . .” Or possibly “noauthenticate”: “noauthenticate: Do not perform any authentication . . ." 2. Is “nologin” functionally equivalent to specifying no password in the password field ? I am assuming that setting a null password (even without “nologin”), prevents login with ANY or NO password as a blank field would default to a {CRYPT} scheme and a call to crypt() cannot return a null string. As background to why I want to do this, I have a server with a basic Dovecot setup that provides SMTP SASL AUTH, IMAP and LMTP for Postfix. For the passdb and userdb, I use the same passwd-style file: /etc/dovecot/dovecot.conf userdb { driver = passwd-file args = /etc/dovecot/passwd } passdb { driver = passwd-file args = /etc/dovecot/passwd } I use usernames for SMTP SASL AUTH and IMAP that differ from either: user(a)example.com or user. So for one user, for example, I have: /etc/dovecot/passwd # SMTP SASL AUTH and IMAP user accounts and passwords user_account_1:{PLAIN}password: . . . # LMTP username/e-mail address user(a)example.com:: . . . :/var/mail/vhosts/example.com/user_account_1 So in the LMTP entry I specify no password between the colons to prevent someone trying to logon via IMAP using the LMTP username/e-mail address. Is this correct and: is there a better way to do this ? Thanks, - J Sources: [1] https://wiki.dovecot.org/PasswordDatabase/ExtraFields

1 0

Get rid of the "dbox-Mails"-folder
by Hativ 07 Jul '18

07 Jul '18

Hey to all, is it possible to get rid of the "dbox-Mails"-folder when using sdbox? Currently my folder structure looks like this (I hope the output from tree would be formatted well): /srv/mail/ └── example.com └── user ├── dovecot-acl-list ├── dovecot-attributes ├── dovecot.list.index.log ├── dovecot.mailbox.log ├── dovecot-uidvalidity ├── dovecot-uidvalidity.5b3f746f ├── mailboxes │ ├── Drafts │ │ └── dbox-Mails │ │ └── dovecot.index.log │ ├── INBOX │ │ └── dbox-Mails │ │ ├── dovecot.index.cache │ │ ├── dovecot.index.log │ │ └── u.1 │ ├── Junk │ │ └── dbox-Mails │ │ └── dovecot.index.log │ ├── Sent │ │ └── dbox-Mails │ │ └── dovecot.index.log │ └── Trash │ └── dbox-Mails │ └── dovecot.index.log └── subscriptions I would like to let it look like this: /srv/mail/ └── example.com └── user ├── dovecot-acl-list ├── dovecot-attributes ├── dovecot.list.index.log ├── dovecot.mailbox.log ├── dovecot-uidvalidity ├── dovecot-uidvalidity.5b3f746f ├── mailboxes │ ├── Drafts │ │ └── dovecot.index.log │ ├── INBOX │ │ └── dovecot.index.cache │ │ └── dovecot.index.log │ │ └── u.1 │ ├── Junk │ │ └──dovecot.index.log │ ├── Sent │ │ └── dovecot.index.log │ └── Trash │ └── dovecot.index.log └── subscriptions My path configuration: mail_attribute_dict = file:%h/dovecot-attributes mail_home = /srv/mail/%d/%n/ mail_location = sdbox:~/ I have tried mail_location = sdbox:~/:FULLDIRNAME= and mail_location = sdbox:~/:FULLDIRNAME=/ but it doesn't work. The first doesn't change anything. The second auto-creates the folders after first login like I want, but after next login they are greyed out and no longer accessible. Is it possible to get rid of the "dbox-Mails"-folder? I want this because I don't like to have an unneeded deep folder structure. Or is there a good reason to let the "dbox-Mails" folder in my setup? Greetings, Hativ

2 3

build failure with glibc >= 2.26
by Eray Aslan 07 Jul '18

07 Jul '18

Sun RPC was removed from glibc-2.26 [1] resulting in /bin/sh ../../../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -std=gnu99 -march=native -O2 -pipe -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -module -avoid-version -Wl,-O1 -Wl,--as-needed -o lib10_doveadm_quota_plugin.la -rpath /usr/lib64/dovecot/doveadm doveadm-quota.lo rquota_xdr.c:4:10: fatal error: rpc/rpc.h: No such file or directory #include <rpc/rpc.h> ^~~~~~~~~~~ compilation terminated. make[4]: *** [Makefile:826: rquota_xdr.lo] Error 1 during build. Apparently, rquota code needs some love. This is dovecot-2.3.2 but 2.2 branch should also result in the same error during make. -- Eray [1] https://fedoraproject.org/wiki/Changes/SunRPCRemoval

1 0

Question about password field in passwd-file
by J Doe 07 Jul '18

07 Jul '18

Hello, I have a question regarding the password field of the passwd-file [1]. According to the wiki, the password field assumes a {SCHEME} of CRYPT when the {SCHEME} is not prefixed to this field. So, a passwd-file like: user:password: . . . … is equivalent to: user:{CRYPT}password: . . . Does that mean an example passwd-file with NEITHER {SCHEME} or password, like: user(a)example.com:: . . . (note no scheme or password specified between colons) …means that the user(a)example.com user does not have any valid crypted password and therefore the user(a)example.com user cannot be authenticated ? For example, if I use doveadm to create a null CRYPT password: $ sudo doveadm pw -s CRYPT -p “” -u user(a)example.com … gives the result: {CRYPT}txR1JRq9140Qk … which differs from the example password field having NEITHER {SCHEME} or password, like: user(a)example.com:: . . . … so if I attempt to logon using a null password for user(a)example.com when nothing is specified in the password field for the passwd-file: /etc/dovecot/passwd user(a)example.com:: . . . $ sudo doveadm auth test user(a)example.com password: passdb: user(a)example.com auth failed … it is impossible to logon as user(a)example.com with ANY PASSWORD and/or a NULL password ? Thanks, - J Sources: [1] https://wiki2.dovecot.org/AuthDatabase/PasswdFile

2 1

Re: support for Blowfish $2y$10$
by Graham S. Jarvis 06 Jul '18

06 Jul '18

Hei Aki! # doveadm pw -t '{BLF-CRYPT}$2y$10$UEm8SR/IuX.ZONebRt40XOKTuZ9bXktYWpGDiLw2h7MTPcnvmuIRK' Enter password to verify: {BLF-CRYPT}$2y$10$UEm8SR/IuX.ZONebRt40XOKTuZ9bXktYWpGDiLw2h7MTPcnvmuIRK (verified) - Great, thanks! -Graham- PS: Sorry I just "posted" to your personal address instead of the list. Aki Tuomi wrote on 06/07/18 23:06: > Hi! > > $2y$ is supported in 2.3, and supported in 2.2 if your bcrypt provider > supports it. > > You can use doveadm pw -t '{BLF-CRYPT}$2y$...' to verify this. > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Graham S. Jarvis" <gsjarvis(a)pt.lu> > Date: 07/07/2018 00:03 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: support for Blowfish $2y$10$ > > Hello, > > does dovecot support bcrypt $2y$ version? (BLF-CRYPT - Blowfish crypt) > > > doveadm pw -s BLF-CRYPT > generates a > {BLF-CRYPT}$2a$05$....... > password. > > Does this mean that dovecote will not authenticate against a > $2y$10$....... > password? > > Thanks in advance, > > -Graham-

1 0

support for Blowfish $2y$10$
by Graham S. Jarvis 06 Jul '18

06 Jul '18

Hello, does dovecot support bcrypt $2y$ version? (BLF-CRYPT - Blowfish crypt) doveadm pw -s BLF-CRYPT generates a {BLF-CRYPT}$2a$05$....... password. Does this mean that dovecote will not authenticate against a $2y$10$....... password? Thanks in advance, -Graham-

2 1

Replication fails over SSL
by Vladimir Tiukhtin 06 Jul '18

06 Jul '18

Hi Replication works fine on poor TCP, when I enable SSL it fails Jul 06 17:28:48 mail dovecot[13114]: doveconf: Fatal: execvp(/usr/libexec/dovecot/managesieve) failed: Argument list too long Jul 06 17:28:48 mail dovecot[13114]: config: Error: managesieve-login: dump-capability process returned 89 Jul 06 17:28:48 mail dovecot[13114]: doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 Jul 06 17:28:48 mail dovecot[13114]: doveadm: Error: Couldn't initialize SSL parameters, disabling SSL I have set: service doveadm { inet_listener { address = {{ dovecot_doveadm_listen_address }} port = {{ dovecot_doveadm_listen_port }} ssl = yes } } ssl_client_ca_file = </etc/ssl/certs/ca-bundle.crt plugin { mail_replica = tcps:{{ dovecot_replica }}:{{ dovecot_doveadm_listen_port }} } I am running native dovecot 2.2.10 on Centos 7. File ssl-parameters.dat exists. I have already removed it and regenerated - does not help Thanks for any advice. Vladimir

1 0

Re: user/password Authentication via Joomla database
by Harald Leithner 06 Jul '18

06 Jul '18

Hi, I think there is no reason to be offlist. Your setup should work, only problem could be the freebsd userid. My setup has only one user for all accounts and no "real" users. I only have a vmail user. Maybe a tutorial for dovecot and mysql only would help you ( I don't have a link here, but google has) hope that helps Harald Am 06.07.2018 um 15:18 schrieb Graham S. Jarvis: > MANY thanks Harald, > > it was the SQL that is my problem ;) > > I don't know whether the detail below belongs in the mailing list - so I > thought I'd pm you with this first. > > Two questions: > A) If I read the dovecot documentation right - it is going to need to > say where the mail is - home directory (and Maildir or mbox ?). > > My setup is fairly small/restricted - I want to give the committee > members of a non-profit a way of changing the IMAP/SMTP passwords for > their Thunderbird/Apple Mail clients by using their Joomla login password. > I'm going to use FreeBSD's adduser command to add any new committee > members and this creates a standard directory structure under > /usr/home/<USERNAME> and I'll (manually) make sure that <USERNAME> is > the same as the Joomla User name that they created. The Virtual Users > Map and Aliases files to point the the actual home (Maildir) directories. > Once it's done it won't change very often. > I'm assuming that Dovecot will first do the SQL lookup and only try > /etc/passwd if it fails - so I can adduser with a locked password, so > that the alias map works and Postfix finds the Maildir. > > B) I didn't yet get my mind around Joomla groups and for example how to > give all committee members a way to change the password for their mail > accounts but only some of the members access to the front-end Mailing > list management (ACYMailer). > I think just creating a new group "committee_mail" is good enough and > this will be the <ID OF THE JOOMLA GROUP> in your SQL. > Otherwise I might want to have the SQL check the existence of various > Joomla groups. > > > What do you think? > > -Graham- > > > >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 5 Jul 2018 17:37:44 +0200 >> From: Harald Leithner <leithner(a)itronic.at> >> To: dovecot(a)dovecot.org >> Subject: Re: user/password Authentication via Joomla database >> Message-ID: <180fd3b8-3369-9102-0216-94e41033f379(a)itronic.at> >> Content-Type: text/plain; charset="windows-1252" >> >> Hi, >> >> this shouldn't be to hard. >> >> Your dovecot-sql.conf.ext could look something like this: >> >> --- >> driver = mysql >> connect = host=<host> dbname=<dbname> user=<username> password=<password> >> >> default_pass_scheme = BLF-CRYPT >> password_query = \ >> SELECT \ >> u.username, \ >> u.password, \ >> FROM <JOOMLA_PREFIX>_users u \ >> LEFT JOIN <JOOMLA_PREFIX>_user_usergroup_map g ON u.id = >> g.user_id \ >> WHERE \ >> u.username = '%u' AND u.block = 0 AND g.group_id = <ID OF THE >> JOOMLA GROUP> >> >> user_query = \ >> SELECT \ >> u.username, \ >> u.password, \ >> FROM <JOOMLA_PREFIX>_users u \ >> LEFT JOIN <JOOMLA_PREFIX>_user_usergroup_map g ON u.id = >> g.user_id \ >> WHERE \ >> u.username = '%u' AND u.block = 0 AND g.group_id = <ID OF THE >> JOOMLA GROUP> >> >> iterate_query = SELECT username AS user FROM <JOOMLA_PREFIX>_users u \ >> LEFT JOIN <JOOMLA_PREFIX>_user_usergroup_map g ON u.id = >> g.user_id \ >> WHERE \ >> u.block = 0 AND g.group_id = <ID OF THE JOOMLA GROUP> >> >> --- >> >> But I'm not sure if dovecot supports Blowfish $2y$ Version used by >> Joomla as default. >> >> Also I didn't tested this configuration, so there maybe someflaws in it. >> >> bye >> Harald >> >> >> Am 05.07.2018 um 16:05 schrieb Graham S. Jarvis: >>> Hello, >>> >>> did anyone ever set up Authentication via lookups to a Joomla (mysql) >>> database? >>> >>> What I'd like to do is lookup Joomla users (who are in specific/multiple >>> groups) in the Joomla database and then fallback to /etc/passwd >>> authentication to let system users authenticate. >>> >>> I'm running : >>> # 2.2.35 (b1cb664): /usr/local/etc/dovecot/dovecot.conf >>> # OS: FreeBSD 11.1-RELEASE-p10 amd64 >>> >>> Thanks in advance, >>> >>> -Graham- >> -- Harald Leithner ITronic Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria Tel: +43-1-545 0 604 Mobil: +43-699-123 78 4 78 Mail: leithner(a)itronic.at | itronic.at

1 0

Benchmarks with imaptest
by João Paulo Sacchetto Ribeiro Bastos 06 Jul '18

06 Jul '18

Hey guys, Has anybody ever used imaptest to benchmark *ONLY* reads? I'm trying to run a battery of tests in my new cluster and apparently no combination of parameters works, because fetch instruction doesn't run. Below is the command I'm using and its partial output imaptest/src/imaptest host=$SERVER_IP port=143 user=teste%d(a)example%d.com pass=$TEST_PASS users=10 domains=10 clients=100 - append=0 select=100 fetch=100 Logi Sele Fetc Logo 100% 100% 100% 100% 166 156 0 156 99/100 223 230 0 230 100/100 206 203 0 203 97/100 Can anybody help me understand why fetch doesn't work and how to fix this? Regards, -- João Paulo Bastos DevOps Engineer at Mav Tecnologia Belo Horizonte - Brazil +55 31 99279-7092

2 2

2.3.2 is still crashing (lmtp)
by Martynas Bendorius 06 Jul '18

06 Jul '18

Dovecot 2.3.2 still has the same issue we reported for 2.3.X: Jul 05 15:10:49 lmtp(2730445): Panic: file lib-event.c: line 182 (event_pop_global): assertion failed: (event != NULL) Jul 05 15:10:49 lmtp(2730445): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xce054) [0x7f7f7c92f054] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f7f7c92f09a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7f7c89e444] -> /usr/lib/dovecot/libdovecot.so.0(+0xe9e42) [0x7f7f7c94ae42] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4ff88) [0x7f7f7cc2cf88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_context_deactivate+0x5d) [0x7f7f7c94670d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x85) [0x7f7f7c946b05] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7f7f7c9483df] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f7f7c946be2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f7f7c946e08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7f7c8c2783] -> dovecot/lmtp [local READY](main+0x229) [0x7f7f7d3634b9] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7f7c4b63d5] -> dovecot/lmtp [local READY](+0x55e5) [0x7f7f7d3635e5] gdb: Core was generated by `dovecot/lmtp [lo'. Program terminated with signal 6, Aborted. #0 0x00007f6502506207 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt full #0 0x00007f6502506207 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 2826461 selftid = 2826461 #1 0x00007f65025078f8 in __GI_abort () at abort.c:90 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction = 0x1}, sa_mask = {__val = { 520, 173, 140071844479056, 513, 140071811839987, 257, 140071844479056, 513, 7749847442339820800, 140071844479056, 140071812055443, 140071844479056, 140727678224992, 140071844567296, 140071812055801, 140071844479056}}, sa_flags = 43400170, sa_restorer = 0x7ffdb7454a01} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007f650296b01b in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:247 backtrace = 0x7f6504888088 "/usr/lib/dovecot/libdovecot.so.0(+0xce054) [0x7f650296b054] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f650296b09a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f65028da"... recursed = 0 #3 0x00007f650296b09a in default_fatal_handler (ctx=0x7ffdb7454ad0, format=<optimized out>, args=<optimized out>) at failures.c:261 status = 0 #4 0x00007f65028da444 in i_panic ( format=format@entry=0x7f65029a6fa8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:325 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0, log_prefix = 0x0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffdb7454bc0, reg_save_area = 0x7ffdb7454b00}} #5 0x00007f6502986e42 in event_pop_global (event=<optimized out>) at lib-event.c:182 __func__ = "event_pop_global" #6 0x00007f6502c68f88 in mail_storage_service_io_deactivate_user_cb (user=0x7f65048e4708) at mail-storage-service.c:823 ---Type <return> to continue, or q <return> to quit--- event = 0x0 __func__ = "mail_storage_service_io_deactivate_user_cb" #7 0x00007f650298270d in io_loop_context_deactivate (ctx=0x7f65048df850) at ioloop.c:1054 cb_end = 0x7f65048e78f0 cb = 0x7f65048e78d0 __func__ = "io_loop_context_deactivate" #8 0x00007f6502982b05 in io_loop_call_io (io=0x7f650489d8c0) at ioloop.c:680 ioloop = 0x7f6504890c60 t_id = 0 __func__ = "io_loop_call_io" #9 0x00007f65029843df in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7f6504890c60) at ioloop-epoll.c:222 ctx = 0x7f650489c200 list = 0x7f650489d920 io = <optimized out> tv = {tv_sec = 2147483, tv_usec = 0} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> __func__ = "io_loop_handler_run_internal" #10 0x00007f6502982be2 in io_loop_handler_run (ioloop=ioloop@entry=0x7f6504890c60) at ioloop.c:726 __func__ = "io_loop_handler_run" #11 0x00007f6502982e08 in io_loop_run (ioloop=0x7f6504890c60) at ioloop.c:699 __func__ = "io_loop_run" #12 0x00007f65028fe783 in master_service_run (service=0x7f6504890af0, callback=callback@entry=0x7f650339f6e0 <client_connected>) at master-service.c:767 No locals. #13 0x00007f650339f4b9 in main (argc=2, argv=0x7f6504890890) at main.c:158 set_roots = {0x7f6502c0dea0 <smtp_submit_setting_parser_info>, 0x7f6503173ba0 <lda_setting_parser_info>, 0x7f65035a5500 <lmtp_setting_parser_info>, 0x0} ---Type <return> to continue, or q <return> to quit--- service_flags = <optimized out> storage_service_flags = <optimized out> tmp_base_dir = 0x7f6504888040 "\003" c = <optimized out> error = 0x0 -- Best regards, Martynas Bendorius

2 2