On Fri, 27 Apr 2018, Dianne Skoll wrote:
On Fri, 27 Apr 2018 14:39:43 -0500 (CDT)
David B Funk <dbf...@engineering.uiowa.edu> wrote:
[snip]
Define two classes of recipients:
class A == all users who want everything
class B == all users who want "standard" filtering
This works if you have a limited number of classes, but in some cases
users can make their own rules and settings so the number of classes
can be the same as the number of RCPTs.
Even in the two-class case, there's still a delay for the subsequent
class(es).
If you have that many different classes of recipients, just set the number of
allowed recipients/transaction to one and be done with it.
The delay is entirely up to the sending side, they could immediately retry the
subsequent recipients.
I was just trying to suggest a solution to your conundrum that didn't require
you to drop messages. I didn't say it was optimal, just avoiding the loss of
messages.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
