[Mimedefang] Questions about stream_by_recipient and problems it creates.

[Matthew Schumacher]

List,

I am deliberating over the best way to handle email where two recipients
want different spam settings and can't seem to find a solution I like.
Seemingly there are only two real solutions:

1.  Detect the spam and reject it in filter_end which is very clean, but
causes problems when there are two recipients, one which wants the
message, and one who wants it to be bounced as spam.

2.  Call stream_by_recipient and re-queue the message for each recipient
causing all messages to multiple recipients to be accepted then later
rejected if detected as spam.  This also causes a new bounce message
sourced from MAILER-DAEMON to be sent to the sender, which in the case
of spam, is almost always spoofed.

I really dislike both solutions.  Solution 1 doesn't offer the
flexibility to have one recipient accept and tag the message while the
other recipient can opt to have the message rejected.  Solution 2 just
feels like a dirty hack that will cause a bunch of load, double bounces,
rejected bounce messages, and other problems.

So my question to the list is, what have you all done to get around
these problems or am I not seeing a better way to handle this?

Thanks,
schu