Kolab primary email address and sunday morning reboot

Erik Kramer erikkramer at gmail.com
Mon Oct 3 21:56:10 CEST 2016


The workaround here:

https://issues.kolab.org/show_bug.cgi?id=3553

almost helps me out except for the dot "." between '%(givenname)s'[0:1] and
%(surname)s does not show up...

I have this kolab-webadmin package installed:

Version     : 3.2.6
Release     : 4.5.el7.kolab_3.4



On 3 October 2016 at 20:50, Erik Kramer <erikkramer at gmail.com> wrote:

> Hi,
>
> I've done a fresh install of kolab 3.4 and am faced with the same issue as
> before.
> And I'm not too fond of my previous hack.
>
> I'd like to use prinmary email addresses such as j.doe at domain.org
>
> I've tried this in kolab.conf:
>
> primary_mail = '%(givenname)s'[0:1].%(surname)s@%(domain)s
>
> (Rebooted the server)
>
> At first it seems to work just fine. When I fill out the new kolab user
> form, in web admin panel, it gives me the correct preview:
> j.doe at domain.org.
>
> But when I hit save, and look at the new user, his primary email address
> became: 'john'[0:1].doe at domain.org
> With 3 secundary addresses: j.doe at domain.org; john.doe at domain.org;
> doe at domain.org
>
> Any ideas?
>
> Thanks,
>
>
> Erik
>
>
> On 1 April 2015 at 00:04, Erik Kramer <erikkramer at gmail.com> wrote:
>
>>
>> Can you post your configuration?
>>>
>>
>> I got it to work by using https://docs.kolab.org/a
>> dministrator-guide/configuring-the-kolab-server.html#
>> disabling-the-recipient-policy
>> And then also delete the values for primary and secondary email from the
>> [kolab] section.
>>
>> I run the following script with cron every couple of minutes:
>>>
>>> #!/bin/bash
>>>
>>> pscount=$(ps -e -o pid,cmd | grep '[/]usr/sbin/apache' | wc -l)
>>>
>>> if [ "$pscount" = "1" ]; then
>>>   apachepid=$(cat /var/run/apache2.pid)
>>>   if kill -0 $apachepid 2> /dev/null; then
>>>     :
>>>   else
>>>     pid=$(ps -e -o pid,cmd | grep '[/]usr/sbin/apache' | awk '{ print $1
>>> }')
>>>     kill -9 $pid
>>>     /usr/sbin/service apache2 start
>>>   fi
>>> fi
>>>
>>> That way an "apache reload" has only some minutes downtime. There are
>>> times besides logrotate where apache config is reloaded... Not a fix but
>>> a workaraound.
>>>
>>>
>> I have no experience with running scripts with cron yet.
>> Will have a look, thanks.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20161003/a4d0ee1d/attachment.html>


More information about the users mailing list