On 04/07/17 11:51, Robert Moskowitz wrote:
I solved my mysql access problem with dovecot; turned out it was trying
a tcp connection and mysql is not listening on tcp. Fixed that to use
mysql.sock.
So this got me digging into how postfix was successfully accessing
mysql. I see in my various
On 04/07/2017 01:38 PM, John Fawcett wrote:
On 04/07/2017 07:33 PM, Robert Moskowitz wrote:
On 04/07/2017 01:19 PM, Wietse Venema wrote:
Robert Moskowitz:
I solved my mysql access problem with dovecot; turned out it was trying
a tcp connection and mysql is not listening on tcp. Fixed that
On 04/07/2017 07:33 PM, Robert Moskowitz wrote:
>
>
> On 04/07/2017 01:19 PM, Wietse Venema wrote:
>> Robert Moskowitz:
>>> I solved my mysql access problem with dovecot; turned out it was trying
>>> a tcp connection and mysql is not listening on tcp. Fixed that to use
>>> mysql.sock.
>>>
>>> So
On 04/07/2017 01:19 PM, Wietse Venema wrote:
Robert Moskowitz:
I solved my mysql access problem with dovecot; turned out it was trying
a tcp connection and mysql is not listening on tcp. Fixed that to use
mysql.sock.
So this got me digging into how postfix was successfully accessing
mysql.
Robert Moskowitz:
> I solved my mysql access problem with dovecot; turned out it was trying
> a tcp connection and mysql is not listening on tcp. Fixed that to use
> mysql.sock.
>
> So this got me digging into how postfix was successfully accessing
> mysql. I see in my various .cf files that
I solved my mysql access problem with dovecot; turned out it was trying
a tcp connection and mysql is not listening on tcp. Fixed that to use
mysql.sock.
So this got me digging into how postfix was successfully accessing
mysql. I see in my various .cf files that access mysql that I have: