I just came across a request from a customer asking for combining all the Delivery Failure Reports the user gets when they do a mass mailing to a large group. This is a very common request as it's quite common for any user to use an already existing group and send mail to them. We do this all the time in our organization. And of course, some businesses do this as part of their business for mass-mailing. Mailing groups are never up-to-date, so you are bound to receive 1 or more delivery failures. And if you are doing a mass mailing, the number of delivery failures can be more than 100 (or even in thousands). Once you have those, opening each to figure out which ID needs to be removed from the mailing list becomes a nightmare, along with how the heck do I manage my inbox after this.
I feel with the Notes/Domino platform being a great application development platform, there's a very easy solution, which can be custom developed for your own use-case.
First of all, I believe doing this in a product in a generic way might be too complicated. When you do mass mailings, the mails are sent by the router, and it will receive the failures one at a time. It will never get all of them at the same time. Everything depends on the destination server returning the failure. So some reports might come quickly while others can be delayed by minutes. So it would not be prudent to have the router deal with these.
Which is why I feel a custom solution based on your needs is an ideal one. Here are my thoughts:
-- If you look at the delivery failure, the message is from "PostMaster", with a subject starting with "DELIVERY FAILURE" (notice the case as well), and the message body contains:
Subject: test email. Ignore if you get it.
was not delivered to:
- Once you have this knowledge, you can simply right an Agent in your mailfile (you could then publish this as part of the customized mail template in your organization), where the user provides the original mail and runs the agents with the context of the mail that was sent (to get the Subject out of it).
- The agent can run through your mail file, looking for messages that fit the above pattern. Once it finds a mail, it can simply keep appending the "email address" and the reason (text after 'because:') into a new mail, and once it has scanned the entire inbox to remove all those mails (maybe move them to a backup folder) and send the newly combined mail with all the delivery failure reports to the same user.
That's it. This will meet the required for a combined report of all the "Delivery Failures" to the user.
This is the beauty of Notes/Domino and the App Dev.
Of course, if you don't want to do all of this, a simple rule can be created to move all the mails from "PostMaster" with a subject containing "DELIVERY FAILURE:" into a new folder.
Looking forward to comments or if someone has already created an agent within their organization.