Postfix3 - Revision history

Pj: 21 revisions imported

2025-08-30T09:41:27Z

21 revisions imported

← Older revision	Revision as of 09:41, 30 August 2025
(No difference)

Pj: Fix code blocks

2024-09-02T09:06:39Z

Fix code blocks

← Older revision		Revision as of 09:06, 2 September 2024
Line 8:		Line 8:

	* Postfix 3.0 introduced the compatibility_level setting which permits backwards compatibility while allowing defaults to change in future versions of postfix as needed. When you upgrade from older versions postfix will maintain many backwards compatible defaults until you update the compatibility_level setting to tell Postfix that you want the newer defaults. Postfix will, however, issue warnings about compatibility_level not being set and also tell you which settings you should change before updating the compatibility_level setting when those settings are used by postfix. The following command is recommended to see all settings that will be changed when you update compatibility_level:		* Postfix 3.0 introduced the compatibility_level setting which permits backwards compatibility while allowing defaults to change in future versions of postfix as needed. When you upgrade from older versions postfix will maintain many backwards compatible defaults until you update the compatibility_level setting to tell Postfix that you want the newer defaults. Postfix will, however, issue warnings about compatibility_level not being set and also tell you which settings you should change before updating the compatibility_level setting when those settings are used by postfix. The following command is recommended to see all settings that will be changed when you update compatibility_level:
	~~<code>~~<pre>
			<pre>
	postconf \| grep -F \$compatibility_level		postconf \| grep -F \$compatibility_level
	</pre~~></code~~>		</pre>

	...it is recommended that you run the above command after a Postfix update and if you want any of the listed settings to remain at their previous defaults then you should add them to main.cf explicitly.		...it is recommended that you run the above command after a Postfix update and if you want any of the listed settings to remain at their previous defaults then you should add them to main.cf explicitly.
Line 21:		Line 22:

	* List the currently installed postfix packages:		* List the currently installed postfix packages:
	~~<code>~~<pre>
			<pre>
	# rpm -qa postfix\*		# rpm -qa postfix\*
	</pre~~></code~~>		</pre>

	* Install the gf-release package as per [[Usage]].		* Install the gf-release package as per [[Usage]].

	* Use the dnf shell command to update your system to postfix3:		* Use the dnf shell command to update your system to postfix3:
	~~<code>~~<pre>
			<pre>
	# dnf shell --enablerepo=gf-plus		# dnf shell --enablerepo=gf-plus
	> remove postfix*		> remove postfix*
	> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre
	</pre>~~</code>~~		</pre>

	EL has individual packages for the various dictionary types and should be replaced with the same postfix3 packages from GhettoForge as listed in the first step above.		EL has individual packages for the various dictionary types and should be replaced with the same postfix3 packages from GhettoForge as listed in the first step above.
	~~<code>~~<pre>
			<pre>
	> run		> run
	</pre>~~</code>~~		</pre>

	... You will be prompted to update to postfix3 and associated sub-packages.		... You will be prompted to update to postfix3 and associated sub-packages.
	~~<code>~~<pre>
			<pre>
	> quit		> quit
	</pre~~></code~~>		</pre>

	* Restart Postfix:		* Restart Postfix:
	~~<code>~~<pre>
			<pre>
	# service postfix restart		# service postfix restart
	</pre~~></code~~>		</pre>

	...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Also see the postconf command above to list all settings affected by compatibility_level. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.		...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Also see the postconf command above to list all settings affected by compatibility_level. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.
Line 67:		Line 75:
	Switching back to the stock postfix consists largely of doing the reverse steps from the above. There is one caveat in that the stock postfix packages have a bug where they will attempt to create the alternatives links before the postfix3 package removes them. The easiest way to fix this is to reinstall the stock postfix a second time after it has been installed and it should create the links then:		Switching back to the stock postfix consists largely of doing the reverse steps from the above. There is one caveat in that the stock postfix packages have a bug where they will attempt to create the alternatives links before the postfix3 package removes them. The easiest way to fix this is to reinstall the stock postfix a second time after it has been installed and it should create the links then:

	~~<code>~~<pre>		<pre>
	# dnf shell		# dnf shell
	> remove postfix3*		> remove postfix3*
Line 74:		Line 82:
	> quit		> quit
	# dnf reinstall postfix		# dnf reinstall postfix
	</pre~~></code~~>		</pre>

	~~<code>~~<pre>		<pre>
	# cp /etc/postfix/main.cf /etc/postfix/main.cf.postfix3		# cp /etc/postfix/main.cf /etc/postfix/main.cf.postfix3
	# postconf -X compatibility_level		# postconf -X compatibility_level
	</pre~~></code~~>		</pre>

	Then restart postfix and you should be done.		Then restart postfix and you should be done.

	[[Category:Packages]]		[[Category:Packages]]

Pj: Various changes related to archival of EL7.

2024-09-02T09:04:02Z

Various changes related to archival of EL7.

← Older revision		Revision as of 09:04, 2 September 2024
Line 7:		Line 7:
	Postfix3 replaces the EL stock postfix packages and will always contain the latest version of postfix available. These packages are backwards compatible with the EL stock postfix packages with the following caveats:		Postfix3 replaces the EL stock postfix packages and will always contain the latest version of postfix available. These packages are backwards compatible with the EL stock postfix packages with the following caveats:

	* Postfix 3.0 introduced the compatibility_level setting which permits backwards compatibility while allowing defaults to change in future versions of postfix as needed. When you upgrade from older versions postfix will maintain many backwards compatible defaults until you update the compatibility_level setting to tell Postfix that you want the newer defaults. Postfix will, however, issue warnings about compatibility_level not being set and also tell you which settings you should change before updating the compatibility_level setting.		* Postfix 3.0 introduced the compatibility_level setting which permits backwards compatibility while allowing defaults to change in future versions of postfix as needed. When you upgrade from older versions postfix will maintain many backwards compatible defaults until you update the compatibility_level setting to tell Postfix that you want the newer defaults. Postfix will, however, issue warnings about compatibility_level not being set and also tell you which settings you should change before updating the compatibility_level setting when those settings are used by postfix. The following command is recommended to see all settings that will be changed when you update compatibility_level:
			<code><pre>
			postconf \| grep -F \$compatibility_level
			</pre></code>

	* Postfix 3.~~0 introduced dynamic map support~~. ~~With this we have moved support for many table types to individual packages~~. ~~You will need to install~~ the ~~individual packages for each table type~~ you want ~~support for. To support~~ the ~~same table types as in the EL7 stock postfix packages~~ you should ~~install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre~~		...it is recommended that you run the above command after a Postfix update and if you want any of the listed settings to remain at their previous defaults then you should add them to main.cf explicitly.

	* Postfix 3.6.0 ~~now requires openssl 1.1.1 or higher~~. ~~As a result the EL7 postfix3 package now requires openssl11-libs from the EPEL repository~~. ~~Since EPEL is already required~~ to ~~be enabled~~ for ~~use of GhettoForge this should not be an issue, and the required dependency should be pulled in automatically on update~~.		* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for.

	----		----

	=== Instructions for replacing the EL stock postfix packages with the postfix3 packages in GhettoForge ===		=== Instructions for replacing the EL stock postfix packages with the postfix3 packages in GhettoForge ===

			* List the currently installed postfix packages:
			<code><pre>
			# rpm -qa postfix\*
			</pre></code>

	* Install the gf-release package as per [[Usage]].		* Install the gf-release package as per [[Usage]].

	* Use the ~~yum~~ shell command to update your system to postfix3:		* Use the dnf shell command to update your system to postfix3:
	<pre>		<code><pre>
	# ~~yum~~ shell --enablerepo=gf-plus		# dnf shell --enablerepo=gf-plus
	> remove postfix*		> remove postfix*
	> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre
	</pre>		</pre></code>
	~~(note that the stock postfix from EL7~~ has compiled-in support for ldap, mysql and pcre table types, but you may not need to support all these table types. If you don't feel free to leave them out of the install command above. EL8 and 9 have individual packages for the various dictionary types and should be replaced with the same postfix3 packages from GhettoForge)		EL has individual packages for the various dictionary types and should be replaced with the same postfix3 packages from GhettoForge as listed in the first step above.
	<pre>		<code><pre>
	> run		> run
	</pre>		</pre></code>
	... You will be prompted to update to postfix3 and associated sub-packages.		... You will be prompted to update to postfix3 and associated sub-packages.
	<pre>		<code><pre>
	> quit		> quit
	</pre>		</pre></code>

	* Restart Postfix:		* Restart Postfix:
	<pre>		<code><pre>
	# service postfix restart		# service postfix restart
	</pre>		</pre></code>

	...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.		...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Also see the postconf command above to list all settings affected by compatibility_level. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.

	Note that Postfix will not complain about compatibility settings until that setting is used, so for that reason it is recommended to run postfix under the old compatibility_level setting for a period of time (minutes, hours or days depending on your email traffic) to see what else Postfix might complain about in the logs before you update the compatibility_level setting.		Note that Postfix will not complain about compatibility settings until that setting is used, so for that reason it is recommended to run postfix under the old compatibility_level setting for a period of time (minutes, hours or days depending on your email traffic) to see what else Postfix might complain about in the logs before you update the compatibility_level setting. Alternatively you can run the postconf command above to see all settings affected by compatibility_level at once.

	Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of checking /etc/services.		Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of only checking /etc/services.

	If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the Libera IRC network for assistance.		If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the Libera IRC network for assistance.
Line 49:		Line 57:
	----		----

	===~~Yum~~ updates===		===DNF updates===

	Because the postfix3 packages are in the gf-plus repository you will need to explicitly enable them to get future updates with the "~~yum~~ update" command. See [[Usage]] for details.		Because the postfix3 packages are in the gf-plus repository you will need to explicitly enable them to get future updates with the "dnf update" command. See [[Usage]] for details.

	----		----
Line 59:		Line 67:
	Switching back to the stock postfix consists largely of doing the reverse steps from the above. There is one caveat in that the stock postfix packages have a bug where they will attempt to create the alternatives links before the postfix3 package removes them. The easiest way to fix this is to reinstall the stock postfix a second time after it has been installed and it should create the links then:		Switching back to the stock postfix consists largely of doing the reverse steps from the above. There is one caveat in that the stock postfix packages have a bug where they will attempt to create the alternatives links before the postfix3 package removes them. The easiest way to fix this is to reinstall the stock postfix a second time after it has been installed and it should create the links then:

	<pre>		<code><pre>
	# ~~yum~~ shell		# dnf shell
	> remove postfix3*		> remove postfix3*
	> install postfix postfix-ldap postfix-mysql postfix-pcre		> install postfix postfix-ldap postfix-mysql postfix-pcre
	> run		> run
	> quit		> quit
	# ~~yum~~ reinstall postfix		# dnf reinstall postfix
	</pre>		</pre></code>

	~~EL7 only: You should backup your main.cf file and then remove the compatibility_level setting to avoid warnings in the logs from an unrecognized setting:~~

	<pre>		<code><pre>
	# cp /etc/postfix/main.cf /etc/postfix/main.cf.postfix3		# cp /etc/postfix/main.cf /etc/postfix/main.cf.postfix3
	# postconf -X compatibility_level		# postconf -X compatibility_level
	</pre>		</pre></code>

	Then restart postfix and you should be done.		Then restart postfix and you should be done.

	[[Category:Packages]]		[[Category:Packages]]

Pj: Update for EL8 and 9, various minor fixes.

2022-08-05T12:12:46Z

Update for EL8 and 9, various minor fixes.

← Older revision		Revision as of 12:12, 5 August 2022
Line 25:		Line 25:
	> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre
	</pre>		</pre>
	(note that the stock postfix from EL has compiled-in support for ldap, mysql and pcre table types, but you may not need to support all these table types. If you don't feel free to leave them out of the install command above)		(note that the stock postfix from EL7 has compiled-in support for ldap, mysql and pcre table types, but you may not need to support all these table types. If you don't feel free to leave them out of the install command above. EL8 and 9 have individual packages for the various dictionary types and should be replaced with the same postfix3 packages from GhettoForge)
	<pre>		<pre>
	> run		> run
Line 45:		Line 45:
	Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of checking /etc/services.		Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of checking /etc/services.

	If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the ~~FreeNode~~ IRC network for assistance.		If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the Libera IRC network for assistance.

	----		----
Line 68:		Line 68:
	</pre>		</pre>

	EL7 only: You should backup your main.cf file and then remove the compatibility_level setting to avoid warnings in the logs from an ~~unrecognised~~ setting:		EL7 only: You should backup your main.cf file and then remove the compatibility_level setting to avoid warnings in the logs from an unrecognized setting:

	<pre>		<pre>

Pj: Specify EL7 for openssl11 requirement.

2021-09-28T01:02:51Z

Specify EL7 for openssl11 requirement.

← Older revision		Revision as of 01:02, 28 September 2021
Line 11:		Line 11:
	* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for. To support the same table types as in the EL7 stock postfix packages you should install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for. To support the same table types as in the EL7 stock postfix packages you should install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre

	* Postfix 3.6.0 now requires openssl 1.1.1 or higher. As a result the postfix3 package now requires openssl11-libs from the EPEL repository. Since EPEL is already required to be enabled for use of GhettoForge this should not be an issue, and the required dependency should be pulled in automatically on update.		* Postfix 3.6.0 now requires openssl 1.1.1 or higher. As a result the EL7 postfix3 package now requires openssl11-libs from the EPEL repository. Since EPEL is already required to be enabled for use of GhettoForge this should not be an issue, and the required dependency should be pulled in automatically on update.

	----		----

Pj: Add note about compatibility settings not getting logged right away.

2021-04-30T23:34:13Z

Add note about compatibility settings not getting logged right away.

← Older revision		Revision as of 23:34, 30 April 2021
Line 41:		Line 41:
	...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.		...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.

	Note that Postfix ~~3.6.0 introduced the "respectful_logging"~~ setting~~. This~~ is ~~also affected by compatibility_level but is not shown if~~ it is ~~unset with~~ compatibility_level ~~set lower than 3.6. When~~ setting ~~compatibility_level~~ to ~~a setting >= 3.6 if~~ you ~~want~~ the ~~old behavior you should explicitly set respectful_logging to "no"~~.		Note that Postfix will not complain about compatibility settings until that setting is used, so for that reason it is recommended to run postfix under the old compatibility_level setting for a period of time (minutes, hours or days depending on your email traffic) to see what else Postfix might complain about in the logs before you update the compatibility_level setting.

	Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of checking /etc/services.		Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of checking /etc/services.

Pj: Postfix 3.6.0 changes.

2021-04-30T15:35:01Z

Postfix 3.6.0 changes.

← Older revision		Revision as of 15:35, 30 April 2021
Line 10:		Line 10:

	* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for. To support the same table types as in the EL7 stock postfix packages you should install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for. To support the same table types as in the EL7 stock postfix packages you should install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre

			* Postfix 3.6.0 now requires openssl 1.1.1 or higher. As a result the postfix3 package now requires openssl11-libs from the EPEL repository. Since EPEL is already required to be enabled for use of GhettoForge this should not be an issue, and the required dependency should be pulled in automatically on update.

	----		----

Pj: Postfix 3.6.0 changes.

2021-04-30T15:32:17Z

Postfix 3.6.0 changes.

← Older revision		Revision as of 15:32, 30 April 2021
Line 38:		Line 38:

	...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.		...At this point you should have a look in /var/log/maillog. You will see warnings about compatibility_level and various settings that you should change before changing compatibility_level, but other than that Postfix should start up and run and be fully backwards compatible with the stock version you were running before. You can now explicitly set the various settings that Postfix complains about to remove the warnings for them. Do not update the compatibility_level setting until all other settings are fixed and Postfix no longer complains about any of them except for compatibility_level itself.

			Note that Postfix 3.6.0 introduced the "respectful_logging" setting. This is also affected by compatibility_level but is not shown if it is unset with compatibility_level set lower than 3.6. When setting compatibility_level to a setting >= 3.6 if you want the old behavior you should explicitly set respectful_logging to "no".

			Note that there is a new setting, "known_tcp_ports" in Postfix 3.6.0. The default changes the Postfix behavior to ignore certain service to port mappings from the /etc/services file. Normally this would not be an issue, but if you have custom ports set for any of these services in /etc/services then you should edit this setting accordingly, or explicitly set it empty to revert Postfix to the old behavior of checking /etc/services.

	If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the FreeNode IRC network for assistance.		If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the FreeNode IRC network for assistance.

Pj: el6 is now EOL

2020-12-21T03:00:10Z

el6 is now EOL

← Older revision		Revision as of 03:00, 21 December 2020
Line 6:		Line 6:

	Postfix3 replaces the EL stock postfix packages and will always contain the latest version of postfix available. These packages are backwards compatible with the EL stock postfix packages with the following caveats:		Postfix3 replaces the EL stock postfix packages and will always contain the latest version of postfix available. These packages are backwards compatible with the EL stock postfix packages with the following caveats:

	* Postfix 2.6 (EL 6) does not support the smtpd_relay_restrictions setting which was introduced in Postfix 2.10. The default for this setting is not backwards compatible, it should be set to nothing (blank) or "permit" for full backwards compatibility.

	* Older versions of Postfix do not support SMTPUTF8 and EL6 versions of postfix3 from GhettoForge are compiled without SMTPUTF8 support due to lack of library support in EL6. Postfix 3.0 introduced the smtputf8_enable setting which defaults to "yes" which causes postfix to issue a warning about the lack of compiled in support in EL6. To get rid of the warning you should explicitly set smtputf8_enable to "no".

	* Postfix 3.0 introduced the compatibility_level setting which permits backwards compatibility while allowing defaults to change in future versions of postfix as needed. When you upgrade from older versions postfix will maintain many backwards compatible defaults until you update the compatibility_level setting to tell Postfix that you want the newer defaults. Postfix will, however, issue warnings about compatibility_level not being set and also tell you which settings you should change before updating the compatibility_level setting.		* Postfix 3.0 introduced the compatibility_level setting which permits backwards compatibility while allowing defaults to change in future versions of postfix as needed. When you upgrade from older versions postfix will maintain many backwards compatible defaults until you update the compatibility_level setting to tell Postfix that you want the newer defaults. Postfix will, however, issue warnings about compatibility_level not being set and also tell you which settings you should change before updating the compatibility_level setting.

	* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for. To support the same table types as in the stock postfix packages you should install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		* Postfix 3.0 introduced dynamic map support. With this we have moved support for many table types to individual packages. You will need to install the individual packages for each table type you want support for. To support the same table types as in the EL7 stock postfix packages you should install the following packages: postfix3 postfix3-ldap postfix3-mysql postfix3-pcre

	----		----
Line 24:		Line 20:
	<pre>		<pre>
	# yum shell --enablerepo=gf-plus		# yum shell --enablerepo=gf-plus
	> remove postfix		> remove postfix*
	> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre		> install postfix3 postfix3-ldap postfix3-mysql postfix3-pcre
	</pre>		</pre>
Line 34:		Line 30:
	<pre>		<pre>
	> quit		> quit
	~~</pre>~~

	* EL6 only: Fix non-backwards-compatible settings:
	~~<pre>~~
	~~# postconf smtpd_relay_restrictions=permit smtputf8_enable=no~~
	</pre>		</pre>

Line 64:		Line 55:
	<pre>		<pre>
	# yum shell		# yum shell
	> remove postfix3\*		> remove postfix3*
	> install postfix		> install postfix postfix-ldap postfix-mysql postfix-pcre
	> run		> run
	> quit		> quit
Line 71:		Line 62:
	</pre>		</pre>

	You should backup your main.cf file and then remove the compatibility_level setting to avoid warnings in the logs from an unrecognised setting:		EL7 only: You should backup your main.cf file and then remove the compatibility_level setting to avoid warnings in the logs from an unrecognised setting:

	<pre>		<pre>
	# cp /etc/postfix/main.cf /etc/postfix/main.cf.postfix3		# cp /etc/postfix/main.cf /etc/postfix/main.cf.postfix3
	# postconf -X compatibility_level		# postconf -X compatibility_level
	~~</pre>~~

	~~EL6 only: you should also remove the smtputf8_enable and smtpd_relay_restrictions settings:~~

	~~<pre>~~
	~~# postconf -X smtputf8_enable smtpd_relay_restrictions~~
	</pre>		</pre>

Pj: Add section for updates

2018-01-18T02:09:08Z

Add section for updates

← Older revision		Revision as of 02:09, 18 January 2018
Line 49:		Line 49:

	If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the FreeNode IRC network for assistance.		If you have problems or need further assistance feel free to join #ghettoforge or #postfix on the FreeNode IRC network for assistance.

			----

			===Yum updates===

			Because the postfix3 packages are in the gf-plus repository you will need to explicitly enable them to get future updates with the "yum update" command. See [[Usage]] for details.

	----		----