-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aaron Stone wrote:
> That's because there are no such defined variables... it's done with
> matching now.
> See section 3.2 of RFC 5229: http://www.ietf.org/rfc/rfc5229.txt
>
> The only right place for this code is in the interpreter itself. I more
> than welcome work on libSieve! It's great to new people submitting code,
> and even though I have had rather limited time lately, I'm still going
> to try to see that the code ends up in the right places ;-)
>
> Cheers,
> Aaron
>
Aaron
I'd be happy take a look at libsieve modifications. I probably won't
have the same level of autonomy in understanding what to change, so I
may need additional advice along the way :-)
I'd really like to add variables extension to libsieve, so then the
patch for sieve notification in dbmail can be simplified.
However, I would start with something simpler: in the current dbmail
patch (once again by comparison to cyrus functionality) I am reading the
destination of the notification from the "options string". This is
exactly how squirrelmail writes it and how cyrus can read it.
However, the latest ietf drafs states: "Notify tag ":options". This tag
is not used by the mailto method."
So I'd like to get the destination address from the right place, which
is from the string following "method".
Usage: notify [":from" string]
[":importance" <"1" / "2" / "3">]
[":options" string-list]
[":message" string]
<method: string>
Also ":method" is no longer a keyword followed by the method, but a
parameter stating the method.
On an additional point, priority parameter (low, medium, high) has now
been replaced by an additional keyword ":importance" and different
parameter values.
- From looking over the code, I think the first point to intervene is:
sv_parser/sieve_lex.l for the new tokens
sv_parser/sieve.y for the grammar modifications
sv_interface/script.c and callbacks.c for addtional value (destinatino
URI of the notification) to return to calling program
does that make sense? Or am I looking in the wrong places? Any
additional things to change?
thansk,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHv9Dmd4I3jTtt9EIRAnxrAKDSJvt4TQkzLg/wOPKJUlBd/6zpUwCcDkTX
WVl0UjrlOGrVI/W2XSRoprU=
=TzbA
-----END PGP SIGNATURE-----
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
