Idea ID 2701623
We want the GWIA scanner function back which was part of GWAVA/SMG up to version 6.x. We use this only for outbound mail scanning. The reason we've setup outbound mail in such a way is that it has the benefit that messages are scanned only in this direction while maintaining the GroupWise statuses in the mailbox for "Transferred"; meaning the message has really left the GW system and so the company and if there is a problem this is always with the recipient side. We do not want an outbound appliance in between the GWIA and the internet as this could "tell" the user the message is Transferred, but in the meantime the Appliance could have blocked it anyway. In that vase the user and admin have to keep an eye on the appliance for outbound blocked mail. A minute phone call with the helpdesk/admin can tell the user "transferred" always means a missing message is a problem on the recipient site. With a GWIA Scanner in place and a situation where a message gets blocked by GWAVA/SMG the GroupWise message status will be "On the way", which is telling the user the message has not yet left the GW system. So both the admin and the user now know the issue is "internal" and in that case never with the recipient side. This makes troubleshooting a lot easier and takes away a lot of discussions "where" the issue is and "who" is responsible. That also saves customers (could be expensive) investigation by a 3rd party even if the result is the problem is with the recipient. This has proven to be very effective in the past where a customer called the servicedesk/admin telling "Outbound mail is not working!" when they send a mail and the recipient did not receive such. The only question to ask now is what the message status in the (web) mail client is, and in that says "transferred" we can say for sure it left the company and the problem is "on the other side".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.