[Kolab-devel] Postfix, LDAP and resources

[Paul Boddie]

Hello,

I've been reviewing some of my setup-kolab changes - yes, fixing bugs I've 
introduced, too - and I have to say that I'm a bit baffled by the way Postfix 
is set up to handle virtual aliases for resources and to use Wallace.

First of all, I made the mistake of creating a resource with a space in its 
name. This immediately causes the iTIP mails sent to the resource to have 
their addresses "shredded" so that the conference room resource "The 
Boardroom" with mail address <resource-confroom-theboardroom at example.com> 
becomes <shared+shared/Resources/The at example.com> and <Boardroom at example.com>.

It should, apparently, be <shared+shared/Resources/The Boardroom at example.com> 
with <shared at example.com> being the thing Postfix wants to see and 
"shared/Resources/The Boardroom at example.com" being the IMAP target folder, I 
suppose.

I think the fix for this is to wrap the LDAP result as follows in the 
/etc/postfix/ldap/virtual_alias_maps_sharedfolders.cf file:

result_format = <shared+%s>

Nothing I found by searching gave any really useful suggestions, but this does 
appear to prevent the above misbehaviour. It makes me wonder whether resources 
specifying a target folder with a space in it could really ever have worked, 
though. Then again, I didn't know anything about the above innards of Postfix 
until this last weekend.

Another thing involves Wallace which is supposed to handle iTIP mails, but it 
didn't appear to be invoked at all. Looking through the Postfix configuration, 
it occurred to me that only smtp-amavis was ever really defined explicitly as 
a content filter, so I switched it out with smtp-wallace by defining it in 
/etc/postfix/main.cf as follows:

content_filter = smtp-wallace:[127.0.0.1]:10026

At this point (after a "postfix reload"), Wallace seemed to respond to 
incoming messages. So I guess that the pykolab template and code doesn't set 
this up at all, as far as I can see. Making smtp-wallace (as defined above) 
the content filter for smtp-amavis appears to work, and maybe this is the fix 
here, but once again this is completely new to me and maybe I've overlooked 
some switch somewhere that magically makes all this work correctly. Pointers 
to that are very welcome!

Does any of this sound completely wrong or have I stumbled upon something that 
needs some work?

Paul