Re: Very slow mail download/notification with dovecot 2.2.33 and Thunderbird

[Stuart Henderson]

On 2020-02-11, ml_dove...@thorsten-reichelt.de 
 wrote:
> I know that there are many results if I search for "dovecot thunderbird
> very slow" on Google but none of them helped me with my problem. :(

Do you have imap compression enabled? I had some problems with that and
Thunderbird.

> I just don't know where to look for the cause right now, but I can
> provide configurations (like output of |doveadm config) |and some logfile=

Providing any non-default config is usually helpful.

Re: shared folder name or public folder with mail address

[Armin Schindler]

On 2/14/20 2:23 PM, Tobias Kirchhofer wrote:
> On 14 Feb 2020, at 14:05, Armin Schindler wrote:
> 
>> On 2/14/20 11:44 AM, Tobias Kirchhofer wrote:
>>> On 14 Feb 2020, at 11:06, Armin Schindler wrote:
>>>
>>>     Hello!
> 
> […]
> 
>>> For our new setup (planned with CentOS 8, waiting for the official repo for 
>>> the latest dovecot
>>> version…) we have a prototype on Debian base with the latest version of 
>>> Dovecot. In opposite to our
>>> current solution we will implement global acls with user and groups from 
>>> LDAP. This is very nice.
>>
>> Wow, thanks. This seem to be exactly what I need to go on.
>> Our base system is a Univention UCS, so LDAP users and groups is what we 
>> already have working :-)
>>
>> With your elements I think we really could have the cyrus shared folders 
>> with dovecot by
>> using a namespace of
>>  type=public
>> but with
>>  prefix=shared/
>> (we might use type=shared with prefix=usershared/ later).
> 
> There is not something like one way do to this. You could also make your life 
> easier and choose to
> create a „Share user“ which is only there to share folders. This will then be 
> Dovecot „Shared
> folders“ shared by this pseudo user to other users. You then could use 
> Roundcube or such to maintain
> acl with this pseudo user. But we did not follow this path then for reasons i 
> cannot remember
> anymore :)
> 
> For each Public folder we have a defined namespace. „Newsletter“, „Client1“, 
> „Client2“ etc. We have
> many, around 30 or so. ACL goes on this namespace (namespace/*). I guess ACL 
> are first match. Each
> namespace has its own prefix. (eq. prefix = Newsletter/, prefix = Client1 
> etc.) User can subscribe
> namespace by namespace acl assumed.

What is the benefit using own namespace for each public folder?
If the config is equal for all folders, wouldn't one namespace with subfolders
be the same?
One public namespace would look like it is with cyrus in the client: one 
"shared/"
folder to open/close.

Armin




smime.p7s
Description: S/MIME Cryptographic Signature

Re: .IMAP

[Jos Chrispijn]

On 14-2-20 13:39, Aki Tuomi wrote:

This is why you put mail_location=driver:~/Mail and ensure the mails are 
under there, instead of mail_location=driver:~/


Yes, that is what I thought; when I use that setting, I get this error:

Feb 14 14:32:15  dovecot[8549]: imap(jos)<8739><5ErUO4meZthSsH9H>: 
Initializing mail storage from mail_location setting failed: Unknown 
mail storage driver driver in=0 out=375 deleted=0 expunged=0 trashed=0 
hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0


Currently this is (part of) my dovecot.conf

--- cut ---

auth_mechanisms = plain login
disable_plaintext_auth = no
mail_location = mbox:/home/%u:INBOX=/var/mail/%u
mail_privileged_group = mail

# mail_debug=yes
# auth_debug=yes

passdb {
   driver = pam
}

--- cut ---

When I change

mail_location = mbox:/home/%u:INBOX=/var/mail/%u

into

mail_location = mbox:/home/%u/mail:INBOX=/var/mail/%u

I only get inbox (the /var/mail/%u content) and the Deleted mailbox.

/jos

Re: shared folder name or public folder with mail address

[Tobias Kirchhofer]

On 14 Feb 2020, at 14:05, Armin Schindler wrote:


On 2/14/20 11:44 AM, Tobias Kirchhofer wrote:

On 14 Feb 2020, at 11:06, Armin Schindler wrote:

Hello!


[…]

For our new setup (planned with CentOS 8, waiting for the official 
repo for the latest dovecot
version…) we have a prototype on Debian base with the latest 
version of Dovecot. In opposite to our
current solution we will implement global acls with user and groups 
from LDAP. This is very nice.


Wow, thanks. This seem to be exactly what I need to go on.
Our base system is a Univention UCS, so LDAP users and groups is what 
we already have working :-)


With your elements I think we really could have the cyrus shared 
folders with dovecot by

using a namespace of
 type=public
but with
 prefix=shared/
(we might use type=shared with prefix=usershared/ later).


There is not something like one way do to this. You could also make your 
life easier and choose to create a „Share user“ which is only there 
to share folders. This will then be Dovecot „Shared folders“ shared 
by this pseudo user to other users. You then could use Roundcube or such 
to maintain acl with this pseudo user. But we did not follow this path 
then for reasons i cannot remember anymore :)


For each Public folder we have a defined namespace. „Newsletter“, 
„Client1“, „Client2“ etc. We have many, around 30 or so. ACL 
goes on this namespace (namespace/*). I guess ACL are first match. Each 
namespace has its own prefix. (eq. prefix = Newsletter/, prefix = 
Client1 etc.) User can subscribe namespace by namespace acl assumed.


But as i sad - by writing this i get nervous, cause i now that you must 
immerse deeply with this topic. Otherwise you will not get happy :)


Tobias


Or is the idea of just *one* public folder with name "shared" and with
subdirs for different "projects/departments/topics" not working as 
expected?


ACL is something I didn't look at yet. Is it possible to set different 
permissions
for the folders in the public prefix like /shared/dir1 , /shared/dir2 
, etc.

or even for sub-subfolders?
Global ACLs aren't neccessary when using folder acls, right?

Armin

[…]


--
collect@shift.agency

Re: shared folder name or public folder with mail address

[Armin Schindler]

On 2/14/20 11:44 AM, Tobias Kirchhofer wrote:
> On 14 Feb 2020, at 11:06, Armin Schindler wrote:
> 
> Hello!
> 
> we are about to move from cyrus to dovecot and have one open issue
> for that migration.
> With cyrus we have "shared/" folders with a name that is self defined like
> shared/project-xyz
> but the email address for direct delivery to that folder my be different
> (not project-...@domain.com ).
> 
> With dovecot we try to have it similar (at least how the user sees it in 
> the client)
> like it is now.
> 
> When configuring a namespace of type=shared, I see in the docs the the 
> prefix
> can be configured with %%u , %%n or %%d. But is it possible to configure
> the name different to the email address? E.g. to hide the email address of
> that folder and show a nice name instead?
> 
> I also thought about using public namespace instead. Does this make sense 
> here?
> With public (maybe configured with prefix=shared/) folder I can set any 
> name
> as subdir in prefix, right?
> So would this be more like what we have with cyrus shared folder?
> 
> If so, how could these public folders have an email address for direct 
> mail delivery into?
> Can something like a global sieve rule do that? Or can a public folder 
> have an email address?
> 
> Thanks in advance.
> Armin
> 
> Hi, we went through this some years ago. It is a bit tricky in the details. 
> Involved is postfix,
> public namespace, subscriptions, acl, sieve.
> 
> We found a quite comprehensive solution so far. It is working similar to 
> Cyrus shared folder. Do not
> mix the names. Cyrus „shared“ folders are „public“ folders in Dovecot. 
> Dovecot „shared“ folders are
> personally shared folders from one user to another.
> 
> For our new setup (planned with CentOS 8, waiting for the official repo for 
> the latest dovecot
> version…) we have a prototype on Debian base with the latest version of 
> Dovecot. In opposite to our
> current solution we will implement global acls with user and groups from 
> LDAP. This is very nice.

Wow, thanks. This seem to be exactly what I need to go on.
Our base system is a Univention UCS, so LDAP users and groups is what we 
already have working :-)

With your elements I think we really could have the cyrus shared folders with 
dovecot by
using a namespace of
 type=public
but with
 prefix=shared/
(we might use type=shared with prefix=usershared/ later).

Or is the idea of just *one* public folder with name "shared" and with
subdirs for different "projects/departments/topics" not working as expected?

ACL is something I didn't look at yet. Is it possible to set different 
permissions
for the folders in the public prefix like /shared/dir1 , /shared/dir2 , etc.
or even for sub-subfolders?
Global ACLs aren't neccessary when using folder acls, right?

Armin


> Some elements:
> 
> Global ACL:
> |
> [..]
> Newsletter group=administrator lrwstipekxa
> Newsletter/* group=team lrwstipe
> Newsletter/* user=n...@domain.tld lrwstipe
> […]
> |
> 
> Public folder:
> |
> namespace {
> type = public
> prefix = Newsletter/
> separator = /
> location = 
> maildir:/var/vmail/public/$DOMAIN/newsletter:LAYOUT=fs:INDEXPVT=~/public/$DOMAIN/newsletter
> subscriptions = no
> hidden = no
> list = children
> }
> |
> 
> Subscriptions (! This one was tricky)
> ```
> namespace subscriptions {
> subscriptions = yes
> prefix =
> separator = /
> list = no
> hidden = yes
> }
> 
> namespace inbox {
> inbox = yes
> separator = /
> prefix = INBOX/
> subscriptions = no
> […]
> ```
> 
> „Dovecot“ Shared folder (optional):
> |
> namespace shared {
> type = shared
> separator = /
> prefix = Shared/%%u/
> location = maildir:%%h/:INDEXPVT=~/shared/%%u
> list = children
> subscriptions = no
> }
> |
> 
> The sorting in the according public folder happens in a global sieve script 
> before user scripts are
> fireing. It is combined with the ‚+‘ notation in postfix for sub addresses 
> and an special ‚listadm‘ user
> 
> postfix:
> |
> listadm+Verteiler/info@$DOMAIN
> |
> 
> The sieve script is then reading the generated address and delivers it into 
> the according public
> folder. We learned a lot about sieve scripting with this task :-)
> 
> |sieve_before = /var/vmail/sieve/global/global-before.sieve […] |
> 
> More details would be to much here.
> 
> To be honest, we needed some time to get it done properly. It is a 
> combination of features and A LOT
> OF testing and analysing the behaviour of 
> postfix/dovecot/public-folder/sieve/acl. For now we have a
> Public folder setup which is as nice like it is with Cyrus. With Cyrus this 
> issue is less complex to
> implement.
> 
> Maybe this helps a bit. Take exclusivly one to two weeks for this task and 
> read and test a lot! :-)
> 
> Tobias
> 
> -- 
> collect@shift.agency 
> 



smime.p7s
Description: S/MIME Cryptographic Signature

Re: .IMAP

[Aki Tuomi]

On 14.2.2020 14.35, Jos Chrispijn wrote:
> Dear team,
>
> I have my users in /usr/home/user1 for user1, user2 for user2 etc.
> As these users also have a website, these folders have a
> /usr/home/user1/www folder, which is the docroot of their website.
>
> What happens now is that Dovecot indexes also this /usr/home/user1/www
> folder and creates in every folder a .imap folder which content is an
> exact image of the folder it is created in. In practice this causes 2
> times of webspace (which also in on the account of that user).
>
> Can you pls tell me what I do wrong and how to solve this? I might be
> missing an 'exclude' folder setting for each dovecot user.
>
> Thanks for you expertise,
> Jos
>
This is why you put mail_location=driver:~/Mail and ensure the mails are
under there, instead of mail_location=driver:~/

Aki

.IMAP

[Jos Chrispijn]

Dear team,

I have my users in /usr/home/user1 for user1, user2 for user2 etc.
As these users also have a website, these folders have a 
/usr/home/user1/www folder, which is the docroot of their website.


What happens now is that Dovecot indexes also this /usr/home/user1/www 
folder and creates in every folder a .imap folder which content is an 
exact image of the folder it is created in. In practice this causes 2 
times of webspace (which also in on the account of that user).


Can you pls tell me what I do wrong and how to solve this? I might be 
missing an 'exclude' folder setting for each dovecot user.


Thanks for you expertise,
Jos

Dovecot Proxy - Oauth2 mech add custom fields

[Domenico Pastore]

Hi,

I have a problem with configuring dovecot passdb for Oauth2 with keyclock.
A user can access more mailbox, mailboxes are associated with the user.

When a user login with this method:

OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ 
AUTH=PLAIN] Dovecot ready.
a login mailbox*user password

Dovecot when requiring the grant_url send to Keyclock, for example, this post 
(I have already enabled raw_log for analysis):

grant_type=password&username=domenico&password=test&client_id=imap-client&client_secret=99e26b26-0f2a-4b64-8f57-c0ca2147d3a0&scope=emailPOST
 /auth/realms/example/protocol/openid-connect/token/introspect

The call pass to Keyclock only master_user and miss mailbox info.
In fact, the JSON response after login return the only username without mailbox:

[...]
  "scope": "profile email",
  "email_verified": false,
  "preferred_username": "dome.nico"
[...]

When Dovecot proxy connects to the backend, email attribute and user have the 
same value, master-user. 
This behavior is a problem because when backend tries login access, login with 
the user and not with the mailbox.

This is backend logging:

2020-02-13 19:34:13 auth: Debug: client passdb out: OK  1   user=domenico  
token=eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJYVy1fSmNnVkF3aW9GUXh1NUhwdjVlbk5uNU8zaW42Y1VpaGJsM2dWX0V3In0.eyJqdGkiOiJhYTMwZ
Dk0Yy0xNjE0LTQzN2QtOTA5Zi01ZTAwNGQ2YjNmZTIiLCJleHAiOjE1ODE2MTE5NTQsIm5iZiI6MCwiaWF0IjoxNTgxNjExNjU0LCJpc3MiOiJodHRwczovL2tleWNsb2FrLXBlYy1pYW0ucGVjLWFwcHMucGFyLXRlYy5pdC9hdXRoL3JlYWxtcy9wZWMiLCJhdWQiOiJhY2NvdW50Iiwi
c3ViIjoiZjphNTA1NWUzMi1lYzhkLTRmZjgtOWZjNS00ODM4MmQ1MzRhODc6ZG9tZS5uaWNvIiwidHlwIjoiQmVhcmVyIiwiYXpwIjoiaW1hcC1jbGllbnQiLCJhdXRoX3RpbWUiOjAsInNlc3Npb25fc3RhdGUiOiIyN2M0ZDMzYy01YjdlLTQzMWMtYjZmMi0yYmI4NjIzYzMyMjkiLCJ
hY3IiOiIxIiwicmVhbG1fYWNjZXNzIjp7InJvbGVzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2
ZpbGUiXX19LCJzY29wZSI6InByb2ZpbGUgZW1haWwiLCJlbWFpbF92ZXJpZmllZCI6ZmFsc2UsInByZWZlcnJlZF91c2VybmFtZSI6ImRvbWUubmljbyJ9.LlIx-QeRQPr3lK4Cs1vU0qMvHF3uq3h15BGi1atNCBASkM6oPoYWLV-sYdf8hzpRFyOaTcbxN53SN6LfD0hHvUZ2sKHxh7UJ
idmxS4hf1SsZq8wJTASpebcPLtBIX5JBvXmpxa-cVnZDE1JVw5np5-LLNs0j4sgHwgg85mJEoE2VmYJzbGZjUsSTvaAAoCbvTA0MfsNoKyq0E5JrLVdkI-twX7HjAESFqFD4yHe7BS4FG_UjddrSr3uXmXreB44VLZ8B4xBgVRjK9K-sjjkXT8Bkv8WbxUdEEHaarWU_qanI5DlhA0CZXlJ
CyDsNcRwQfwVHOESxXE7ehgIDPm-NjA

I have a mechanism for adding other attributes with Dovecot when calling 
Keyclock? This for insert email or other fields into the token.

Thanks all,
Domenico

———
Dovecot Frontend

# 2.3.9.2 (cf2918cac): /config/dovecot/dovecot-proxy/dovecot.conf
# OS: Linux 3.10.0-693.17.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 
(Core)  
# Hostname: fe-new.example.it
auth_debug = yes
auth_debug_passwords = yes
auth_master_user_separator = *
auth_verbose = yes
auth_verbose_passwords = yes
base_dir = /data/dovecot/var/run/dovecot-proxy
default_vsz_limit = 768 M
disable_plaintext_auth = no
first_valid_gid = 101
first_valid_uid = 102
imap_id_send = 
import_environment = TZ MASTERPWD
info_log_path = /LOGS/imap/dovecot-proxy.log
instance_name = dovecot-proxy
listen = fe-new_imap
log_path = /LOGS/imap/dovecot-proxy.log
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_gid = 101
mail_location = maildir:%h/Maildir
mail_max_userip_connections = 50
mail_plugins = quota expire mail_log notify
mail_uid = 102
maildir_broken_filename_sizes = yes
mbox_write_locks = fcntl
namespace inbox {
  inbox = yes
  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 = INBOX.
  separator = .
  subscriptions = yes
  type = private
}
passdb {
  args = /config/dovecot/dovecot-proxy/dovecot-oauth2.conf
  driver = oauth2
  master = yes
  mechanisms = plain login
}
plugin {
  mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename
  mail_log_fields = uid box msgid size
}
postmaster_address = po...@foo.it
protocols = imap pop3
service anvil {
  client_limit = 3000
}
service auth {
  client_limit = 4096
  unix_listener auth-userdb {
mode = 0600
  }
}
service imap-login {
  inet_listener imap {
port = 0
  }
  inet_listener imaps {
port = 993
ssl = yes
  }
  process_limit = 2500
  process_min_avail = 5
}
service imap {
  drop_priv_before_exec = yes
  process_limit = 2500
  process_min_avail = 5
}
service lmtp {
  inet_listener lmtp {
port = 24
  }
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
service managesieve {
  drop_priv_before_exec = yes
  process_limit = 1024
}
service pop3-login {
  inet_listener pop3 {
port = 0
  }
  inet_listener pop3s {
port = 995
ssl = yes
  }

Re: shared folder name or public folder with mail address

[Tobias Kirchhofer]

On 14 Feb 2020, at 11:06, Armin Schindler wrote:


Hello!

we are about to move from cyrus to dovecot and have one open issue
for that migration.
With cyrus we have "shared/" folders with a name that is self defined 
like

  shared/project-xyz
but the email address for direct delivery to that folder my be 
different

(not project-...@domain.com).

With dovecot we try to have it similar (at least how the user sees it 
in the client)

like it is now.

When configuring a namespace of type=shared, I see in the docs the the 
prefix
can be configured with %%u , %%n or %%d. But is it possible to 
configure
the name different to the email address? E.g. to hide the email 
address of

that folder and show a nice name instead?

I also thought about using public namespace instead. Does this make 
sense here?
With public (maybe configured with prefix=shared/) folder I can set 
any name

as subdir in prefix, right?
So would this be more like what we have with cyrus shared folder?

If so, how could these public folders have an email address for direct 
mail delivery into?
Can something like a global sieve rule do that? Or can a public folder 
have an email address?


Thanks in advance.
Armin


Hi, we went through this some years ago. It is a bit tricky in the 
details. Involved is postfix, public namespace, subscriptions, acl, 
sieve.


We found a quite comprehensive solution so far. It is working similar to 
Cyrus shared folder. Do not mix the names. Cyrus „shared“ folders 
are „public“ folders in Dovecot. Dovecot „shared“ folders are 
personally shared folders from one user to another.


For our new setup (planned with CentOS 8, waiting for the official repo 
for the latest dovecot version…) we have a prototype on Debian base 
with the latest version of Dovecot. In opposite to our current solution 
we will implement global acls with user and groups from LDAP. This is 
very nice.


Some elements:

Global ACL:
```
[..]
Newsletter group=administrator lrwstipekxa
Newsletter/* group=team lrwstipe
Newsletter/* user=n...@domain.tld lrwstipe
[…]
```

Public folder:
```
namespace {
  type = public
  prefix = Newsletter/
  separator = /
  location = 
maildir:/var/vmail/public/$DOMAIN/newsletter:LAYOUT=fs:INDEXPVT=~/public/$DOMAIN/newsletter

  subscriptions = no
  hidden = no
  list = children
}
```

Subscriptions (! This one was tricky)
```
namespace subscriptions {
subscriptions = yes
prefix =
separator = /
list = no
hidden = yes
}

namespace inbox {
inbox = yes
separator = /
prefix = INBOX/
subscriptions = no
[…]
```

„Dovecot“ Shared folder (optional):
```
namespace shared {
type = shared
separator = /
prefix = Shared/%%u/
location = maildir:%%h/:INDEXPVT=~/shared/%%u
list = children
subscriptions = no
}
```

The sorting in the according public folder happens in a global sieve 
script before user scripts are fireing. It is combined with the ‚+‘ 
notation in postfix for sub addresses and an special ‚listadm‘ user


postfix:
```
listadm+Verteiler/info@$DOMAIN
```

The sieve script is then reading the generated address and delivers it 
into the according public folder. We learned a lot about sieve scripting 
with this task :-)



```
sieve_before = /var/vmail/sieve/global/global-before.sieve

[…]

```

More details would be to much here.

To be honest, we needed some time to get it done properly. It is a 
combination of features and A LOT OF testing and analysing the behaviour 
of postfix/dovecot/public-folder/sieve/acl. For now we have a Public 
folder setup which is as nice like it is with Cyrus. With Cyrus this 
issue is less complex to implement.


Maybe this helps a bit. Take exclusivly one to two weeks for this task 
and read and test a lot! :-)


Tobias



--
collect@shift.agency

shared folder name or public folder with mail address

[Armin Schindler]

Hello!

we are about to move from cyrus to dovecot and have one open issue
for that migration.
With cyrus we have "shared/" folders with a name that is self defined like
  shared/project-xyz
but the email address for direct delivery to that folder my be different
(not project-...@domain.com).

With dovecot we try to have it similar (at least how the user sees it in the 
client)
like it is now.

When configuring a namespace of type=shared, I see in the docs the the prefix
can be configured with %%u , %%n or %%d. But is it possible to configure
the name different to the email address? E.g. to hide the email address of
that folder and show a nice name instead?

I also thought about using public namespace instead. Does this make sense here?
With public (maybe configured with prefix=shared/) folder I can set any name
as subdir in prefix, right?
So would this be more like what we have with cyrus shared folder?

If so, how could these public folders have an email address for direct mail 
delivery into?
Can something like a global sieve rule do that? Or can a public folder have an 
email address?

Thanks in advance.
Armin



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Dovecot 2.3 repo for CentOS 8.

[Peter]

On 14/02/20 10:10 pm, Tobias Kirchhofer wrote:

would it be useful/advisable to use this repo for productive operation?

An official repo is still not available for CentOS 8 https://repo.dovecot.org/

We would like to set up our new mail server on CentOS 8 and are waiting… :)

What is your advice?


As others have mentioned there are missing -devel packages in CentOS 8, 
which is because there are missing -devel packages in RHEL 8, most 
notably in this case is quota-devel.  tcp wrappers is also missing but 
that's because they are deprecated in CentOS 8 so building without tcp 
wrapper support is not a big deal, but I would assume that a lot of 
people will want quota support, so I wouldn't want to build a dovecot 
package without it.


Personally I'm trying to get the GhettoForge build system modified so it 
can get missing -devel packages by rebuilding the source rpms for them, 
this is a work in progress.  There is also work on the CentOS side to 
build and offer up the missing -devel packages.  At the end of the day 
nobody will be able to build decent dovecot packages until one of these 
things happens.


For now you can use the stock dovecot 2.2.36 that comes with CentOS or 
you can wait.  CentOS and Red Hat have not made this easy so it is going 
to take time.


Also on a personal note, I think that pushing out any production server 
on CentOS 8 at this time is premature.  CentOS 8 simply is not ready 
yet, imo.



Peter

Re: Dovecot 2.3 repo for CentOS 8.

[Tobias Kirchhofer]

Hi Filip,

On 12 Dec 2019, at 12:01, fil...@centrum.cz wrote:

> Hello,
> I have builded some dovecot packages for CentOS 8 in my personal
> repository:
> http://repo.joomhosting.eu/centos/8/x86_64/
> and SRPMS are in
> http://repo.joomhosting.eu/centos/8/SRPMS/
>
> I you want you can try it.
>
> With best regards,
> Filip Bartmann

would it be useful/advisable to use this repo for productive operation?

An official repo is still not available for CentOS 8 https://repo.dovecot.org/

We would like to set up our new mail server on CentOS 8 and are waiting… :)

What is your advice?

Tobias

> On Thu, 12 Dec 2019 12:31:45 +0200
> Reio Remma  wrote:
>
>> On 09/12/2019 17:25, Aki Tuomi via dovecot wrote:
 On 09/12/2019 17:20 Reio Remma via dovecot 
 wrote:


 Hello!

 Are there any plans for an official Dovecot repo for CentOS 8?

 Thanks,
 Reio
>>> (sorry for duplicate, user error in earlier one...)
>>>
>>> Yes. There are plans for the repo, unfortunately there are still
>>> technical problems due to how CentOS8 repositories are organized.
>>> But soon.
>>>
>>> Aki
>>
>> I tried rebuilding the RPM for CentOS 8 but I see it's missing some
>> notable required packages like tcp wrappers and quota-devel. Managed
>> to rebuild by switching these off in the spec file
>> (--without-libwrap), but that's probably not a good idea. :)
>>
>> Reio


-- 
collect@shift.agency