Re: Discuss: safety net for other compatibility breaks

2014-10-07 Thread LuKreme
On 07 Oct 2014, at 15:55 , Wietse Venema wrote: > As for biff, I haven't used that since I switched from a BSD/OS > workstation to a FreeBSD server in 2000. Fourteen years of UDP > datagrams wasted... It was pretty cool back in the 90s though, unless you were playing mTrek when you got the biff

Re: Discuss: safety net for other compatibility breaks

2014-10-07 Thread Wietse Venema
Noel Jones: > On 10/7/2014 10:53 AM, Viktor Dukhovni wrote: > > On Tue, Oct 07, 2014 at 11:32:47AM -0400, Wietse Venema wrote: > > > >> What else needs to be considered? > >> > >> There are more settings whose defaults can be confusing to people > >> who aren't familiar with 10+ years of Postfix h

Re: Discuss: safety net for other compatibility breaks

2014-10-07 Thread A. Schulze
Mark Martinec: Some more archaisms that can be changed to: biff = no swap_bangpath = no allow_percent_hack = no funny, all of the already mentioned settings I also set explicit set here ... other suggestions: - disable_vrfy_command = yes - enable_long_queue_ids = yes - smtpd_tls_p

Re: virtual_alias_maps order

2014-10-07 Thread LuKreme
On 07 Oct 2014, at 11:24 , Wietse Venema wrote: > However, lookup is recursive. The above result from B will be used > for a subsequent query. That may still query A and B and C, finding > a result in C. Excellent! Than you. -- Vader means father in German. Oh, you know German. Now I know why y

Re: virtual_alias_maps order

2014-10-07 Thread Wietse Venema
LuKreme: > virtual_alias_maps = > hash:$config_directory/virtual > pcre:$config_directory/virtual.pcre, > pcre:$config_directory/virtual_sql.pcre, > proxy:mysql:$config_directory/mysql_virtual_alias_maps.cf > > I want to be sure that the ORDER of declarations in virtual_alias_maps

virtual_alias_maps order

2014-10-07 Thread LuKreme
virtual_alias_maps = hash:$config_directory/virtual pcre:$config_directory/virtual.pcre, pcre:$config_directory/virtual_sql.pcre, proxy:mysql:$config_directory/mysql_virtual_alias_maps.cf I want to be sure that the ORDER of declarations in virtual_alias_maps is significant. For e

Re: Discuss: safety net for other compatibility breaks

2014-10-07 Thread Mark Martinec
Wietse wrote: What else needs to be considered? There are more settings whose defaults can be confusing to people who aren't familiar with 10+ years of Postfix history. - relay_domains (default: $mydestination). This should be empty. - mynetworks-style (default: subnet). This should be "host". I

Re: Discuss: safety net for other compatibility breaks

2014-10-07 Thread Noel Jones
On 10/7/2014 10:53 AM, Viktor Dukhovni wrote: > On Tue, Oct 07, 2014 at 11:32:47AM -0400, Wietse Venema wrote: > >> What else needs to be considered? >> >> There are more settings whose defaults can be confusing to people >> who aren't familiar with 10+ years of Postfix history. >> >> - relay_doma

Re: Discuss: safety net for other compatibility breaks

2014-10-07 Thread Viktor Dukhovni
On Tue, Oct 07, 2014 at 11:32:47AM -0400, Wietse Venema wrote: > What else needs to be considered? > > There are more settings whose defaults can be confusing to people > who aren't familiar with 10+ years of Postfix history. > > - relay_domains (default: $mydestination). This should be empty. >

Discuss: safety net for other compatibility breaks

2014-10-07 Thread Wietse Venema
Last week I introduced a safety net based on a compatibility level. If you upgrade to a Postfix version that has a higher compatibility level than the main.cf compatibility level (default: 0) then Postfix will use backwards-compatible default settings and log warnings when the old Postfix configur