Next try ... the forum-software said, that I am not allowed to write in this forum?!
OK ... it seems, that the server of Telekom and Mercury are playing pingpong due to that forward / bounce rule. I guess I had that problem too a long time ago with Mercury/NLM (but not due to forwarding):
When Mercury is forwarding the mail, Telekom's server refuses it due to SPAM. Mercury generates a message on this error (appending the mail) to Postmaster and to the mailaddress standing in "return-path" in the header of that mail. I asume while forwarding Mercury changes return-path to the mailaddress of the forwarding mailaccount. So the message goes to this mailaddress and will be forwarded to Teleom's server ... and will be refused, because it contains the SPAM as attachment ... and so on.
As I remember, my solution was to reduce the amount of returnlines. In configuration of Core Module on tag "General" type in i.e. a 15 for returnlines. Try it (may be you must reload Mercury).
bye Olaf
<p>Next try ... the forum-software said, that I am not allowed to write in this forum?!
</p><p>OK ... it seems, that the server of Telekom and Mercury are playing pingpong due to that forward / bounce rule. I guess I had that problem too a long time ago with Mercury/NLM (but not due to forwarding):
</p><p>When Mercury is forwarding the mail, Telekom's server refuses it due to SPAM. Mercury generates a message on this error (appending the mail) to Postmaster and to the mailaddress standing in "return-path" in the header of that mail. I asume while forwarding Mercury changes return-path to the mailaddress of the forwarding mailaccount. So the message goes to this mailaddress and will be forwarded to Teleom's server ... and will be refused, because it contains the SPAM as attachment ... and so on.</p><p>As I remember, my solution was to reduce the amount of returnlines. In configuration of&nbsp; Core Module on tag "General" type in i.e. a 15 for returnlines. Try it (may be you must reload Mercury).</p><p>bye &nbsp; Olaf</p><p>&nbsp;</p>