User manual BARRACUDA EMAIL SECURITY SERVICE ADMINISTRATOR GUIDE V1

[. . . ] Barracuda Email Security Service Administrator's Guide Version 1. x Barracuda Networks Inc. Campbell, CA 95008 http://www. barracuda. com Copyright Notice Copyright 2004-2010, Barracuda Networks www. barracuda. com v1. 0-101202-01-1202 All rights reserved. Information in this document is subject to change without notice. Trademarks Barracuda Email Security Service is a trademark of Barracuda Networks. All other brand and product names mentioned in this document are registered trademarks or trademarks of their respective holders. 2 Barracuda Email Security Service Administrator's Guide Contents Chapter 1 ­ Introduction . [. . . ] If of the form accountname@domain. com, the username is transformed into a proper LDAP bind DN like CN=accountname, CN=users, DC=domain, DC=com when accessing the LDAP server. Sometimes the default transformation does not generate a proper bind DN. Password: Password used to connect to the LDAP service on the specified LDAP Server. The default value will look up the 'defaultNamingContext' top-level attribute and use it as the search base. Authentication Filter: Filter used to look up an email address and determine if it is valid for this domain. The filter consists of a series of attributes that might contain the email address. If the email address is found in any of those attributes, then the account is valid and is allowed into the Barracuda Email Security Service. Mail Attributes: Enter the LDAP attributes you want to use (ex: mail, proxyAddress, etc. ). Synchronize Automatically: Select Yes if you want The Barracuda Email Security Service to automatically synchronize your users with your LDAP server on a regular basis. Synchronization means accounts will be created in the Barracuda Email Security Service for each user in your LDAP directory for the domain. Select No if you want to synchronize manually in case your LDAP server is not always available. Use LDAP for Authentication: Enable or disable authentication of email recipients using your existing LDAP server. Once you have entered information about your LDAP server, click the Test Settings button to ensure that the Barracuda Email Security Service can communicate with the server. LDAP server types supported include Active Directory, Novell eDirectory, Domino Directory and OpenLDAP. Secured Message Transmission To prevent data leakage and ensure compliance with financial, health care and other federallyregulated agency information policies, you can configure inbound and outbound message traffic to be transmitted over a TLS channel. However, if the peer SMTP server does not support TLS, the message will not be encrypted. If you require a TLS connection, an outbound message will bounce if the receiving SMTP server does not support TLS. For complete message encryption and ensured delivery of outbound messages, use the Barracuda Message Center. You can enable encryption for each domain from the Outbound Settings > Encryption page. For details about using encryption with the Barracuda Message Center, see Encryption of Outbound Mail, page 28. TLS For Secured Inbound and Outbound Messages TLS provides secure transmission of email content, both inbound and outbound, using the Secure Sockets Layer (SSL) - also known as TLS. From the Domains > Domain Details page you can select: · Required: All messages between the Barracuda Email Encryption Service and the destination server MUST be delivered via a TLS channel. If the destination server does not support a TLS connection, the message will not be delivered (it will `bounce'). Advanced Configuration 37 · Optional: All messages between the Barracuda Email Encryption Service and the destination server will be delivered via TLS if the destination server supports TLS connections. TLS transmission is disabled. 38 Barracuda Email Security Service Administrator's Guide Chapter 8 Managing Accounts You can either manually create user accounts in the Barracuda Email Security Service, or you can synchronize your LDAP server with the service to automatically create valid accounts. Use this chapter to understand managing user accounts and configure per-user settings. [. . . ] If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. [. . . ]