On Sat, 28 Feb 2015 16:13:18 -0800, Hugo Osvaldo Barrera <[email protected]>
wrote:
Use sieve on the LDA side for that, and reject messages. You can provide
a
custom message when rejecting via sieve.
Your second choice is to pass it via some proxy (look at the examples on
how
DKIMProxy is used), and reject the message there according to it's
origin.
My only concern with using sieve is that it might be difficult to write
filters that catch all of the custom domains assimilated by the Google
Apps borg.
People using any of those providers already don't care about PRISM
though, so
you'll most likely just stop receiving email from them. If they cared to
move
out, they would have moved already.
I agree but would prefer to keep this thread focused strictly on the
technical implementation aspects.
I'm happy to have a discussion about the philosophical issues but would
like to take that off list or at the very least spun off in a separate
thread.
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
