Initial situation:
After processing by the SEPPmail Secure E-Mail Gateway, emails are to be returned to the same IP address from which they were sent to the SEPPmail Secure E-Mail Gateway.
Reason:
In an infrastructure in which the SEPPmail Secure E-Mail Gateway is operated in parallel with an upstream relay cluster (see also Parallel To Protection Component), it should be ensured that emails are returned from this cluster to the same machine from which they were transferred to the SEPPmail Secure E-Mail Gateway. This can make it easier to track an email in an error situation, for example.
Solution:
Up to SEPPmail Secure E-Mail Gateway version 11.1.11, the option Re-inject mails to sending mailserver was available for this. In version 11.1.11, this was replaced by the new option Use custom delivery method. With the entry "loop", the same behaviour is achieved with this option as previously with Re-inject mails to sending mailserver.
|
Forwarding servers and outgoing servers are ignored or used as fallback settings if this function is activated. |
|
Activating this option may create an email loop if the sending email system does not support this function or was configured incorrectly. |
|
In the update, the setting from Re-inject mails to sending mailserver is automatically adopted into the new option Use custom delivery method (entry "loop"). |
