Re: Thanks: Input requested: append_dot_mydomain default change

2014-09-29 Thread Matthias Andree
Am 24.09.2014 um 16:29 schrieb Wietse Venema: The implementation will probably be a compatibility_level parameter that is 1 for installations that pre-date this feature, that is 2 for new installations, and that is incremented by 1 for each compatibility break. People who don't care can set

Re: Thanks: Input requested: append_dot_mydomain default change

2014-09-29 Thread Wietse Venema
Matthias Andree: 3 - is there a useful way to log warnings about unqualified domains when they are observed and qualified in mid-flight, so that people have something to watch for before flipping the switch? It seems there already is, check_{sender,recipient}_access + WARN action + regexp map

Re: Thanks: Input requested: append_dot_mydomain default change

2014-09-28 Thread LuKreme
On 26 Sep 2014, at 13:04 , John j...@klam.ca wrote: The idea of handing out email addresses that do not have a fully qualified domain in them seems to be rather dumb. The issue, as I understand it, is in files like aliases or virtual where you may have something like

Re: Thanks: Input requested: append_dot_mydomain default change

2014-09-26 Thread John
On 24/09/2014 10:29 AM, wie...@porcupine.org (Wietse Venema) wrote: Thanks for the first-hand input, both on- and off-list. The responses show that there is a massive problem with what Rumsfeld called the unknown unknowns. That is, except for those who have total control over their clients,

Thanks: Input requested: append_dot_mydomain default change

2014-09-24 Thread Wietse Venema
Thanks for the first-hand input, both on- and off-list. The responses show that there is a massive problem with what Rumsfeld called the unknown unknowns. That is, except for those who have total control over their clients, people generally have no idea what legacy systems might be sending