On 2018-02-03 17:09, @lbutlr wrote: > On 1 Feb 2018, at 21:31, Olivier olivier.nic...@cs.ait.ac.th> wrote: >> Is that a know problem? Is there a fix? > > It is not. I have a postfix 3.2 install and primary use Macs to access > it. Works fine one new and old accounts. > > However, this sounds like a dovecot issue, not a postfix issue. And > you didn't provide any logs for the "can't use old accounts" events, > so it's hard to say. > > Or maybe you are using something other than dovecot, in which case use > dovecot. > > Ah, I see reading ahead that you are using cyrus. > > I found cyrus to be poorly documented and fragile, and switched to > dovecot on recommendations on this list. I've been pleased with it. > > In all likelihood, the settings for authentication need to be updated > on the Macs. Generally the Mac does a good job of setting the accounts > up correctly, but it will not change the settings when your server > changes. > > Check the port number and the authentication method and make sure they > match a working account. > > <https://www.dropbox.com/s/85xy4tc24i5twqr/Screenshot%202018-02-03%2010.06.26.png?dl=0> > > (That is for macOS High Sierra v10.13, earlier versions may look different) > > I suspect either the port is wrong or the Authentication method is > wrong, or both are wrong.
I have few people connecting using Macs. I had similar issue when I upgraded libssl to 1.1.0f-4 all of them couldn't connect as they are still using TLS 1.0. I had to temporarily downgrade to 1.1.0f-3 until the problem was fixed in 1.1.0g-1. The problem was that developers decided to disable TLS1.0, which impacted a lot of things. My point is: are you sure that you upgraded just postfix or maybe you hit same issue by running apt-get upgrade or similar? I don't know what version of Mac is still using TLS1.0 as I can't stand Macs and avoid them at all cost. I also don't know if using TLS1.0 is account sticky which would be ridiculous. k. -- Karol Augustin ka...@augustin.pl http://karolaugustin.pl/ +353 85 775 5312
