Just updated my customer's server to 10.4.3. The avelsieve install now works. It fixes the problem people have been having with sieve! Yippee! Vacation and other server side filters are now working! Cool. No other problems observed as yet. It seems a lot of bugs have been squashed and that it has been beta tested thoroughly! It was in testing for about 3-4months I think!

Cool.

timsieved is definately fixed and avelsieve seems to be working correctly. I can see my rules saved out to /usr/sieve/k/kevinhalpin/phpscript.script. However they do not filter my mail. Permissions for /usr/sieve are cyrusimap:wheel. The contents of my directory are rw-------. Under 10.4.2 I could monitor /var/log/mailaccess.log for sieve activity. But now I don't see anything. Even if I revert back to the sieve script I had created manually (under 10.4.2) which _does_ still work.

Kevin
mac-fusion

I have just upgarded to 10.4.3 and having problems getting my out of replys to work from a clean set up can anyone give me their set up checklist.

Thanks

Not sure what is going on here with timsieved

Any ideas?

Nov 3 19:47:57 server master[55]: process 4706 exited, signaled to death by 10
Nov 3 19:47:57 server master[55]: service sieve pid 4706 in READY state: terminated abnormally
Nov 3 19:47:57 server master[4708]: about to exec /usr/bin/cyrus/bin/timsieved
Nov 3 19:47:57 server sieve[4708]: executed
Nov 3 19:47:57 server sieve[4708]: DBERROR db4: fatal region error detected; run recovery
Nov 3 19:47:57 server sieve[4708]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery

Hi All

I'm getting the same error as BING.

What I've done - Changed the User to CyrsuImap in the TimSeive installer post install so that it installs OK. Trashed the packages and reninstalled SASL, BDB and AvelSieve. Checked the permissions on the pwauxprop.la and pwauxprop.sa and USR/Sieve.

Nov 4 12:18:51 server1 master[11015]: about to exec /usr/bin/cyrus/bin/timsieved
Nov 4 12:18:51 server1 sieve[11015]: executed
Nov 4 12:18:51 server1 sieve[11015]: DBERROR db4: fatal region error detected; run recovery
Nov 4 12:18:51 server1 sieve[11015]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Nov 4 12:18:51 server1 master[8424]: process 11015 exited, signaled to death by 10
Nov 4 12:18:51 server1 master[8424]: service sieve pid 11015 in READY state: terminated abnormally
Nov 4 12:18:51 server1 master[11017]: about to exec /usr/bin/cyrus/bin/timsieved
Nov 4 12:18:51 server1 sieve[11017]: executed
Nov 4 12:18:51 server1 sieve[11017]: DBERROR db4: fatal region error detected; run recovery
Nov 4 12:18:51 server1 sieve[11017]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery

We've seen when the mail store gets corrupted - but teverything works fine on my webamail account.

Any Ideas?

NoSpin

You need to repair your cyrus db. We have articles on it as does the Apple KB. Plus the button in SA might even be working now, but I haven't tested it.

---

Breaking my server to save yours. Josh Wisenbaker www.afp548.com

As noted elsewhere on AFP548 (and the Apple forums), the latest Tiger updater has fixed the problems many were having with Sieve scripts, particularly using the SquirrelMail plug-in avelsieve. Below is guide to getting this working if you're starting from scratch, something I see a number of people are asking for...


Installing Web-Based Sieve scripting on OS X Server 10.4.3 using avelsieve
===========================================

Prerequisites
=========
I have used the following setup on a fresh install of Mac OS X 10.4 Server, with the 10.4.3 Combo Update installed. I then added a user to the local netinfo domain as a test case, and along with the default admin account have enabled mail for these users - Note: Open Directory is not currently running.

Web, DNS, SMTP and IMAP/POP are all running, and SquirrelMail has been enabled in Web Services. SquirrelMail has been tested for the two users mentioned above, and both accounts log in correctly, displaying empty mail boxes.

To enable sieve scripts via Squirrelmail
=========================

1) If it doesn't already exist, create the following directory as root or using sudo from the Terminal;

% sudo mkdir -p /usr/sieve
% sudo chown cyrusimap /usr/sieve
% sudo chgrp wheel /usr/sieve

Directory permissions should then look like;

drwxr-xr-x 3 cyrusimap wheel 102 Nov 3 21:31 sieve

2) Add (or un-comment if it exists) the following line to the /etc/services file. To do this you either need to su to root, or use sudo to edit the file using the Terminal.

sieve 2000/tcp # Sieve mail filtering

3) Stop the mail services from Server Admin.

