[Top] [All Lists]

Re: [sieve] On "reject" and :fcc

2017-01-18 06:07:45
As it turns out, the point with soon be moot w.r.t. Cyrus. I realized last night that I never implemented ereject, and when I do, Cyrus will reject at the LMTP level and therefore no DSN or MDN.

On 01/18/2017 04:06 AM, Sebastian Hagedorn wrote:

--On 17. Januar 2017 um 16:24:12 -0800 NED+mta-filters(_at_)mauve(_dot_)mrochek(_dot_)com wrote:

Sometimes you want to keep the junk that was sent to you while saying to
the sender that nobody got that message.  Making that hard within the
standard will just cause people to work around it by doing things like
capturing all mail that hits the MXes before sieve processes it.  Not
providing a facility because it can be used to lie doesn't change that.

As I said before, if you really think it's perfectly OK to provide a
mechanism to your users that allows them to instruct the system to lie in
an offical system message about them not having gotten the content of a
mail message, then we have nothing further to talk about.

For the record, I agree with Bron on this. It's up to the users if they want to lie.

Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

sieve mailing list

<Prev in Thread] Current Thread [Next in Thread>