Regigate appliance tech - Revision history

Regify: /* My regigate logs "4.7.1 Service unavailable - try again later" */

2026-03-16T13:19:45Z

My regigate logs "4.7.1 Service unavailable - try again later"

Regify: /* My regigate logs "4.7.1 Service unavailable - try again later" */

2026-03-16T13:16:11Z

My regigate logs "4.7.1 Service unavailable - try again later"

Regify: /* My regigate logs "4.7.1 Service unavailable - try again later" */

2026-03-16T10:39:40Z

My regigate logs "4.7.1 Service unavailable - try again later"

Regify: /* My regigate logs "4.7.1 Service unavailable - try again later" */

2026-03-16T10:39:28Z

My regigate logs "4.7.1 Service unavailable - try again later"

Regify: /* My regigate logs "4.7.1 Service unavailable - try again later" */

2026-03-16T10:37:36Z

My regigate logs "4.7.1 Service unavailable - try again later"

Regify: /* People receiving undecrypted emails (rgf file attached) */

2026-03-16T10:36:05Z

People receiving undecrypted emails (rgf file attached)

Regify: /* Re-sign your route certificate */

2025-08-05T13:18:54Z

Re-sign your route certificate

Regify: /* Re-sign your route certificates */

2025-08-05T12:20:43Z

Re-sign your route certificates

Regify: /* Re-sign your route certificates */

2025-08-05T12:18:40Z

Re-sign your route certificates

Regify: /* Updating Rule-Lists automatically */

2025-08-05T12:17:26Z

Updating Rule-Lists automatically

@@ Line 30: / Line 30: @@
 # The regigate certificate for regigate is expired. They are valid for three years.
 #* Normally, the regigate admin gets daily notification emails a few days before, sent to the email address [https://manuals.regify.com/docs/regigate/5.3/appliance_manual#_set_administrative_e_mail configured as Administrative E-mail]...
-#* '''Do a debug'''. You can [https://wiki.regify.com/index.php?title=Regigate_appliance_tech#Debugging_regigate enable debug on your regigate]. If the log covers such thing, it will tell us for sure. Search for any CRIT and WARN messages.
+#* '''Do a debug'''. You can [[Regigate_appliance_tech#Debugging_regigate|enable debug on your regigate]]. If the log covers such thing, it will tell us for sure. Search for any CRIT and WARN messages.
 #* The log is also telling regify support if other issues are causing the problem. So the debug log is essential!
-#* Find information here about [https://wiki.regify.com/index.php?title=Regigate_faq#How_do_I_renew_the_regigate_certificate.3F re-signing the regigate route certificate].
+#* Find information here about [[Regigate_faq#How_do_I_renew_the_regigate_certificate.3F|re-signing the regigate route certificate]].
 # The regigate is not able to connect to the connected sub-provider.
 #* Maybe someone activated some outgoing firewall rule or removed the whitelist entry in your firewall?
 #* '''Check your company firewall rules''' if regigate is still able to connect to the regify provider.
 # Maybe there is no matching regify account at the connected sub-provider (eg missing regify account to decypt or encrypt)?

@@ Line 26: / Line 26: @@
 == My regigate logs "4.7.1 Service unavailable - try again later" ==
-Usual reasons for regigate milter instance to answer like that are:
+Usual reasons for an answer like that from the regigate milter instance are:
-* No regify account at the connected sub-provider (eg missing regify account to decypt or encrypt).
+# The regigate certificate for regigate is expired. They are valid for three years.
-* The regigate is not able to connect to the connected sub-provider.
+#* Normally, the regigate admin gets daily notification emails a few days before, sent to the email address [https://manuals.regify.com/docs/regigate/5.3/appliance_manual#_set_administrative_e_mail configured as Administrative E-mail]...
-** Maybe someone activated some outgoing firewall rule or removed the whitelist entry in your firewall?
+#* '''Do a debug'''. You can [https://wiki.regify.com/index.php?title=Regigate_appliance_tech#Debugging_regigate enable debug on your regigate]. If the log covers such thing, it will tell us for sure. Search for any CRIT and WARN messages.
-** '''Check your company firewall rules''' if regigate is still able to connect to the regify provider.
+#* The log is also telling regify support if other issues are causing the problem. So the debug log is essential!
-* The regigate certificate for regigate is expired. They are valid for three years.
+#* Find information here about [https://wiki.regify.com/index.php?title=Regigate_faq#How_do_I_renew_the_regigate_certificate.3F re-signing the regigate route certificate].
-** Normally, the regigate admin gets daily emails a few days before, sent to the email address [https://manuals.regify.com/docs/regigate/5.3/appliance_manual/#_set_administrative_e_mail configured as Administrative E-mail]...
+# The regigate is not able to connect to the connected sub-provider.
-** '''Do a debug'''. You can [https://wiki.regify.com/index.php?title=Regigate_appliance_tech#Debugging_regigate enable debug on your regigate]. If the log covers such thing, it will tell us for sure.
+#* Maybe someone activated some outgoing firewall rule or removed the whitelist entry in your firewall?
-** The log is also telling regify support if other issues are causing the problem. So the debug log is essential!
+#* '''Check your company firewall rules''' if regigate is still able to connect to the regify provider.
-** Find information here about [https://wiki.regify.com/index.php?title=Regigate_faq#How_do_I_renew_the_regigate_certificate.3F re-signing the regigate route certificate].
+# Maybe there is no matching regify account at the connected sub-provider (eg missing regify account to decypt or encrypt)?
-Therefore, check your firewall and then your regigate.
+Therefore, check your regigate and your firewall.
 == Debugging regigate ==

@@ Line 28: / Line 28: @@
 Usual reasons for regigate milter instance to answer like that are:
-* No regify account at the connected sub-provider at esante (eg missing regify account to decypt or encrypt).
+* No regify account at the connected sub-provider (eg missing regify account to decypt or encrypt).
 * The regigate is not able to connect to the connected sub-provider.
 ** Maybe someone activated some outgoing firewall rule or removed the whitelist entry in your firewall?

@@ Line 29: / Line 29: @@
 * No regify account at the connected sub-provider at esante (eg missing regify account to decypt or encrypt).
-* The regigate is not able to connect to the eSante sub-provider.
+* The regigate is not able to connect to the connected sub-provider.
 ** Maybe someone activated some outgoing firewall rule or removed the whitelist entry in your firewall?
 ** '''Check your company firewall rules''' if regigate is still able to connect to the regify provider.

@@ Line 35: / Line 35: @@
 ** Normally, the regigate admin gets daily emails a few days before, sent to the email address [https://manuals.regify.com/docs/regigate/5.3/appliance_manual/#_set_administrative_e_mail configured as Administrative E-mail]...
 ** '''Do a debug'''. You can [https://wiki.regify.com/index.php?title=Regigate_appliance_tech#Debugging_regigate enable debug on your regigate]. If the log covers such thing, it will tell us for sure.
 ** Find information here about [https://wiki.regify.com/index.php?title=Regigate_faq#How_do_I_renew_the_regigate_certificate.3F re-signing the regigate route certificate].

← Older revision		Revision as of 10:36, 16 March 2026
Line 23:		Line 23:

	If the above does not apply, please activate [[#Debugging regigate\|debugging]] and check for errors like "''EC:''", "''requestKey status was invalid''" or "''Leaving message encrypted''".		If the above does not apply, please activate [[#Debugging regigate\|debugging]] and check for errors like "''EC:''", "''requestKey status was invalid''" or "''Leaving message encrypted''".
		+
		+	== My regigate logs "4.7.1 Service unavailable - try again later" ==
		+
		+	Usual reasons for regigate milter instance to answer like that are:
		+
		+	* No regify account at the connected sub-provider at esante (eg missing regify account to decypt or encrypt).
		+	* The regigate is not able to connect to the eSante sub-provider.
		+	** Maybe someone activated some outgoing firewall rule or removed the whitelist entry in your firewall?
		+	** '''Check your company firewall rules''' if regigate is still able to connect to the regify provider.
		+	* The regigate certificate for regigate is expired. They are valid for three years.
		+	** Normally, the regigate admin gets daily emails a few days before, sent to the email address [https://manuals.regify.com/docs/regigate/5.3/appliance_manual/#_set_administrative_e_mail configured as Administrative E-mail]...
		+	** '''Do a debug'''. You can [https://wiki.regify.com/index.php?title=Regigate_appliance_tech#Debugging_regigate enable debug on your regigate]. If the log covers such thing, it will tell us for sure.
		+	** Find information here about [https://wiki.regify.com/index.php?title=Regigate_faq#How_do_I_renew_the_regigate_certificate.3F re-signing the regigate route certificate].
		+
		+	Therefore, check your firewall and then your regigate.

	== Debugging regigate ==		== Debugging regigate ==

@@ Line 146: / Line 146: @@
 == Re-sign your route certificate ==
-Yopur regigate appliance routes are connected to your specific regify (sub)provider. In order to secure that connection, the connection is using signed certificates. If your certificate has expired in the meantime, follow these steps to re-sign it:
+Your regigate appliance routes are connected to your specific regify (sub)provider. In order to secure that connection, the connection is using signed certificates. If your certificate has expired in the meantime, follow these steps to re-sign it:
 # In [https://manuals.regify.com/docs/regigate/current/appliance_manual/#_appliance_menu regigate appliance menu], enter the route settings for the first route ("regigate..." → Select route).

@@ Line 145: / Line 145: @@
 '''Hint:''' If an e-mail is sent to regigate in exactly the moment where the rfmilter is not available because of the restart, the sending MTA will get a 4.x.x error (temporary problem). Normally, an MTA then will try it again in a minute and the e-mail(s) will only be a little late.
-== Re-sign your route certificates ==
+== Re-sign your route certificate ==
 Yopur regigate appliance routes are connected to your specific regify (sub)provider. In order to secure that connection, the connection is using signed certificates. If your certificate has expired in the meantime, follow these steps to re-sign it:

@@ Line 146: / Line 146: @@
 == Re-sign your route certificates ==
-The regigate appliance routes are connected to specific regify (sub)providers. In order to secure that connection, the connection is using signed certificates. If your certificate has expired in the meantime, follow these steps to re-sign it:
+Yopur regigate appliance routes are connected to your specific regify (sub)provider. In order to secure that connection, the connection is using signed certificates. If your certificate has expired in the meantime, follow these steps to re-sign it:
 # In [https://manuals.regify.com/docs/regigate/current/appliance_manual/#_appliance_menu regigate appliance menu], enter the route settings for the first route ("regigate..." → Select route).
 # Do "[https://manuals.regify.com/docs/regigate/current/appliance_manual/#_show_certificate_request Show Certificate Request]" and copy the request.
-# Go to your (sub)provider administration page and log in
+# Go to your (sub)provider administration page and log in.
 # Enter "Manage regigates" and click the key symbol behind your regigate entry.
 # Paste the certificate request and let it sign.

← Older revision		Revision as of 12:17, 5 August 2025
Line 144:		Line 144:

	'''Hint:''' If an e-mail is sent to regigate in exactly the moment where the rfmilter is not available because of the restart, the sending MTA will get a 4.x.x error (temporary problem). Normally, an MTA then will try it again in a minute and the e-mail(s) will only be a little late.		'''Hint:''' If an e-mail is sent to regigate in exactly the moment where the rfmilter is not available because of the restart, the sending MTA will get a 4.x.x error (temporary problem). Normally, an MTA then will try it again in a minute and the e-mail(s) will only be a little late.
		+
		+	== Re-sign your route certificates ==
		+	The regigate appliance routes are connected to specific regify (sub)providers. In order to secure that connection, the connection is using signed certificates. If your certificate has expired in the meantime, follow these steps to re-sign it:
		+
		+	# In [https://manuals.regify.com/docs/regigate/current/appliance_manual/#_appliance_menu regigate appliance menu], enter the route settings for the first route ("regigate..." → Select route).
		+	# Do "[https://manuals.regify.com/docs/regigate/current/appliance_manual/#_show_certificate_request Show Certificate Request]" and copy the request.
		+	# Go to your (sub)provider administration page and log in
		+	# Enter "Manage regigates" and click the key symbol behind your regigate entry.
		+	# Paste the certificate request and let it sign.
		+	# Copy the signed certificate.
		+	# Go back to your regigate route and select "[https://manuals.regify.com/docs/regigate/current/appliance_manual/#_import_signed_certificate Import Signed Certificate]" option.
		+	# Paste the certificate and confirm with CTRL+D.
		+	# Repeat that for all your routes (usually two).