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

2017-02-14T10:47:17Z

MW-577: adapt documentation to new ConfigCascade possibility

← Older revision		Revision as of 10:47, 14 February 2017
Line 83:		Line 83:


	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]]

WolfgangRosenauer at 08:29, 5 December 2016

2016-12-05T08:29:15Z

← Older revision		Revision as of 08:29, 5 December 2016
Line 1:		Line 1:
	= Introduction =		= Introduction =

	This OXpedia article describes, how to set up a spamhandler which reports ham and spam via mail to any email address system with Open-Xchange.		This OXpedia article describes, how to set up a spamhandler which optionally reports ham and spam via mail to any email address system with Open-Xchange.

			In addition it moves the mail to the spam folder if marked as spam and into the Inbox if a message in the spam folder is again marked as ham. The exact behaviour can be configured.

			To get the UI controls all users need to be provisioned accordingly. There is no global switch to enable/disable.


	= Prerequisites =		= Prerequisites =

WolfgangRosenauer: Created page with "= Introduction = This OXpedia article describes, how to set up a spamhandler which reports ham and spam via mail to any email address system with Open-Xchange. = Prerequisit..."

2016-12-05T08:25:29Z

Created page with "= Introduction = This OXpedia article describes, how to set up a spamhandler which reports ham and spam via mail to any email address system with Open-Xchange. = Prerequisit..."

New page

= Introduction =

This OXpedia article describes, how to set up a spamhandler which reports ham and spam via mail to any email address system with Open-Xchange.

= Prerequisites =

== Target mail ==

For setting up the spamhandler you require the address where to send ham and spam reports to.

= Installation =

We will need to install the following package on the Open-Xchange server.
[Please note that even if the package carries the name cloudmark it is not bound to Cloudmark product. Though Cloudmark uses the same very generic reporting method.]

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

= Configuration =

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

Edit the following parameter to:

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

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

Edit the following parameters to configure the reporting service:
<pre>
# Defines the eMail address to which the selected eMails will be bounced. If no
# address is specified the bounce will be skipped, but moving the selected mails
# to the target folder will still be processed (if configured)
com.openexchange.spamhandler.cloudmark.targetSpamEmailAddress=

# Defines the eMail address to which the selected eMails will be bounced, if they
# are marked as Ham. If no address is specified the bounce will be skipped,
# but moving the selected mails back to the Inbox will still be processed (if configured).
# Privacy note: This will send private mails of users to that address when marked as Ham
com.openexchange.spamhandler.cloudmark.targetHamEmailAddress=

# Defines to which folder the selected mails should be moved to after they have
# been bounced to the target eMail address. If no option is configured the
# selected mails will be moved to the users trash folder. Possible options are:
#
# 0 = Do not move the message at all (not recommended)
# 1 = User's trash folder (Default)
# 2 = User's SPAM folder
# 3 = Subscribed confirmed-spam folder (experimental)
com.openexchange.spamhandler.cloudmark.targetSpamFolder=2

# Defines if the spam/ham message is passed as a nested message to the target address
#
# ----------------------------------== /!\ ==----------------------------------------
# Note: This option needs to be clarified with your running Cloudmark service that
# passing the spam/ham message as a nested message is accepted and properly
# handled!
# -----------------------------------------------------------------------------------
#
# Default is "true"
com.openexchange.spamhandler.cloudmark.wrapMessage=true
</pre>

Once done then reboot the OX Service
<pre>
$ service open-xchange restart
</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 contextID -u username --gui_spam_filter_capabilities_enabled true
</pre>

[[Category: Administrator]]

[[Category: AppSuite]]

[[Category: Spamhandling]]

MailReportSpamhandler - Revision history

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

WolfgangRosenauer at 08:29, 5 December 2016

WolfgangRosenauer: Created page with "= Introduction = This OXpedia article describes, how to set up a spamhandler which reports ham and spam via mail to any email address system with Open-Xchange. = Prerequisit..."