Spamassassin - Revision history

Martin.schneider: MW-577: adapt documentation to new ConfigCascade possibility

2017-02-14T10:44:20Z

MW-577: adapt documentation to new ConfigCascade possibility

← Older revision		Revision as of 10:44, 14 February 2017
Line 82:		Line 82:


	Finally, we will need to enable the ~~GUI Capabilities~~ for SPAM. To do this we have to run the following command for e.g.		Finally, we will need to enable the capabilities for SPAM. To do this we have to run the following command for e.g.

	<pre>		<pre>
	$ changeuser -A oxadmin -P admin_password -c contextID -u username --gui_spam_filter_capabilities_enabled true		$ changeuser -A oxadmin -P admin_password -c contextID -u username --gui_spam_filter_capabilities_enabled true
	</pre>		</pre>

			or to set the property <tt>com.openexchange.spamhandler.enabled</tt> to <tt>true</tt> via ConfigCascade

	[[Category: Administrator]]		[[Category: Administrator]]
Line 94:		Line 96:

	[[Category: Spamhandling]]		[[Category: Spamhandling]]


	= Basic Troubleshooting =		= Basic Troubleshooting =

Usman.ahmad: /* SpamAssassin */

2014-08-25T15:10:19Z

SpamAssassin

← Older revision		Revision as of 15:10, 25 August 2014
Line 13:		Line 13:
	== SpamAssassin ==		== SpamAssassin ==

	You will also need to install and configure the [http://spamassassin.apache.org/ SpamAssassin]. Since we will '''not''' cover the installation part of SpamAssassin in this article, therefore we will only tell the important configuration settings needed for ~~Sieve~~ to get integrated with Open-Xchange.		You will also need to install and configure the [http://spamassassin.apache.org/ SpamAssassin]. Since we will '''not''' cover the installation part of SpamAssassin in this article, therefore we will only tell the important configuration settings needed for SpamAssassin to get integrated with Open-Xchange.

	= Installation =		= Installation =

Usman.ahmad: /* Troubleshooting */

2014-08-22T14:31:47Z

Troubleshooting

← Older revision		Revision as of 14:31, 22 August 2014
Line 96:		Line 96:


	= Troubleshooting =		= Basic Troubleshooting =

	1. Make sure that you configure your Firewall to allow ports e.g. '''Port 4190''' for Sieve and '''Port 783''' for SpamAssassin in your Server environment.		1. Make sure that you configure your Firewall to allow ports e.g. '''Port 4190''' for Sieve and '''Port 783''' for SpamAssassin in your Server environment.

Usman.ahmad: /* Troubleshooting */

2014-08-22T14:31:26Z

Troubleshooting

← Older revision		Revision as of 14:31, 22 August 2014
Line 98:		Line 98:
	= Troubleshooting =		= Troubleshooting =

	1. Make sure that you configure your Firewall to allow ports e.g. Port 4190 for Sieve and Port 783 for SpamAssassin in your Server environment.		1. Make sure that you configure your Firewall to allow ports e.g. '''Port 4190''' for Sieve and '''Port 783''' for SpamAssassin in your Server environment.

	2. Check /var/log/maillog for any issues as well. Also can turn the mail Debug logging for Dovecot e.g.		2. Check '''/var/log/maillog''' for any issues as well. Also can turn the mail Debug logging for Dovecot e.g.

	<pre>		<pre>

Usman.ahmad at 14:30, 22 August 2014

2014-08-22T14:30:32Z

← Older revision		Revision as of 14:30, 22 August 2014
Line 94:		Line 94:

	[[Category: Spamhandling]]		[[Category: Spamhandling]]


			= Troubleshooting =

			1. Make sure that you configure your Firewall to allow ports e.g. Port 4190 for Sieve and Port 783 for SpamAssassin in your Server environment.

			2. Check /var/log/maillog for any issues as well. Also can turn the mail Debug logging for Dovecot e.g.

			<pre>
			$ vi /etc/dovecot/conf.d/10-logging.conf
			</pre>
			and change the config parameter

			<pre>
			$ mail_debug = yes
			</pre>

			3. For SpamAssassin, you can also check the Open-Xchange Server logs to make sure that the settings are loaded correctly.

Usman.ahmad: /* For SpamAssassin */

2014-08-22T14:22:52Z

For SpamAssassin

← Older revision		Revision as of 14:22, 22 August 2014
Line 85:		Line 85:

	<pre>		<pre>
	$ changeuser -A oxadmin -P admin_password -c 1 -u username --gui_spam_filter_capabilities_enabled true		$ changeuser -A oxadmin -P admin_password -c contextID -u username --gui_spam_filter_capabilities_enabled true
	</pre>		</pre>

Usman.ahmad at 13:42, 21 August 2014

2014-08-21T13:42:43Z

← Older revision		Revision as of 13:42, 21 August 2014
Line 87:		Line 87:
	$ changeuser -A oxadmin -P admin_password -c 1 -u username --gui_spam_filter_capabilities_enabled true		$ changeuser -A oxadmin -P admin_password -c 1 -u username --gui_spam_filter_capabilities_enabled true
	</pre>		</pre>

			[[Category: Administrator]]

			[[Category: OX6]]
			[[Category: AppSuite]]

			[[Category: Spamhandling]]

Usman.ahmad: Created page with "= Introduction = This OXpedia article describes, how to connect the [http://spamassassin.apache.org/ SpamAssassin] system with Open-Xchange. It allows accessing your SpamAssa..."

2014-08-21T13:15:11Z

Created page with "= Introduction = This OXpedia article describes, how to connect the [http://spamassassin.apache.org/ SpamAssassin] system with Open-Xchange. It allows accessing your SpamAssa..."

New page

= Introduction =

This OXpedia article describes, how to connect the [http://spamassassin.apache.org/ SpamAssassin] system with Open-Xchange.
It allows accessing your SpamAssassin settings from within Open-Xchange and use the spam- and ham
Learning mechanisms of SpamAssassin directly from within the Open-Xchange UI.

= Prerequisites =

== Sieve ==

You will need to install and configure the [http://sieve.info/ SIEVE] Mail filter program on your mail server. Since we will '''not''' cover the installation part of Sieve in this article, therefore we will only tell the important configuration settings needed for Sieve to get integrated with Open-Xchange.

== SpamAssassin ==

You will also need to install and configure the [http://spamassassin.apache.org/ SpamAssassin]. Since we will '''not''' cover the installation part of SpamAssassin in this article, therefore we will only tell the important configuration settings needed for Sieve to get integrated with Open-Xchange.

= Installation =

We will need to install the following two packages on the Open-Xchange server.

{{InstallPlugin|pluginname=open-xchange-spamhandler-spamassassin open-xchange-mailfilter|sopath=6.22/backend|version=v6.22.x}}

{{InstallPlugin|pluginname=open-xchange-spamhandler-spamassassin open-xchange-mailfilter|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}

= Configuration =

== For Sieve ==

As we have now already installed the needed package '''open-xchange-mailfilter'''. Now we need to configure the setting the configuration file so that Open-Xchange can be integrated with Sieve.

Open the following file in your Linux editor.
<pre>
$ /opt/open-xchange/etc/mailfilter.properties
</pre>

Edit the following lines

<pre>
SIEVE_SERVER=localhost //your sieve server name, localhost is default for single machine

SIEVE_PORT=4190 //this port should be same as the one you define during the installation of Sieve.
</pre>

Save the changes and reboot Open-Xchange service.

<pre>
$ /etc/init.d/open-xchange restart
</pre>

Verify that the mailfilter bundle has started properly and should be ACTIVE.
<pre>
$ listbundles | grep filter

bundlename: com.openexchange.mail.filter status: ACTIVE
</pre>

== For SpamAssassin ==

Open the following file in Linux editor
<pre>
$ /opt/open-xchange/etc/imap.properties
</pre>

Edit the following parameter to:

<pre>
com.openexchange.imap.spamHandler=SpamAssassin
</pre>

Once done then reboot the OX Service
<pre>
$ /etc/init.d/open-xchange restart
</pre>

Make sure that SpamAssassin port is also open Port 783 (by default). Also verify that spam bundles loaded successfully.

<pre>
$ /opt/open-xchange/sbin/listbundles | grep spam
bundlename: com.openexchange.spamhandler.spamassassin status: ACTIVE
</pre>

Finally, we will need to enable the GUI Capabilities for SPAM. To do this we have to run the following command for e.g.

<pre>
$ changeuser -A oxadmin -P admin_password -c 1 -u username --gui_spam_filter_capabilities_enabled true
</pre>