Re: List of open issues with Sieve reject draft(draft-ietf-sieve-refuse-reject-02.txt)

On Tue, 2006-07-11 at 13:59 +0100, Nigel Swinson wrote:
> > there are no logging actions in Sieve, but most implementations can
> > provide such logs without it being triggered by explicit script actions.
> 
> Well our implementation doesn't provide any end user accesible
> operational logs, so using fileinto seems like an excellent low cost
> implementation.

what do you gain by doing reject?  no spammer ever washes their lists
based on response codes, anyway.  (*perhaps* after negative response to
RCPT TO, for DATA, no way.)

> > I don't think this is sufficient reason to allow an e-mail system to
> > misrepresent the delivery status.
> 
> I'm quite happy to interpret reject as "I never want to see any mail
> like that ever again".  If the server carries on delivering/processing
> that message then I think that's up to the mail server.

RFC 2821, section 4.2.5:

   When an SMTP server returns a permanent error status (5yz) code after
   the DATA command is completed with <CRLF>.<CRLF>, it MUST NOT make
   any subsequent attempt to deliver that message. 

I don't think that's open to interpretation.
--

-- 
Kjetil T.