Re: Question about password field in passwd-file

[Aki Tuomi]

you can add nopassword attribute to the end. See 
https://wiki.dovecot.org/PasswordDatabase/ExtraFields

---Aki TuomiDovecot oy
 Original message From: J Doe  Date: 
07/07/2018  02:39  (GMT+02:00) To: dovecot@dovecot.org Subject: Question about 
password field in passwd-file 
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:

    u...@example.com:: . . . (note no scheme or password specified between 
colons)

…means that the u...@example.com user does not have any valid crypted password 
and therefore the
u...@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 u...@example.com

… gives the result:

    {CRYPT}txR1JRq9140Qk

… which differs from the example password field having NEITHER {SCHEME} or 
password, like:

    u...@example.com:: . . .

… so if I attempt to logon using a null password for u...@example.com when 
nothing is specified in the
password field for the passwd-file:

    /etc/dovecot/passwd
    u...@example.com:: . . .

    $ sudo doveadm auth test u...@example.com
    password:
    passdb: u...@example.com auth failed 

… it is impossible to logon as u...@example.com with ANY PASSWORD and/or a NULL 
password ?

Thanks,

- J

Sources:

    [1] https://wiki2.dovecot.org/AuthDatabase/PasswdFile

dsync panic

[Infoomatic]

Hi,
I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 
2.2.19, but now panics (user with shared folder):
/opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser

dsync(standl2): Panic: file mailbox-attribute.c: line 360 
(mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || 
value_r->value_stream != NULL)
dsync(standl2): Error: Raw backtrace: 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> 
/opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] -> 
/opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) [0x56234f7b68dd] 
-> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) [0x56234f7b217d] -> 
/opt/dovecot/bin/doveadm(dsync_brain_run+0x538) [0x56234f7adb28] -> 
/opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> 
/opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> 
/opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> 
/opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> 
/opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> 
/opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9]

regards,
infoomatic

Re: Get rid of the "dbox-Mails"-folder

[Hativ]

Hey again,

I've found a working configuration: mail_location = sdbox:~/:FULLDIRNAME=.

I use a dot instead of slash or empty value.

Now my folder structure looks like I want and Dovecot is working fine.

Can anyone (maybe even a Dovecot developer?) say if the configuration is 
okay? I've tried to check the source code, but I don't know C as good as 
it's needed for that.


Greetings,

Hativ

Am 06.07.2018 um 16:10 schrieb Hativ:

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

Question about password field in passwd-file

[J Doe]

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:

u...@example.com:: . . . (note no scheme or password specified between 
colons)

…means that the u...@example.com user does not have any valid crypted password 
and therefore the
u...@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 u...@example.com

… gives the result:

{CRYPT}txR1JRq9140Qk

… which differs from the example password field having NEITHER {SCHEME} or 
password, like:

u...@example.com:: . . .

… so if I attempt to logon using a null password for u...@example.com when 
nothing is specified in the
password field for the passwd-file:

/etc/dovecot/passwd
u...@example.com:: . . .

$ sudo doveadm auth test u...@example.com
password:
passdb: u...@example.com auth failed 

… it is impossible to logon as u...@example.com with ANY PASSWORD and/or a NULL 
password ?

Thanks,

- J

Sources:

[1] https://wiki2.dovecot.org/AuthDatabase/PasswdFile

Re: support for Blowfish $2y$10$

[Graham S. Jarvis]

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" 
Date: 07/07/2018 00:03 (GMT+02:00)
To: dovecot@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-

Re: support for Blowfish $2y$10$

[Aki Tuomi]

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 TuomiDovecot oy
 Original message From: "Graham S. Jarvis"  
Date: 07/07/2018  00:03  (GMT+02:00) To: dovecot@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-

support for Blowfish $2y$10$

[Graham S. Jarvis]

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-

Replication fails over SSL

[Vladimir Tiukhtin]

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 =   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

Re: user/password Authentication via Joomla database

[Harald Leithner]

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/ and I'll (manually) make sure that  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  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 
>> To: dovecot@dovecot.org
>> Subject: Re: user/password Authentication via Joomla database
>> Message-ID: <180fd3b8-3369-9102-0216-94e41033f...@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= dbname= user= password=
>>
>> default_pass_scheme = BLF-CRYPT
>> password_query = \
>>    SELECT \
>>  u.username, \
>>  u.password, \
>>    FROM _users u \
>>  LEFT JOIN _user_usergroup_map g ON u.id =
>> g.user_id \
>>    WHERE \
>>  u.username = '%u' AND u.block = 0 AND g.group_id = > JOOMLA GROUP>
>>
>> user_query = \
>>    SELECT \
>>  u.username, \
>>  u.password, \
>>    FROM _users u \
>>  LEFT JOIN _user_usergroup_map g ON u.id =
>> g.user_id \
>>    WHERE \
>>  u.username = '%u' AND u.block = 0 AND g.group_id = > JOOMLA GROUP>
>>
>> iterate_query = SELECT username AS user FROM _users u \
>>  LEFT JOIN _user_usergroup_map g ON u.id =
>> g.user_id \
>>    WHERE \
>>  u.block = 0 AND g.group_id = 
>>
>> ---
>>
>> 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: leith...@itronic.at | itronic.at



signature.asc
Description: OpenPGP digital signature

Get rid of the "dbox-Mails"-folder

[Hativ]

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

Re: Benchmarks with imaptest

[João Paulo Sacchetto Ribeiro Bastos]

