--On 9 July 2009 11:27:55 -0400 Jorey Bump <list@xxxxxxxxxxxxx> wrote: > Ian Eiloart wrote, at 07/09/2009 10:46 AM: >> >> --On 9 July 2009 09:54:31 -0400 Adam Tauno Williams >> <adam@xxxxxxxxxxxxxxxx> wrote: >> >>>>> Ian Eiloart wrote, at 07/09/2009 05:39 AM: >>>>>> Except that the sieve server ought to be on the border MTA, so that >>>>>> the user can tell the server to reject the message at SMTP time. >>>>> That's not feasible for mail with multiple recipients. >>>> It is if your rule is to reject all email from a specific sender. >>> No, because the MTA either accepts or rejects a message [in >>> connection]. >> >> Not true. The MTA can decide *per recipient* whether to accept mail from >> a specific sender. > > How? Well, you have to have the right software to begin with. Some MTA software simply accepts all email, then decides what to do with it. You don't want that type. To understand how this works, you need to understand the SMTP protocol. Perhaps info-cyrus isn't the right place to be explaining that, but read through the example at <http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#SMTP_transport_example>. Imagine that theboss has blacklisted Bob, but Alice hasn't. -- Ian Eiloart IT Services, University of Sussex 01273-873148 x3148 For new support requests, see http://www.sussex.ac.uk/its/help/ ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
