- 1 Postfix - MTA
- 1.1 Actual MTA & Postfix Topics Homepage
- 1.2 Missing main.cf Error
- 1.3 User Alias Mapping And Mail Transport with Postfix & LDAP
- 1.4 Automatic BCC
- 1.5 Limiting Or Increasing Number Of Recipents / Messages
- 1.6 Controlling SMTPD Client Connections
- 1.7 Spam Control And Related Issues
- 1.8 Using Different SMTP Server For Webclient (ZWC), Mobiles, And ZCO
- 1.9 Global Disclaimer Options
Postfix - MTA
Actual MTA & Postfix Topics Homepage
Please see Ajcody-MTA-Postfix-Topics
Missing main.cf Error
If you get something like:
postfix/postqueue: fatal: open /opt/zimbra/postfix-220.127.116.11z/conf/main.cf: No such file or directory
All you need to do is create an empty main.cf file and zimbra will rewrite it.
When you now do something to start the mta, it will generate the values for main.cf
zmmtactl stop zmmtactl start
User Alias Mapping And Mail Transport with Postfix & LDAP
Please see the following:
- Postfix workaround
- "User defined auto bcc"
- "Next rev of (mail) identities preferences management (server side)"
Limiting Or Increasing Number Of Recipents / Messages
Mailing Lists - Distribution Lists
If you want to restrict messages per hour, you can look into Policy Daemon:
Also, there are some default postfix parameters set to control sending a message to x amount recipients. The parameters you will need to look at are smtpd_recipient_limit & smtpd_recipient_overshoot_limit, these have a default value of 1000.
Postfix defines these parameters as:
- smtpd_recipient_limit: The maximum number of recipients that the Postfix SMTP server accepts per message delivery request.
- smtpd_recipient_overshoot_limit: The number of recipients that a remote SMTP client can send in excess of the limit specified with $smtpd_recipient_limit, before the Postfix SMTP server increments the per-session error count for each excess recipient.
From the command line you can change the default values.
su - zimbra postconf -e smtpd_recipient_limit=<new value> postconf -e smtpd_recipient_overshoot_limit=<new value> postfix reload
Controlling SMTPD Client Connections
Postfix Resources At Their Site (All Clients/Connections):
- Measures against clients that make too many connections
- anvil - Postfix session count and request rate control
- anvil_rate_time_unit - The time unit over which client connection rates and other rates are calculated.
- smtpd_client_connection_count_limit - How many simultaneous connections any client is allowed to make to this service.
- smtpd_client_message_rate_limit - The maximal number of message delivery requests that any client is allowed to make to this service per time unit, regardless of whether or not Postfix actually accepts those messages.
- smtpd_client_recipient_rate_limit - The maximal number of recipient addresses that any client is allowed to send to this service per time unit, regardless of whether or not Postfix actually accepts those recipients.
- smtpd_client_connection_rate_limit - The maximal number of connection attempts any client is allowed to make to this service per time unit.
Postfix Resources At Their Site (Exceptions To Clients/Connections Or Single Source):
- smtpd_client_event_limit_exceptions - Clients that are excluded from connection count, connection rate, or SMTP request rate restrictions.
Spam Control And Related Issues
A list of resources you'll find useful:
Wiki articles that have been assigned to the anit-spam category:
Down to the end-user:
Using Different SMTP Server For Webclient (ZWC), Mobiles, And ZCO
There a variable called zimbraSmtpHostname that is in the global (zmprov gacf) and server (zmprov gs `hostname`) configs. It's defaulted to 'localhost' - at least on a single ZCS configuration.
In cases where you need/want all mail to be processed by, for example, an external non-Zimbra spam filter box you could set this variable to the spam filter boxes hostname.
zmprov mcf zimbraSmtpHostname hostname-of-ext-server
zmprov ms servername zimbraSmtpHostname hostname-of-ext-server
Global Disclaimer Options
Here's the url to review for a "current" possibility:
And in the notes section there's a comment about multi-servers:
Please note though, "This article is a community contribution and may include unsupported customizations." Meaning, it's an unsupported customization, so please take the necessary precautions.
In regards to an official and supported way to do this, please review this RFE: