Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: herman on July 04, 2009, 10:04:28 PM
-
Doing some testing with Zarafa, after a while playing with zarafa, I want to disable zarafa for mail.
How can I let the mail not doing to zarafa again ( the opposite of 'config setprop zarafa-server GlobalForward enabled' )
Tia
Herman
-
Hi
Try
config setprop zarafa-server GlobalForward disabled
-
Thanks for the reply shawnbishop.
I tried that already yesterday. But it didn't work.
Solfed the problem with a fresh install of version 7.4
Thank anyway,
Herman
-
Blast, I wanted to know that too, and I do not have the option to re install.
Drift
-
herman
config setprop zarafa-server GlobalForward disabled
Did you follow that with the appropriate commands to instigate that change ?
I don't use zarafa, but these should cover all possibilities (theoretically only the post-upgrade and reboot should be necessary but as I don't use zarafa the other commands may be needed, it won't hurt to issue them as well).
config setprop zarafa-server GlobalForward disabled
/etc/e-smith/events/actions/qmail-update-user
/etc/e-smith/events/actions/zarafa-create-user
/etc/e-smith/events/actions/zarafa-update
signal-event post-upgrade
signal-event reboot
Alternatively if that does not achieve the result required, then
config delprop zarafa-server GlobalForward
(which will remove the db entry and the default value will be applied by the post upgrade command)
/etc/e-smith/events/actions/qmail-update-user
/etc/e-smith/events/actions/zarafa-create-user
/etc/e-smith/events/actions/zarafa-update
signal-event post-upgrade
signal-event reboot
-
You beat me to the post, thanks for all that information that I shall make a note of.
I only needed to kill it for a little while, whilst I transferred the data from another server, the global disable does not make a blind bit of difference. The way I found was just to delete the use :-)
Thanks
Paul