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
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 se
On 26 Sep 2014, at 13:04 , John 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
user...@secondarydomin.tld userbar
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,
On September 24, 2014 3:05:54 AM EDT, Stefan Foerster
wrote:
>* Wietse Venema :
>> - Some distributions already ship with "append_dot_mydomain = no".
>> This is an opportunity to eliminate the inconsistency.
Debian (and thus Ubuntu and other derivatives) have set this for quite some
time. I
On 24 Sep 2014, at 11:16 , Ansgar Wiechers wrote:
> On 2014-09-23 A. Schulze wrote:
>> I already explicit set 'append_dot_mydomain = no'.
> Same here.
Is there any simple way to test if setting this will break things other than
setting it and watching the logs?
--
The way I see it, the longer
On 2014-09-23 A. Schulze wrote:
> wietse:
>> Dammit, I want to hear from people who expect to have problems
>> or not.
>
> OK, I don't expect problems for /my/ systems
> because I already explicit set 'append_dot_mydomain = no'.
Same here.
Regards
Ansgar Wiechers
--
"Abstractions save us time w
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
inc
* Wietse Venema :
> - Some distributions already ship with "append_dot_mydomain = no".
> This is an opportunity to eliminate the inconsistency.
This will probably break mail setups that used to rely on unqualified
names in a way that's hard to diagnose, especially if there is
a namespace clash w
On 22 Sep 2014, at 12:29 , Noel Jones wrote:
> My thought: there are popular distros that have set this explicitly
> to "no" for years, and yet we get very few questions here where the
> artificial "no" setting causes a problem. So in a sense it's already
> been tested for us.
Sort of.
Is there
Am 23.09.2014 um 01:33 schrieb Wietse Venema :
> Viktor Dukhovni:
>> On Mon, Sep 22, 2014 at 11:41:00AM -0400, Wietse Venema wrote:
>>
>>> This time PLEASE refrain from sidetracking the discussion. I want
>>> to know what will break when the default changes, if that is not
>>> too much to ask fo
Wietse Venema writes:
Dammit, I want to hear from people who expect to have problems
or not.
I don't expect problems on our systems because we also have set
append_dot_mydomain to no.
Furthermore, one of the great things about Postfix is its documentation, and
if the change is mentioned in
wietse:
Dammit, I want to hear from people who expect to have problems
or not.
OK, I don't expect problems for /my/ systems
because I already explicit set 'append_dot_mydomain = no'.
Andreas
On Sep 22, 2014, at 11.41, Wietse Venema wrote:
> This time PLEASE refrain from sidetracking the discussion. I want
> to know what will break when the default changes, if that is not
> too much to ask for.
>
> Summary:
>
> Until now, Postfix has a default setting "append_dot_mydomain = yes".
>
Viktor Dukhovni:
> On Mon, Sep 22, 2014 at 11:41:00AM -0400, Wietse Venema wrote:
>
> > This time PLEASE refrain from sidetracking the discussion. I want
> > to know what will break when the default changes, if that is not
> > too much to ask for.
> >
> > Summary:
> >
> > Until now, Postfix has
On Mon, Sep 22, 2014 at 11:41:00AM -0400, Wietse Venema wrote:
> This time PLEASE refrain from sidetracking the discussion. I want
> to know what will break when the default changes, if that is not
> too much to ask for.
>
> Summary:
>
> Until now, Postfix has a default setting "append_dot_mydom
On 22/09/14 18:41, Wietse Venema wrote:
> Until now, Postfix has a default setting "append_dot_mydomain = yes".
> This performs autocompletion from user@host to user@host.$mydomain.
> But this default setting is becoming problematic.
With hindsight, append_dot_mydomain = yes is a bad idea. Partia
On Sep 22, 2014, at 2:43 PM, Viktor Dukhovni wrote:
> On Mon, Sep 22, 2014 at 01:29:37PM -0500, Noel Jones wrote:
>
>> My thought: there are popular distros that have set this explicitly
>> to "no" for years, and yet we get very few questions here where the
>> artificial "no" setting causes a p
On Mon, Sep 22, 2014 at 01:29:37PM -0500, Noel Jones wrote:
> My thought: there are popular distros that have set this explicitly
> to "no" for years, and yet we get very few questions here where the
> artificial "no" setting causes a problem. So in a sense it's already
> been tested for us.
Than
On 9/22/2014 10:41 AM, Wietse Venema wrote:
> This time PLEASE refrain from sidetracking the discussion. I want
> to know what will break when the default changes, if that is not
> too much to ask for.
>
> Summary:
>
> Until now, Postfix has a default setting "append_dot_mydomain = yes".
> This p
Am 22.09.2014 um 18:26 schrieb Viktor Dukhovni:
> On Mon, Sep 22, 2014 at 05:55:16PM +0200, Robert Schetterer wrote:
>
>> my vote for default
>> append_dot_mydomain = no
>
> Rationale? What problem does this solve or avoid for you?
>
Hi Viktor, i dont see it as a big problem whatever the param
On Mon, Sep 22, 2014 at 05:55:16PM +0200, Robert Schetterer wrote:
> my vote for default
> append_dot_mydomain = no
Rationale? What problem does this solve or avoid for you?
--
Viktor.
Am 22.09.2014 um 17:41 schrieb Wietse Venema:
> This time PLEASE refrain from sidetracking the discussion. I want
> to know what will break when the default changes, if that is not
> too much to ask for.
>
> Summary:
>
> Until now, Postfix has a default setting "append_dot_mydomain = yes".
> This
This time PLEASE refrain from sidetracking the discussion. I want
to know what will break when the default changes, if that is not
too much to ask for.
Summary:
Until now, Postfix has a default setting "append_dot_mydomain = yes".
This performs autocompletion from user@host to user@host.$mydomain
24 matches
Mail list logo
