Skip to Content
Last modified by Sebastian Marsching on 2022/05/29 13:59
From version 3.1
edited by Sebastian Marsching
on 2022/05/29 13:59
Change comment: There is no comment for this version
To version 1.1
edited by Sebastian Marsching
on 2022/04/03 22:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
1 -Network
Content
... ... @@ -22,7 +22,7 @@
22 22   $final_spam_destiny = D_DISCARD;
23 23  ```
24 24  
25 -This should send every e-mail passed through Zimbra to the address `my-archiving-address@example.com`. This is the POP3 or IMAP mailbox that MailStore uses to receive all e-mails. Amavis will take care of writing headers that help MailStore identify to which e-mail address the e-mail actually belongs, so that it can be archived in the right MailStore account.
25 +This should send every e-mail passed through Zimbra to the address `my-archiving-address@example.com`. This is the POP3 or IMAP mailbox that [MailStore](https://sebastian.marsching.com/wiki/MailStore) uses to receive all e-mails. Amavis will take care of writing headers that help [MailStore](https://sebastian.marsching.com/wiki/MailStore) identify to which e-mail address the e-mail actually belongs, so that it can be archived in the right [MailStore](https://sebastian.marsching.com/wiki/MailStore) account.
26 26  
27 27  I have been using this configuration with ZCS 7.1, 7.2 and 8.6. For other versions, the configuration file and thus the changes might look different.
28 28  
... ... @@ -40,25 +40,19 @@
40 40  
41 41  The change described above will have no effect on hosts listed in `zimbraMtaMyNetworks`. Therefore, if you have mail-server acting as a front-end to the Zimbra server, you should not list it in `zimbraMtaMyNetworks`. `zimbraMtaMyNetworks` should only contain the Zimbra server itself (and the loopback address).
42 42  
43 -However, for OpenDKIM and SpamAssassin, you also want to trust your other mail servers. You can get this effect by editing the configuration files and adding the appropriate IP addresses there:
43 +However, for OpenDKIM and [SpamAssassin](https://sebastian.marsching.com/wiki/SpamAssassin), you also want to trust your other mail servers. You can get this effect by editing the configuration files and adding the appropriate IP addresses there:
44 44  
45 45  `/opt/zimbra/conf/opendkim-localnets.conf.in` (Zimbra 8 only):
46 46  
47 -```
48 -%%zimbraMtaMyNetworksPerLine%%
49 -192.0.2.1/32
50 -[2001:db8::1]/128
51 -```
47 + %%zimbraMtaMyNetworksPerLine%%
48 + 192.0.2.1/32
49 + [2001:db8::1]/128
52 52  
53 -`/opt/zimbra/conf/salocal.cf.in`:
51 + %%uncomment VAR:zimbraMtaMyNetworks%%trusted_networks %%zimbraMtaMyNetworks%% 192.0.2.1/32 [2001:db8::1]/128
54 54  
55 -```
56 -%%uncomment VAR:zimbraMtaMyNetworks%%trusted_networks %%zimbraMtaMyNetworks%% 192.0.2.1/32 [2001:db8::1]/128
57 -```
58 -
59 59  In recent Zimbra versions (ZCS 8.5 and newer) it might be more elegant to add your own `trusted_networks` line to `/opt/zimbra/data/spamassassin/localrules/sauser.cf`.
60 60  
61 -**Important note:** Earlier versions of this tutorial suggested also adding the hosts to the `@mynetworks` list in `amavisd.conf.in`. However, this is not a good idea because it will cause SpamAssassin to treat all e-mail as "submitted" by an authenticated client and thus it will also treat all hosts as trusted, even if it would not otherwise (as explained on the [SpamAssassin mailing list](http://mail-archives.apache.org/mod_mbox/spamassassin-users/201604.mbox/%3Cxn0k4sewlxfk5pi005%40news.gmane.org%3E)). For this reason, `zimbraMtaMyNetworks` should only contain the Zimbra server itself and the `@mynetworks` option in the Amavis configuration should not be changed.
55 +**Important note:** Earlier versions of this tutorial suggested also adding the hosts to the `@mynetworks` list in `amavisd.conf.in`. However, this is not a good idea because it will cause [SpamAssassin](https://sebastian.marsching.com/wiki/SpamAssassin) to treat all e-mail as "submitted" by an authenticated client and thus it will also treat all hosts as trusted, even if it would not otherwise (as explained on the [SpamAssassin mailing list](http://mail-archives.apache.org/mod_mbox/spamassassin-users/201604.mbox/%3Cxn0k4sewlxfk5pi005%40news.gmane.org%3E)). For this reason, `zimbraMtaMyNetworks` should only contain the Zimbra server itself and the `@mynetworks` option in the Amavis configuration should not be changed.
62 62  
63 63  # Mailbox Selected READ-ONLY Error in Thunderbird
64 64  
... ... @@ -248,7 +248,7 @@
248 248  
249 249  # Enabling SpamAssassin rule updates
250 250  
251 -Since Zimbra 8, it might be necessary to explicitly enable SpamAssassin rule updates (see [this article](https://wiki.zimbra.com/wiki/Anti-spam_Strategies) in the Zimbra knowledge-base). You can do this through `zmlocalconfig`:
245 +Since Zimbra 8, it might be necessary to explicitly enable [SpamAssassin](https://sebastian.marsching.com/wiki/SpamAssassin) rule updates (see [this article](https://wiki.zimbra.com/wiki/Anti-spam_Strategies) in the Zimbra knowledge-base). You can do this through `zmlocalconfig`:
252 252  
253 253  ```bash
254 254  zmlocalconfig -e antispam_enable_rule_updates=true
... ... @@ -290,7 +290,7 @@
290 290  ln -s ../pyzor /opt/zimbra/data/amavisd/.pyzor
291 291  ```
292 292  
293 -Optionally, increase the timeout for Pyzor by adding the `pyzor_timeout` option to the SpamAssassin configuration. For example:
287 +Optionally, increase the timeout for Pyzor by adding the `pyzor_timeout` option to the [SpamAssassin](https://sebastian.marsching.com/wiki/SpamAssassin) configuration. For example:
294 294  
295 295   pyzor_timeout 20
296 296