[Dovecot] sieve plugin - reject sends MDN. Can it 550 reject ?
I'm using dovecot-1.2-sieve-0.1.15 with dovecot-1.2.11.
I have a reject test filter that looks like this:
require "reject"; if header :contains "subject" "reject" { reject "bye"; }
Is there any way to get a "reject" filter to send back a 550 reject as detailed in http://ietfreport.isoc.org/idref/rfc5429/#section-2.5 rather than a MDN?
The MDN can result in blowback spam. :-(
Thanks, Ken
-- Ken Anderson Pacific Internet - http://www.pacific.net
on 4-15-2010 2:05 PM Ken A spake the following:
I'm using dovecot-1.2-sieve-0.1.15 with dovecot-1.2.11.
I have a reject test filter that looks like this:
require "reject"; if header :contains "subject" "reject" { reject "bye"; }
Is there any way to get a "reject" filter to send back a 550 reject as detailed in http://ietfreport.isoc.org/idref/rfc5429/#section-2.5 rather than a MDN?
The MDN can result in blowback spam. :-(
Thanks, Ken
Only the MTA can do that. By the time dovecot gets the message it has already been accepted, and it is too late for a reject. You could try a milter that runs in front of your mailserver and can reject a message during the data phase. Once accepted, and the connection is closed, there is no way to do what you ask.
On 4/15/2010 4:37 PM, Scott Silva wrote:
on 4-15-2010 2:05 PM Ken A spake the following:
I'm using dovecot-1.2-sieve-0.1.15 with dovecot-1.2.11.
I have a reject test filter that looks like this:
require "reject"; if header :contains "subject" "reject" { reject "bye"; }
Is there any way to get a "reject" filter to send back a 550 reject as detailed in http://ietfreport.isoc.org/idref/rfc5429/#section-2.5 rather than a MDN?
The MDN can result in blowback spam. :-(
Thanks, Ken
Only the MTA can do that. By the time dovecot gets the message it has already been accepted, and it is too late for a reject. You could try a milter that runs in front of your mailserver and can reject a message during the data phase. Once accepted, and the connection is closed, there is no way to do what you ask.
That makes sense, duh. Default behavior is to send an immediate MDN, which is not what I expected. I found the setting in to get it to Defer, "EX_TEMPFAIL" instead (quota_full_tempfail = yes). That makes it compatible with my existing over quota monitoring. :-)
Thanks, Ken
-- Ken Anderson Pacific Internet - http://www.pacific.net
Ken A wrote:
That makes sense, duh. Default behavior is to send an immediate MDN, which is not what I expected. I found the setting in to get it to Defer, "EX_TEMPFAIL" instead (quota_full_tempfail = yes). That makes it compatible with my existing over quota monitoring. :-)
Note that Sieve currently does not respect the -e deliver option:
http://wiki.dovecot.org/LDA#Parameters
I have plans to fix this together with implementing the ereject extension. Implementation is commencing, bot not trivial however.
Regards,
Stephan
participants (3)
-
Ken A
-
Scott Silva
-
Stephan Bosch