Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 08-07-2007, 04:58 AM
Active Member
 
Posts: 44
Default Multiple domains?

We have multiple domains, all like company.com/company.net/company.org etc. All of the users should get the mails for every domain, so an e-mail to user1@company.com should reach user1 but an e-mail to user1@company.net should also be delivered to user1.

Should this be done with a virtual host or do I have to do something else? In postfix this is normally done by changing mydestination in main.cf, but I don't think it is necessary to manually edit this file?
Reply With Quote
  #2 (permalink)  
Old 08-07-2007, 10:48 AM
Zimbra Consultant & Moderator
 
Posts: 14,540
Default

Set-up a second (third, fourth etc.) domain in Zimbra and add the alias for the domain you want to the users account.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 08-07-2007, 02:13 PM
Active Member
 
Posts: 44
Default

So that means that I will have to add four aliases for every user that I have? Why isn't this possible in a way it is with postfix?
Reply With Quote
  #4 (permalink)  
Old 08-07-2007, 02:29 PM
Zimbra Employee
 
Posts: 6,095
Default

Well the question becomes are you going to allow them to send from/appear as user1@domain.com & user1@example.net & any other alias addresses?


Individually - incoming & the user could select any of their choice on outgoing:

Incoming:
If you have a domain domain.com and you want the domain example.net to be an alias for it, so that sending mail to user1@example.net is the same as sending mail to user1@domain.com (delivered to the same mailbox), you can designate example.net as a domain alias when creating the domain. This example assumes domain.com already exists, but example.net does not:
Quote:
zmprov cd example.net zimbraDomainType alias zimbraMailCatchAllAddress @example.net zimbraMailCatchAllForwardingAddress @domain.com
If already created it might be like: (not sure this works as well-seems best to create the alias from the get go)
Quote:
zmprov md example.net zimbraMailCatchAllAddress @example.net zimbraMailCatchAllForwardingAddress @domain.com zimbraMailTransport lmtp:server.domain.com

Outgoing:
If you want mail from user1@domain.com to appear to come from user1@example.net, you can set the canonical address for the entire domain.
Quote:
zmprov md domain.com zimbraMailCatchAllAddress @domain.com zimbraMailCatchAllCanonicalAddress @example.net

or yes as you we're asking:
Postfix Address Rewriting
__________________
-Mike Morse (MCode151)

ZCS-to-ZCS Migrations & Moves | Admin Tools & Tidbits » ZimbraBlog.com | ZimbraCommunity.com

Last edited by mmorse : 08-07-2007 at 02:54 PM.
Reply With Quote
  #5 (permalink)  
Old 08-08-2007, 06:32 AM
Active Member
 
Posts: 44
Default

Quote:
Originally Posted by mmorse View Post
zmprov cd example.net zimbraDomainType alias zimbraMailCatchAllAddress @example.net zimbraMailCatchAllForwardingAddress @domain.com
This was the solution as far as I can see. It works like I wanted it to for now. Thanks for the support.
Reply With Quote
  #6 (permalink)  
Old 08-08-2007, 10:22 AM
Zimbra Employee
 
Posts: 6,095
Default

no problem
__________________
-Mike Morse (MCode151)

ZCS-to-ZCS Migrations & Moves | Admin Tools & Tidbits » ZimbraBlog.com | ZimbraCommunity.com
Reply With Quote
  #7 (permalink)  
Old 08-22-2007, 12:06 PM
Active Member
 
Posts: 31
Default Local Recipient Rejection?

I've been trying to set this up as well, and have run into one rather serious issue with this solution. In my case "avlsi.com" is aliased to fulcrummicro.com.

Old configuration: include in /etc/postfix/main.cf
Code:
mydestination = fulcrummicro.com, avlsi.com
Result:
user@avlsi.com is delivered correctly
notauser@avlsi.com is rejected as an illegal destination

New configuration:
fulcrummicro.com configured as the primary domain in Zimbra
If I do the suggested configuration of
Quote:
zmprov cd avlsi.com zimbraDomainType alias zimbraMailCatchAllAddress @avlsi.com zimbraMailCatchAllForwardingAddress @fulcrummicro.com
user@avlsi.com is indeed delivered correctly, but mail addressed to notauser@avlsi.com is accepted for delivery (and later bounced). This turns us into a giant backscatter source and cripples the server under the extra load of processing invalid recipients.

Looking for an alternate solution within the zimbra configuration...
Reply With Quote
  #8 (permalink)  
Old 01-06-2008, 12:48 PM
Active Member
 
Posts: 26
Default

is the issued solve? In my situation, (before i using zimbra) i just simply add additional domain in the mydestination and configure the outlook for different user to use different domain(for sending).

But i can't seem to change main.cf file, zimbra revert back to whatever admin console configured.

Can someone update the issue?
Reply With Quote
  #9 (permalink)  
Old 01-06-2008, 07:59 PM
Former Zimbran
 
Posts: 5,606
Default

try changing your postfix value with postconf, ie:
postconf -e (attrib)=(value)
Reply With Quote
  #10 (permalink)  
Old 03-21-2008, 02:04 PM
Active Member
 
Posts: 34
Default

Quote:
Originally Posted by Bevan Bennett View Post
I've been trying to set this up as well, and have run into one rather serious issue with this solution. In my case "avlsi.com" is aliased to fulcrummicro.com.

Old configuration: include in /etc/postfix/main.cf
Code:
mydestination = fulcrummicro.com, avlsi.com
Result:
user@avlsi.com is delivered correctly
notauser@avlsi.com is rejected as an illegal destination

New configuration:
fulcrummicro.com configured as the primary domain in Zimbra
If I do the suggested configuration of

user@avlsi.com is indeed delivered correctly, but mail addressed to notauser@avlsi.com is accepted for delivery (and later bounced). This turns us into a giant backscatter source and cripples the server under the extra load of processing invalid recipients.

Looking for an alternate solution within the zimbra configuration...
Was this resolved? I have a similar multi-domain situation and the backscatter may have gotten me into blacklist trouble...
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com