Re: mysql lookup table and utf8

On 15/09/2016 16:47, Viktor Dukhovni wrote: On Thu, Sep 15, 2016 at 09:51:11AM -0400, Wietse Venema wrote: Stephan Seitz: On Thu, Sep 15, 2016 at 06:49:08AM -0400, Wietse Venema wrote: FYI, Postfix uses libmysqlclient. So what's up with not reading the default config file? Can it be the

Re: Processing order of canonical maps

Thank you! The documentation seems a bit ambiguous on this topic. After reading canonical(5) and the canonical_maps section of postconf(5), I think it's not clear which of the processing orders, mentioned in the first email, it actually uses. Would you like me to write a patch for this?

Re: Processing order of canonical maps

canonical(5) section "TABLE SEARCH ORDER": "With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, patterns are tried in the order as listed below:" That really does what it says: try the first query. Try the second query. And so

Re: Effects of very large message_size_limit?

On Thu Sep 15 2016 14:00:46 mro...@insiberia.net said: > > But can anyone answer my question - what factors should I consider when > increasing the limit in the 30-50MB range (or higher)? Are there drawbacks to > doing this? The main factor is that the limit used

Re: Processing order of canonical maps

It just doesn't seem very clear to me. And one of our customers even got the wrong impression about the search order. I think a sentence like the following could be dropped in there somewhere: "First, a match of 'user@domain' is searched for across all the listed tables in the order the tables

Re: Processing order of canonical maps

As a new administrator of postfix I am not able to determine which of the two orders is correct from the existing documentation. An additional sentence would be very helpful. Perhaps, under canonical(5) section "TABLE SEARCH ORDER": "Each pattern is looked for across the entire set of tables