Lawful Interception: Difference between revisions
From Open-Xchange
No edit summary |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
= | = Lawful Interception (Telekommunikationsüberwachung) = | ||
This article describes the configuration to activate the | This article describes the configuration options which are needet to activate the client IP transmission for email service usage. | ||
== Configuration == | == Configuration == | ||
==Mail Store Access (IMAP)== | ==Mail Store Access (IMAP)== | ||
For | For IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via | ||
vim /opt/open-xchange/etc | vim /opt/open-xchange/etc/imap.properties | ||
option to change is: | option to change is: | ||
| Line 14: | Line 14: | ||
com.openexchange.imap.propagateClientIPAddress=false | com.openexchange.imap.propagateClientIPAddress=false | ||
in case | in case users are allowed to configure external email accounts, a list of imap servers can be specified, which, when added as external accounts, will also receive a noop command with IP as argument direct after login: | ||
# Configure a comma-separated list of external IMAP server's host names | # Configure a comma-separated list of external IMAP server's host names | ||
| Line 22: | Line 22: | ||
==MTA access (SMTP)== | ==MTA access (SMTP)== | ||
For all emails send by the groupware process, it is possible to | For all emails send by the groupware process, it is possible to set the custom header "X-Originating-IP" with the "real" client IP as argument. This can be achieved by editing mail.properties: | ||
vim /opt/open-xchange/etc | vim /opt/open-xchange/etc/mail.properties | ||
option to change is: | option to change is: | ||
# Set whether client's IP address should be added to mail headers on delivery | # Set whether client's IP address should be added to mail headers on delivery | ||
# as custom header "X-Originating-IP" | # as custom header "X-Originating-IP" | ||
com.openexchange.mail.addClientIPAddress=true | com.openexchange.mail.addClientIPAddress=true | ||
Latest revision as of 12:04, 27 November 2015
Lawful Interception (Telekommunikationsüberwachung)
This article describes the configuration options which are needet to activate the client IP transmission for email service usage.
Configuration
Mail Store Access (IMAP)
For IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via
vim /opt/open-xchange/etc/imap.properties
option to change is:
# Whether client's IP address should be propagated by a NOOP command; e.g. "A01 NOOP <CLIENT_IP>" com.openexchange.imap.propagateClientIPAddress=false
in case users are allowed to configure external email accounts, a list of imap servers can be specified, which, when added as external accounts, will also receive a noop command with IP as argument direct after login:
# Configure a comma-separated list of external IMAP server's host names # which should receive client's IP address by a NOOP command, too com.openexchange.imap.propagateHostNames=
MTA access (SMTP)
For all emails send by the groupware process, it is possible to set the custom header "X-Originating-IP" with the "real" client IP as argument. This can be achieved by editing mail.properties:
vim /opt/open-xchange/etc/mail.properties
option to change is:
# Set whether client's IP address should be added to mail headers on delivery # as custom header "X-Originating-IP" com.openexchange.mail.addClientIPAddress=true