[prev in list] [next in list] [prev in thread] [next in thread]
List: kroupware
Subject: bounced on alias name
From: Thorsten Schnebeck <thorsten.schnebeck () gmx ! net>
Date: 2008-11-03 16:59:44
Message-ID: 200811031759.44964.thorsten.schnebeck () gmx ! net
[Download RAW message or body]
Hi,
I use a kolab 2.2 master slave setup.
master server 1 lives in the internet and is imap host of domain A
slave server 2 lives in an intranet and is imap host of domain B
Kolab uses an LDAP mirror in a master slave setup.
There is user alpha. User alpha is a member of both domains. As in current
Kolab you can not put one person to two email accounts user alpha uses one
email address and an alias name:
mail: alpha@domain.a and alias: beta@domain.b
Everything works fine BUT I have here one side effect:
if I send a message as beta@domain.b to e.g. gamma@domain.b and
kolabfilter has a problem (like exe-file as attachment) and wants to inform me,
I see this:
to=<beta@domain.b>, relay=kolabmailboxfilter, delay=0.16,
delays=0.02/0.01/0/0.13, dsn=5.3.0, status=bounced (service
unavailable. Command output: Failed to set recipient: Mailbox unknown.
Either there is no mailbox associated with this name or you do not have
authorization to see it. 5.1.1 User unknown,
code=550, original code 550)
This is correct, there is no mailbox "beta@domain.b" as this is only an alias.
This also happens when I don't use an alias but a distribution list.
Why does postfix and co does not know that a special alias belongs to a
special mailbox?
Anyone?
Bye Thorsten
_______________________________________________
Kolab-users mailing list
Kolab-users@kolab.org
https://kolab.org/mailman/listinfo/kolab-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic