[swrightsls]

Originally Posted by mmorse

In it's simplest form on the secondary you run the following commands:

zmprov md domain.com zimbraMailCatchAllAddress @domain.com 
zmprov md domain.com zimbraMailCatchAllForwardingAddress @domain.com
zmprov md domain.com zimbraMailTransport smtp:primary.domain.com

On your primary in /opt/zimbra/conf/zmmta.cf I would change the line for smtpd_reject_unlisted_recipients to yes, save the file and 'postfix reload'.
(Which drops traffic on the floor to non-existent addresses rather than spending time processing.)

Thanks for this, I will give it a try.

As far as cutting down on spam through the secondary (not that the users would see, but that affects server load and traffic):

You can provision all users on the secondary itself, then set the ZimbraMailTransport on each account individually. Just have to remember to maintain both places.

If we do not provision any users on the secondary, I assume this transfers the load for all spam to the primary, correct? I'm wondering if this method is less effective at catching spam than having all the users setup on the secondary? Our current system (qmail+assp) fails miserably if the secondary does not have a similar anti-spam setup.

In a relay-only Zimbra setup as described in the first part above, does spamassassin come into play at all on the secondary?

Thanks.