[Top] [All Lists]

Re: Sieve reject at SMTP time possible with which implementations?

2003-10-23 05:24:53

On Thu, 23 Oct 2003 ned(_dot_)freed(_at_)mrochek(_dot_)com wrote:

Which in turn means that handling reject at the SMTP level would be 
with the sieve specification.

Yes, thats what I meant ;)

Of course nothing prevents an implementation from adding a separate action
other than reject for this. But SMTP level errors don't match up to sieve
actions very well. Why? Because sieve evaluation almost always requires having
the entire message on hand. In SMTP this means the only reponse code that's
left is the last one, where the server accepts or rejects the message on 
of all recipients. This becomes a problem when there are multiple recipients
and some reject the message and some do not.

While difficult/impossible in the SMTP situation, it can be done at the
"SMTP level," provided the last hop is over LMTP instead of SMTP, since
LMTP gives per-recipient status codes.


Rob Siemborski | Andrew Systems Group * Research Systems Programmer
PGP:0x5CE32FCC | Cyert Hall 207 * rjs3(_at_)andrew(_dot_)cmu(_dot_)edu * 
Version: 3.12
GCS/IT/CM/PA d- s+: a-- C++++$ ULS++++$ P+++$ L+++(++++) E W+ N o? K-
w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-@ b+ DI+++ G e h r- y?