Re: One domain in multiple storage

2020-06-29 Thread Viktor Dukhovni
On Tue, Jun 30, 2020 at 12:05:27AM +0300, Dima Veselov wrote: > > The "uid" attribute is too "flat" for use in routing email to > > distributed mail stores. Therefore you need a second > > email-address-valued attribute that holds the destination mailbox > > address: > > > > uid: ivan > >

Re: One domain in multiple storage

2020-06-29 Thread Dima Veselov
On 29.06.2020 21:22, Viktor Dukhovni wrote: I have a domain, let's say example.com and my virtual users (stored in LDAP) are located in different cities. I would like to store their mail closer to them and we have enough servers. My question is - what is the best practice to configure users to ac

fyi, +1 on lightweight postfix spam milter alternative: 'spamassassin-milter'

2020-06-29 Thread PGNet Dev
for anyone interested, 'spamassassin-milter' https://gitlab.com/glts/spamassassin-milter a modern/current, rust-coded, SpamAssassin milter -- that cleanly submits msgs via spamc to spamd -- is, for me, working quite nicely with current/latest Postfix. it appears to be lightweight, fast

Re: One domain in multiple storage

2020-06-29 Thread Viktor Dukhovni
On Mon, Jun 29, 2020 at 08:15:36PM +0300, Dima Veselov wrote: > I have a domain, let's say example.com and my virtual users (stored in > LDAP) are located in different cities. I would like to store their mail > closer to them and we have enough servers. My question is - what is the > best practice

One domain in multiple storage

2020-06-29 Thread Dima Veselov
Greetings, I have a domain, let's say example.com and my virtual users (stored in LDAP) are located in different cities. I would like to store their mail closer to them and we have enough servers. My question is - what is the best practice to configure users to achieve that? My current configura

Postfix stable release 3.5.4 and legacy releases 3.4.14, 3.3.12, 3.2.17

2020-06-29 Thread Wietse Venema
[An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-3.5.4.html] Fixed in Postfix 3.5.4, 3.4.14: * The connection_reuse attribute in smtp_tls_policy_maps always resulted in an "invalid attribute name" error. Fix by Thorsten Habich.