Ajcody-MTA-Postfix-Topics

Revision as of 22:08, 16 November 2008 by Ajcody (talk | contribs) (New page: {{NotOfficial}} ==Postfix - MTA== ===Actual MTA & Postfix Topics Homepage=== Please see Ajcody-MTA-Postfix-Topics ===Missing main.cf Error=== If you get something like: postfix/...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Template:NotOfficial

Postfix - MTA

Actual MTA & Postfix Topics Homepage

Please see Ajcody-MTA-Postfix-Topics

Missing main.cf Error

If you get something like:

postfix/postqueue[8739]: fatal: open /opt/zimbra/postfix-2.4.7.5z/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.

touch main.cf

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

See User_Alias_Mapping_and_Mail_Transport_with_Postfix_&_LDAP

Automatic BCC

Please see the following:

Limiting Or Increasing Number Of Recipents / Messages

Mailing Lists - Distribution Lists

Please see Ajcody-Notes#Problems_Resolving_Virtual_Aliases_For_Members_Of_Large_Distribution_Lists

Policy Daemon

If you want to restrict messages per hour, you can look into Policy Daemon:

Postfix

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):

Postfix Resources At Their Site (Exceptions To Clients/Connections Or Single Source):

Spam Control And Related Issues

A list of resources you'll find useful:

http://wiki.zimbra.com/index.php?title=Zimbra_MTA#Anti-Spam_Training_Filters

http://wiki.zimbra.com/index.php?title=CLI_zmtrainsa

http://wiki.zimbra.com/index.php?title=Improving_Anti-spam_system

http://wiki.zimbra.com/index.php?title=Postfix_Policyd

http://wiki.zimbra.com/index.php?title=IP_Address_whitelisting

http://wiki.zimbra.com/index.php?title=Spam_training

Wiki articles that have been assigned to the anit-spam category:

http://wiki.zimbra.com/index.php?title=Category:Anti-spam

Down to the end-user:

http://wiki.zimbra.com/index.php?title=Cool_User_Spam_Filters

http://www.zimbra.com/community/end_user_guide_and_how_to.html

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.

Global:

zmprov mcf zimbraSmtpHostname hostname-of-ext-server

Per 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:

Jump to: navigation, search