Currently (and all along) when you delete an email set for delayed delivery (from sent items), it is still retained and sent from a file called ngwdfr.db. There is only one way to ensure an email that was set to send at a later date is removed is to delete this db file. Problem, any email from any user that was flagged to sent via delayed delivery is also recorded in this db file. Because the db is in the flaim format, you can't open this file to see what other mail is set to delayed delivery. Removing this file then removes any other user delayed mail from sending. I would think this is common sense that if you delete the sent item it should know enough to remove it from the delayed send db, but it does not remove it from the db. Not sure why this is set like this, but it's supposedly working as designed.
This needs to be fixed somehow. Whether it's an admin function or not, users think they are removing the email from being sent when it really isn't and the mail is being sent anyway.
Instead of one all encompassing db to track these, maybe individual db's for each user could be implemented.
by: Steve H. | over a year ago | Windows Client
Comments
Message Retraction is a big selling point for GroupWise. Being able to retract a message that has not been opened by the receipient is the concept. So having a message waiting to be delivered which has not been opened by the receipient yet falls under this concept. A GroupWise developer for sure can remove the one message entry being retracted from that ngwdfr.db.
Are you sure when you delete the sent item that you choose to delete from all mailboxes (aka retract). If you do not, then yes it will still send and will only remove your tracked copy