4) On the Mail -> Settings -> Advanced tab, ensure you have IMAP set to allow 'PLAIN' as well as 'Clear' Authentication.

5) Start the mail services from Server Admin.

6) Run the following command using the Terminal, as any user;
% telnet localhost 2000

You should see the following output;

Trying ::1...
Connected to localhost.
Escape character is '^]'.
"IMPLEMENTATION" "Cyrus timsieved v2.2.12-OS X 10.4.0"
"SASL" "PLAIN"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex"
"STARTTLS"
OK

7)If you see this, your timsieved is working correctly. Use the escape character to leave the daemon, and quit telnet.

8) Download the most recent avelsieve distribution from the web page at http://email.uoa.gr/projects/squirrelmail/avelsieve_download.php. I used the more recent Dev Branch version: avelsieve-1.9.3.tar.gz, and haven't tested the earlier 1.0.1 version. If anyone has this working also, let me know.

9) Un-tar this in the squirrelmail plugins directory ( /usr/share/squirrelmail/plugins ), again as root or using sudo via the Terminal and cd into ( avelsieve/config/ ). Copy the example config 'config_sample.php' to 'config.php' IN THE SAME DIRECTORY (this is different from the V1.0.1 setup I believe). I didn't need to edit anything in the config.

10) Run the SquirrelMail config perl script, using sudo like so;
% sudo /etc/squirrelmail/config/conf.pl

Choose Option 8, "Plugins" from the menu, and enable "avelsieve" by selecting it from the resultant list. Save your changes and quit the utility.

11) Login in to one of the mail accounts using SquirrelMail, and the "Filters" menu should now be an option - choosing this allows you to create your sieve scripts, including a vacation mail 'auto-reply'.

12) Looking in the /usr/sieve/a/admin directory (for example) should show the following files;

lrwx------ 1 cyrusima wheel 12 Nov 4 11:41 defaultbc -> phpscript.bc
-rw------- 1 cyrusima wheel 232 Nov 4 11:42 phpscript.bc
-rw------- 1 cyrusima wheel 1056 Nov 4 11:42 phpscript.script


Please let me know comments and/or corrections, especially if you have achieved this differently.

Regards,

Ian Butler

Ian

Thankyou so much for those instructions.

I was able to fix my messed up install by dumping the 10.4.3 reciept and reinstalling the combo update. Following your instructions my server is now sending out vacation messages again.

Brialliant.

Steve

Thanks Ian

Sorted !!

Just remove recepit for 10.4.3 Server combo, followed your notes. all worked first go.

Bing

Has anyone had this issue? Rules seem to work fine, except for the notify me feature. It doesn't seem to send out e-mails. All else is working. I am running avelsieve ver. 1.9.3.

Thanks much!

I would follow the instruction above but have a concern. In my /etc/services file, I have port 2000 listed as "callbook". I'm happy to comment that out and out in the sieve line but wanted to make sure that is the right thing to do.

This is a fresh 10.4.4 install on a Mac Quad G5. I have had a lot of problems with this install. It appears (keep your fingers crossed) that my last small nit is lmtpunix can not find defaultbc. In fact, aside from /usr/sieve (which I just created), the whole directory tree is not there.

Currently, I have not enabled squirrelMail. I do not know what it is but assume it is a method to read mail via a web browser. I suppose I would like to get the sieve scripts working but I have not used them before. I'm actually just trying to get a sane stable platform. I think this error is not a real concern but thought I would try and fix it along the way just to make sure. The sieve stuff sounds pretty cool -- but, what computer science person ever takes a vacation? :-)

Thank you for your help

---

Thank you, Perry Smith

I have the same problem in that when I pico the services file, and add in the sieve line, the resulting file looks like this:

tcp-id-port 1999/tcp # cisco identification port
#
callbook 2000/udp # callbook
callbook 2000/tcp # callbook
# Devon Bowen
sieve 2000/tcp # Sieve mail filtering
wizard 2001/udp # curry

I can't install the timsieve installer that is provided under the 10.3 sieve article. On the assumption that helpful guide in this forum is the best way to work with 10.4.5 can anyone shed any light please?

Thanks

Justyn

Followed the instructions above, on a 10.4.5 server (that has since been upped to 10.4.6, but the problem exists on both).

I can get into Avelsieve and create filters no problem.

The problem arises when one of the rules is matched. I created a large message reject rule, an out of office reply test (which I removed pretty quickly) and a reject message if I try to send myself something. If any of the rules matched, instead of sieve creating the expected mail, I get the following in a mail from postfix:

