A user here sends out mass notifications and she selects the option in Delivery Options for “Do not notify me if recipient(s) are running out of office”. However, she consistently receives the OOO replies to these emails. Is there a bug with this feature when sending emails to mail groups? Or is it designed to only work with individual addresses?
Subject: Feature is intended to be used with groups…
Hi - This feature was designed primarily for the use-case of sending emails to large groups, so that shouldn’t be a problem. It works by tagging outgoing emails with a $autoforward=1 item, which signals the OOO code to ignore the incoming message.
The one bug I’m aware of is:
KMUR6NMDZB: “Do not notify me if recipient are running out of office” doesn’t create $autoforward field if click ESC when sending memo.
If the sender sets ‘do not notify me if…’ delivery option, and then sends the message by hitting and selecting “Send Only” – this delivery option is lost (flag is not added to email).
Are you able to confirm whether or not the user in question tends to send mail this way? Because we’d be very interested to know whether customers are hitting this bug, or whether there may be something going on that we haven’t found.
Otherwise, we’ve consistently seen this feature to work well.
Subject: User is clicking the Send button
She clicks the Send button… the email goes. Checked the sent mail and the $autoforward field is set to 1. Spoke to the user and this is the real scenario:
“I send 2 emails to a mailing list… one on Wednesday and one on Friday. I set the delivery option and then click Send. I do not get any OOO responses until Monday morning.”
Our OOO agents run every 30 minutes, so essentially, if she were to get an OOO response, it would be within 30 minutes. So it seems like it’s working… until Monday morning and then she’s bombarded with them.
Subject: Need more info…
Sorry, but we’d need more info before we could try to diagnose this. Is there any chance one of the two emails didn’t have the “Do not notify me if…” option set? The OOO responses that came in Monday morning – were they all for the same message, or a mix of both messages?
OOO responses sometimes back up and all come in a batch when servers are down. You’d want to look at the doc properties on the OOO responses to see when they were generated and where they got stuck.
And it’s actually the received messages where you’d want to check for the $autoforward flag. Finding this in a sent/saved copy is a good start – that confirms the sender did indeed set “Do not notify me if…” (again, do we know whether this is true for both the Weds and Fri messages?). But for any OOO responses that we think shouldn’t have been generated, it would be helpful to find the received emails that triggered these, and to check whether these have the $autoforward flag – which could potentially have been stripped by a gateway or a process somewhere along the line.
Also, are your servers and users mostly R8+? If so, you may want to consider moving to the OOO service, which is inherently more robust (and more trouble-free) than the OOO agent.
Subject: More info…
Just to clarify… yes… both the Wednesday and Friday emails in the sent view had the flag set. Unfortunately, I have to wait until the next time she sends these notifications to troubleshoot further because the OOO responses have been deleted. The distribution list is the entire company, so we can’t do a test. Sometime in mid-February is the next time these emails will go out. Once that happens, she has been instructed to retain the OOO responses so we can see who they’re coming from. Then we can check their inboxes to see if the flag was still set.
Subject: Have notified owner of OOO to response this