upgrading Dovecot and adding Sieve

[scottgutman]

Hi. I just started using ebox and let me say thanks to the developers and contributors.  Great job.

I wanted to add SIEVE to Dovecot and it looks like the best way to do that is to upgrade dovecot to 1.2.  I have a few questions to that end.

• 1. Is there a good way to upgrade dovecot 1.0.10 (ebox 1.2) to dovecot 1.2?
• 2. What changes need to be made to /usr/share/ebox/stubs/mail/dovecot.conf.mas
• 3. What is the best way to install Sieve?
• 4. Should I consider upgrading to EBox 1.3
• 5. Can SIEVE be installed without upgrading Dovecot?

[J. A. Calvo]

• 4. Should I consider upgrading to EBox 1.3

If you do that we will be very grateful as you will help us with the testing. However, I don't recommend to do this in a production machine, as the migration is not straightforward, better if you test a fresh install.

[scottgutman]

The box is being used in a production environment. 
I would like to help you with testing though. 

If I wanted to move to help you, what would we do?
How can I help you and you help me?

I am using almost all of the ebox features.  The features used are the PDC, File server, Email host, VPN Server, mail filtering, traffic shaping, firewall, LDAP Server, DNS server, DHCP server and router.

[J. A. Calvo]

If you want to help us testing 1.3, you can install it on a different test machine, for example a Virtual Machine. Once you have eBox 1.3 ready in the test machine, you can try to make a backup of your production machine and restore on the test one. If you get all the services on the new eBox working successfully you are ready to do the migration. Of course, any problem you encounter you can tell us and we will try to help you

[scottgutman]

i have an identical server to load 1.3.  I will do that tomorrow.

Do you have any suggestions on how to do the backup and restore? Is there a document i should follow, besides the pdf manual?

[J. A. Calvo]

Do you mean backup of the eBox configuration? Have a look at this: http://doc.ebox-platform.com/en/backup.html#configuration-backups

[Javier Amor Garcia]

Hello,
 if you upgrade to ebox-mail-1.3.10 or greater it has already built-in sieve support so you dont have to touch any template file.

[scottgutman]

I noticed in ebox 1.2 in the master.cf.mas, that the line for dovecot is commented out

#dovecot   unix  -       n       n        -      -       pipe
#  flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d $(recipient)

• 1. If deliver never gets the mail from postfix, can SIEVE Work? 
• 2. If I enable the line in master.cf, will it break any other part of the mail/spam/AV/filtering system?
• 3. Is EBox 1.3 ready to be used in a production environment?  What is not working in 1.3 as of now?

Thanks for your help so far.

[Javier Amor Garcia]

This commented line was a  leftover from development process so dont try anything with it. In 1.3 dovecot transport is used so SIEVE is not invoked by postfix deliver protocol but by dovecot's.

1.3 is not intended as production version, is a testing version and you should expect a greater rate of errors than in a stable version. However errors in 1.3 are fixed we are found and new packages with fixes released with regularity. (the latest fixes were released the 24th of this month).

If you want to see what sort of errors could you expect, go to the Announcements' forum and see what things of errors are fixed in the various 1.3.x releases

[scottgutman]

If i don't use sieve, is there another way to have mail routed to specific folders under inbox. Is there another way to institute rules for the mail?

[jsalamero]

i'm afraid only sieve is the solution for per user filtering ...

[scottgutman]

I installed 1.3 on another box, but i am having a problem importing the LDAP users info

[Javier Amor Garcia]

As jsalamero says, sieve is the only filtering solution supported by eBox server. Another options is that users filter themselves their mail using their mail program's filters. Using another server-based filter, like procmail, will need large custom changes.

As for the importing thing, have you tried with a backup?. If you have tried with a backup what is the exact problem?

[scottgutman]

When I tried to restore with the backup from 1.2, the restore failed and crashed.  Then when I tried to reboot, any service that used LDAP would not start and I was not able to access the eBox server except from the console.

Here is the exact error after attempting to restore.

Some error has happened in eBox:

read_file '/var/lib/ebox/tmp//backup.CY0r2X/eboxbackup/users.bak/master-config.ldif' - sysopen

I tried to attach the logs from the eBox 1.3 server after the restore, but the uploader says it's full.  you can download them here.

https://linux105.mysite4now.net/fphcuser/www/error.log
https://linux105.mysite4now.net/fphcuser/www/ebox-restore.log

Thanks for your help.

[Javier Amor Garcia]

Sorry for the delay.

There have been important changes in the LDAP configuration between 1.2 and 1.3. Unfortunately, the backup compatibility between 1.2 and 1.3 in LDAP data is not done yet. We plan to have it donme in 1-2 weeks.

In the meantime, how many users have you? is feasible to migrate them by hand or not?