Ajcody-MailingLists-And-Mailman
- This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information. |
Mailing Lists, Distribution Lists, And Mailman
Actual Mailing Lists And Mailman Notes Homepage
Please see Ajcody-MailingLists-And-Mailman
Introduction And Choices
If you are planning to use a distro list of over 60K members, you may be inclined to use a dedicated machine for this purpose. According to bug 19153, you have 2 options: "set up mailing list manager or change the value of virtual_alias_expansion_limit as a customization. We have never tested with > 1000 so this should be done carefully, and will pound LDAP for any messages with lots of recipients." Mailman integration is an option. There is a forum thread on how to integrate zcs and mailman. This would be the preferred fix to your issue, also noted in the bug report. We probably won't see Mailman integration in ZCS at least for another year or so, not until 6.0
Restricting Who Can Send To Mailing List
These are unsupport customizations. Please be sure to make backup copies of modifications to prevent lost after upgrades/restores of Zimbra.
Please see:
- Restrict by user
- Restrict by ip addresses and other items:
Also see the following RFE:
- "Mail policies and access control for sending to distribution lists"
Restrict Sending To Certain Domains
Please see:
Add Everyone To Distribution List - Admin Console
RFE was made for this:
- "Admin>DistributionList: AddAll to add members that are in only current-search-page"
Everyone@domain Without Manually Adding Users To A DL
Investigating if this can be done. Please don't attempt anything below, I'm simply keeping track of my "notes" here.
DON'T ATTEMPT ANY OF THIS! THIS WILL MOST LIKELY GET POSTED INTO BUGZILLA AS AN RFE
RFE Made For This:
- http://bugzilla.zimbra.com/show_bug.cgi?id=32341
- Was marked as a duplicate of the following:
- "Dynamic distribution lists"
- Was marked as a duplicate of the following:
One Possible Way Described In An External Resource:
main.cf: there is a line to resolve aliases: virtual_aias_maps = ldap: $ config_directory / ldap / ldap-aliases.cf ldap-aliases.cf that relates to filter: query_filter = (&(objectclass=mailgroup)(|(mail=%s)(mailalternateaddress=%s))) result_attribute = mail result_attribute = mail special_result_attribute = uniqueMember, memberUrl in LDAP-e for everyone is recording with such attributes: mail = everyone@domain.ru memberurl = ldap :///ou=People,o=organization??sub? (&(objectclass=person)(uid=*)) objectclass=mailgroup
- Had to use the following to get it to work:
receive_override_options = no_address_mappings Was a global setting.
Another Possible Way, again an external resource:
- Use Of mailAlternateAddress
- Confirmation that it can be done?
- New LDAP map transports:
Problems Resolving Virtual Aliases For Members Of Large Distribution Lists
See the following bug:
Other wiki page is here - Error_(MTA):_unreasonable_virtual_alias_maps_map_expansion_size
The default expansion that will be done is for 1000 accounts.
Solution
Note, the bug above recommends NOT going over 1000 due to ldap performance. They recommend looking into mailman as an alternative.
Increase the virtual_alias_expansion_limit Postfix parameter to the value of the highest number of distribution list members. All commands run as the zimbra user.
Check configuration
$ postconf virtual_alias_expansion_limit
Set configuration
$ postconf -e virtual_alias_expansion_limit=3000
Restart Postfix
$ postfix stop $ postfix start
Mailman Configuration
http://wiki.zimbra.com/index.php?title=ZCS_Mailman_Integration
http://bugzilla.zimbra.com/show_bug.cgi?id=8968
http://www.zimbra.com/forums/administrators/1380-solved-zimbra-mailman-howto.html
Duplicate Emails With Distribution Lists
Situation arises when a message goes out and the effected user is somehow targeted twice in the To/CC fields by either use of a DL list, multiple DL lists, and/or a direct inclusion of their email address as well.
There was a change between 4.5.x and 5.x . New variable is zimbraMessageIdDedupeCacheSize.
The "zimbraMessageIdDedupeCacheSize" attribute might be set to zero.
su - zimbra zmprov gacf | grep zimbraMessageIdDedupeCacheSize
If you need to change the setting.
zmprov mcf zimbraMessageIdDedupeCacheSize 3000 zmmailboxdctl restart
Related Bugs: