[index] [text page] [<<start] [<prev] [next>] [last>>]
Page 77: How the design affects policy

Page 77

Per-user stuff especially painful in a federated university, and
filtering is much more complicated than @cam (say).

Making the recipient do the work is a change from past practice, but
it makes sense because a problem with the content of a message
doesn't mean it can't be delivered, so a bounce isn't required.

Note that non-hubbed servers that use ppsw as a backup MX will not
have their email filtered during a temporary outage, since if the
email would have gone to the server directly the recipient address
will match MailScanner's opt-out rules.

Generated by MagicPoint