Robert Moskowitz:
> > It remembers only the last line. I suppose that this is documented
> > somewhere, but since this is almost 20 years old, memory is a little
> > hazy.
>
> And I DID actually tried to research this first before asking! But then
> my search foo is nothing to brag about...
>
On 04/07/2017 04:39 PM, Wietse Venema wrote:
Robert Moskowitz:
I seem to have things running, now I am cleaning up my test setup before
building the new production server.
I perhaps got a little too fancy on modifying master.cf. After I worked
out other packages like dovecot and
Robert Moskowitz:
> I seem to have things running, now I am cleaning up my test setup before
> building the new production server.
>
> I perhaps got a little too fancy on modifying master.cf. After I worked
> out other packages like dovecot and roundcubemail, I started rethinking
> how I
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
I seem to have things running, now I am cleaning up my test setup before
building the new production server.
I perhaps got a little too fancy on modifying master.cf. After I worked
out other packages like dovecot and roundcubemail, I started rethinking
how I alter master.cf for my needs. It
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:
Adriel Avila Pe?a:
> I have problems with the relay
>
> Helo gmail.com
> Mail from: usua...@yahoo.es
> Rcpt to: u...@mydomain.com
>
> Sends it
>
> What I want to do is check the mail from match helo gmail.com
Just block 'helo gmail.com'. It is bogus.
Wietse
Hi,
waiting for CGPro upcoming release with promised search fixing, I've sorted out
the warning: dict_ldap_lookup: Search error 1: Operations error, adding a
domain= list of my internal domains in ldaprfx.cf, and so stopping mail=%s
expansion .
In main.cf I’ve added
I have problems with the relay
Helo gmail.com
Mail from: usua...@yahoo.es
Rcpt to: u...@mydomain.com
Sends it
What I want to do is check the mail from match helo gmail.com
13 matches
Mail list logo
