Re: [Kolab-devel] Postfix, LDAP and resources

Hi Paul,

I have a note to do about wallace: in your config you just disabled
amavis, which is not a wise idea. But you are right, looking at my
current config it looks like wallace is disabled from kolab 3.1. May
be it has still some rough edge to sort out.... with kolab 3.0 I had
to disable it due to UTF-8 issues. Or this is simply an oversight.

That said if you need it the best way to enable it again is:

# Listener to re-inject email from Amavisd into Postfix
127.0.0.1:10025 inet    n   -   n   -       100 smtpd
    -o content_filter=smtp-wallace:[127.0.0.1]:10026
....

in master.cf. The idea is the mail is scanned with amavisd reinjected
into postfix which passes it wallace and again to postfix. In kolab
3.0 it was working like that.

Hope it helps.

Kind regards
Enrico

On Mon, Mar 24, 2014 at 10:57 PM, Paul Boddie <[email protected]> wrote:
> 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 <[email protected]>
> becomes <shared+shared/Resources/[email protected]> and <[email protected]>.
>
> It should, apparently, be <shared+shared/Resources/The [email protected]>
> with <[email protected]> being the thing Postfix wants to see and
> "shared/Resources/The [email protected]" 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
> _______________________________________________
> devel mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/devel