Resources in multi-domain setup. Does it work in Kolab 3.4?

[Cornelius Hald]

Hi Franz,

thanks for the information. So it looks like the situation with 3.4 is
even worse as it was with 3.3. Not nice :(

The issue I have with booking resources is exactly the one you're
describing as well. It's a pity that the multi-domain setup is so buggy
because for me this was the one single reason to (try to) switch to
Kolab...

Anyway, thanks for your help. It's very welcome!
Conny


On Tue, 2015-05-05 at 18:42 +0200, Franz Skale wrote:
> Hi,
> what i've got working is, freebusy get but not freebusy display in
> roundcube.
> Also, sending mail to a resource email doensn't work.
> I think, i have the right setup but, like i mentioned in a post some
> time ago, there's a issue regarding lmtp and verify user.
> It simply uses the wrong notation.
> Look at my post from 23.03.2015 for details.
> Also, right now i'm struggling with kolabd and the Reconnect facility,
> which simply doesn't work with imaps.
> I couldn't get imap to work. So it would be really cool to have all
> possible options in kolab.conf been well documented.
> Excerpt from my post on 23.03.2015 regarding the resource issues:
> 
> 3.) Mail to shared folder on multidomain setup, which worked in 3.3 now
> refuses to work with 3.4.
> I found out that, whenever a resource got booked a mail is sent to the
> resource which doesn't work anymore.
> Simple explanation is that the primary domain will always be added
> regardless of the receipeint domain:
> 
> E.g:
> Mar 22 20:30:13 mail postfix/lmtp[12329]: C7D579274B0:
> to=<shared+shared/Resources/buero at example.com>,
> orig_to=<shared+shared/Resources/buero at example.com@primarydomain.com>,
> relay=mail.example.com[/var/lib/imap/socket/lmtp], delay=0.04,
> delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (host
> mail.example.com[/var/lib/imap/socket/lmtp] said: 550-Mailbox unknown. 
> Either there is no mailbox associated with this 550-name or you do not
> have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT
> TO command))
> 
> How to teach roundcube to not use the primary domain in adressing ?
> Of course i read the changes and added " to the virtual alias maps which
> changed anything !
> 
> 
> Rgds.
> 
> Franz
> 
> 
> 
> Am 05.05.15 um 14:55 schrieb Cornelius Hald:
> > Hi,
> >
> > from what I know it is a known bug that you can't use resources with
> > Kolab 3.3 in a multi-domain setup. See:
> >
> > https://issues.kolab.org/show_bug.cgi?id=4331
> >
> > Did anyone try that with 3.4? Does it work there?
> >
> > I'm really trying to figure this out because it would be the last piece
> > to a completely working setup.
> >
> > Thanks!
> > Conny
> >
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> 
>