Re: Inconsistency between postconf(5) and IPV6_README
On 2022-05-01 18:14, Wietse Venema wrote: Pau Amma: Still, there is room for making the link text shorter than I suggested while still providing enough context. For example, "tips how to port Postfix IPv6 support" or "how to port Postfix IPv6 support" may be enough context. I don't know the audience for this document well enough to say. I just found that there is a heading "IPv6 Support for unsupported platforms", so I'll use that in the link text. Thanks. That should work as well. -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila)
Re: Inconsistency between postconf(5) and IPV6_README
Pau Amma: > >> Revised patch per above. While in proto/IPV6_README.html, I tweaked > >> the > >> link text in one spot for better screenreader accessibility per > >> https://webaim.org/techniques/hypertext/#alpha_links. (Other links > >> there > >> or elsewhere in the documentation may need similar changes. Let me > >> know > >> if you & WV want to do that yourselves.) > > > > Thank you. I'm not familiar with 'screen reader tweaks'. Is this > > for people with limited eye sight? I generally avoid many-word > > links except in case of links to a heading. > > People with vision impairment are indeed the main users of screenreading > software, but I hear they also help some people as a workaround for > dyslexia. And I suggested a longer link text because screenreaders > sometimes (at the user's options) list links separately from running > text, and a link that just says "below" would be hard to interpret in > that case. Still, there is room for making the link text shorter than I > suggested while still providing enough context. For example, "tips how > to port Postfix IPv6 support" or "how to port Postfix IPv6 support" may > be enough context. I don't know the audience for this document well > enough to say. I just found that there is a heading "IPv6 Support for unsupported platforms", so I'll use that in the link text. Wietse
Re: Inconsistency between postconf(5) and IPV6_README
On 2022-05-01 00:09, Wietse Venema wrote: Pau Amma: On 2022-04-30 05:06, Viktor Dukhovni wrote: > On Sat, Apr 30, 2022 at 12:49:30AM +, Pau Amma wrote: > >> I finally got around to this, or rather to the half that didn't have a >> mention of NO_IPV6. While there, I noticed a stray uppercase letter >> elsewhere (2x) and fixed that as well. Patch (generated from >> postfix-3.8-20220421) attached. > > The source file for IPV6_README is: proto/IPV6_README.html > >> +++ postfix-tmp/README_FILES/IPV6_README 2022-04-30 02:35:27.514645000 >> +0200 > > This is a derived file, and the patch should be against the "proto" > file. > >> +++ postfix-tmp/proto/INSTALL.html 2022-04-30 02:40:25.455297000 +0200 > > THis is the only "INSTALL" file to edit. Revised patch per above. While in proto/IPV6_README.html, I tweaked the link text in one spot for better screenreader accessibility per https://webaim.org/techniques/hypertext/#alpha_links. (Other links there or elsewhere in the documentation may need similar changes. Let me know if you & WV want to do that yourselves.) Thank you. I'm not familiar with 'screen reader tweaks'. Is this for people with limited eye sight? I generally avoid many-word links except in case of links to a heading. People with vision impairment are indeed the main users of screenreading software, but I hear they also help some people as a workaround for dyslexia. And I suggested a longer link text because screenreaders sometimes (at the user's options) list links separately from running text, and a link that just says "below" would be hard to interpret in that case. Still, there is room for making the link text shorter than I suggested while still providing enough context. For example, "tips how to port Postfix IPv6 support" or "how to port Postfix IPv6 support" may be enough context. I don't know the audience for this document well enough to say. -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila)
Re: Inconsistency between postconf(5) and IPV6_README
Pau Amma: > On 2022-04-30 05:06, Viktor Dukhovni wrote: > > On Sat, Apr 30, 2022 at 12:49:30AM +, Pau Amma wrote: > > > >> I finally got around to this, or rather to the half that didn't have a > >> mention of NO_IPV6. While there, I noticed a stray uppercase letter > >> elsewhere (2x) and fixed that as well. Patch (generated from > >> postfix-3.8-20220421) attached. > > > > The source file for IPV6_README is: proto/IPV6_README.html > > > >> +++ postfix-tmp/README_FILES/IPV6_README 2022-04-30 02:35:27.514645000 > >> +0200 > > > > This is a derived file, and the patch should be against the "proto" > > file. > > > >> +++ postfix-tmp/proto/INSTALL.html 2022-04-30 02:40:25.455297000 +0200 > > > > THis is the only "INSTALL" file to edit. > > Revised patch per above. While in proto/IPV6_README.html, I tweaked the > link text in one spot for better screenreader accessibility per > https://webaim.org/techniques/hypertext/#alpha_links. (Other links there > or elsewhere in the documentation may need similar changes. Let me know > if you & WV want to do that yourselves.) Thank you. I'm not familiar with 'screen reader tweaks'. Is this for people with limited eye sight? I generally avoid many-word links except in case of links to a heading. Wietse
Re: Inconsistency between postconf(5) and IPV6_README
On 2022-04-30 05:06, Viktor Dukhovni wrote: On Sat, Apr 30, 2022 at 12:49:30AM +, Pau Amma wrote: I finally got around to this, or rather to the half that didn't have a mention of NO_IPV6. While there, I noticed a stray uppercase letter elsewhere (2x) and fixed that as well. Patch (generated from postfix-3.8-20220421) attached. The source file for IPV6_README is: proto/IPV6_README.html +++ postfix-tmp/README_FILES/IPV6_README 2022-04-30 02:35:27.514645000 +0200 This is a derived file, and the patch should be against the "proto" file. +++ postfix-tmp/proto/INSTALL.html 2022-04-30 02:40:25.455297000 +0200 THis is the only "INSTALL" file to edit. Revised patch per above. While in proto/IPV6_README.html, I tweaked the link text in one spot for better screenreader accessibility per https://webaim.org/techniques/hypertext/#alpha_links. (Other links there or elsewhere in the documentation may need similar changes. Let me know if you & WV want to do that yourselves.) -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila) diff -ru postfix-3.8-20220421/proto/INSTALL.html postfix-tmp/proto/INSTALL.html --- postfix-3.8-20220421/proto/INSTALL.html 2021-12-20 23:11:11.0 +0100 +++ postfix-tmp/proto/INSTALL.html 2022-04-30 02:40:25.455297000 +0200 @@ -837,7 +837,7 @@ -DNO_IPV6 Do not build with IPv6 support. By default, IPv6 support is compiled in on platforms that are known to have IPv6 support. Note: this directive is for debugging -And testing only. It is not guaranteed to work on all platforms. +and testing only. It is not guaranteed to work on all platforms. If you don't want IPv6 support, set "inet_protocols = ipv4" in main.cf. diff -ru postfix-3.8-20220421/proto/IPV6_README.html postfix-tmp/proto/IPV6_README.html --- postfix-3.8-20220421/proto/IPV6_README.html 2021-12-20 23:11:11.0 +0100 +++ postfix-tmp/proto/IPV6_README.html 2022-04-30 11:48:22.583354000 +0200 @@ -78,8 +78,8 @@ On other platforms Postfix will simply use IPv4 as it has always done. - See below for tips how to port Postfix -IPv6 support to other environments. + See below for tips how to port Postfix +IPv6 support to other environments. Configuration @@ -127,6 +127,9 @@ Note 2: on older Linux and Solaris systems, the setting "inet_protocols = ipv6" will not prevent Postfix from accepting IPv4 connections. + + Note 3: to pretend IPv6 isn't supported (for testing only), use the NO_IPV6 +compilation option. The other new parameter is smtp_bind_address6. This sets the local interface address for outgoing IPv6 SMTP
Re: Inconsistency between postconf(5) and IPV6_README
On Sat, Apr 30, 2022 at 12:49:30AM +, Pau Amma wrote: > I finally got around to this, or rather to the half that didn't have a > mention of NO_IPV6. While there, I noticed a stray uppercase letter > elsewhere (2x) and fixed that as well. Patch (generated from > postfix-3.8-20220421) attached. The source file for IPV6_README is: proto/IPV6_README.html > +++ postfix-tmp/README_FILES/IPV6_README 2022-04-30 02:35:27.514645000 > +0200 This is a derived file, and the patch should be against the "proto" file. > +++ postfix-tmp/proto/INSTALL.html2022-04-30 02:40:25.455297000 +0200 THis is the only "INSTALL" file to edit. -- Viktor.
Re: Inconsistency between postconf(5) and IPV6_README
On 2021-01-21 05:03, Viktor Dukhovni wrote: On Thu, Jan 21, 2021 at 04:37:19AM +, Pau Amma wrote: http://www.postfix.org/postconf.5.html#inet_protocols says: inet_protocols = all (DEFAULT) http://www.postfix.org/IPV6_README.html says: inet_protocols = ipv4 (DEFAULT: enable IPv4 only) The inconsistency should be fixed. Sure, but it may be worth noting that the default is actually platform and compile-time configuration dependent. I finally got around to this, or rather to the half that didn't have a mention of NO_IPV6. While there, I noticed a stray uppercase letter elsewhere (2x) and fixed that as well. Patch (generated from postfix-3.8-20220421) attached. -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila) diff -ru postfix-3.8-20220421/README_FILES/IPV6_README postfix-tmp/README_FILES/IPV6_README --- postfix-3.8-20220421/README_FILES/IPV6_README 2021-12-20 23:12:03.0 +0100 +++ postfix-tmp/README_FILES/IPV6_README 2022-04-30 02:35:27.514645000 +0200 @@ -83,6 +83,9 @@ Note 2: on older Linux and Solaris systems, the setting "inet_protocols = ipv6" will not prevent Postfix from accepting IPv4 connections. +Note 3: to pretend IPv6 isn't supported (for testing only), use the NO_IPV6 +compilation option. + * The other new parameter is smtp_bind_address6. This sets the local interface address for outgoing IPv6 SMTP connections, just like the smtp_bind_address parameter does for IPv4: diff -ru postfix-3.8-20220421/html/INSTALL.html postfix-tmp/html/INSTALL.html --- postfix-3.8-20220421/html/INSTALL.html 2021-12-20 23:11:55.0 +0100 +++ postfix-tmp/html/INSTALL.html 2022-04-30 02:40:06.987062000 +0200 @@ -837,7 +837,7 @@ -DNO_IPV6 Do not build with IPv6 support. By default, IPv6 support is compiled in on platforms that are known to have IPv6 support. Note: this directive is for debugging -And testing only. It is not guaranteed to work on all platforms. +and testing only. It is not guaranteed to work on all platforms. If you don't want IPv6 support, set "inet_protocols = ipv4" in main.cf. diff -ru postfix-3.8-20220421/proto/INSTALL.html postfix-tmp/proto/INSTALL.html --- postfix-3.8-20220421/proto/INSTALL.html 2021-12-20 23:11:11.0 +0100 +++ postfix-tmp/proto/INSTALL.html 2022-04-30 02:40:25.455297000 +0200 @@ -837,7 +837,7 @@ -DNO_IPV6 Do not build with IPv6 support. By default, IPv6 support is compiled in on platforms that are known to have IPv6 support. Note: this directive is for debugging -And testing only. It is not guaranteed to work on all platforms. +and testing only. It is not guaranteed to work on all platforms. If you don't want IPv6 support, set "inet_protocols = ipv4" in main.cf.
Re: Inconsistency between postconf(5) and IPV6_README
On Thu, Jan 21, 2021 at 04:37:19AM +, Pau Amma wrote: > http://www.postfix.org/postconf.5.html#inet_protocols says: > inet_protocols = all (DEFAULT) > http://www.postfix.org/IPV6_README.html says: inet_protocols = ipv4 > (DEFAULT: enable IPv4 only) > > The inconsistency should be fixed. Sure, but it may be worth noting that the default is actually platform and compile-time configuration dependent. src/util/sys_defs.h: #ifndef DEF_INET_PROTOCOLS #ifdef HAS_IPV6 #define DEF_INET_PROTOCOLS INET_PROTO_NAME_ALL #else #define DEF_INET_PROTOCOLS INET_PROTO_NAME_IPV4 #endif #endif So it could also be "ipv4" on some system where IPv6 is not supported, or disabled at compile time via: CCARGS='... -DDEF_INET_PROTOCOLS="ipv4" ...' On most modern systems with no explicit compile-time overrides it will be "ipv6". -- Viktor.
