Re: Sieve help

2003-06-13 Thread Ken Murchison


pnelson wrote:
On Fri, 2003-06-06 at 10:29, Ken Murchison wrote:

Patrick Nelson wrote:

Running Cyrus-imap 2.1.13 on RH9 and alls well.  Moved the whole company
off of exchange a week ago and so far not even a hickup.
So, now I want to explore sieve, but I'm not sure where to begin.  Is
there any good docs you all would recommend.  Or maybe highlight to me
your course of knowledge on this? 
For writing scripts or configuring Cyrus to handle them?

For authoring, this might be the best place to start.

http://www.cyrusoft.com/sieve/

For setup, the Cyrus docs _should_ be enough to get you started.


Have sieve working but the cyrusoft sites sieve docs are kind of
lacking.  Anyone else know of a good ole' howto on the syntax of sieve?


There isn't much.  The best docs are the RFCs and IDs themselves.  They 
are all listed on the doc/specs.html page in the distro.



--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp


Re: Sieve help

2003-06-13 Thread pnelson
On Fri, 2003-06-06 at 10:29, Ken Murchison wrote:
> Patrick Nelson wrote:
> > Running Cyrus-imap 2.1.13 on RH9 and alls well.  Moved the whole company
> > off of exchange a week ago and so far not even a hickup.
> > 
> > So, now I want to explore sieve, but I'm not sure where to begin.  Is
> > there any good docs you all would recommend.  Or maybe highlight to me
> > your course of knowledge on this? 
> 
> For writing scripts or configuring Cyrus to handle them?
> 
> 
> For authoring, this might be the best place to start.
> 
> http://www.cyrusoft.com/sieve/
> 
> 
> For setup, the Cyrus docs _should_ be enough to get you started.

Have sieve working but the cyrusoft sites sieve docs are kind of
lacking.  Anyone else know of a good ole' howto on the syntax of sieve?



Re: Sieve help

2003-06-06 Thread Ken Murchison


Patrick Nelson wrote:
Running Cyrus-imap 2.1.13 on RH9 and alls well.  Moved the whole company
off of exchange a week ago and so far not even a hickup.
So, now I want to explore sieve, but I'm not sure where to begin.  Is
there any good docs you all would recommend.  Or maybe highlight to me
your course of knowledge on this? 
For writing scripts or configuring Cyrus to handle them?

For authoring, this might be the best place to start.

http://www.cyrusoft.com/sieve/

For setup, the Cyrus docs _should_ be enough to get you started.

--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp


Re: sieve help

2002-10-30 Thread Damian Gerow
Spake Damian Gerow on 30/10/2002, 10:59:02 -0500:
>> Here is what I did to get sieve to working on Solaris 8 with cyrus-imapd-2.1.9.
>
> Alright, I just noticed that I have 2.0.16 installed.  I'm going to
> update to 2.1.9, and see if that will help any.  Arg.  Thanks for the
> help.
 
That fixed it.

So a note to all FreeBSD users -- looks like the cyrus-imapd port
doesn't work properly with sieve.  Install cyrus-imapd2 instead.

Now I just need to figure out why my script is failing...  :)




Re: sieve help

2002-10-30 Thread Damian Gerow
Spake Mark Keasling on 29/10/2002, 11:24:21 +0900 (JST):
> Here is what I did to get sieve to working on Solaris 8 with cyrus-imapd-2.1.9.

Alright, I just noticed that I have 2.0.16 installed.  I'm going to
update to 2.1.9, and see if that will help any.  Arg.  Thanks for the
help.




Re: sieve help

2002-10-29 Thread Mark Keasling
Hi,

Here is what I did to get sieve to working on Solaris 8 with cyrus-imapd-2.1.9.
I don't think these actions are OS specific so I'm passing them along.

If you haven't already done so, check the documentation...
Man pages: imapd.conf(5), cyrus.conf(5), timsieved(8), master(8)
doc files: install-sieve.html, sieve-protocol.html, sieve.html

You need to have a sieve line in the /etc/cyrus.conf file's services section
something like:
-/etc/cyrus.conf-
<...>
SERVICES {
  <...>
  sieve cmd="timsieved" listen="sieve" prefork=0
  # this is only necessary if you are using notifications
  notifycmd="notifyd" listen="/var/imap/socket/notify" proto="udp" prefork=1
  <...>
}
<...>
-

In /etc/services add a line like the one below if one is not already there:
-/etc/services--
<...>
sieve   2000/tcp


There are some configuration parameters in the /etc/imapd.conf file that also
need to be set:
-/etc/imapd.conf-
<...>
##  I'm not using home directories to store scripts. So I comment out
# sieveusehomedir: yes
##  and set the location where scripts are stored.
sievedir: /var/imap/sieve
## the following is necessary to enable notifications (I think)
sievenotifier: null
sendmail: /usr/lib/sendmail
notifysocket: /var/imap/socket/notify
--

Restarting the master process should allow you to access the sieve server.

Test by attempting to telnet to the sieve server.  If you can connect, enter
"logout" to exit.  After this is successful, you can use sivtest or sieveshell
to fiddle around.  Sample session using cyrus-imapd-2.1.9 should look like:
$ telnet localhost sieve
T> Trying 192.168.0.1...
T> Connected to imap.example.com.
T> Escape character is '^]'.
S> "IMPLEMENTATION" "Cyrus timsieved v1.1.0"
S> "SASL" "PLAIN OTP LOGIN GSSAPI DIGEST-MD5 CRAM-MD5"
S> "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational 
regex"
S> OK
C> logout
S> OK "Logout Complete"
T> Connection closed by foreign host.
$ sivtest -u user -a user -p 2000 imap.example.com
S: "IMPLEMENTATION" "Cyrus timsieved v1.1.0"
S: "SASL" "PLAIN OTP LOGIN GSSAPI DIGEST-MD5 CRAM-MD5"
S: "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational 
regex"
S: OK
C: AUTHENTICATE "DIGEST-MD5"
S: {224}
S: <...b64data...>
Please enter your password: 
C: {340+}
<...b64data...>
S: OK (SASL "<..b64data...>")
S> Authenticated.
S> Security strength factor: 128
C> listscripts
S> "aaa"
S> "bbb"
S> "ccc" ACTIVE
S> OK
C> getscript "aaa"
S> {105}
S> require ["reject","fileinto"];
S> if address :is :all "From" "[EMAIL PROTECTED]"
S> {
S>   reject "testing";
S> }
S> 
S> OK
C> logout
S> OK "Logout Complete"
S> Connection closed.

Regards,
Mark Keasling <[EMAIL PROTECTED]>