Heu Timo, thanks for your answer. Actually I tried to be careful about
empty mailboxes before running the read tests but and my big surprise, I
still had empty ones and this might have been the case =/
On Fri, 6 Jul 2018 at 05:44 Timo Sirainen  wrote:

> On 4 Jul 2018, at 20.10, João Paulo Sacchetto Ribeiro Bastos <
> joaopaulos...@gmail.com> wrote:
>
>
> 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@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  1560  156  99/100
>  223  2300  230 100/100
>  206  2030  203  97/100
>
> Can anybody help me understand why fetch doesn't work and how to fix this?
>
>
> I think the users simply don't have any mails in their INBOX. You can also
> add "rawlog" parameter and imaptest writes rawlog.* files. From them you
> can see what the IMAP traffic is. Especially if it says "* 0 EXISTS" then
> there are no mails.
>
> --

João Paulo Bastos
DevOps Engineer at Mav Tecnologia
Belo Horizonte - Brazil
+55 31 99279-7092

Re: 2.3.2 is still crashing (lmtp)

[Timo Sirainen]

> On 6 Jul 2018, at 11.42, Timo Sirainen  wrote:
> 
> On 6 Jul 2018, at 1.53, Martynas Bendorius  wrote:
>> 
>> 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)
> ...
>> #5  0x7f6502986e42 in event_pop_global (event=) at 
>> lib-event.c:182
>>   __func__ = "event_pop_global"
>> #6  0x7f6502c68f88 in mail_storage_service_io_deactivate_user_cb 
>> (user=0x7f65048e4708)
>>   at mail-storage-service.c:823
>> ---Type  to continue, or q  to quit---
>>   event = 0x0
>>   __func__ = "mail_storage_service_io_deactivate_user_cb"
> 
> Could you also run in gdb:
> 
> fr 6
> p *user
> p *user->pool
> 
> Also what's your doveconf -n?

Also, does this happen to fix it? 
https://github.com/dovecot/core/commit/231865af423b4fa4da209a0721de57840c9b91de.patch
 

Re: 2.3.2 director imap-login segfaults

[Tom Sommer]

On 2018-07-06 10:30, Timo Sirainen wrote:

On 5 Jul 2018, at 15.12, Tom Sommer  wrote:


My director has started segfaulting since upgradeing to 2.3.2:

#0  0x7fa19b3ec6ed in i_stream_get_root_io () from 
/usr/lib64/dovecot/libdovecot.so.0

No symbol table info available.
#1  0x7fa19b3ec9b5 in i_stream_set_input_pending () from 
/usr/lib64/dovecot/libdovecot.so.0

No symbol table info available.
#2  0x7fa198d48b35 in openssl_iostream_bio_sync () from 
/usr/lib64/dovecot/libssl_iostream_openssl.so

No symbol table info available.
#3  0x7fa198d4920a in openssl_iostream_more () from 
/usr/lib64/dovecot/libssl_iostream_openssl.so

No symbol table info available.


Can you try if the attached patch fixes it?


I just switched away from source to the centos repo, so I will have to 
do a complete reinstall from source - But if you really need me to, I 
can do that.


---
Tom

Re: Benchmarks with imaptest

[Timo Sirainen]

On 4 Jul 2018, at 20.10, João Paulo Sacchetto Ribeiro Bastos 
 wrote:
> 
> 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@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  1560  156  99/100
>  223  2300  230 100/100
>  206  2030  203  97/100
> 
> Can anybody help me understand why fetch doesn't work and how to fix this?

I think the users simply don't have any mails in their INBOX. You can also add 
"rawlog" parameter and imaptest writes rawlog.* files. From them you can see 
what the IMAP traffic is. Especially if it says "* 0 EXISTS" then there are no 
mails.

Re: 2.3.2 is still crashing (lmtp)

[Timo Sirainen]

On 6 Jul 2018, at 1.53, Martynas Bendorius  wrote:
> 
> 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)
...
> #5  0x7f6502986e42 in event_pop_global (event=) at 
> lib-event.c:182
>__func__ = "event_pop_global"
> #6  0x7f6502c68f88 in mail_storage_service_io_deactivate_user_cb 
> (user=0x7f65048e4708)
>at mail-storage-service.c:823
> ---Type  to continue, or q  to quit---
>event = 0x0
>__func__ = "mail_storage_service_io_deactivate_user_cb"

Could you also run in gdb:

fr 6
p *user
p *user->pool

Also what's your doveconf -n?

Re: 2.3.2 director imap-login segfaults

[Timo Sirainen]

On 5 Jul 2018, at 15.12, Tom Sommer  wrote:
> 
> My director has started segfaulting since upgradeing to 2.3.2:
> 
> #0  0x7fa19b3ec6ed in i_stream_get_root_io () from 
> /usr/lib64/dovecot/libdovecot.so.0
> No symbol table info available.
> #1  0x7fa19b3ec9b5 in i_stream_set_input_pending () from 
> /usr/lib64/dovecot/libdovecot.so.0
> No symbol table info available.
> #2  0x7fa198d48b35 in openssl_iostream_bio_sync () from 
> /usr/lib64/dovecot/libssl_iostream_openssl.so
> No symbol table info available.
> #3  0x7fa198d4920a in openssl_iostream_more () from 
> /usr/lib64/dovecot/libssl_iostream_openssl.so
> No symbol table info available.

Can you try if the attached patch fixes it?



ssl-crash-fix.diff
Description: Binary data