E-Mail Quota settings an then you can´t restart E-Mail daemon

[koehler@…]

here is the error. How can i repair it? Reinstall?

A really nasty bug has occurred Exception Unknown error at EBox::Ldap::setAttribute attribute 'quota' not allowed Trace Unknown error at EBox::Ldap::setAttribute attribute 'quota' not allowed at /usr/share/perl5/EBox/Ldap.pm line 712 EBox::Ldap::_errorOnLdap('Net::LDAP::Modify=HASH(0xc0286bc)', 'HASH(0x9e19e2c)') called at /usr/share/perl5/EBox/Ldap.pm line 373 EBox::Ldap::modify('EBox::Ldap=HASH(0xa636880)', 'uid=admin,ou=Users,dc=E-Server,dc=linux-itservice,dc=local', 'HASH(0x9e19e2c)') called at /usr/share/perl5/EBox/Ldap.pm line 541 EBox::Ldap::setAttribute('EBox::Ldap=HASH(0xa636880)', 'uid=admin,ou=Users,dc=E-Server,dc=linux-itservice,dc=local', 'quota', 0) called at /usr/share/perl5/EBox/MailUserLdap.pm line 341 EBox::MailUserLdap::setUserLdapValue('EBox::MailUserLdap?=HASH(0xc030684)', 'admin', 'quota', 0) called at /usr/share/perl5/EBox/MailUserLdap.pm line 813 EBox::MailUserLdap::setMaildirQuota('EBox::MailUserLdap?=HASH(0xc030684)', 'admin', 0) called at /usr/share/perl5/EBox/MailUserLdap.pm line 834 EBox::MailUserLdap::regenMaildirQuotas('EBox::MailUserLdap?=HASH(0xc030684)') called at /usr/share/perl5/EBox/Mail.pm line 428 EBox::Mail::_setMailConf('EBox::Mail=HASH(0xbfe7e74)') called at /usr/share/perl5/EBox/Mail.pm line 1287 EBox::Mail::_regenConfig('EBox::Mail=HASH(0xbfe7e74)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 627 EBox::Module::Service::restartService('EBox::Mail=HASH(0xbfe7e74)') called at /usr/share/perl5/EBox/CGI/EBox/RestartService.pm line 51 EBox::CGI::EBox::RestartService::_process('EBox::CGI::EBox::RestartService?=HASH(0x9006940)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262 EBox::CGI::Base::run('EBox::CGI::EBox::RestartService?=HASH(0x9006940)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120 EBox::CGI::Run::run('EBox::CGI::Run', 'EBox/RestartService', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19 ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec?=SCALAR(0xbd9bed4)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204 eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204 ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xbe6ab98)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xbe6ab98)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31 ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec?=SCALAR(0xbd9bed4)') called at -e line 0 eval {...} called at -e line 0

[juruen@…]

Could you please detail a bit more how you got this error, I'm failing to reproduce it...

[javier.amor.garcia@…]

This a LDAP error. Have you upgraded your eBox from a previous version?.

In any case, maybe you can fix it with this actions:

• in the console run the command 'sudo /usr/share/ebox/ebox-unconfigure-module mail'
• go to the administrative web interface to 'Module status' and enable the mail module again

Anyway, if this error is after an upgrade, please share with us what was your pevious verison

[javier.amor.garcia@…]

Unable to reproduce it, we will need further feedback to reopen this ticket

[anonymous]

Hi there,

I was geting the same error with the ebox and figured it out what was the cause in my case. I was integrating separate egroupware and vtigercrm install with ldap authentication.

The reason why I did install separate egroupware was because of the bug when installing the croatian language with postgresql database. So I created separate virtual host and installed egroupware with mysql database and ldap auth from ebox.

When I installed egroupware, install added admin user to the ldap and that was the problem. When I deleted admin user (through ebox interface) that was not added through ebox interface , mail module restarted ok.

So to keep it short if for some reason there are users that got created not through ebox interface delete them and your mail module will start ok.

I hope this will help , regards, Vladimir