[Dovecot] Sieve Notify Error

[Uldis Pakuls]

Leroy Philippe wrote:
> Hello,
>  
> I'm using dovecot 1.1.1 and dovecot-sieve-1.1.5  .
> I'm very interested in the notify plugin, I've tried many code which have generated some errors (coding errors that have been arrived in the .dovecot.sieve.err) but these errors are fixed.
> But Notify is still not working, I've the following in mail.log :deliver(webmaster at xxx.net): SIEVE ERROR: Unknown [unimplemented] notify method mailto:phxxx at xxp.comhere is my .dovecot.sieve :require ["fileinto", "notify"];# Move spam to spam folderif exists "X-Spam-Flag" {  fileinto "spam";  # Stop here so that we do not reply on spams  stop;}notify  :method "mailto:phxxx at xxp.com":message "Vous avez recu un message sur votre adresse";           # Don't send any further notifications           stop;What's wrong? I've tried example from http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-12.txt but they are not working.Thanks for helpPhilippe 
> _________________________________________________________________
> Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
> http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
>   
Dovecot sieve implementation is based on RFC draft-ietf-sieve-notify-2.txt

notify

 :method "mailto"
 :options "user at example.com"
 [...]

Mail address (one or more) must be specified as options to method.

Current dovecot's sieve code don't accept URI form "mailto:user at domain.com" specified in latest versions of RFC. Use ":options" instead   


Dovecot's sieve code originaly is taken from cyrus imapd.  And cyrus 
works this way.  Notify method  was unimplemented in first release of 
dovecot's sieve plugin by Timo.  I wrote patch  which implements this 
method. Most code actualy was taken form cyrus "notifyd" sources (as all 
sieve parsing code Timo adopted form cyrus unchanged.). Later Timo 
included this patch in 1.0 stable branch. Things changed... but notify 
methods code remains unchanged... my be it's time to implement latest 
RFC specifications.



Uldis