Re: ldap lookups timing out?

On Thu, Aug 22, 2019 at 05:19:37PM +, Gomes, Rich wrote: > I am seeing a lot of Temporary lookup failure errors in the maillog. At > first I thought it was an issue related to reverse DNS lookups as each of > the sending servers had no reverse record in DNS (this is an internal only > relay).

Re: ldap lookups timing out?

On 2019-08-22 13:19, Gomes, Rich wrote: I am seeing a lot of Temporary lookup failure errors in the maillog. At first I thought it was an issue related to reverse DNS lookups as each of the sending servers had no reverse record in DNS (this is an internal only relay). But when I added verbose lo

ldap lookups timing out?

I am seeing a lot of Temporary lookup failure errors in the maillog. At first I thought it was an issue related to reverse DNS lookups as each of the sending servers had no reverse record in DNS (this is an internal only relay). But when I added verbose logging, it appears to be related to LDAP l

Re: Default connection limiting?

On 2019-08-22 12:56, Wietse Venema wrote: MRob: I have group of user behind single WAN using mine Postfix submission service. Sometimes they cann't connect but I dont know why. I thought its cause that Postfix has default connection maximum from single IP source, is this true? What is the erro

Re: Default connection limiting?

MRob: > I have group of user behind single WAN using mine Postfix submission > service. Sometimes they cann't connect but I dont know why. I thought > its cause that Postfix has default connection maximum from single IP > source, is this true? What is the error message? > * What is error/fail

Re: postfix with JMAP

Eliza: > Hi, > > will postfix get JMAP compatible in future? > see: https://jmap.io/ "JMAP (JSON Meta Application Protocol) is a modern standard for email clients to connect to mail stores" POSTFIX has no remote-access mailstore. DOVECOT does. Wietse

FIXED: server configuration error with non-ASCII records in passwd

On 22.08.19 09:47, Matus UHLAR - fantomas wrote: I have upgraded debian 8 (postfix 2.11) to debian 9 (postfix 3.1) on a mailserver. Now, whenever user who has utf-8 character in /etc/passwd as part of their username, has to receive mail, postfix outputs: 451 4.3.5 Server configuration error

server configuration error with non-ASCII records in passwd

Hello, I have upgraded debian 8 (postfix 2.11) to debian 9 (postfix 3.1) on a mailserver. Now, whenever user who has utf-8 character in /etc/passwd as part of their username, has to receive mail, postfix outputs: 451 4.3.5 Server configuration error there are many users who have utf-8 characte

Re: postfix with JMAP

On 22.08.19 15:02, Eliza wrote: will postfix get JMAP compatible in future? see: https://jmap.io/ I strongly doubt. Postfix is a MTA and it's sedigned to accept and receive e-mail. JMAP is outside of this scope, different services are to be used for JMAP. -- Matus UHLAR - fantomas, uh...@fanto

Re: Sorry for non-list post

On 8/21/19 2:21 PM, Wietse Venema wrote: UDP/53 is DNS. There will be a hit each time there is email for you from a Postfix mailing list, with one request that has type MX, and one or more requests that have type A or . On 21.08.19 14:50, ghe wrote: I get thousands a day from China and Bra

Re: Default connection limiting?

hi on 2019/8/22 14:49, MRob wrote: Sometimes they cann't connect but I dont know why. what did postfix server return? You may check the logs of DA (Delivery agent). regards.

postfix with JMAP

Hi, will postfix get JMAP compatible in future? see: https://jmap.io/ thanks.