Command time limit exceeded: "/usr/bin/cyrus/bin/deliver"

Any ideas out there?

ian, thanks a bunch for those instructions!!!
Enabling PLAIN authentication was the thing that did it for me.

For those of you fancy some security and who do not want to enable PLAIN can find a desciption of the solution here: http://discussions.apple.com/thread.jspa?threadID=131554&start=25&tstart=0 where "tknospdr" writes:
--------------------------------------
Posted: Jun 24, 2006 12:29 AM in response to: tknospdr

I answered my own question by finally taking the time to read the config.php file myself.
If you want your webmail to be a bit more secure and don't want to enable plain or clear...

Change line 48 in config.php from:
$sieve_preferred_sasl_mech = 'PLAIN';

to
$sieve_preferred_sasl_mech = 'PLAIN CRAM-MD5';

That's it, now you can sleep better at night, well at least I can anyway.
--------------------------------------

This was the one bit of information I was missing before I wanted to install it on my server

Hello forum,

I am getting this error:

Nov 4 12:18:51 server1 sieve[11017]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery

I have spent quite a bit of time trying to get it going using the various solutions posted in this forum and have had no luck.

We are looking to hire someone to take a look at our server and get timsieved working. Our server is in production and we would require that you work on the server in the evening after 6pm PST.

If you are interested please contact me directly.

Thanks
-Joe Crain

Then I would reccommend to take a look at http://osx.topicdesk.com They look extremely suited for a job just like yours

Thanks for the pointer TvE, I have sent them a request. If I have any luck I will post the results.

I have the same problem as you impax, I can't install the timsieved.pkg I downloaded from here. I got ahead and follow the directions given but I soon as I telnet the following madness ensues and I can't even end my telnet session no matter what I try. I have to start and stop mail services.

Jun 21 18:52:22 nameserver sieve[3214]: DBERROR: dbenv->open '/Volumes/Data/Mail/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 21 18:52:22 nameserver master[1833]: process 3214 exited, signaled to death by 10
Jun 21 18:52:22 nameserver crashdump[3215]: timsieved crashed
Jun 21 18:52:22 nameserver master[1833]: service sieve pid 3214 in READY state: terminated abnormally
Jun 21 18:52:22 nameserver crashdump[3215]: crash report written to: /Library/Logs/CrashReporter/timsieved.crash.log
Jun 21 18:52:22 nameserver sieve[3216]: DBERROR db4: fatal region error detected; run recovery

so i went ahead and skipped the telnet section, lo and behold I got filters into squirrelmail but guess what? after I click on filter the DBError drama kicks in again. Now my question is should I be using mailbfr to repair my whole mail database or is this just a fluke?

: DBERROR db4: fatal region error detected; run recovery
Jul 10 16:29:54 nameserver sieve[20368]: DBERROR: dbenv->open '/Volumes/Data/Mail/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Jul 10 16:29:55 nameserver master[303]: process 20368 exited, signaled to death by 10
Jul 10 16:29:55 nameserver crashdump[20369]: timsieved crashed
Jul 10 16:29:55 nameserver master[303]: service sieve pid 20368 in READY state: terminated abnormally
Jul 10 16:29:55 nameserver crashdump[20369]: crash report written to: /Library/Logs/CrashReporter/timsieved.crash.log
DBERROR db4: fatal region error detected; run recovery
Jul 10 16:30:07 nameserver sieve[20438]: DBERROR: dbenv->open '/Volumes/Data/Mail/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Jul 10 16:30:07 nameserver crashdump[20440]: timsieved crashed
Jul 10 16:30:07 nameserver master[303]: process 20438 exited, signaled to death by 10
Jul 10 16:30:07 nameserver master[303]: service sieve pid 20438 in READY state: terminated abnormally
Jul 10 16:30:08 nameserver crashdump[20440]: crash report written to: /Library/Logs/CrashReporter/timsieved.crash.log
Jul 10 16:30:08 nameserver sieve[20443]: DBERROR db4: fatal region error detected; run recovery
Jul 10 16:30:08 nameserver sieve[20443]: DBERROR: dbenv->open '/Volumes/Data/Mail/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery


This is the new error I'm getting, any help?

I got everything installed using this method for 10.4.10, but i didn't have to separately install timsieve, it was in my os install already, all i had to do was open up the port and install avelsieve....

however! i am having a problem where avelsieve will not send emails out, it will do all of its other jobs of filtering and moving and redirecting emails, but it will not send out vacation messages or rejection replies.

anyone have any advice? lmk!