Manfred, I am a little confused as to why you would send a spam notification message to the distant end recipient? If they were in the same domain as the company, maybe. If you do things like that then the ASG sort of becomes a spam generator. My opinion and I expect that is the same as the original poster, you would only want mail error messages kept within your company and on your side of the firewall. The distant user will not be in likely hood configured in your ASG, so can't release the message. What you are suggesting would appear to be a bug, not a feature
Manfred, I am a little confused as to why you would send a spam notification message to the distant end recipient? If they were in the same domain as the company, maybe. If you do things like that then the ASG sort of becomes a spam generator. My opinion and I expect that is the same as the original poster, you would only want mail error messages kept within your company and on your side of the firewall. The distant user will not be in likely hood configured in your ASG, so can't release the message. What you are suggesting would appear to be a bug, not a feature
in my opinion it is a feature. The distant end recipient gets only the spam report if the ASG scans it's messages and catch some of them. It is to the interest of the recipient to get a spam report of their own messages.
If the ASG scans messages, why should the recipient not be notified if something wasn't delivered?
If you configure the ASG in the correct way it should be possible to release a spam message for a distant end recipient.
Email Securitz -> End User Spam Report -> Advanced:
1. The hostname should be resolvable from outside.
2. The allowed networks should include the external network.
Good morning Manfred, I would have thought an attached statement to the e-mail would be a better arrangement and cause less e-mail traffic, some which might end up being identified as spam.
