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
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.
-
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_domains (default:
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
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
-
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.
-
On 07 Oct 2014, at 15:55 , Wietse Venema wie...@porcupine.org 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
