#wizard ---------------------------------------------------------------
<found>found</found>
<support>support</support>
<yesterday>yesterday</yesterday>
<documents>documents</documents>
<january>January</january>
<february>February<february>
<march>March</march>
<april>April</april>
<may>May</may>
<databases>databases</databases>
<june>June</june>
<july>July</july>
<august>August<august>
<september>September</september>
<october>October</october>
<november>November</november>
<december>December</december>
<sunday>Sunday</sunday>
<nickname>nickname</nickname>
<search_by>search by</search_by>
<language>language</language>
<monday>Monday</monday>
<tuesday>Tuesday</tuesday>
<wednesday>Wednesday</wednesday>
<thursday>Thursday</thursday>
<friday>Friday</friday>
<saturday>Saturday</saturday>
<filedate>File date</filedate>
<filesize>File size</filesize>
<database_name>Database name</database_name>
<source_path>Source path</source_path>
<APPLY_SETTINGS_POSTFIX>Save your Postfix configuration in the system and restart Mail services</APPLY_SETTINGS_POSTFIX>
<related>Related</related>
<subject>subject</subject>
<fetchmail_main_settings>Fetchmail global settings</fetchmail_main_settings>
<mailman_main_settings>Mailman policies</mailman_main_settings>
<fetch>fetch server</fetch>
<confirm>confirm</confirm>
<fetchmail_rules>Fetchmail rules</fetchmail_rules>
<from>from</from>
<network_address>Network address</network_address>
<server_name>Server name</server_name>
<to>to</to>
<switch_view>Switch view</switch_view>
<notif_save_conf_ldap>Parameters are saved to temporary storage,
don't forget to - Save & Apply settings - to make them in production mode</notif_save_conf_ldap>
<manage_your_server>Manage your server</manage_your_server>
<server>server</server>
<emails_addresses>eMails addresses</emails_addresses>
<postalcode>Postal code</postalcode>
<mail>eMail</mail>
<uid>Unique identifier</uid>
<done>done</done>
<street>Street</street>
<extracting>Extracting</extracting>
<score>score</score>
<corrupted>corrupted</corrupted>
<emails>emails</emails>
<deny_countries>Deny countries</deny_countries>
<deny_countries_text_spam>Add metadata to the Bayesian filtering process, allowing the Bayesian filters to learn information based on countries</deny_countries_text_spam>
<surbl_rules>Spam URI Realtime Blacklist</surbl_rules>
<surbl_rules_text>SURBLs differ from RBLs rules in that they are used to detect spam based on message body html hypertext links.</surbl_rules_text>
<rbl_check>Realtime Blackhole Lists rules</rbl_check>
<rbl_check_text>Create rules on Realtime Blackhole List / Relay Blocking List</rbl_check_text>
<deny_countries_text>Deny or put in quarantine emails from a specific country</deny_countries_text>
<countries_and_cities>Countries and cities</countries_and_cities>
<use>use</use>
<quarantine>quarantine</quarantine>
#ERRORS ---------------------------------------------------------------------------------------------------------------------------------
<license_error>License error</license_error>
<ERROR_VALUE_MISSING_PLEASE_FILL_THE_FORM>Error, a value missing, please fill correctly the form</ERROR_VALUE_MISSING_PLEASE_FILL_THE_FORM>
<ERROR_NO_RESOURCE_SELECTED>Error no resource selected</ERROR_NO_RESOURCE_SELECTED>
<ERROR_SHARE_SELECTED_NO_CREDENTIALS>Warning, the selected item did not have remote username and password. Remote operations should be failed</ERROR_SHARE_SELECTED_NO_CREDENTIALS>
<cyrus_connection_error>There is a problem while connecting to imap server...Please restart later</cyrus_connection_error>
<error_network>Network error</error_network>
<error_want_operation>Do you want perform this operation ?</error_want_operation>
<error_unable_to_upload_file>Error: Unable to upload your file</error_unable_to_upload_file>
<error_file_extension_not_match>Error: the file extension didn't match rule</error_file_extension_not_match>
<error_unable_to_move_file>Error: unable to move the file</error_unable_to_move_file>
<error_unable_process_file>Error: Unable to process the file</error_unable_process_file>
<error_give_email_or_domain>Error: Give one eMail address or one domain name</error_give_email_or_domain>
<error_give_server_or_domain>Error: Give a domain or a server name</error_give_server_or_domain>
<error_choose_email_or_domain>Error: choose email or domain</error_choose_email_or_domain>
<error_domain_exists>Error this domain already exists</error_domain_exists>
<ERROR_CURL_NOT_INSTALLED>Error: curl binary file is not installed</ERROR_CURL_NOT_INSTALLED>
<error_no_datas>There is no datas saved..aborting..</error_no_datas>
<error_no_ipaddr>Please, set the network address</error_no_ipaddr>
<error_no_localization>Please, set the localization of your object</error_no_localization>
<error_no_socks>Framework error ! It seems that artica daemon (boa daemon) is not loaded or socket port is not be able to listen</error_no_socks>
<ERROR_NO_DOMAINS_CREATED_FIRST>Unable to add licence domains, You must create global domains first</ERROR_NO_DOMAINS_CREATED_FIRST>
<error_no_domains_created>Error: You must an SMTP domain first</error_no_domains_created>
<error_bad_mail_formated>Please, verify email address format, it is not SMTP address compliance</error_bad_mail_formated>
<ERROR_DELETE_TRANSPORT>Delete redirection entry?</ERROR_DELETE_TRANSPORT>
<error_creating_mailbox>Error creating mailbox on local server</error_creating_mailbox>
<ERROR_NO_FIRST_NAME>Please, set the first name</ERROR_NO_FIRST_NAME>
<ERROR_NO_LAST_NAME>Please, set the last name</ERROR_NO_LAST_NAME>
<ERROR_NO_EMAIL>Please, set the email address</ERROR_NO_EMAIL>
<ERROR_NO_DIPLAYNAME>Please, set the surname</ERROR_NO_DIPLAYNAME>
<ERROR_MYSQL_CONNECTION>Mysql connection failed</ERROR_MYSQL_CONNECTION>
<ERROR_DELETE_USER>Do want to really delete this user </ERROR_DELETE_USER>
<ERROR_value_exceed_maximum_number_allowed>Error: The value exceed maximum number allowed</ERROR_value_exceed_maximum_number_allowed>
<ERROR_INCORRECT_DATA>Error: incorrect data type</ERROR_INCORRECT_DATA>
<error_no_array_mynetworks>Authorized networks is not set, nobody can send eMails to Internet</error_no_array_mynetworks>
<error_no_server_specified>Error: there is no server set</error_no_server_specified>
<error_no_domain_specified>Error: There is no domain set</error_no_domain_specified>
<error_please_select_an_organization>Please select an organization first</error_please_select_an_organization>
<ERR_NO_PASS>Error: please input password before submiting</ERR_NO_PASS>
<ERR_NO_USERNAME>Error: please set username before submit</ERR_NO_USERNAME>
<ERR_MYSQL_IS_REMOTE>Error: Mysql has been set has remote server (not local) this feature cannot be performed</ERR_MYSQL_IS_REMOTE>
<ERR_NO_PASS_MATCH>Error: passwords fields did not match.</ERR_NO_PASS_MATCH>
<ERR_SET_QUOTA_SUCCESS>Set quota success</ERR_SET_QUOTA_SUCCESS>
<ERR_NO_DOC_FOUND>No document match your query</ERR_NO_DOC_FOUND>
<ERROR_SLAPDCONF_LOCKED>Artica is not allowed to change the slpad.conf file[br]remove "/etc/artica-postfix/no-ldap-change" file before using this feature</ERROR_SLAPDCONF_LOCKED>
<Error>Error</Error> 
<error_check_dates>Error: please check your dates</error_check_dates>
<error_miss_datas>Error: data missing</error_miss_datas>
<error_give_address>Error: give address</error_give_address>
<error_give_pattern>Error: give pattern</error_give_pattern>
<error_give_server>Error: give server name or server ip</error_give_server>
<error_integer_waiting>Error: you need to set an integer value</error_integer_waiting>
<error_task_already_exists>Error: this task already exists</error_task_already_exists>
<error_no_ou>Error no organization specified</error_no_ou>
<error_no_userid>Error no unique identifier specified</error_no_userid>
<error_no_password>Error no password specified</error_no_password>
<error_no_licence>Error no licence</error_no_licence>
<error_alias_exists>Error, it seems that this alias is already added in the database</error_alias_exists>
<error_email_invalid>Error,Invalid email address</error_email_invalid>
<error_no_ou_saved>This setting as no Organization selected/saved</error_no_ou_saved>
<error_no_user_exists>Error, it seems that this user doesn't exists on LDAP Database, please retry...</error_no_user_exists>
<error_unknown_domain>Error, unknown domain</error_unknown_domain>
<error_module_not_installed>This module is not installed</error_module_not_installed>
<error_module_not_enabled>This module is not enabled</error_module_not_enabled>
<error_smbmount_not_installed>Warning, smbmount tool is not installed</error_smbmount_not_installed>
<error_need_smbmount_feature>To enable this feature, you need smbmount application</error_need_smbmount_feature>
<error_no_ftp_users>Error no ftp users set</error_no_ftp_users>
<error_no_ftp_users_text>If you want FTP server running, you need to add at least one FTP user...</error_no_ftp_users_text>
<fileshare>Files Sharing</fileshare>
<ERROR_NO_PRIVS>Error, Insufficient privileges</ERROR_NO_PRIVS>
<ERROR_NO_PRIVILEGES_OR_PLUGIN_DISABLED>This option is disabled, check if the associated module is enabled or your group privileges</ERROR_NO_PRIVILEGES_OR_PLUGIN_DISABLED>
<no_errors>Currently, there are no errors</no_errors>
<error_php_curl>Curl for Php is not installed</error_php_curl>
<ERROR_GDPHP_NOT_INSTALLED>It seems that the GD (php*-gd) library is not installed !</ERROR_GDPHP_NOT_INSTALLED>
<system error>There was a system problem, perhaps a preg_match problem or no sockets opens</system error>
<error_feature_not_installed>Error this feature is not installed or disabled, check your system or your plugins activation settings</error_feature_not_installed>
<error_please_install_phpmysql>Error php5-mysql is not installed, please install it by your repository manager[br]And restart web server</error_please_install_phpmysql>
<error_please_install_phpldap>Error php5-ldap is not installed, please install it by your repository manager[br]And restart web server</error_please_install_phpldap>
<error_please_install_phpimap>Error php5-imap is not installed, please install it by your repository manager[br]And restart web server</error_please_install_phpimap>
<error_please_install_phpsieve>Error php-pear-Net-Sieve/php-net-sieve is not installed, please install it by your repository manager[br]And restart web server</error_please_install_phpsieve>
<error>error</error>
<error_cannot_be_ip_address>Error this cannot be an ip address</error_cannot_be_ip_address>
<error_must_be_ip_address>Error this must be a TCP/IP address</error_must_be_ip_address>
<error_passwords_mismatch>Error passwords mismatch</error_passwords_mismatch>
<error_no_global_status>Error, unbable to stat global_status.ini file</error_no_global_status>
<LDAP_ERROR_TEXT>Error, no LDAP connection !</LDAP_ERROR_TEXT>
<error_not_mounted>Error, device is not mounted</error_not_mounted>
<error_not_plugged>Error, device is not plugged</error_not_plugged>
<error_app_not_installed_disabled>This feature is disabled because some mandatories applications are not installed on this system</error_app_not_installed_disabled>
<error_waiting_sync>Error, waiting synchronization...</error_waiting_sync>
<error_unable_to_find_path>Error, Unable to stat file in path</error_waiting_sync>
<todaysenderscountry>Sender's countries (today)</todaysenderscountry>
<error_mysql_user>Error on MYSQL account</error_mysql_user>
<error_mysql_user_text>It seems that the Mysql account is not set or failed, please set it on GLOBAL SETTINS/Mysql database</error_mysql_user_text>
<error_postfix_ldap_compliance>Error Postfix LDAP compliance</error_postfix_ldap_compliance>
<error_postfix_ldap_compliance_text>Your postfix is not LDAP compliance, you should install postfix-ldap by your repositories manager !</error_postfix_ldap_compliance_text>
<error_bad_recipient_pattern>Error, the recipient pattern is not correctly formated</error_bad_recipient_pattern>
<error_match_recipient_domain>Error the recipient domain not match</error_match_recipient_domain>
<error_path_cannot_be_null>Error: Defined path cannot be null!</error_path_cannot_be_null>
<error_group_not_in_your_organization>Error, this group is not stored by your organization</error_group_not_in_your_organization>
<ERROR_GROUP_STORE_NO_MEMBERS>Error this group currently store no member</ERROR_GROUP_STORE_NO_MEMBERS>
<ERROR_OBJECT_ALREADY_EXISTS>requested object already exists</ERROR_OBJECT_ALREADY_EXISTS>
<ERROR_INVALID_EMAIL_ADDR>Error: invalid email address</ERROR_INVALID_EMAIL_ADDR>
<ERROR_NEED_TO_SAVEAPPLY>You need to perform a Save & Apply to apply these parameters on production mode</ERROR_NEED_TO_SAVEAPPLY>
<APP_MSMTP_NOT_INSTALLED>You need to install new SMTP engine version in order to use Authentication feature</APP_MSMTP_NOT_INSTALLED>
<WANT_INSTALL>Do you want to install the selected product ?</WANT_INSTALL>
<ERROR_NOT_INSTALLED_REDIRECT>The software is not installed, you will be redirected to the install process</ERROR_NOT_INSTALLED_REDIRECT>
<error_curl_resolve>Could not resolve host</error_curl_resolve>
<error_wrong_artica_version>Error wrong Artica version</error_wrong_artica_version>
<error_gluster_not_installed>Error, GlusterFS is not installed</error_gluster_not_installed>
#------------------------------------------------------------------------------------------------------------------------------------------
<locked>locked</locked>
<upgrade_artica>New artica version</upgrade_artica>
<upgrade_artica_text>A new Artica version is available, you can perform update if you want...</upgrade_artica_text>
<table>table</table>
<size>size</size>
<use%>Use %</use%>
<path>path</path>
<update_settings>Update settings</update_settings>
<environement>environement</environement>
<results>Results</results>
<remove_this_prog>Uninstall this application on your system</remove_this_prog>
<install_this_prog>Install this application.[br]If it exists, artica will update this program.</install_this_prog>
<addremoveprog>Add/Remove/Update Programs</addremoveprog>
<help>help</help>
<show>show</show>
<detach>Detach</detach>
<running>running</running>
<processes>processes</processes>
<more_infos>More informations</more_infos>
<email_scenarios>eMail Scenarios</email_scenarios>
<version>version</version>
<delete_ou>Delete This organization</delete_ou>
<delete_ou_text>Delete all items about this organization (include users)</delete_ou_text>
<delete_this_user>Delete this user</delete_this_user>
<delete_this_user_text>Are you sure to delete this user ?</delete_this_user_text>
<pattern_ver>Pattern version</pattern_ver>
<back>back</back>
<import>import</import>
<upload>upload</upload>
<use_pid>Use pid number</us_pid>
<row>row</row>
<management>Management</management>
<content_analyze>Content analyze</content_analyze>
<security_analyze>Security analyze</content_analyze>
<black_lists>Black lists engines</black_lists>
<delete_members>Delete&nbsp;members</delete_members>
<home>Home</home>
<rename>rename</rename>
<options>options</options>
<privileges>privileges</privileges>
<artica_filtersext_rules>Forbidden attachments</artica_filtersext_rules>
<artica_filtersext_rules_text>Set renattach plugin parameters in order to deny email attachments fo your organization</artica_filtersext_rules_text>
<refresh>Refresh</refresh>
<note>note</note>
<overview>overview</overview>
<senders>Senders</senders>
<top>top</top>
<today>Today</today>
<menus_left_main>Index section</menus_left_main>
<artica_policy_status>Artica-policy status</artica_policy_status>
<kav_milter_status>Kaspersky Milter status</kav_milter_status>
<emailrelay_status>E-MailRelay Status</emailrelay_status>
<emails_recieved>emails recieved</emails_recieved>
<detected_spam>Spams</detected_spam>
<filtered_spam>Filtered</filtered_spam>
<faked_spam>Faked</faked_spam>
<black_spam>Blacklisted</black_spam>
<sended>sended</sended>
<infected_spam>Infected</infected_spam>
<manage_your_org>Manage your organization</manage_your_org>
<artica_filters_rules>Others filters rules</artica_filters_rules>
<artica_filters_rules_text>Add more global checking rules in order to decrease spam emails</artica_filters_rules>
<wizard1_welcome>Welcome on artica-postfix first settings</wizard1_welcome>
<wizard1_welcome_text>This wizard will help you to create quickly first settings in order to provide a full email server in production
mode.</wizard1_welcome_text>
<network_settings>Network settings</network_settings>
<network_settings_text>You need to choose wich network interface the Postfix mail server will hook, choose on the field above</network_settings_text>
<question_company_name>Give your company name</question_company_name>
<question_domain_name>Give your eMail domain</question_domain_name>
<your_server_type>your MTA server is set as</your_server_type>
<black list>Black List</black list>
<white list>White List</white list>
<add_new_domain_mta_text>Give the domain name and point it to the mail server in order to relay your mails</add_new_domain_mta_text>
<domain_name>Domain name</domain_name>
<relay_ip>Relay IP address</relay_ip>
<smtp_server_address>SMTP server address</smtp_server_address>
<dns_servers>DNS Servers</dns_servers>
<properties>properties</properties>
<dns_server>DNS server</dns_server>
<smtp_server_port>SMTP server port</smtp_server_port>
<MX_lookups>MX lookups</MX_lookups>
<MX_lookups_text>the MX lookups option enable/disable the suppress  MX  lookups.[br]   This prevents  mail  routing loops when your machine is primary MX host.</MX_lookups_text>
<finish>finish</finish>
<audit_main_domains>Audit the main.cf about domains</audit_main_domains>
<mails_received>Emails received</mails_received>
<content_rules>Content rules</content_rules>
<content_rules_text>Add/Edit rules that discard messages [b]before[/b] saving them into your mailbox</content_rules_text>
<add_new_sieve_rule>Add a new Mailbox rule</add_new_sieve_rule>
<sieve_rules_text>Add/Edit rules in order to organize mails [b]after[/b] saving them into your mailbox</sieve_rules_text>
<spam_detection_families>Anti-spam detection families</spam_detection_families>
<virus_by_sender_domains>Virus detections by sender domains</virus_by_sender_domains>
<statistics_ou_text>View all emails statistics about your Organization</statistics_ou_text>
<all_settings_saved>All settings are saved...</all_settings_saved>
<hardware_info>Hardware Informations</hardware_info>
<hardware_info_text>See components of your system and disks usage</hardware_info_text>
<feature_disabled>This feature is currently disabled</feature_disabled>
<mailbox_main_settings>Mailboxes settings</mailbox_main_settings>
<tasks_main_settings>Cron tasks settings</tasks_main_settings>
<no_mailboxes>No mailboxes saved..</no_mailboxes>
<all>all</all>
<create_org_postfix>Create your first settings and organization</create_org_postfix>
<create_org_postfix_text>This wizard help you step by step to set your first server settings</create_org_postfix_text>
<artica_wizard>Artica wizards</artica_wizard>
<return_to>return to</return_to>
<quarantines_graph>Quarantine Graph</quarantines_graph>
<antispam_rules>Global rules</antispam_rules>
<antispam_rules_text>Define here settings when scanning emails content for all organizations</antispam_rules_text>
<monthly>monthly</monthly>
<see_config>View the generated file</see_config>
<yearly>Yearly</yearly>
<quarterly>Quartely</quarterly>
<generate_config>Rebuild config</generate_config>
<generate_config_text>Build all yours settings to a temporary ldap field</generate_config_text>
<weekly>Weekly</weekly>
<daily>Daily</daily>
<antispam_user_rules>Your SPAM settings</antispam_user_rules>
<antispam_user_rules_text>Define actions used when a SPAM to you is detected.</antispam_user_rules>
<messages_performance>Messages performance</messages_performance>
<messages_performance_text>Statistics and charts according eMails sent to you...</messages_performance_text>
<updates_error>Updates error</updates_error>
<daemon_error>Daemon errors</daemon_error>
<updates_success>Success updates</updates_success>
<details>details</details>
<update_now>perform update now</update_now>
<clean_update>Clean updates & perform update</clean_update>
<schedule>schedule</schedule>
<antivirus_settings>Antivirus Settings</antivirus_settings>
<antivirus_settings_text>Define here settings when scanning emails content</antivirus_settings_text>
<ave_pattern_date>Pattern database date is </ave_pattern_date>
<click_to_change_notif_content>Click in order to view/edit [br]template settings for this event</click_to_change_notif_content>
<group_behavior>Groups behavior</group_behavior>
<relay_behavior>Relay behavior</relay_behavior>
<relay_behavior_text2>Define here is your server is only an MTA that relay inbound mails to other servers (relay) but allow to verify users addresses
or just verify domains (Hub) [br]
if your server is a full mail server set the option to mail.
</relay_behavior_text2>
<group_behavior_text>
Some applications use settings by group.
enable or disable this feature.</group_behavior_text>
<group_behavior_text2>Some applications allows you to specify settings for each groups. (antivirus, anti-spam...). If you enable this feature, you must allocate users on specific group that store defined settings
</group_behavior_text2>
<only_postfix_events>Only Postfix events</only_postfix_events>
<all_events>All events</all_events>
<relay_behavior_text>Define the behavior of your relay: if is a simple MTA or a full mail server</relay_behavior_text>
<queue_monitoring_text>Read all mails stored in Postfix queue and flush the queue...</queue_monitoring_text>
<time_date_com_text_moscow>Click to visit the web site timeanddate.com[br]In order to see the current time in [b]moscow[/b]</time_date_com_text_moscow>

<kas_main_settings>Kaspersky Anti-Spam settings</kas_main_settings>
<remove_mailqueue>Remove all mails in queue</remove_mailqueue>
<remove_mailqueue_text>Are you sure to remove this mailqueue ?
All the emails will be deleted and not be able to restore...</remove_mailqueue_text>
<lines>lines</lines>
<reprocess_queue>reprocess all queues</reprocess_queue>
<file>file</file>
<page>page</page>
<from_cache_file>from cache file</from_cache_file>
<unable_to_locate>unable to stat</unable_to_locate>
<find_messages_whose>Find messages whose</find_messages_whose>
<apply_scripts_mailbox>apply rules to your mailbox</apply_scripts_mailbox>
<From Address>From Address</From Address>
<To Address>To Address</To Address>
<CC Address>CC Address</CC Address>
<Bcc Address>Bcc Address</Bcc Address> 
<vacation>vacation</vacation><nic_static_dns>Static DNS Servers</nic_static_dns>
<nic_static_dns_text>If your ISP provides you with a fixed or static IP DNS address server, and you want to host your own mail server</nic_static_dns_text>
<start>Start</start>
<every>every</every>
<sieve_vacation_text>This is a rule for notification that messages will not be immediately answered.</sieve_vacation_text>
<vacation_default>Hello,I am gone for a while and will read your message upon my return.</vacation_default>
<recipient>Recipient</recipient>
<recipients>recipients</recipients>
<recipient_address>Recipient Address</recipient_address>
<Connection>Connection</Connection>
<sender_address>Sender Address</sender_address>
<localdomains>Manage email domains</localdomains>
<localdomains_text>Manage all internet SMTP domains of your organization</localdomains_text>
<Correspondent>Correspondent</Correspondent>
<Sender>Sender</Sender>{postfix_network}
<Subject>Subject</Subject>
<Body>Body</Body>
<Header Field>Header Field</Header Field>
<Entire Message>Entire Message</Entire Message>
<Size>Size</Size>
<apply_settings>Apply these settings to the server and put them in production mode</apply_settings>
<Is>Is</Is>
<is regex>Regular Expression matches</is regex>
<is not regex>Regular Expression not matches</is not regex>
<from_ip_address>from tcp/ip address</from_ip_address>
<to_ip_address>to tcp/ip address</to_ip_address>
<mac_addr>MAC Address</mac_addr>
<example>example</example>
<using>using</using>
<with>with</with>
<next>next</next>
<previous>previous</previous>
<and>and</and>
<add_local_domain>Add a new local domain</add_local_domain>
<localdomains>Manage SMTP Domains</localdomains>
<localdomains_text>Add or delete SMTP domains of your organization</localdomains_text>
<or>or</or>
<view_script>View script</view_script>
<cancel>cancel</cancel>
<rule_number>Rule number</rule_number>
<prompt_add_rule_name>Give name of your new rule</prompt_add_rule_name>
<Is not>Is not</Is not>
<Contains>Contains</Contains>
<Does not Contain>Does not Contain</Does not Contain>
<Start With>Start With</Start With>
<Does not start width>Does not start width</Does not start width>
<End With>End With</End With>
<Does not End width>Does not End width</Does not End width>
<Matches>Matches</Matches>
<Does not matches>Does not matches</Does not matches>
<operator>operator</operator>
<Is greater than>is greater than</Is greater than>
<sieve rules>Mailbox rules</sieve rules>
<sieve_rules>Mailbox rules</sieve_rules>
<sieve__text>Select operations when rules matches</sieve__text>
<fileinto>Put into imap folder</fileinto>
<sieve_fileinto_text>This operation action delivers the message into the specified folder.[br]
   Implementations SHOULD support this action, but in some environments this may be impossible.
</sieve_fileinto_text>  

<sieve_reject_text>
It refuses delivery of a message by sending back an [MDN] to the sender.[br]
 It resends the message to the sender, wrapping it in a "reject" form, noting that it was rejected by the
   recipient.[br] In the following rule, message A is rejected and returned to the sender.
</sieve_reject_text>


<redirect>Redirect to email address</redirect>
<sieve_redirect_text>The "redirect to email" action is used to send the message to another user at
   a supplied address, as a mail forwarding feature does.[br]  This
  action makes no changes to the message body or existing headers, but it may add new headers.[br]
  It modifies the envelope recipient.
</sieve_redirect_text>

<keep>Keep</keep>
<sieve_keep_text>It is whatever action is taken in lieu of all other
   actions, if no filtering happens at all; generally, this simply means
   to file the message into the user's main mailbox.[br]  It
   provides a way to execute this action without needing to know the
   name of the user's main mailbox, providing a way to call it without
   needing to understand the user's setup, or the underlying mail
   system.
</sieve_keep_text>   

<discard>discard</discard>
<sieve_discard_text>
It is used to silently throw away the message.[br]  It does so by
   simply canceling the implicit keep action.[br]  If discard is used with other
   actions, the other actions still happen.[br]  Discard is compatible with
   all other actions.[br]  (For instance "Put into imap folder"+"discard" is equivalent to
   "Put into imap folder".)
</sieve_discard_text>


<add_action>add new operation</add_action>
<execute_operation>Performed operation</execute_operation>
<hotmail>Hotmail & Live</hotmail>
<fetch_hotmail>Fetch your mails from hotmail and live account</fetch_hotmail>

<Is less than>is less than</is less than>
<manage_services>Manage services</manage_services>
<manage_services_text>Start/stop managed services</manage_services_text>
<add_new_sieverule_text>Create a new rule for your mailbox, discard messages, transfert messages, move messages to a folder...</add_new_sieverule_text>
<mailbox_usage>Mailbox usage</mailbox_usage>
<manage_your_mailbox_rules>Your Mailbox rules</manage_your_mailbox_rules>
<manage_your_mailbox_rules_text>Here you can manage rules that help you to automatically order your mailbox when mails is saved into.</manage_your_mailbox_rules_text>
<system_perfomances>System perf.</system_perfomances>
<system_perfomances_datas>System datas perf.</system_perfomances_datas>
<system_perfomances_datas_text>System I/O, Hard drive and network statistics</system_perfomances_datas_text>
<system_perfomances_text>system load, memory performances statistics</system_perfomances_text>
<day>Day</day>
<week>week</week>
<month>month</month>
<mailgraph_install>Install mailgraph application</mailgraph_install>
<mailgraph_about>Mailgraph is a very simple mail statistics RRDtool frontend for Postfix and Sendmail that produces daily, weekly, monthly and yearly graphs of received/sent and bounced/rejected mail.</mailgraph_about>
<remove_mailgraph>remove mailgraph application</remove_mailgraph>
<queuegraph_about>Queuegraph is a very simple mail statistics RRDtool frontend for Postfix that produces daily, weekly, monthly and yearly graphs of Postfix's active, deferred, incoming and bounce queues.</queuegraph_about>


<APP_QUEUEGRAPH>QueueGraph</APP_QUEUEGRAPH>
<APP_GEOIP>GeoIp Databases</APP_GEOIP>
<APP_GETLIVE>Hotmail remote-mail retrieval</APP_GETLIVE>
<APP_HOTWAYD>Hotwayd remote-mail retrieval</APP_HOTWAYD>
<APP_KAV4PROXY>Kaspersky For Squid</APP_KAV4PROXY>
<APP_SQUID>Squid cache proxy</APP_SQUID>

<remove_queuegraph>Remove QueueGraph application</remove_queuegraph>
<AllowViewStatistics>View statistic area</AllowViewStatistics>
<AllowEditOuSecurity>Edit Organization Policies</AllowEditOuSecurity>
<statistics>Statistics</statistics>
<net_statistic>Network bandwith</net_statistic>

<cpu_stat>CPU Usage</cpu_stat>
<mem_stat>Memory Usage</mem_stat>
<load_stat>Load average</load_stat>
<hd_stat>Hard Drive performances</hd_stat>
<hdFree_stat>Hard drive space statistics</hdFree_stat>
<proc_stat>Process number statistics</proc_stat>

<emails_flow>eMails flow</emails_flow>
<emails_flow_day>Sent & receive per day</emails_flow_day>
<emails_flow_hour>Send & receive per hour</emails_flow_hour>
<emails_flow_week>Send & receive per week</emails_flow_week>
<emails_flow_month>Send & receive per month</emails_flow_month>

<queue_flow>Queue flow</queue_flow>
<queue_flow_day>Messages stored per day</queue_flow_day>
<queue_flow_hour>Messages stored per hour</queue_flow_hour>
<queue_flow_week>Messages stored per week</queue_flow_week>
<queue_flow_month>Messages stored per month</queue_flow_month>

<APP_YOREL>YorHel's RRD scripts</APP_YOREL>
<yorel_about>YorHel's RRD scripts si maintain by Yoran Heling live in Gieten (Netherlands) he had written usefull rrd scripts[br][a href='http://stats.yorhel.nl/info/rrdtool/']YorHel website[/a]</yorel_about>
<remove_yorel>Remove YorHel's RRD scripts</remove_yorel>
<install_yorel>Install YorHel's RRD scripts</install_yorel>

<queue_flow_text>View statistics of messages stored in PostFix queues</queue_flow_text>
<emails_flow_text>View history of eMails sended and received on your server</emails_flow_text>
<install_queuegraph>Install QueueGraph application</install_queuegraph>
<domains>domains</domains>
<mailgraph_postfix_database>emails flow rrd database</mailgraph_postfix_database>
<mailgraph_virus_database>Infected flow rrd database</mailgraph_virus_database>
<reload>reload</reload>
<statistics_engine>statistics engines</statistics_engine>
<statistics_engine_text>Enable Artica Statistics engine,graphs and monitoring functions</statistics_engine_text>
<add_new_domain>add new domain</add_new_domain>
<source config>Settings source code</source config>
<Services_Status>Services status</Services_Status>
<service_not_installed>The service is not installed</service_not_installed>
<service_running>The service currently running</service_running>
<service_stopped>The service is stopped!</service_stopped>
<postfix_status>Postfix mail system status</postfix_status>
<using_version>using version number</using_version>
<pid>process ID</pid>
<cyrus_status>Cyrus IMAP Status</cyrus_status>
<artica_filter_status>Artica-filter daemon</artica_filter_status>
<aveserver_status>Kaspersky Mail server status</aveserver_status>
<no_infos>No information can be receive</no_infos>
<action_start_service>Start the service</action_start_service>
<action_stop_service>Stop the service</action_stop_service>
<pattern_update_date>Pattern database update date</pattern_update_date>
<since>since</since>
<days>days</days>
<hours>hours</hours>
<original>original</original>
<postfix_last_error>Last postfix error found</postfix_last_error>
<license>license</license>
<pattern_database>Pattern Database date</pattern_database>
<action_keepup2date>Update database now</action_keepup2date>
<kas_status>Anti-spam status</kas_status>
<kas3>K. Anti-spam</kas3>
<some_service_is_stopped>stopped</some_service_is_stopped>
<mode>mode</mode>
<all_services_running>running</all_services_running>
<add new domain>Add a new Internet domain</add new domain>
<explain 1>Give the email domain (after the @ of your mailboxes)</explain 1>
<ou>Organisation unit</ou>
<domainName>SMTP Domain</domainName>
<members>members</members>
<address>Address</address>
<phone>Office phone</phone>
<mobile>mobile phone</mobile>
<postalAddress>Postal address</postalAddress>
<CP>Postal code</CP>
<installed_applications>installed applications</installed_applications>
<APP_MYSQL>Mysql database server</APP_MYSQL>
<installed_applications_text>See wich applications versions are installed in your system</installed_applications_text>
<town>town</town>
<BP>Post Office Box</BP>
<address_text>Define the member address,phone number,street and others informations</address_text>
<add_member>Add a new member</add_member>
<add_new_member>New member</add_new_member>
<add_new_member_text>Add a new member into your organization and selected group</add_new_member_text>
<delete>delete</delete>
<pass>pass</pass>
<compile kas config>Compiling anti-spam configurations</compile kas config>
<not allowed>You have not enough privileges to perform this operation</not allowed>
<no_usb_devices_connected>There is no USB devices connected on this computer</no_usb_devices_connected>
<no_privileges>You have not enough privileges to perform this operation</no_privileges>
<build postfix config>Building postfix main settings</build postfix config>
<select task>Select task</select task>
<task_postfix_network_auto>Postfix Prevent DHCP change IP interfaces (eth0 & eth1)</task_postfix_network_auto>
<maintenance>maintenance</maintenance>
<Anti-spam>Anti-spam</Anti-spam>
<update>update</update>
<database>database</database>
<antivirus>antivirus</antivirus>
<frequency>frequency</frequency>
<each>each</each>
<minutes>minutes</minutes>
<hours>hours</hours>
<days>days</days>
<events>events</events>
<network>network</network>
<inet_interface>Inet interface</inet_interface>
<local network>Local network</local network>
<give the new interface>Give the new interface</give the new interface>
<give the new network>Give the new network</give the new network>


<installed applications>installed applications</installed applications>
<nic_interfaces>NIC Interfaces</nic_interfaces>

<creating_mailbox>creating mailbox</creating_mailbox>
<free>free</free>
<cyrus_apply_config>Apply these settings to imap server</cyrus_apply_config>
<status>status</status>
<process_name>process name</process_name>
<stop_daemon>stop service</stop_daemon>
<start_daemon>start service</start_daemon>
#KAS
<Process Server Settings>Process Server Settings</Process Server Settings>
<Max. number of filtration processes>Max. number of filtration processes</Max. number of filtration processes>
<Anti-Spam Engine>Anti-Spam Engine</Anti-Spam Engine>
<Number of filtration processes at server start-up>Number of filtration processes at server start-up</Number of filtration processes at server start-up>
<Number of spare filtration processes>Number of spare filtration processes</Number of spare filtration processes>
<Filtration Process>Filtration Process</Filtration Process>
<Max. number of mail messages to be processed>Max. number of mail messages to be processed</Max. number of mail messages to be processed>
<Max. number of mail messages randomization>Max. number of mail messages randomization</Max. number of mail messages randomization>
<Max_idle_time_in_seconds>Max. idle time (in seconds)</Max_idle_time_in_seconds>
<Exit_delay_in_seconds>Exit delay (in seconds)</Exit_delay_in_seconds>
<Check Options>Check Options</Check Options>
<Overall timeout of all DNS requests>Overall timeout of all DNS requests (in seconds)</Overall timeout of all DNS requests>
<Check MS Word and RTF files>Check MS Word and RTF files</Check MS Word and RTF files>
<UDS_enabled>Enable UDS</UDS_enabled>
<Timeout for receiving response from UDS server>Timeout for receiving response from UDS server (in seconds)</Timeout for receiving response from UDS server>
<MTA Clients Settings>MTA Clients Settings</MTA Clients Settings>
<Filtering size limit>Filtering size limit (KB)</Filtering size limit>
<On filtering error>On filtering error</On filtering error>
<accept message>accept message</accept message>
<reject message>reject message</reject message>
<generate temporary error>generate temporary error</generate temporary error>
<Default domain>Default domain</Default domain>
<ClientDefaultDomain>Domain used for recipients whose addresses contain only the local part.[br]If this parameter is not specified, then the substitution of the domain name will not be performed[br]
(no value will be specified by default).</ClientDefaultDomain>
<Connection timeout>Connection timeout (in seconds)</Connection timeout>
<ClientDataTimeout>
	Maximum allowable waiting time (in seconds) when exchanging data with the filtering process (socket read/write timeout).
	[br]The default value is 30.
	[br] Possible values are from 10 to 100.
</ClientDataTimeout>
<Data exchange timeout>Data exchange timeout</Data exchange timeout>

<ClientConnectTimeout>
Maximum allowable waiting time (in seconds)when establishing connection with the filtering process.[br]
The default value is 40.[br]
Possible values are from 10 to 100.
</ClientConnectTimeout>

<ClientFilteringSizeLimit>The maximum message size (in kilobytes) that can be passed to the filtering process. Larger messages will be passed on without filtering.
[br]If the value of this parameter is 0 (not recommended), then this limit will not be applied and all messages will be sent to the filtering process.[br]
The default value is 500.
[br]Possible values are from 0 to 10000.
</ClientFilteringSizeLimit>

<ClientOnError>
error processing mode (unable to establish connection with the filtering process, waiting time exceeded when exchanging data, etc.)
The default is accept message.
</ClientOnError>

#Domains global ##########################################################################################################

<TITLE_DOMAINS>Global settings</TITLE_DOMAINS>
<ARRAY_TITLE>Domains list</ARRAY_TITLE>
<entities>Entities</entities>
<input_select_list>Select in list</input_select_list>

<js_del_domain>Delete this domain and all aliases</js_del_domain>
<js_expand_domain>Manage aliases and relays</js_expand_domain> 
<js_add_domain>Add a new domain</js_add_domain>
<js_add_entity>Add a new entity</js_add_entity>
<js_kav_delete_licence>Remove this domain from licence</js_kav_delete_licence>
<ARRAY_TITLE_AV>Antivirus</ARRAY_TITLE_AV>
<ARRAY_TITLE_USERS>Users num.</ARRAY_TITLE_USERS>
<ARRAY_TITLE_TRANSPORT>Relay to</ARRAY_TITLE_TRANSPORT>
<nb_domains>domains num.</nb_domains>
<av_settings>eMail antivirus settings</av_settings>

<Add_new_entity>Add a new global entity</Add_new_entity>
<xdelete_domain_text>Are tou sure to remove this domain ? 
aliases and/or transport generated for this domain will be removed too
mailboxes will not remove
</xdelete_domain_text>
<text_add_entity>Give the name of the new entity:</text_add_entity>
<text_add_domain_entity>Give the emails domain of this entity:
example : user.name@domain.tlb -> domain.tlb
</text_add_domain_entity>
<kav_add_protection_domain>Protect a new domain</kav_add_protection_domain>
<kav_legend_protection_domain>Domain to protect</kav_legend_protection_domain>


#Domains list ##########################################################################################################


<goback>Return to domains list</goback>
<ARRAY_TRANSPORT>relay redirections</ARRAY_TRANSPORT>
<bt_modify_transport>Modify transport</bt_modify_transport>
<bt_delete_transport>Delete</bt_delete_transport>



<ARRAY_ALIASES>Email Aliases</ARRAY_ALIASES>
<no_mailbox_cause_transport>This domain does not store aliases cause all emails will be forwarded to another service/server</no_mailbox_cause_transport>

<label_add_transport>Add a relay server for this domain</label_add_transport>
<label_edit_transport>Edit relay server for this domain</label_edit_transport>
<label_delete_transport>Delete relay server for this domain</label_delete_transport>
<transport_single>Transport for this domain</transport_single>
<transport_type>Service</transport_type>
<transport_ip>Destination</transport_ip>
<transport_port>Destination port</transport_port>
<transport_domain>Every mails for</transport_domain>
<transport_will_translate_to>will be redirect to </transport_will_translate_to>
<transport_add>Add relay destination</transport_add>
<transport_text_delete>Delete this transport</transport_text_delete>
<relay>relay</relay>
<relay explain>If this server didn't store users, you must point to the new mail server in order to relay your mails</relay explain>
<relay explain 2>Click on the button above in order to create a transport rule</relay explain 2>
<relay explain 3>Give the server name or ip to relay mails to</relay explain 3>
<add domain explain>Add a new Internet SMTP domain in your organisation</add domain explain>
<add group explain>Add a new users group in your organisation</add group explain>
<add user explain>Add a new user in your organisation</add user explain>
<inputbox add group>Give the group name</inputbox add group>
<inputbox add user>Give the first name and last name or eMail address of your new user</inputbox add user>
<inputbox delete group>Delete this group ?</inputbox delete group>
<delete group explain>Delete this group from tree</delete group explain>
<privileges>privileges</privileges>
<mail_from>From</mail_from>
<pages>pages</pages>
<mail_to>To</mail_to>
<date>date</date>
<operation>operation</operation>
<label_email_from>eMail address</label_email_from>
<label_email_to>target address</label_email_to>
<label_redirect>Redirect to</label_redirect>

<bt_add_aliases>save alias</bt_add_aliases>
<bt_delete_alias>delete alias</bt_delete_alias>
<bt_edit_mailbox>Edit Mailbox</bt_edit_mailbox>

<js_delete_alias_text>Are you sure to delete this alias ?</js_delete_alias_text>

<redirect_to_mailbox>Go to local mailbox</redirect_to_mailbox>
<domain_activated>Domain enabled</domain_activated>
<redirect_to_alias>Go to other</redirect_to_alias>
<users>Users</users>
<add_user>Add user</add_user>
<edit_user>Edit this user</edit_user>
<edit>Edit.</edit>

<delete_thisuser>Delete this user</delete_thisuser>
<firstname>First Name</firstname>
<lastname>Last Name</lastname>
<email>eMail address</email>
<login>Login</login>

<title>Artica-PostFix events</title>
<text>This page show you every 10 seconds events generated by Postfix mail system.</text>
<seconds>seconds</seconds>


#Mailbox ###################################################################################
<create_user_all>All users</create_user_all>
<create_user_title>eMail redirection</create_user_title>
<create_user_email>Internet address</create_user_email>
<create_user_local>Local address</create_user_local>
<create_user_remote_server>Or redirect to other server</create_user_remote_server>
<mailboxstorage_title>mailbox</mailboxstorage_title>
<mailboxstorage_path>User local path</mailboxstorage_path>
<mailboxstorage_not_define>This user currently has no Mailbox storage system, you must create it</mailboxstorage_not_define>
<bt_add_mailbox>Add Local Mailbox</bt_add_mailbox>
<mailboxstorage_password>IMAP/POP3 password</mailboxstorage_password>
<MailboxActive>Local Mailbox</MailboxActive>
<username>User name</username>
<displayname>Display name</displayname>
<surname>Surname</surname>
<subnet>subnet</subnet>
<bad_format>bad format</bad_format>
<firstname>First Name</firstname>
<lastname>Last Name</lastname>
<email>eMail address</email>
<submit>Submit</submit>
<password>Password</password>
<userid>Unique identifier[br] (mailbox)</userid>
<account_name>Account settings</account_name>
<manage_account_text>Define the global eMails settings of this account</manage_account_text>
<manage_aliases_text>Set the differents address that this user can handle to receive mails</manage_aliases_text>
<manage_mailbox_text>Define the settings, quotas... of the local mailbox of this user</manage_mailbox_text>
<move_member>Group member</move_member>
<move_member_text>Add/move this member into a group</move_member_text>
<add_member_to_group>Add member to this group</add_member_to_group>
<member_of_group>Member of groups</member_of_group>
<no_group_affected>Not affected group</no_group_affected>
<unknown>unknown</unknown>
<entries>entrie(s)</entries>
<aliases>Aliases</aliases>
<search>search</search>
<manage_mailbox>Manage Mailbox</manage_mailbox>
<are_you_sure_to_delete>Are you sure to delete</are_you_sure_to_delete>
<add>add</add>
<new>new</new>
<task>task</task>
<tasks>tasks</tasks>
<task_q1>Give the task name</task_q1>

<create_mailbox>No mailbox found: Create Mailbox</create_mailbox>
<mailbox>Mailbox</mailbox>
<mailbox_name>Mailbox name</mailbox_name>
<set_quota>Set quota</set_quota>
<list_mailboxes>List mailboxes</list_mailboxes>
<click_to_launch>Click in order to perform this operation</click_to_launch>
<imap_connection_broken>Imap connection is currently broken and informations could not be read</imap_connection_broken>
<storage_usage>Storage usage</storage_usage>
<storage_limit>Storage limit</storage_limit>
<message_usage>Messages usage</message_usage>
<message_limit>Messages limit</message_limit>
<imap_connection_locked>The imap connection is currently locked cause the imap server didn't respond on time</imap_connection_locked>
<unlock_imap_session>Unlock and try to connect to imap server</unlock_imap_session>
<account>Account</account>
<index page>index</index page>
<givenname>First Name</givenname>
<sn>Last Name</sn>
<add aliase>Add new aliase</add aliase>
<delete aliase>Delete this aliase</delete aliase>
<apply>apply</apply>
<apply config>Save & apply your policies</apply config>
<apply_settings_text>All settings are stored into the database.Modules and daemon are not changed automatically.[br]If you click on the left picture, yours settings will be applied to the server</apply_settings_text>
<apply config text>This operation will compile all your settings on the server and make them in production mode.</apply config text>
<notify_templates>notify templates</notify_templates>
<admin>Administrator</admin>

#kaspersky ##########################################################################################################
<antivirus_protection_enabled>Enable/disable antivirus domain scanning</antivirus_protection_enabled>
<antivirus_protection>Antivirus protection</antivirus_protection>
<bt_edit_antivirus_protection>submit</bt_edit_antivirus_protection>		
<js_antivirus_settings>Edit antivirus settings for this domain</js_antivirus_settings>
<LoadKasperskySettings_title>eMails scanning settings</LoadKasperskySettings_title>
<LoadKasperskySettings_general_title>General Settings</LoadKasperskySettings_general_title>
<LoadKasperskySettings_adminaddr>administrator address</LoadKasperskySettings_adminaddr>
<Infected>Infected</Infected>  	 	 
<title>Kaspersky For Mail server Global settings</title>
<LoadKasperskySettings_Check>Enable antivirus protection</LoadKasperskySettings_Check>
<LoadKasperskySettings_AddXHeaders>Add antivirus infos in mails Headers</LoadKasperskySettings_AddXHeaders>
<title_infos>Statics informations</title_infos>
<BasesPath>Antivirus database path</BasesPath>
<LocalSocketPath>Local Socket path</LocalSocketPath>
<ForwardMailer>Forward Mail ip/port</ForwardMailer>
<protected_domains>Protected domains</protected_domains>
<pversion>Program version</pversion>
<add_Kav_LicenseDomain>Add a domain in licence</add_Kav_LicenseDomain>
<license_info>License information</license_info>
<license_info_text>Display license and update it</license_info_text>
<update_kaspersky_database_title>Update antivirus database</update_kaspersky_database_title>
<recommend_update_kaspersky>You should update kaspersky antivirus database, current version is out-of-date[br]Kaspersky recommend to update it's database each hour</recommend_update_kaspersky>

# smtpscanner.logs.php

<title_logs>Kaspersky Events</title_logs> 
<text_logs>This is realtime logs of the current daemon of Kaspersky For Mail server[br]These page is refresh every 5 seconds</text_logs>
<title_licence_infos>Licence informations</title_licence_infos>
<expire_date>Expiration date</expire_date>
<product>Product</product>	   	 	 	 	 
<Cured>Cured</Cured> 			  				 
<Suspicious>Suspicious</Suspicious> 			  				 
<Corrupted>Corrupted</Corrupted> 			  				 
<Warning>Warning</Warning> 			  				 
<Filtered>Filtered</Filtered> 			  				 
		  				 
<Protected>Protected</Protected>
<av_notify_rules>Notify & actions rules</av_notify_rules>
<objects>Objects</objects>
<Quarantine>Quarantine</Quarantine>
<Administrator_rules>Administrator rules</Administrator_rules>
<notify>Notify</notify>##########################################################################################################
<actions>Action</actions>
<sender_rules>Sender&nbsp;rules</sender_rules>
<recipient_rules>Recipient&nbsp;Rules</recipient_rules>
<attach_report>Attach&nbsp;report</attach_report>
<bt_edit_notify>submit</bt_edit_notify>
<QuarantinePath>Quarantine path</QuarantinePath>


#mailbox ####################################################################################################

<mailbox_title>Edit mailbox</mailbox_title>
<mailbox_password>Password</mailbox_password>
<mailbox_created>Created on</mailbox_created>
<mailbox_path>Directory</mailbox_path>
<mailbox_username>Username</mailbox_username>
<bt_mailbox_edit>Edit mailbox settings</bt_mailbox_edit>
<quota>Mailbox size limit</quota>
<used>used</used>
<quota_0>0 means illimited</quota_0>
<bt_set_quota>Set quota</bt_set_quota>
<mailbox_confirm_password>Confirm password</mailbox_confirm_password>


#Postfix settings
<postfix_main_settings>Postfix main settings</postfix_main_settings>
<pcfg_title1>Basic Configuration</pcfg_title1>
<pcfg_title2>View main.cf</pcfg_title2>
<pcfg_title3>View master.cf</pcfg_title3>
<title_main_hash>main.cf: Hash files</title_main_hash>
<title_main_transport>main.cf: Emails transport settings</title_main_transport>
<text1>These settings allows you to pe<title>Kaspersky For Mail server Global settings</title>
<title_infos>Statics informations</title_infos>
<BasesPath>Antivirus database path</BasesPath>
<LocalSocketPath>Local Socket path</LocalSocketPath>
<ForwardMailer>Forward Mail ip/port</ForwardMailer>
<protected_domains>Protected domains</protected_domains>
<pversion>Program version</pversion>

# smtpscanner.logs.php

<title_logs>Kaspersky Events</title_logs> 
<text_logs>This is realtime logs of the current daemon of Kaspersky For Mail server[br]These page is refresh every 5 seconds</text_logs>
<title_licence_infos>Licence informations</title_licence_infos>
<expire_date>Expiration date</expire_date>
<product>Product</product>
<text1>Personalize all the connections requests to the PostFix mail system.</text1>
<myorigin_title>What domain name to use in outbound mail ?</myorigin_title>
group user policy
<myorigin_text>This parameter specifies the domain that appears in mail that is posted on this machine.[br]
The default is to use the local machine name, $myhostname, which defaults to the name of the machine.[br] Unless you are running a really small site, you probably want to change that into $mydomain, which defaults to the parent domain of the machine name.
[br]For the sake of consistency between sender and recipient addresses, myorigin also specifies the domain name that is appended to an unqualified recipient address.</myorigin_text>


<myhostname_title>hostname ?</myhostname_title>
<myhostname_text>
This parameter specifies the fully-qualified domain name of the machine running the Postfix system.[br] $myhostname appears as the default value in many other Postfix configuration parameters.[br]

By default, myhostname is set to the local machine name.[br] If your local machine name is not in fully-qualified domain name form, or if you run Postfix on a virtual interface, you will have to specify the fully-qualified domain name that the mail system should use.
[br]
Alternatively, if you specify mydomain in main.cf, then Postfix will use its value to generate a fully-qualified default value for the myhostname parameter.[br]
Examples (specify only one of the following):
[ul]
[li]host.local.domain (machine name is not FQDN)[/li]		
[li]host.virtual.domain (virtual interface)[/li]
[li]virtual.domain (virtual interface)[/li]
[/ul]
</myhostname_text>


<mynetworks_title>What clients to relay mail from ?</mynetworks_title>
<mynetworks_text>By default, Postfix will forward mail from clients in authorized network blocks to any destination.[br]
Authorized networks are defined groupwith this configuration parameter.[br]
The default is to authorize all clients in the IP subnetworks that the local machine is attached to.[br]
[i]IMPORTANT: If your machine is connected to a wide area network then your default mynetworks setting may be too friendly.[/i]

Examples:[ul]
       [li]127.0.0.0/8   (safe: authorize local machine only)[/li]
       [li]168.100.189.2/32 (authorize local machine)[/li] 
       [li]!192.168.0.1 (not this IP)[/li]
       [li][::1]/128[/li]
       [li][2001:240:587::]/64[/li]
[/ul]
[b]Note: IP version 6 address information must be specified inside [] these addresses contain the ":" character, 
and would otherwise be confused with a "type:table" pattern.
</mynetworks_text>

<mynetworks_single_text>Specify here subnet and ip address in order to allow sender to relay mail</mynetworks_single_text>

<mydestination_title>What domains to receive mail for ?</mydestination_title>
<mydestination_text>
[b](default: $myhostname, localhost.$mydomain, localhost)[/b]

    This is the list of domains that are delivered via the mail delivery transport.[br]
     By default this is the Postfix local delivery agent which looks up all recipients.[br]
    The default mydestination value specifies names for the local machine only.
    [br] On a mail domain gateway, you should also include $mydomain.
</mydestination_text> 





<bt_add_inet>Add inet interface</bt_add_inet>
<inet_interfaces_title>Bind interfaces</inet_interfaces_title>
<inet_interfaces_text>
The network interface addresses that this mail system receives mail on.[br]
Specify "all" to receive mail on all network interfaces (default), and "loopback-only" to receive mail on loopback network interfaces only 
(Postfix version 2.2 and later). [br]
The parameter also controls delivery of mail to user@[ip.address].[br]

    [i]Note 1: you need to stop and start Postfix when this parameter changes.[/i][br]

    [i]Note 2: address information may be enclosed inside [], but this form is not required here.[/i]

    [br]
    When inet_interfaces specifies just one IPv4 and/or IPv6 address that is not a loopback address,
     the Postfix SMTP client will use this address as the IP source address for outbound mail.[br]
     Support for IPv6 is available in Postfix version 2.2 and later.[br]

    On a multi-homed firewall with separate Postfix instances listening on the "inside" and "outside" interfaces,
    this can prevent each instance from being able to reach servers on the "other side" of the firewall.
    [br]A better solution for multi-homed firewalls is to leave inet_interfaces at the default value and instead use explicit IP addresses in the master.cf[br]
    SMTP server definitions.
    [br]This preserves the Postfix SMTP client's loop detection, by ensuring that each side of the firewall knows that 
    the other IP address is still the same host.[br]
     Setting $inet_interfaces to a single IPv4 and/or IPV6 address is primarily useful with virtual hosting of domains on secondary IP addresses,
     when each IP address serves a different domain (and has a different $myhostname setting).[br]
	[br]
  
    Examples:
    [ul]
	[li]all (DEFAULT)[/li]
    [li]loopback-only (Postfix version 2.2 and later)[/li]
    [li]127.0.0.1[/li]
    [li][::1] (Postfix version 2.2 and later)[/li]
    [li]192.168.1.2[/li]
    [/ul]
</inet_interfaces_text>

#service status

<WELCOME>Welcome on Artica-Postfix</WELCOME>
<db_method>Database method</db_method>
<db_enable_mailboxes>Manage local mailboxes</db_enable_mailboxes>
<domains_title>Your domains</domains_title>
<domains_link>Add, Edit, manage your eMail domains</domains_link>
<srv_postfix>Postfix service status</srv_postfix>
<srv_postfix_infos>Postfix infos</srv_postfix_infos>
<srv_postfix_version>Postfix major version</srv_postfix_version>
<srv_kav_mail>Kaspersky Antivirus For Postfix</srv_kav_mail>
<srv_artica>Artica service</srv_artica>
<using_pid>using pid number</using_pid>
<services_status>Status of artica services</services_status>
<service_name>Daemon name</service_name>
<global_memory>Global memory used</global_memory>
<process_number>Processes number</process_number>
<global_services_status>Global services status</global_services_status>
<ok_listen>The service currently listen the defined port</ok_listen>
<request_start_artica_service>You should start or restart artica service by execute /etc/init.d/artica-postfix restart</request_start_artica_service>
<postfix_status_stopped>Postfix mail system is stopped</postfix_status_stopped>
<recommend_restart_postfix>It is mandatory to restart postfix in order to accept mails</recommend_restart_postfix>
<build kav config>Building Kaspersky antivirus configurations</build kav config>
<build kas config>Preparing Kaspersky Anti-spam configurations</build kas config>
<execute>execute</execute>
#kaspersky AV
<kav_title>Kaspersky For Mail server Global settings</kav_title>
<kav_title_infos>Statics informations</kav_title_infos>
<BasesPath>Antivirus database path</BasesPath>
<LocalSocketPath>Local Socket path</LocalSocketPath>
<ForwardMailer>Forward Mail ip/port</ForwardMailer>		
<protected_domains>Protected domains</protected_domains>
<pversion>Program version</pversion>
<antivirus settings>Antivirus Settings</antivirus settings>

# smtpscanner.logs.php

<title_logs>Kaspersky Events</title_logs> 
<text_logs>This is realtime logs of the current daemon of Kaspersky For Mail server[br]These page is refresh every 5 seconds</text_logs>
<title_licence_infos>Licence informations</title_licence_infos>
<expire_date>Expiration date</expire_date>
<product>Product</product>
<save parameters>Save Parameters</save parameters>
<success>Success</success>
<failed>Failed</failed>
<on port>on socket port</on port>
<Postfix Global settings>Postfix Global settings</Postfix Global settings>
<add_new_group>Add a new group</add_new_group>
<group list>Groups list</group list>
<group name>Group name</group name>
<description>Description</description>
<identity>Identity</identity>
<rules>Rules</rules>
<users>Users</users>
<group>Group</group>
<success>Success</success>
<userPassword>Password</userPassword>
<rename to>Rename To</rename to>
<AllowFetchMails>Fetch mails</AllowFetchMails>
<AllowChangeKav>Change antivirus settings</AllowChangeKav>
<AllowChangeKas>Change Anti-Spam settings</AllowChangeKas>
<AllowChangeUserPassword>Change password</AllowChangeUserPassword>
<AllowEditAliases>Add/edit/delete aliases</AllowEditAliases>
<AllowAddGroup>Add/Delete/Modify groups</AllowAddGroup>
<AllowAddUsers>Add/Delete/Modify users</AllowAddUsers>
<AllowEditAsWbl>Anti-spam White & black lists</AllowEditAsWbl>
<AllowEditAsWbl_text>Define you banned senders and friends filter</AllowEditAsWbl_text>
<AllowChangeDomains>Add/Delete Internet domains</AllowChangeDomains>
<AsPostfixAdministrator>Manage postfix settings</AsPostfixAdministrator>
<AsArticaAdministrator>Can navigate to the entire tree</AsArticaAdministrator>
<AsSystemAdministrator>Linux system operations</AsSystemAdministrator>
<AsMailBoxAdministrator>Local Mailbox manager</AsMailBoxAdministrator>
<AllowChangeAntiSpamSettings>Define its own anti-spam settings</AllowChangeAntiSpamSettings>
<AsSquidAdministrator>Define HTTP proxies access and rules</AsSquidAdministrator>

<global settings>Global settings</global settings>
<logoff>Disconnect</logoff>
<group policy>Group policy</group policy>
<group user policy>Group users policy</group user policy>
<allow to add users>Allow to add users</allow to add users>
<group how to add user>Click on an user to add it into this group</group how to add user>
<domain>Domain</domain>
<SESSION_END>[center][h2]This session is terminated... please logon[/center][/h2]</SESSION_END>
<group how to del user>Click on user to delete it from group</group how to del user>
<your>Your</your>
<antivirus>antivirus</antivirus>
<protection>protection</protection>
<attachments filters>Attachments filters</attachments filters>
<give ext>fill the attachments extension in order to block it</give ext>
<added>Added</added>
<deleted>deleted</deleted>
<config file>Datas config</config file>
<groups>groups</groups>
<allow>allow</allow>
<logon>Logon</logon>
<white list explain>Managing the list of trusted addresses.[br] Messages from these addresses are not checked for the presence of spam signs</white list explain>
<black list explain>Managing thegroup list of banned addresses.[br] Messages from these addresses are automatically checked as Spam</black list explain>
<add email>Add eMail address</add email>
<delete mail>Delete this email address</delete mail>
<administrators>administrators</administrators>
<accountID>Account identifier</accountID>
<manage_mailman_lists>Manage Mailman lists</manage_mailman_lists>
<manage_mailman_lists_text>Create and affect distributions lists to yours organizations</manage_mailman_lists_text>

#KAS Settings
<ActionsGroup>Actions - Group</ActionsGroup>
<ActionsGroupDESC>Actions to be performed on incoming messages</ActionsGroupDESC>
<rulegeneral>Rules - General</rulegeneral>
<prepend to the subject>Prepend to the Subject</prepend to the subject>				
<kas settings>Kaspersky Anti-Spam</kas settings>
<spam option 1>If a message is recognized as 'Spam'</spam option 1>
<spam option 2>If a message is recognized as 'Probable Spam'</spam option 2>
<spam option 3>If a message is recognized as 'Blacklisted'</spam option 3>
<spam option 4>If a message is recognized as 'Formal'</spam option 4>
<spam option 5>If a message is recognized as 'Trusted'</spam option 5>
<spam option 6>If a message is recognized as 'Not Detected'</spam option 6>

<spam option 1r>Spam</spam option 1r>
<spam option 2r>Probable Spam</spam option 2r>
<spam option 3r>Blacklisted</spam option 3r>
<spam option 4r>Formal</spam option 4r>
<spam option 5r>Trusted</spam option 5r>
<spam option 6r>Not Detected</spam option 6r>


<xspamtest>Set X-SpamTest-Header</xspamtest>
<acceptmessage>Accept this message</acceptmessage>
<kassendcopy>Send a copy of this message to other recipient(s)</kassendcopy>
<kasforward>Redirect this message to other recipient(s)</kasforward>
<kasreject>Reject this message</kasreject>
<kasdelete>Delete this message</kasdelete>
<sendto>Send message to</sendto>
<save>Save</save>
<cron>cron</cron>
<files>files</files>
<ensure>ensure</ensure>
<is up>is up</is up>
<high>High</high>
<detection>Detection</detection>
<level>level</level>
<associatedDomain>Internet Domain</associatedDomain>
<opcheck1>Check artica-postfix service status</opcheck1>


<APP_MAILMAN_TEXT>Mailman is the GNU Mailing List Manager has a free software for managing electronic mail discussion and e-newsletter lists</APP_MAILMAN_TEXT>
<click_deny_skip>Click to switch between Deny or skip action[br]
[ul]
    [li][b]Green:skip[/b][/li]
    [li][b]Red:Deny[/b][/li]
[/ul]
</click_deny_skip>
<move>move</move>
    
    
<UseProxy>Enable proxy server</UseProxy>
<APP_AVESERVER>Kaspersky For Mail server</APP_AVESERVER>
<APP_MAILMAN>Mailing List Manager (mailman)</APP_MAILMAN>
<APP_KAS3>Kaspersky Anti-spam Gateway</APP_KAS3>
<APP_POSTFIX>Postfix MTA Mail system</APP_POSTFIX>
<APP_LDAP>OpenLdap Server</APP_LDAP>
<APP_CYRUS>Cyrus imap MDA system</APP_CYRUS>
<APP_FETCHMAIL>Fetchmail remote-mail retrieval</APP_FETCHMAIL>
<APP_FETCHMAIL_TINY>Fetch yours mails</APP_FETCHMAIL_TINY>
<APP_EMAILRELAY>E-MailRelay</APP_EMAILRELAY>
<APP_RENATTACH>Renattach</APP_RENATTACH>
<APP_INADYN>Inadyn Dynamic DNS updater</APP_INADYN>
<APP_DANSGUARDIAN>DansGuardian</APP_DANSGUARDIAN>
<APP_PUREFTPD>Pure-ftpd</APP_PUREFTPD>
<APP_DAR_MANAGER>Disk Archive Manager</APP_DAR_MANAGER>
<squid_status>Squid Status</squid_status>
<dansguardian_status>DansGuardian status</dansguardian_status>

<kav4proxy_status>Kaspersky For squid status</kav4proxy_status>
<nic_dynamic_dns>Dynamic DNS</nic_dynamic_dns>
<remote-mail retrieval>remote-mail retrieval</remote-mail retrieval>
<install>install</install>
<calling_daemon_to_perform_operation>calling artica daemon to perform operations</calling_daemon_to_perform_operation>
<default>default</default>
<protocol>protocol</protocol>
<remote server mailbox>Your mailbox remote server</remote server mailbox>
<remote username>remote username</remote username>
<remote password>remote password</remote password>
<Leave messages on server>Leave messages on server</Leave messages on server>
<Connect in SSL mode>Connect in SSL mode</Connect in SSL mode>
<add_routing_relay_recipient_rule>Add recipients to relay</add_routing_relay_recipient_rule>
<add_server>Add a server</add_server>
<rule>rule</rule>
<selected_rule>Selected rule</selected_rule>
<add mode>Add mode</add mode>
<edit mode>edit mode</edit mode>
<list>list</list>
<fetchmail>fetchmail</fetchmail>
<fetchmail_status>fetchmail daemon status</fetchmail_status>
<daemon>daemon</daemon>
<pool>pool</pool>
<postmaster>postmaster</postmaster>
<settings>settings</settings>
<servers_list>Servers list</servers_list>
<number_users>Users number</number_users>
<artica config>Artica daemon settings</artica config>
<AutomaticConfig>Save automatically settings on system</AutomaticConfig>
<postfix rules>postfix rules</postfix rules>
<add_new_rule>Add new rule</add_new_rule>
<header_rule>header rule</header_rule>
<match_in>Match in</match_in>The default is to permit everything.
<if>if</if>
<contains>contains</contains>
<exact_match>exact match</exact_match>
<string>string</string>
<discard>discard</discard>
<hold>hold</hold>
<prepend_text>prepend the matched text to</prepend_text>
<redirect_to_mail>redirect mail to</redirect_to_mail>
<replace_line>replace current line with</replace_line>
<reject>reject</reject>
<warn>warn</warn>
<not_match>didn't match</not_match>
<then>then</then>
<match>match</match>
<width>width</width>
<regex_filter_explain> * caracter is supported. If you want to use regex operation, prepend the line width [code][b]REGEX:[b][/code]</regex_filter_explain>
<INFOS_DISCARD_EXPLAIN>
[b]DISCARD[/b][br][i]Claim  successful delivery and silently discard the message.[br] Log the optional text if specified,  otherwise log a generic message.[/i]
</INFOS_DISCARD_EXPLAIN>
<INFOS_HOLD_EXPLAIN>
[b]HOLD[/b][br][i]
Arrange  for  the  message to be placed on the hold
              queue, and inspect the next input rule.[br]   The  message  remains  on hold until someone either deletes
              it or releases it for delivery.  Log  the  optional
              text if specified, otherwise log a generic message.
              [/i]
</INFOS_HOLD_EXPLAIN>
<INFOS_PREPEND_EXPLAIN>
[b]PREPEND[/b][br][i]
Prepend  the matched  line  with  the  specified  text, and
              inspect the next rule.[br]

              Notes:

              [li]The prepended text is output on  a  separate
                     line,  immediately  before  the  input  that
                     triggered the PREPEND action.[/li][br]

              [li]The prepended text is not considered part of
                     the  input  stream:  it  is  not  subject to
                     header/body checks or address rewriting, and
                     it does not affect the way that Postfix adds
                     missing message headers.[/li][br]

            [li]When prepending text before a message header
                     line,  the  prepended text must begin with a
                     valid message header label.[br][/li]

              
</INFOS_PREPEND_EXPLAIN>
<INFOS_REDIRECT_EXPLAIN>
[b]REDIRECT[/b][br][i]
Write a message redirection request  to  the  queue
              file,  and  inspect  the next input rule. After the
              message is queued, it will be sent to the specified
              address instead of the intended recipient(s).[br]
Fetchmail is a one-stop solution to the remote mail retrieval problem for Unix machines, quite useful to anyone with an intermittent PPP or SLIP connection to a remote mailserver. It can collect mail using any variant of POP or IMAP and forwards via port 25 to the local SMTP listener, enabling all the normal forwarding/filtering/aliasing mechanisms that would apply to local mail or mail arriving via a full-time TCP/IP connection.

Fetchmail is not a toy or a coder's learning exercise, but an industrial-strength tool capable of transparently handling every retrieval demand from those of a simple single-user ISP connection up to mail retrieval and rerouting for an entire client domain. Fetchmail is easy to configure, unobtrusive in operation, powerful, feature-rich, and well documented.

Fetchmail is open-source software. The openness of the sources is the strongest assurance of quality you can have. Extensive peer review by a large, multi-platform user community has shown that fetchmail is as near bulletproof as the underlying protocols permit.

Fetchmail is licensed under the GNU General Public License
              Note:  this action overrides the FILTER action, andrewriting of the addresses
              affects all recipients of the message. If  multiple
              REDIRECT  actions  fire,  only the last one is executed.
</INFOS_REDIRECT_EXPLAIN>
<INFOS_REPLACE_EXPLAIN>
[b]REPLACE[/b][br][i]
Replace  the  current line with the specified text,and inspect the next input line.[br]
Notes:
[li]When replacing a message  header  line,  the
                     replacement  text  must  begin  with a valid
                     header label.[/li][br]

[li]The replaced text remains part of the  input
                     stream.  Unlike  the result from the PREPEND
                     action, a replaced  message  header  may  be
                     subject  to address rewriting and may affect
                     the way that Postfix  adds  missing  message
                     headers.[/li]
</INFOS_REPLACE_EXPLAIN>
<INFOS_REJECT_EXPLAIN>
[b]REJECT[/b][br][i]
Reject  the  entire  message.  Reply  with optional
              text... when the optional text is specified, other-
              wise reply with a generic error message.[br]

              Note:   this  action  disables  further  header  or
              body_checks inspection of the current  message  and
              affects all recipients.[br]

              [br]When no code is specified at the beginning of optional text..., Postfix inserts a default
              enhanced status code of "5.7.1".
</INFOS_REJECT_EXPLAIN>
<INFOS_WARN_EXPLAIN>
[b]WARN[/b][br][i]
Log a warning with the optional text... (or  log  a
              generic  message), and inspect the next input rule.
              This action is useful for debugging and for testing
              a pattern before applying more drastic actions.
</INFOS_WARN_EXPLAIN>
<INFOS__EXPLAIN>Select the action operation when matching the rule</INFOS__EXPLAIN>
<TLS_EXPLAIN>
[b]Secure SMTP over Transport Layer Security[/b][br]SMTP servers and clients normally communicate in the clear over the Internet.[br]
In many cases, this communication goes through one or more router that is not controlled or trusted by either entity.[br]
Such an untrusted router might allow a third party to monitor or alter the communications between the server and client.[br]
Further, there is often a desire for two SMTP agents to be able to authenticate each others` identities.[br]
For example, a secure SMTP server might only allow communications from other SMTP agents it knows, or it might act differently for messages received from an agent it knows than from one it doesn't know.[br]
TLS [TLS], more commonly known as SSL, is a popular mechanism for  enhancing TCP communications with privacy and authentication. 
[br]TLS is in wide use with the HTTP protocol, and is also being used for adding security to many other common protocols that run over TCP.
</TLS_EXPLAIN>
<tls_title>Transport Layer Security</tls_title>
<tls_logging> Server-side TLS activity logging</tls_logging>
<tls_logging_intro>To get additional information about Postfix SMTP server TLS activity you can increase the log level.[br]
Each logging level also includes the information that is logged at a lower logging level.[br]
<ul style=margin:5px>[li]Use log level "{tls_log_field_3}" [br]only in case of problems.[/li]
[li]Use of log level "{tls_log_field_4}" [br]is strongly discouraged[/li][/ul]
</tls_logging_intro>
<tls_log_field_0>Disable logging of TLS activity</tls_log_field_0>
<tls_log_field_1>Log TLS handshake and certificate information</tls_log_field_1>
<tls_log_field_2>Log levels during TLS negotiation</tls_log_field_2>
<tls_log_field_3>Log hexadecimal and ASCII dump of TLS negotiation process</tls_log_field_3>
<tls_log_field_4>Log hexadecimal and ASCII dump of complete transmission after STARTTLS</tls_log_field_4>


<certificate infos>certificate infos</certificate infos>
<countryName>Country Name</countryName>
<stateOrProvinceName>State or province name</stateOrProvinceName>
<localityName>locality name</localityName>
<organization>organization</organization>
<choose_org>Choose organization</choose_org>
<organizationName>organization name</organizationName>
<organizationalUnitName>organizational unit name</organizationalUnitName>
<commonName>common name</commonName>
<emailAddress>email address</emailAddress>
<certificate password>Certificate password</certificate password>
<generate certificate>generate certificate</generate certificate>
<smtpd_tls_key_file>RSA private key file</smtpd_tls_key_file>
<smtpd_tls_cert_file>RSA certificate file </smtpd_tls_cert_file>
<smtpd_tls_CAfile>certificate of the Certification Authority file</smtpd_tls_CAfile>
<enable tls postfix>enable TLS for PostFix</enable tls postfix>
<disable tls postfix>disable TLS for postfix</disable tls postfix>
<disable_all_filters>Disable all filters</disable_all_filters>
<enable_this_filter>Enable this filter</enable_this_filter>
<organizations>organizations</organizations>
<add_new_organisation>Add a new organisation</add_new_organisation>
<add_new_organisation_explain>Add a global area that will store groups and users</add_new_organisation_explain>
<add_new_organisation_text>Give the organisation name:</add_new_organisation_text>
<delete_organisation_text>Really sure to delete this organization ?</delete_organisation_text>
<manage_organisations>Manage organizations</manage_organisations>
<manage_organisation>Manage your organization</manage_organisation>
<manage_organisations_text>Edit and add groups,edit, delete, add users into your groups into to your organization</manage_organisations_text>
<privileges>Privileges</privileges>
<privileges_text>Edit privileges and security role of users stored in this group</privileges_text>
<cyrus_imap>Cyrus IMAP</cyrus_imap>
<group_identity>Group Identity</group_identity>
<group_identity_text>Edit the group name and others infomations about this group</group_identity_text>
<synchronize mailboxes>synchronize mailboxes</synchronize mailboxes>
<mailboxes_stored_cyrus>mailboxes stored on cyrus</mailboxes_stored_cyrus>
<mailboxes_stored_ldap>mailboxes stored on LDAP</mailboxes_stored_ldap>
<success operations>success operations</success operations>
<mailbox settings>mailbox settings</mailbox settings>
<mailbox account>Account</mailbox account>
<mailbox quota>mailbox quota</mailbox quota>
<import users>import users in this organization</import users>
<import users explain>
This form allows you to put a csv file in order to import users in this organization.[br]
[ul]
[li]Your file must be in [strong]csv formatted[/strong][/li][br]
[li]Each line must be separated by a carriage return.[/li][br]
[/ul]
[code]&quot;Display Name&quot;;&quot;email&quot;;&quot;local mailbox (yes|no)&quot;;[br]
&quot;group name&quot;;
&quot;Mailbox account&quot;;&quot;password&quot;;&quot;Mailbox quota (mb)&quot;[/code]
[br]If some informations didn't exists in the file, the engine try to fill itself the better information in order to perform a success importation operation.[br] For example, if the &quot;group name field&quot; is empty, the engine will import the user into the global area.[br]
</import users explain>
<upload file>Upload file</upload file>


<import users explain 2>This is the result of the 5 lines parsed on your file.[br]Please check it if the operation will be successfull</import users explain 2>
<continue_next_process>Continue next process operation</continue_next_process>
<star_explain>Caracter * is supported on this field</star_explain>
<find user>Find user</find user>
<entries>entries</entries>
<antivirus daemon>antivirus daemon</antivirus daemon>
<logs>events</logs>
<webmail>webmail</webmail>
<licence status>licence status</licence status>
<licence operations>licence operations</licence operations>
<add new licence>add new licence</add new licence>
<aveserver_licence_add>Upload the *.key file about Kaspersky for Unix Mail server in order to update the licence.</aveserver_licence_add>
<extra infos>extra informations</extra infos>
<aveserver_main_settings>Kaspersky Anti-Virus for Postfix settings</aveserver_main_settings>
<kav4proy_main_settings>Kaspersky Anti-Virus for Squid settings</kav4proy_main_settings>
<squid_main_settings>Squid-cache settings</squid_main_settings>
<logs monitor explain>Logs monitor allows you to open a monitor console in order to show you logs files in realtime[br]This console help you to select which application you want to scan.</logs monitor explain>
<start_log_monitor>start log monitor</start_log_monitor>
<counter>counter</counter>
<refresh time>refresh time</refresh time>
<web_server_path>Full path to php artica source folder</web_server_path>
<manage_imap>Allow artica to manage IMAP server</manage_imap>
<listen_port>listen port</listen_port>
<keepup2date settings>keepup2date settings</keepup2date settings>
<UseUpdateServerUrl>Use Update Server Url</UseUpdateServerUrl>
<UseUpdateServerUrlOnly>Use Update Server Url Only</UseUpdateServerUrlOnly>
<PassiveFtp>Use Passive Ftp</PassiveFtp>
<UpdateServerUrl>Update Server Url</UpdateServerUrl>
<ProxyAddress>Proxy Address</ProxyAddress>
<ConnectTimeout>Connect Timeout</ConnectTimeout>
<filter>filter</filter>
<install_wait_few_minutes>The installation is executed and running in background mode...[br]please wait few minutes in order to see if this operation is successfull</install_wait_few_minutes>
<APP_RRDTOOL>Round Robin Database (rrdtool)</APP_RRDTOOL>
<APP_ROUNDCUBE>RoundCube WebMail system</APP_ROUNDCUBE>
<APP_ROUNDCUBE3>RoundCube WebMail system 3</APP_ROUNDCUBE3>
<plugins>plugins</plugins>
<clean_database>clean database</clean_database>
<ROUNDCUBE_NEWVERSION>New RoundCube version</ROUNDCUBE_NEWVERSION>
<ROUNDCUBE_NEWVERSION_TEXT>Upgrade your webmail software and give new features</ROUNDCUBE_NEWVERSION_TEXT>
<queue_monitoring>Queue monitoring</queue_monitoring>
<queue>queue</queue>
<email_number>email number</email_number>
<statistics>statistics</statistics>
<system statistics>system statistics</system statistics>
<ldap settings>ldap settings</ldap settings>
<ldap admin>LDAP Administrator</ldap admin>
<ldap password>LDAP password</ldap password>
<ldap suffix>LDAP suffix</ldap suffix>
<cyrus admin>Cyrus master account</cyrus admin>
<cyrus password>Cyrus Master account password</cyrus password>
<your mailbox usage>your mailbox usage</your mailbox usage>
<APP_MAILGRAPH>MailGraph[br](rrdtool frontend for mail statistics)</APP_MAILGRAPH>
<sender_canonical>rewriting sent address</sender_canonical>
<AllowSender_canonical>Change rewriting sent address</AllowSender_canonical>
<SMTP SASL Authentication>SMTP SASL Authentication</SMTP SASL Authentication>
<SMTP SASL Authentication text>ISPs usually try to avoid that their smtp server becomes an open relay.[br] Thus, they either only open it up for their customers IP ranges or they require authentication[br]This option allows Postfix to send username password for a determined domain</SMTP SASL Authentication text>
<SMTP SASL Authentication enable>Enable SMTP SASL Authentication mode</SMTP SASL Authentication enable>
<click_enable_disable>[strong]Click[/strong][br]Switch enable/disable option</click_enable_disable>
<form add/mod>Form Add & modify</form add/mod>
<manage smtpd_client_restrictions>Manage smtp client rules</manage smtpd_client_restrictions>
<smtpd_client_restrictions>Clients access restrictions rules</smtpd_client_restrictions>
<smtpd_recipient_restrictions>Recipients restrictions rules</smtpd_recipient_restrictions>
<no_rules>No rules saved..</no_rules>

<smtpd_client_restrictions_text>
Optional SMTP server access restrictions in the context of a client SMTP connection request.[br]
The default is to allow all connection requests.[br]
This section allows you to manage rules will put restrictions on what systems will be able to send mail through this server based on the client IP and host information (name).[br]
As restrictions are looked at in order, you will typically want to look at filters or restrictions that are based on local information first, in order to limit the external communications that will be initiated for each message.</smtpd_client_restrictions text>
<smtpd_sender_restrictions text>Optional restrictions that the Postfix SMTP server applies in the context of the MAIL FROM command.[br]
The default is to permit everything.[br]Restrictions are applied in the order as specified; the first restriction that matches wins
</smtpd_client_restrictions_text>

<smtpd_sender_restrictions>smtp sender rules</smtpd_sender_restrictions>
<smtpd_sender_restrictions_text>
Optional restrictions that the Postfix SMTP server applies in the context of the MAIL FROM command.
[br]
The default is to permit everything.[br]
Specify a list of restrictions,continue long lines by starting the next line.[br]
Restrictions are applied in the order as specified; the first restriction that matches wins. 
</smtpd_sender_restrictions_text>

<smtpd_recipient_restrictions_text>
The access restrictions that the Postfix SMTP server applies in the context of the RCPT TO command.[br]
The purpose of the {smtpd_recipient_restrictions} feature is to control how Postfix replies to the RCPT TO command.
[br]If the restriction list evaluates to REJECT or DEFER, the recipient address is rejected;[br]
no surprises here. If the result is PERMIT, then the recipient address is accepted.[br]
And this is where surprises can happen.
</smtpd_recipient_restrictions_text>

<check_relay_domains>Check relay domains</check_relay_domains>
<check_relay_domains_text>Permit when the client hostname matches $relay_domains, or when the resolved destination address 
matches $relay_domains, otherwise reject.[br]
The relay_domains_reject_code parameter specifies the response code for rejected requests (default: 550).[br]
</check_relay_domains_text>

<smtpd_helo_restrictions>HELO rules</smtpd_helo_restrictions>
<smtpd_helo_restrictions_text>Optional restrictions that the Postfix SMTP server applies in the context of the SMTP HELO command</smtpd_helo_restrictions_text>
<manage smtpd_sender_restrictions>Manage smtp sender rules</manage smtpd_sender_restrictions>
<up>up</up>
<down>down</down>
<enable>enable</enable>
<enabled>enabled</enabled>
<disabled>disabled</disabled>
<logging>logging</logging>
<smtp_tls_note_starttls_offer> Discovering servers that support TLS</smtp_tls_note_starttls_offer>
<smtp_tls_note_starttls_offer_text>As we decide on a "per site" basis whether or not to use TLS, 
it would be good to have a list of sites that offered "STARTTLS".[br] We can collect it ourselves with this option:[br]
If this feature is enabled and a server offers STARTTLS while TLS is not already enabled for that server, the Postfix SMTP client logs a line as follows:
[code]postfix/smtp[pid]: Host offered STARTTLS: [hostname.example.com][/code]
</smtp_tls_note_starttls_offer_text>

<sasl_title>Simple Authentication and Security Layer</sasl_title>
<sasl_intro>SASL support can be used to authenticate remote SMTP clients to the Postfix SMTP server,
and to authenticate the Postfix SMTP client to a remote SMTP server.[br]
When receiving mail, the Postfix SMTP server logs the client-provided username, 
authentication method, and sender address to the log file, and optionally grants mail access via the "Allow sasl authenticated" in client restriction.[br]
When sending mail, the Postfix SMTP client can look up the remote SMTP server hostname or destination domain (the address right-hand part) 
in a SASL password LDAP, and if a username/password is found, it will use that username and password to authenticate to the remote SMTP server.
</sasl_intro>
<sasl_little_title>SMTP Authentication</sasl_little_title>
<smtpd_sasl_auth_enable>Enable SASL Authentication</smtpd_sasl_auth_enable>
<smtpd_sasl_authenticated_header>Report the SASL authenticated user name in the log smtpd Received message header</smtpd_sasl_authenticated_header>


<permit_mynetworks>premit local network</permit_mynetworks>
<permit_mynetworks_text>Permit the request when the client IP address[br] matches any network or network address[br] listed in network settings.</permit_mynetworks_text>
<reject_rbl_client>reject IP listed in RBL</reject_rbl_client>
<reject_rbl_client_text>reject the SMTP request [br]when the reversed client network address[br] is listed with under RBL hosting service</reject_rbl_client_text>
<permit>permit</permit>
<permit_text>permit the request.[br] This restriction is useful at the end [br]of a restriction list, to make the default policy explicit</permit_text>
<permit_inet_interfaces>permit inet interfaces</permit_inet_interfaces>
<permit_inet_interfaces_text>permit the request when the client IP address matches interfaces settings</permit_inet_interfaces_text>

<permit_sasl_authenticated>permit sasl authenticated</permit_sasl_authenticated>
<permit_sasl_authenticated_text>permit the request when the client is [br]successfully authenticated via the[br] RFC 2554 (AUTH) protocol</permit_sasl_authenticated_text>

<reject_rhsbl_client>Reject IP Listed in RHSBL</reject_rhsbl_client>
<reject_rhsbl_client_text>Reject the request when the client hostname is listed under rbhsbl service</reject_rhsbl_client_text>

<reject_non_fqdn_sender>reject non fqdn sender</reject_non_fqdn_sender>
<reject_non_fqdn_sender_text>Reject the request when the MAIL FROM address[br]is not in fully-qualified domain form,[br] as required by the RFC.[br]This specifies the response code to rejected requests (default: 504).</reject_non_fqdn_sender_text>

<reject_authenticated_sender_login_mismatch>reject authenticated sender login mismatch</reject_authenticated_sender_login_mismatch>
<reject_authenticated_sender_login_mismatch_text>Enforces the reject sender login mismatch restriction for authenticated clients only.</reject_authenticated_sender_login_mismatch_text>

<reject_rhsbl_sender>Reject IP Listed in RHSBL</reject_rhsbl_sender>
<reject_rhsbl_sender_text>Reject the request when the MAIL FROM Domain is listed under rbhsbl service</reject_rhsbl_sender_text>

<reject_rhsbl_recipient>reject rhsbl recipient</reject_rhsbl_recipient>
<reject_rhsbl_recipient_text>Reject the request when the RCPT TO domain is listed with the A record "d.d.d.d" under rbhsbl service</reject_rhsbl_recipient_text>

<reject_sender_login_mismatch>reject sender login mismatch</reject_sender_login_mismatch>
<reject_sender_login_mismatch_text>Reject the request when "mailbox LDAP database" specifies an owner for the MAIL FROM address,[br] but the client is not (SASL) logged[br] in as that MAIL FROM address owner[br] or when the client is (SASL) logged in,[br] but the client login name does not [br]own the MAIL FROM address according to smtpd sender login user@elsewhere@domainmaps</reject_sender_login_mismatch_text>

<reject_unauthenticated_sender_login_mismatch>reject unauthenticated sender login mismatch</reject_unauthenticated_sender_login_mismatch>
<reject_unauthenticated_sender_login_mismatch_text>Enforces the reject sender login mismatch restriction for unauthenticated clients only.</reject_unauthenticated_sender_login_mismatch_text>

<reject_unknown_sender_domain>reject unknown sender domain</reject_unknown_sender_domain>
<reject_unknown_sender_domain_text>Reject the request when Postfix is not final destination[br] for the sender address, and the MAIL FROM address has no DNS or MX record,[br] or when it has a malformed MX record[br] such as a record with a zero-length MX hostname</reject_unknown_sender_domain_text>

<add new rule>add a new rule</add new rule>
<reject_unknown_client_hostname>reject unknown client hostname</reject_unknown_client_hostname>
<reject_unknown_client_hostname_text>Reject the client when[br][ul][li]1) the client IP address=name mapping fails,[/li][li]2) the name=address mapping fails,[/li][li]3) the name=address mapping does not match the client IP address[/li][/ul]</reject_unknown_client_hostname_text>

<reject_unknown_reverse_client_hostname>reject unknown reverse client hostname</reject_unknown_reverse_client_hostname>
<reject_unknown_reverse_client_hostname_text>Reject the SMTP connection when[br] the client IP address has no address=name mapping.[br]
This is a weaker restriction than the reject unknown client hostname rule,[br] which requires not only that[br]the address=name and name=address mappings exist,[br] but also that the two mappings reproduce the client IP address.</reject_unknown_reverse_client_hostname_text>

<reject_unlisted_recipient>reject unlisted recipient</reject_unlisted_recipient>
<reject_unlisted_recipient_text>Reject the request when the RCPT TO address is not listed[br] in the list of valid recipients for its domain class.</reject_unlisted_recipient_text>

<reject_unlisted_sender>reject unlisted sender</reject_unlisted_sender>
<reject_unlisted_sender_text>Reject the request when the MAIL FROM address is not listed[br] in the list of valid recipients for its domain class</reject_unlisted_sender_text>

<reject_unknown_recipient_domain>reject unknown recipient domain</reject_unknown_recipient_domain>
<reject_unknown_recipient_domain_text>Reject the request when Postfix is not final destination for the recipient address,[br] and the RCPT TO address has no DNS A or MX record,[br] or when it has a malformed MX record[br] such as a record with a zero-length MX hostname</reject_unknown_recipient_domain_text>

<reject_unauth_destination>reject unauth destination</reject_unauth_destination>
<reject_unauth_destination_text>Reject the request unless one of the following is true:[br]-[b]Postfix is mail forwarder:[/b] the resolved RCPT TO address matches relay_domains or a subdomain thereof,[br] and contains no sender-specified routing(user@elsewhere@domain),[br][br]-[b]Postfix is the final destination:[/b] the resolved RCPT TO address matches mydestination,
[br]inet interfaces,
[br]proxy interfaces,
[br]virtual alias domains,
[br]or virtual mailbox domains,
[br]and contains no sender-specified routing (user@elsewhere@domain). </reject_unauth_destination_text>

<reject_unverified_recipient>reject unverified recipient</reject_unverified_recipient>
<reject_unverified_recipient_text>Reject the request when mail to the RCPT TO address is known to bounce,[br] or when the recipient address destination is not reachable.</reject_unverified_recipient_text>

<check_policy_service>check policy server</check_policy_service>
<check_policy_service_text>Query the specified policy server</check_policy_service_text>

<reject_multi_recipient_bounce>reject multi-recipient bounce</reject_multi_recipient_bounce>
<reject_multi_recipient_bounce_text>Reject the SMTP Connection when the envelope sender is the null address,[br] and the message has multiple envelope recipients.[br]This usage has rare but legitimate applications:[br] under certain conditions, multi-recipient mail that was posted [br]with the DSN option NOTIFY=NEVER may be forwarded with the null sender address. </reject_multi_recipient_bounce_text>

<reject_plaintext_session>reject plaintext session</reject_plaintext_session>
<reject_plaintext_session_text>Reject the SMTP connection when the connection is not encrypted</reject_plaintext_session_text>

<reject_unauth_pipelining>reject unauth pipelining</reject_unauth_pipelining>
<reject_unauth_pipelining_text>Reject the request when the client sends SMTP commands[br] ahead of time where it is not allowed,[br] or when the client sends SMTP commands ahead of time without knowing[br] that Postfix actually supports ESMTP command pipelining.[br] This stops mail from bulk mail software[br] that improperly uses ESMTP command pipelining[br]in order to speed up deliveries</reject_unauth_pipelining_text>

<check_recipient_access>Check recipient access</check_recipient_access>
<check_recipient_access_text>Search the specified access the resolved RCPT TO address, domain, parent domains, or localpart@, and execute the corresponding action</check_recipient_access_text>

<check_client_access>Check client access</check_client_access>
<check_client_access_text>Search the named access in database for the client name, parent domains, client address, or networks obtained by stripping least significant octets</check_client_access_text>

<check_recipient_mx_access>check recipient mx access</check_recipient_mx_access>
<check_recipient_mx_access_text>Search the specified access the MX hosts for the RCPT TO address,and execute the corresponding action.[br]
[strong]Note: a result of "ACCEPT" is not allowed for safety reasons. Instead, use DUNNO in order to exclude specific hosts from blacklists</check_recipient_mx_access_text>

<check_recipient_ns_access>check recipient dns access</check_recipient_ns_access>
<check_recipient_ns_access_text>Search the specified for the DNS servers for the RCPT TO address, and execute the corresponding action</check_recipient_ns_access_text>

<reject_invalid_helo_hostname>reject invalid helo hostname</reject_invalid_helo_hostname>
<reject_invalid_helo_hostname_text>Reject the request when the HELO or EHLO hostname syntax is invalid</reject_invalid_helo_hostname_text>

<reject_non_fqdn_helo_hostname>reject non fqdn helo hostname</reject_non_fqdn_helo_hostname>
<reject_non_fqdn_helo_hostname_text>Reject the request when the HELO or EHLO hostname is not in fully-qualified domain form, as required by the RFC</reject_non_fqdn_helo_hostname_text>

<reject_unknown_helo_hostname>reject unknown helo hostname</reject_unknown_helo_hostname>
<reject_unknown_helo_hostname_text>Reject the request when the HELO or EHLO hostname has no DNS A or MX record</reject_unknown_helo_hostname_text>

<check_helo_access>check helo access</check_helo_access>
<check_helo_access_text>Search the specified access for the HELO or EHLO hostname or parent domains, and execute the corresponding action</check_helo_access_text>

<check_helo_mx_access>check helo mx access</check_helo_mx_access>
<check_helo_mx_access_text>Search the specified rule for the MX hosts for the HELO or EHLO hostname,[br]and execute the corresponding action.[br][strong]Note: a result of "ACCEPT" is not allowed for safety reasons.[br]
Instead, use DUNNO in order to exclude specific hosts from blacklists.[/strong] </check_helo_mx_access_text>

<check_helo_ns_access>check helo dns access</check_helo_ns_access>
<check_helo_ns_access_text>Search the specified rule for the DNS servers for the HELO or EHLO hostname, and execute the corresponding action.[br][strong] Note: a result of "ACCEPT" is not allowed for safety reasons.[br]
 Instead, use DUNNO in order to exclude specific hosts from blacklists.[/strong]</check_helo_ns_access_text>
 
<check_sender_access>check sender access</check_sender_access>
<check_sender_access_text>Search the specified rule for the MAIL FROM address, domain, parent domains, or localpart@, and execute the corresponding action</check_sender_access_text>

<check_sender_mx_access>check sender mx access</check_sender_mx_access>
<check_sender_mx_access_text>Search the specified access(5) database for the MX hosts for the MAIL FROM address, and execute the corresponding action.[br]
[strong]Note: a result of "ACCEPT" is not allowed for safety reasons. Instead, use DUNNO in order to exclude specific hosts from blacklists[/strong]</check_sender_mx_access_text>

<check_sender_ns_access>check sender dns access</check_sender_ns_access>
<check_sender_ns_access_text>Search the specified rule for the DNS servers for the MAIL FROM address, and execute the corresponding action. [br]
[strong]Note: a result of "ACCEPT" is not allowed for safety reasons. Instead, use DUNNO in order to exclude specific hosts from blacklists[/strong]</check_sender_ns_access>

<permit_auth_destination>permit auth destination</permit_auth_destination>
<permit_auth_destination_text>Permit the request when one of the following is true:[ul]
[li]Postfix is mail forwarder: the resolved RCPT TO address matches relay domains or a subdomain thereof,
and the address contains no sender-specified routing (user@elsewhere@domain),[/li]
[li]Postfix is the final destination: the resolved RCPT TO address matches domains, inet interfaces and the address contains no sender-specified routing (user@elsewhere@domain).[/li]
[/ul]</permit_auth_destination_text>

<smtpd_helo_required>Require Helo command</smtpd_helo_required>

<smtpd_helo_required_text>Require that a remote SMTP client introduces itself at the beginning of an SMTP session with the HELO or EHLO command</smtpd_helo_required_text>

<permit_mx_backup>Permit MX backup</permit_mx_backup>
<permit_mx_backup_text>
Permit the request when the local mail system is backup MX for the RCPT TO address, 
or when the address is an authorized destination (see "permit auth destination" for definition).
[ul]
[li]Safety: Permit MX backup does not accept addresses that have sender-specified routing information (example: user@elsewhere@domain).[/li]
[li]Safety: Permit MX backup can be vulnerable to mis-use when access is not restricted with permit_mx_backup_networks.[/li]
[li]Safety: Permit MX backup no longer accepts the address when the local mail system is primary MX for the recipient domain.[/li]
[li]Exception: Permit MX backup accepts the address when it specifies an authorized destination (see "permit auth destination" for definition).[/li] 
[/ul]
</permit_mx_backup_text>

<reject_non_fqdn_recipient>Reject non fqdn recipient</reject_non_fqdn_recipient>
<reject_non_fqdn_recipient_text>Reject the request when the RCPT TO address is not in fully-qualified domain form, as required by the RFC.
This feature specifies the response code to rejected requests (default: 504).</reject_non_fqdn_recipient_text>

<smtpd_reject_unlisted_recipient>Reject unlisted recipient</smtpd_reject_unlisted_recipient>
<smtpd_reject_unlisted_recipient_text>
Request that the Postfix SMTP server rejects mail for unknown recipient addresses,
even when no explicit "reject unlisted recipient" access restriction is specified.[br]
This prevents the Postfix queue from filling up with undeliverable MAILER-DAEMON messages.
</smtpd_reject_unlisted_recipient_text>

<warn_if_reject>Warn in log if reject</warn_if_reject>
<warn_if_reject_text>Change the meaning of the next restriction,[br] so that it logs a warning instead of rejecting a request[br] (look for logfile records that contain "reject_warning").[br] This is useful for testing new restrictions[br] in a "live" environment without risking unnecessary loss of mail</warn_if_reject_text>
<reject_text>reject...</reject_text>
<SectionSecurityRulesExplainTitle>Security rules section</SectionSecurityRulesExplainTitle>
<SectionSecurityRulesExplain>This section allows you to manage security settings when email go trought your server.
[br]These rules are translated when email agents send data on the postfix in order to recieve emails or send emails.[br]
[h3]Content rules[/h3]
These rules allows postfix to parse keywords directly in datas sended to the postfix port.[br]
you can block mails according specific content in the header part of mails.[br]
[h3]Clients rules[/h3]
These rules check the TCP/IP address of the remote servers/clients that send mails to this server in [b]RCPT TO[/b]
[h3]Senders rules[/h3]
These rules check the TCP/IP address of the remote servers/clients that send mails to this server in [b]MAIL FROM[/b] field[/b][br]
You can enable RBL RHSBL features in order to prevent spams
</SectionSecurityRulesExplain>

<APP_PROCMAIL>Procmail processing</APP_PROCMAIL>
<APP_SMBMOUNT>netshare mount tool</APP_SMBMOUNT>
<shared_folder>Shared folder name</shared_folder>
<sleeping>sleeping</sleeping>

<about_procmail>Procmail is a powerful and robust set of tools that enable you to automatically process mail as you receive it or after it is already in a message folder.[br]
Procmail is a mail processing utility, which can help you filter your mail, sort incoming mail according to sender, Subject line, length of message, keywords in the message, implement an ftp-by-mail server, and much more.[br]
Procmail is also a complete drop-in replacement for your MDA. (If this doesn't mean anything to you, you don't want to know.) </about_procmail>
<procmail_rules>Procmail rules</procmail_rules>

<manage_procmail_rules>Manage procmail rules</manage_procmail_rules>
<manage_procmail_rules_text>Add and edit rules for procmail service</manage_procmail_rules_text>
<procmail_events>Procmail events</procmail_events>
<mailman_events>Mailman daemon events</mailman_events>
<add_edit_rule>Add & edit a rule</add_edit_rule>
<if>if</if>
<select>select</select>
<if_in>if in</if_in>
<put_user_quarantine>put mails into user quarantine</put_user_quarantine>
<delete_mail>delete mail</delete_mail>
<then>then</then>
<do_nothing>do nothing</do_nothing>
<pattern>pattern</pattern>
<rule_name>rule name</rule_name>
<add_rule>add a new rule</add_rule>
<edit_rule>Edit a rule</edit_rule>
<supported>supported</supported>
<form_error>operation canceled...!
There is one or multiple errors
in this form you want to submit</form_error>
<deliver_imap>deliver mails to mailboxes server</deliver_imap>
<your_quarantine>Your quarantine</your_quarantine>
<quarantine_size>Storage size</quarantine_size>
<quarantine_number>eMails number</quarantine_number>
<manage_your_quarantine>Manage your quarantine</manage_your_quarantine>
<delete_quarantine>Delete your quarantine area</delete_quarantine>
<postfix_events>postfix events</postfix_events>
<postfix_rules>postfix rules</postfix_rules>
<security_rules>security rules</security_rules>
<security_rules_text>Edit your synthesis's [strong]SMTP rules[/strong] in one single page in order to view the scanning flow.</security_rules_text>
<security_rules_explain>This area show you all rules enabled when mails pass trought Postfix before sended to the storage mail system</security_rules_explain>
<go_to_section>go to this section</go_to_section>
<connections>Connections</connections>


<Authorized networks>Authorized networks</Authorized networks>
<Authorized networks text>Authorized to send emails trought Internet</Authorized networks text>
<daemon_listen_ip>Daemon listen interfaces</daemon_listen_ip>
<check_in_headers>Verify contents rules in header</check_in_headers>
<in>in</in>
<with_error>with the error</with_error>
<field>field</field>
<width_action>width</width_action>
<rcpt_to_rules>RCPT TO rules (clients rules)</rcpt_to_rules>
<rcpt_from_rules>Mail From rules (sender rules)</rcpt_from_rules>
<installed>installed</installed>
<not_installed>not installed</not_installed>
<postfix_events_text>Monitor the postfix logs in realtime (every 10 seconds) and verify if everything works perfectly...</postfix_events_text>
<storage_rules>Storage rules</storage_rules>
<storage_rules_text>Define here all settings about how postfix will manage it's queue and all messages stored in disks</storage_rules_text>
<soft_bounce>disables locally-generated bounces</soft_bounce>
<soft_bounce_text>Safety net to keep mail queued that would otherwise be returned to the sender.[br] This parameter disables locally-generated bounces,[br] and prevents the Postfix SMTP server from rejecting mail permanently,[br]
by changing 5xx reply codes into 4xx. However, this option is no cure for address rewriting mistakes or mail routing mistakes</soft_bounce_text>
<enable_disable>Red:Option is disabled[br]Green:Option is enabled[br]Click to change</enable_disable>
<bounce_queue_lifetime>Bounce life time</bounce_queue_lifetime>
<bounce_queue_lifetime_text>Maximal time a bounce message irelay_recipient_mapss queued[br]before it is considered undeliverable.[br]
By default, this is the same as the queue life time for regular mail.[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks).(eg:5d or 300s or 10m)[/strong][br] The default time unit is d (days).[br]
Specify 0 when mail delivery should be tried only once.</bounce_queue_lifetime_text>
<bounce_service_name>Bounce service</bounce_service_name>
<bounce_service_name_text>The name of the bounce service.[br] This service maintains a record of failed delivery attempts and generates non-delivery notifications.</bounce_service_name_text>
<bounce_size_limit>Bounce size limite</bounce_size_limit>
<bounce_size_limit_text>The maximal amount of original message text[br] that is sent in a non-delivery notification.[i][b]Specify a byte count[/i][/b]. [br]If you increase this limit, then you should increase the [strong]mime nesting limit[/strong] option value proportionally</bounce_size_limit_text>
<bounce_template_file>message templates</bounce_template_file>
<bounce_template_file_text>The Postfix bounce server produces delivery status notification (DSN) messages for undeliverable mail, delayed mail, successful delivery or address verification requests.
[br]By default, these notifications are generated from built-in templates with message headers and message text.
[br]This option allows you to override the built-in information</bounce_template_file_text>
<failure_template>failure template</failure_template>
<delay_template>Delay template</delay_template>
<success_template>success template</success_template>
<verify_template>verify template</verify_template>
<bounce_messages_rules>Bounce messages rules</bounce_messages_rules>
<bounce_messages_rules_text> The bounce daemon maintains per-message log files with delivery status information.[br]Each log file is named after the queue file that it corresponds to, and is kept in a queue subdirectory named after the service name in the master.cf file (either bounce, defer or trace).</bounce_messages_rules_text>
<bounce_messages_templates_infos>
The usage and specification of template message headers is subject to the following restrictions:
[ul]
[li]Template message header names can be specified in upper case, lower case or mixed case. Postfix always uses the spelling as shown in the example above. [/li]
[li]Template message headers must not span multiple lines. [/li]
[li]Template message headers must not contain main.cf $parameters.[/li]
[li]Template message headers must contain ASCII characters only.[/li]
[/ul]
[br]
[strong]Possible values:[/strong]
[ul]
[li]delay_warning_time_suffix[br]Expands into the value of the delay_warning_time parameter, expressed in the time unit specified by suffix, which is one of seconds, minutes, hours, days, or weeks. [br][/li]
[li]maximal_queue_lifetime_suffix[/li][br]Expands into the value of the maximal_queue_lifetime parameter, expressed in the time unit specified by suffix. See above under delay_warning_time for possible suffix values.[/li]
[/ul]
</bounce_messages_templates_infos>
<bounce_notice_recipient>notifications address</bounce_notice_recipient>
<bounce_notice_recipient_text>The recipient of postmaster notifications with the message headers of mail that Postfix did not deliver and of SMTP conversation transcripts of mail that Postfix did not receive</bounce_notice_recipient_text>
<double_bounce_sender>Notifications Sender address</double_bounce_sender>
<double_bounce_sender_text>The sender address of postmaster notifications that are generated by the mail system.[br]All mail to this address is silently discarded, in order to terminate mail bounce loops</double_bounce_sender_text>
<messages_restriction>Messages restrictions</messages_restriction>
<messages_restriction_text>All global settings that restrict emails about specific formats, size...</messages_restriction_text>
<queue_settings>Queue settings</queue_settings>
<maximal_queue_lifetime>Maximal queue life time</maximal_queue_lifetime>
<maximal_queue_lifetime_text>The maximal time a message is queued before it is sent back as undeliverable.[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks).[/strong]
The default time unit is d (days).[br]Specify 0 when mail delivery should be tried only once</maximal_queue_lifetime_text>
<message_size_limit>message size limit</message_size_limit>
<message_size_limit_text>The maximal size in bytes of a message, including envelope information</message_size_limit_text>
<mime_nesting_limit>mime nesting limit</mime_nesting_limit>
<mime_nesting_limit_text>he maximal recursion level that the MIME processor will handle.[br] Postfix refuses mail that is nested deeper than the specified limit.</mime_nesting_limit_text>
<header_address_token_limit>address limit</header_address_token_limit>
<header_address_token_limit_text>The maximal number of address tokens are allowed in an address message header.[br]Information that exceeds the limit is discarded</header_address_token_limit_text>
<antispam_engine>Antispam Engine</antispam_engine>
<antispam_engine_text>Set the global parameters of the daemon</antispam_engine_text>
<product_update_settings>updates settings</product_update_settings>
<product_update_settings_text>Settings for download updates in order to maintain the security service</product_update_settings_text>
<product_licence>Licence</product_licence>
<product_licence_text>Get the licence info and update your licence definition</product_licence_text>
<antispam_rules_group>Group rules</antispam_rules_group>
<antispam_rules_group_text>Set the anti-spam rules group according your personal privileges</antispam_rules_group_text>
<AllowChangeUserKas>Change anti-spam Settings</AllowChangeUserKas>
<select_group>Select group</select_group>
<select_group_text>Please select in the list the group you want to manage in order to see settings</select_group_text>
<antivirus_engine>Antivirus Engine</antivirus_engine>
<general_settings>general settings</general_settings>
<waiting_settings>waiting parameters</waiting_settings>
<enable_non_encrypted_sessions>Enable non-encrypted sessions</enable_non_encrypted_sessions>
<EHLOsupport8BITMIME>Support 8BITMIME in EHLO</EHLOsupport8BITMIME>
<EHLOsupport8BITMIME_text>
The 8bit-MIME is frequently used when a mail system works with national encodings using SMTP.[br]
Therefore support for that extension has been added.
[b]If your external mail system does not support the 8bit-MIME extension,it must be disabled in Kaspersky Anti-Virus settings, too.[/b]
</EHLOsupport8BITMIME_text>

<EHLOsupportDSN>DSN extension support</EHLOsupportDSN>
<EHLOsupportDSN_text>The smtpscanner component supports the DSN extension of the SMTP protocol.[br]
Support for this extension allows the component to preserve the parameters of a
mail message assigned to the latter by an incoming e-mail system.[br] Smtpscanner
in that case does not analyze the parameters transferring them instead without
modifications to a routing mail system.
[b]Prior to enabling the option, make sure that the routing mail system
supports the DSN extension.[/b]
</EHLOsupportDSN_text>

<EHLOsupportXFORWARD>X-Forward extension support</EHLOsupportXFORWARD>
<EHLOsupportXFORWARD_text>
supports the X-Forward extension for Postfix protocol only if [b]smtp[/b] is used in protocol.(see below).[br]Define the attributes like [code]NAME ADDR PROTO HELO[/code]
</EHLOsupportXFORWARD_text>
<EHLOattrsXFORWARD>X-forward attributes</EHLOattrsXFORWARD>
<report_settings>report settings</report_settings>
<AVStatistics>antivirus statistics</AVStatistics>
<AVStatistics_text>Version 5.5 of Kaspersky Anti-Virus 5.5 features an opportunity for collection and
reviewing of statistics on virus activity for a specified period.[br]
Set a path (like /var/log/kav/5.5/kav4mailservers/smtpscanner.stat) in order to enable antivirus statistics.[br]
If a path is set artica will execute at regular time statistics generation.
</AVStatistics_text>
<events>Daemon events</events>
<events_text>Read all events about this daemon in realtime in order to follow the flow...</events_text>
<read_conf>View global configuration</read_conf>
<antivirus_group_rules>Group rules</antivirus_group_rules>
<antivirus_group_rules_text>Set the antivirus rules group according your personal privileges</antivirus_group_rules_text>
<system_tasks>system tasks</system_tasks>
<system_tasks_text>Define specific tasks in order to maintain securities, productions and monitoring services</system_tasks_text>
<nic_infos>Network interfaces</nic_infos>
<nic_infos_text>Network informations of this server</nic_infos_text>
<fetchmail_about>Fetchmail is a one-stop solution to the remote mail retrieval problem for Unix machines, quite useful to anyone with an intermittent PPP or SLIP connection to a remote mailserver.[br]
It can collect mail using any variant of POP or IMAP and forwards via port 25 to the local SMTP listener, enabling all the normal forwarding/filtering/aliasing mechanisms that would apply to local mail or mail arriving via a full-time TCP/IP connection.[br]
Fetchmail is not a toy or a coder's learning exercise, but an industrial-strength tool capable of transparently handling every retrieval demand from those of a simple single-user ISP connection up to mail retrieval and rerouting for an entire client domain.[br]
Fetchmail is easy to configure, unobtrusive in operation, powerful, feature-rich, and well documented.[br]
Fetchmail is open-source software.[br] The openness of the sources is the strongest assurance of quality you can have.[br]
Extensive peer review by a large, multi-platform user community has shown that fetchmail is as near bulletproof as the underlying protocols permit.[br]
Fetchmail is licensed under the GNU General Public License</fetchmail_about>
<daemon_status>View daemon status, and specifics events</daemon_status>
<daemon_settings>Daemon settings</daemon_settings>
<daemon_settings_text>Set global parameters for the daemon</daemon_settings_text>
<fetchmail_events>fetchmail events</fetchmail_events>
<about_organization>This section allows you to manage users and domains according your privileges</about_organization>
<Give_email_or_domain>set an email address or a domain name</Give_email_or_domain>
<add_entry>Add an entry</add_entry>
<pattern_action>pattern action</pattern_action>
<click_for_help>Click on this icon[br] in order to view[br] help for this field</click_for_help>
<pattern_action_help>
When pattern matches a mail address, domain or host address, it perform an action.
[h4]EMAIL ADDRESS PATTERNS[/h4]
[ul]
[li][code]user@domain[/code][br]Matches the specified mail address.[/li]
[li][code] domain.tld[/code][br]
              Matches  domain.tld  as the domain part of an email
              address.[br]
              The pattern domain.tld also matches domains
              Otherwise,  specify [code].domain.tld[/code]  (note  the  initial  dot)  in order to match subdomains.

[li][code]user@[/code][br]Matches all mail addresses with the specified  user part.
[/ul]
[h4]HOST NAME/ADDRESS PATTERNS[/h4]
[ul][li][code]net.work.addr.ess[/code][/li]
[li][code]net.work.addr[/code][/li]
[li][code]net.work[/code][/li]
[li][code]net[/code][br]
Matches  the specified IPv4 host address or subnetwork.[br]
An IPv4 host address is a  sequence  of  four decimal octets separated by ".".[br]
Subnetworks  are  matched  by repeatedly truncating the last ".octet" from the remote IPv4 host address string  until a match is found in the access table,
or until further truncation is not possible.(eg:192.168.1.0/24)
[/ul]
</pattern_action_help>
<action>action</action>
<BCC_help>Send  one  copy  of  the  message  to the specified recipient.[br]
If multiple BCC actions are  specified  within  the same  SMTP  MAIL  transaction,[br] only the last action will be used.</BCC_help>
<OK_help>Accept the address etc. that matches the pattern</OK_help>
<REJECT_help>Reject  the  address etc. that matches the pattern</REJECT_help>
<DISCARD_help>Claim  successful delivery and silently discard the
              message.[br] Log the optional text if specified,  otherwise log a generic message.[br]
[/i]Note:  this action currently affects all recipients of the message.[/i]
</DISCARD_help>
<optional_text>optional text</optional_text>
<DUNNO_help>
  Pretend that the lookup key  was  not  found.[br]This prevents  Postfix  from  trying  substrings  of the lookup key (such as a subdomain name, or a  network address subnetwork).</DUNNO_help>
  
<FILTER_help>
after the message is queued, send the  entire  message through the specified external content filter or transport type</FILTER_help>
<click_add_filter>Click to add a transport rule or a filter rule</click_add_filter>
<select_filter>Select the appropriate filter</select_filter>

<HOLD_help>
Place the message on the hold queue,[br] where it  will sit  until someone either deletes it or releases it for delivery.[br]              
Log the optional text if  specified,[br]otherwise log a generic message.
</HOLD_help>    
<PREPEND_help>Prepend  the  specified  message header to the message.
[br]When more than one PREPEND action  executes,[br]the  first prepended header appears before the second etc. prepended header.
[br][strong]Note: this action must execute before  the  message content  is received;[br] it cannot execute in the context of "smtpd end of data restrictions"[/strong]
</PREPEND_help>         
<click_to_add_prepend>Click to add a PREPEND rule</click_to_add_prepend>
<REDIRECT_help>After  the  message  is queued,[br] send the message to the  specified  address  instead  of  the  intended recipient(s).[br]
[strong]Note:  this action overrides the FILTER action,[br] and currently affects all recipients of the message.[/strong]
</REDIRECT_help>
<WARN_help>Log a warning with the optional text, together with client information and  if  available,  with  helo,sender, recipient and protocol information.</WARN_help>
<_help>Please select one option</_help>

<transport_table>SMTP routing table</transport_table>
<transport_table_text>Edit the mail transfert routing table according you use relays in your organizations.</transport_table_text>
<transport_table_explain>If this server does not include local mailboxes for message delivery according a specific domain 
therefore all incoming mail messages must be transferred to the local host where such mailbox server is installed.[br]
The rules for transferring (routing) are set in this section.[br]
</transport_table_explain>
<add_routing_rule>Add a routing rule</add_routing_rule>
<add_global_routing_rule>Global routing rule</add_global_routing_rule>
<port>port</port>
<service>service</service>
<smtp_server>SMTP server</smtp_server>
<new_routing_domain>New routing domain</new_routing_domain>
<relay_address>SMTP server address</relay_address>
<smtp_port>SMTP port</smtp_port>
<global_organization>global organization</global_organization>
<relayhost>next-hop destination of non-local mail (relayhost)</relayhost>
<relayhost_title>What delivery method: direct or indirect ?</relayhost_title>
<relayhost_text>By default, Postfix tries to deliver mail directly to the Internet.[br]
Depending on your local conditions this may not be possible or desirable.[br]
For example, your system may be turned off outside office hours, it may be behind a firewall, [br]
or it may be connected via a provider who does not allow direct mail to the Internet.[br]
 In those cases you need to configure Postfix to deliver mail indirectly via a relay host
</relayhost_text>
<others>others</others>
<local_domains_table>SMTP Local domains</local_domains_table>
<sender_dependent_relayhost_maps>Sender-dependent smarthost lookup tables</sender_dependent_relayhost_maps>
<sender_dependent_relayhost_maps_title>Relay senders lookup tables</sender_dependent_relayhost_maps_title>
<add_sender_routing_rule>New sender routing</add_sender_routing_rule>
<sender_dependent_relayhost_maps_text>
[strong]Sender-dependent smarthost lookup tables.[/strong][br]  
The table are searched with the sender address and with the sender domain[br]
A sender-dependent override for the global "next-hop destination of non-local mail (relayhost)" parameter setting.[br]
The tables are searched by the envelope sender address and domain.[br] This information is overruled with {relay_transport}, {default_transport}[br]
If you need an smtp server to relay mail from each domain/email to each  SMTP server,
while distributing domain2.com mail as usual.[br]
[i]It only applies to remote recipients, so local deliveries could be proceed unimpeded too..[/i]
</sender_dependent_relayhost_maps_text>
<smtp_sender_dependent_authentication>sender-dependent authentication</smtp_sender_dependent_authentication>
<smtp_sender_dependent_authentication_text>
Enable sender-dependent authentication in the Postfix SMTP client;[br](see [a href=postfix.routing.table.php]Relay senders lookup tables[/a]) this is available only with SASL authentication,
 and disables SMTP connection caching to ensure that mail from different senders will use the appropriate credentials
</smtp_sender_dependent_authentication_text>

##TLS -----------------------------------------------------------------------------
<use_tls>use TLS</use_tls>
<tls_level>TLS level</tls_level>
<Opportunistic_TLS>Opportunistic TLS</Opportunistic_TLS>
<Mandatory_TLS_encryption>Mandatory TLS encryption</Mandatory_TLS_encryption>
<Mandatory_TLS_verification>Mandatory TLS verification</Mandatory_TLS_verification>
<Secure_channel_TLS>Secure-channel TLS</Secure_channel_TLS>
<use_tls_relay_explain>Use TLS communication width the defined target SMTP server</use_tls_relay_explain>
<tls_table>TLS routing table level</tls_table>
<tls_table_explain>lookup table with the Postfix SMTP client TLS usage policy by next-hop destination and by remote SMTP server hostname</tls_table_explain>
<none>Don't use feature</none>
<add_tls_smtp_server>add target SMTP TLS server</add_tls_smtp_server>
<tls_smtp_server>TLS SMTP Server</tls_smtp_server>

<main.cf>Main configuration file</main.cf>

<main.cf_explain>Read the main configuration file generated and executed by Postfix</main.cf_explain>
<reject_unverified_sender>reject unverified sender</reject_unverified_sender>
<reject_unverified_sender_help>Reject the request when mail to the MAIL FROM address is known to bounce, or when the sender address destination is not reachable</reject_unverified_sender_help>
<reject_unverified_sender_text>Reject the request when mail to the MAIL FROM address is known to bounce, or when the sender address destination is not reachable</reject_unverified_sender_text>

<Filesystem>File system</Filesystem>
<used>used</used>
<available>available</available>
<use%>use %</use%>
<mounted_on>Mounted on</mounted_on>
<disks_usage>Disks usage</disks_usage>
<memory_info>Your system memory</memory_info>
<memory_info_text>All Informations about your computer memory usage</memory_info_text>
<physical_memory>physical memory</physical_memory>
<total>total</total>
<cached>cached</cached>
<shared>shared</shared>
<swap_memory>Swap memory</swap_memory>
<security_classes>security restrictions classes</security_classes>
<postfix_restrictions_classes>Restrictions classes</postfix_restrictions_classes>
<postfix_restrictions_classes_text>Postfix restriction classes allow you to give easy-to-remember names to groups of UCE restrictions(unsolicited commercial email)(such as "permissive", "restrictive", and so on).
[br]The real reason for the existence of Postfix restriction classes is more mundane:[br]
you can't specify a lookup table on the right-hand side of a Postfix access table.[br]
This is because Postfix needs to open lookup tables ahead of time, but the reader probably does not care about these low-level details.
</postfix_restrictions_classes_text> 
<add_new_class>Add a new restriction class</add_new_class>
<give_class_name>Give the class name</give_class_name>
<restrictions_classes_list>Classes list</restrictions_classes_list>
<restrictions>restrictions</restrictions>
<edit_table>Edit the table</edit_table> 
<value>value</value>
<user_class>Personalized class</user_class>
<user_class_text></user_class_text>
<note>Description</note>
<standard_classes>standard classes</standard_classes>
<see_conf>View generated config</see_conf>
<awstats_statistics_index>awstats statistics</awstats_statistics_index>
<awstats_statistics_unknownip>Unresolved IP Address</awstats_statistics_unknownip>
<awstats_statistics_allemailr>all Receiver EMail</awstats_statistics_allemailr>
<awstats_statistics_lastemailr>Last Receiver EMail</awstats_statistics_lastemailr>
<awstats_statistics_allemails>All sender email</awstats_statistics_allemails>
<awstats_statistics_lastemails>Last sender email</awstats_statistics_lastemails>
<awstats_statistics_allhosts>All hosts</awstats_statistics_allhosts>
<awstats_statistics_lasthosts>Last hosts</awstats_statistics_lasthosts>
<main>Main</main>
<awstats>awstats</awstats>
<APP_AWSTATS>awstats</APP_AWSTATS>
<awstats_statistics_plugin_geoip_city_maxmind>Cities</awstats_statistics_plugin_geoip_city_maxmind>
<awstats_statistics_plugin_geoip_org_maxmind>Organizations</awstats_statistics_plugin_geoip_org_maxmind>
<awstats_text>AWStats is a free powerful and featureful tool that generates statistics it designed to support postfix as advanced mail server</awstats_text>
<performances_settings>Performances</performances_settings>
<performances_settings_text>All settings that could accelerate postfix processes</performances_settings_text>
<smtp_connection_cache_destinations>Postfix Connection Cache</smtp_connection_cache_destinations>
<smtp_connection_cache_destinations_minitext>Permanently enable SMTP connection caching for the specified destinations. With SMTP connection caching, a connection is not closed immediately after completion of a mail transaction. </smtp_connection_cache_destinations_minitext>
<smtp_connection_cache_destinations_text>
With SMTP connection caching, Postfix can deliver multiple messages over the same SMTP connection[br]
SMTP Connection caching is a performance feature.[br]
Whether or not it actually improves performance depends on the conditions
[ul]
[li]SMTP Connection caching can greatly improve performance when delivering mail to a destination with multiple mail servers, because it can help Postfix to skip over a non-responding server.[/li]
[li]Otherwise, the benefits of SMTP connection caching are minor: it eliminates the latency of the TCP handshake (SYN, SYN+ACK, ACK), plus the latency of the SMTP initial handshake (220 greeting, EHLO command, EHLO response).[/li]
[li]SMTP Connection caching gives no gains with respect to SMTP session tear-down. The Postfix sender process normally does not wait for the server's reply to the QUIT command, and it never waits for the TCP final handshake to complete.[/li]
[li]SMTP Connection caching introduces some overhead: the client needs to send an RSET command to find out if a connection is still usable, before it can send the next MAIL FROM command[/li]
[/ul]
 When SMTP connection caching is enabled, the sending process does not disconnect after a mail transaction, but gives the connection to the scache 
 server which keeps the connection open for a limited amount of time.[br]
After handing over the open connection to the scache server, the sender process continues with some other mail delivery request.[br]
Meanwhile, any sender process can ask the scache server for that cached connection and reuse it for mail delivery.[br]
The connection cache can be searched by destination domain name and by the IP address of the host at the other end of the connection.[br]
This allows Postfix to reuse a connection even when the remote host is mail server for domains with different names. 
[h4] The Postfix sender process supports two connection caching strategies[/h4]
[ul]
[li][strong]On-demand connection caching.[/strong]
 This is enabled by default.[br]
 When this feature is enabled, the Postfix sender process automatically saves a connection to the connection cache when a destination has a high volume of mail in the active queue. 
[br][/li]
[li][strong]Per-destination connection caching.[/strong][br]
This is enabled by explicitly listing specific destinations.[br]
After completing delivery to a selected destination, the Postfix sender process [i]always[/i] saves the connection to the connection cache
[/li]
[/ul]
</smtp_connection_cache_destinations_text>
<smtp_connection_cache_on_demand>On-demand connection caching</smtp_connection_cache_on_demand>
Temporarily enable SMTP connection caching while a destination has a high volume of mail in the active queue.[br]
With SMTP connection caching, a connection is not closed immediately after completion of a mail transaction.[br]
Instead, the connection is kept open for up to "smtp connection cache time limit" seconds.[br]
This allows connections to be reused for other deliveries, and can improve mail delivery performance.
<smtp_connection_cache_destinations_field>Per-destination connection caching</smtp_connection_cache_destinations_field>
<add_server_domain>Add a server or a domain</add_server_domain>
<disable>disable</disable>
<smtp_connection_cache_time_limit>Connection cache time limit</smtp_connection_cache_time_limit>
<smtp_connection_cache_time_limit_text>When SMTP connection caching is enabled, the amount of time that an unused SMTP client socket is kept open before it is closed.[br][i]Do not specify larger values without permission from the remote sites[/i].</smtp_connection_cache_time_limit_text>
<smtp_connection_reuse_time_limit>Connection reuse time limit</smtp_connection_reuse_time_limit>
<smtp_connection_reuse_time_limit_text>The amount of time during which Postfix will use an SMTP connection repeatedly.[br]
The timer starts when the connection is initiated (i.e. it includes the connect, greeting and helo latency, in addition to the latencies of subsequent mail delivery transactions).[br]
This feature addresses a performance stability problem with remote SMTP servers.
[br]This problem is not specific to Postfix: [i]it can happen when any MTA sends large amounts of SMTP email to a site that has multiple MX hosts.[/i][br]
The problem starts when one of a set of MX hosts becomes slower than the rest.[br]
Even though SMTP clients connect to fast and slow MX hosts with equal probability, the slow MX host ends up with more simultaneous inbound connections than the faster MX hosts, 
because the slow MX host needs more time to serve each client request.[br]
[strong]The slow MX host becomes a connection attractor.[/strong]If one MX host becomes N times slower than the rest, it dominates mail delivery 
latency unless there are more than N fast MX hosts to counter the effect.[br]
And if the number of MX hosts is smaller than N, the mail delivery latency becomes effectively that of the slowest MX host divided by the total number of MX hosts.[br]
The solution uses connection caching by limiting the amount of time during which a connection can be used repeatedly (instead of limiting the number of deliveries over that connection),
 Postfix not only restores fairness in the distribution of simultaneous connections across a set of MX hosts, it also favors deliveries over connections 
 that perform well, which is exactly what we want.[br]
The default reuse time limit, [code]300s[/code], is comparable to the various smtp transaction timeouts which are fair estimates of maximum excess 
latency for a slow delivery.[br][i]Note that hosts may accept thousands of messages over a single connection within the default connection reuse time limit.[/i][br]
This number is much larger than the limit of 10 messages per cached connection.[br]
it may prove necessary to lower the limit to avoid interoperability issues with MTAs that exhibit bugs when many messages are delivered via a single connection.
[br]A lower reuse time limit risks losing the benefit of connection reuse when the average connection and mail delivery latency exceeds the reuse time limit.
</smtp_connection_reuse_time_limit_text>
<connection_cache_ttl_limit>maximal time-to-live</connection_cache_ttl_limit>
<connection_cache_ttl_limit_text>The maximal time-to-live value that the scache server connection cache server allows.[br]
Requests that specify a larger TTL will be stored with the maximum allowed TTL.
[br] The purpose of this additional control is to protect the infrastructure against careless people. </connection_cache_ttl_limit_text>
<connection_cache_status_update_time>Cache status update time</connection_cache_status_update_time>
<connection_cache_status_update_time_text>How frequently the scache server logs usage statistics with connection cache hit and miss rates for logical destinations and for physical endpoints</connection_cache_status_update_time_text>
<address_verify_map>Address verification database</address_verify_map>
<address_verify_map_minitext>Manage Persistent storage of address verification information</address_verify_map_minitext>
<address_verify_map_text>
By default, address verification information is not stored in a persistent file.[br]
You have to specify one.[br]Persistent storage is off by default because it may need more disk space than is available in your file system.[br]
Address verification information is cached by the Postfix [i]verify[/i] daemon.
Postfix has a bunch of parameters that control the caching of positive and negative results.[br]
The Address verification database configuration parameter specifies an optional database for sender or recipient address verification results.[br]
If you don't specify a file, all address verification information is lost after "postfix reload" or "postfix stop".
[br]If your /var file system has sufficient space specify here the path to the database eg [code](/var/postfix/verify)[/code]
[br][i]NOTE: Do not put this file in a file system that may run out of space.[/i]
[br] When the address verification table gets corrupted the world comes to an end. Meanwhile, you will not receive mail via SMTP.
The verify daemon process will create a new database when none exists, and will open/create the file before it enters the chroot jail and before it drops root privileges. 
</address_verify_map_text>
<address_verify_map_field>Verify database path</address_verify_map_field>
<address_verify_sender>eMail for sender notifications</address_verify_sender>
<address_verify_sender_text> The sender address to use in address verification probes; prior the default was "postmaster".[br]
To avoid problems with address probes that are sent in response to address probes, the Postfix SMTP server excludes the probe sender address from all SMTPD access blocks.
Specify an empty value (address_verify_sender =) or <> if you want to use the null sender address.[br]
[i]Beware, some sites reject mail from <>, even though RFCs require that such addresses be accepted[/i].
</address_verify_sender_text> 
<address_verify_negative_cache>Enable caching of failed address</address_verify_negative_cache>
<address_verify_negative_cache_text>Enable caching of failed address verification probe results.[br]
When this feature is enabled, the cache may pollute quickly with garbage.[br]
When this feature is disabled, Postfix will generate an address probe for every lookup.</address_verify_negative_cache_text>
<address_verify_negative_expire_time>time after which a failed probe expires</address_verify_negative_expire_time>
<address_verify_negative_expire_time_text>The time after which a failed probe expires from the address verification cache.[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks).[/strong]</address_verify_negative_expire_time_text>
<address_verify_negative_refresh_time>Time after which a failed address refreshed</address_verify_negative_refresh_time>
<address_verify_negative_refresh_time_text>The time after which a failed address verification probe needs to be refreshed.[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). [/strong]</address_verify_negative_refresh_time_text>
<address_verify_poll_count>Times to query the verify service</address_verify_poll_count>
<address_verify_poll_count_text>How many times to query the verify service for the completion of an address verification request in progress.[br]
[strong]The default poll count is 3.[/strong][br]
Specify [strong]1[/strong] to implement a crude form of [strong]greylisting[/strong], that is, always defer the first delivery request for a never seen before address</address_verify_poll_count_text>
<address_verify_poll_delay>Delay between queries for the completion</address_verify_poll_delay>
<address_verify_poll_delay_text>The delay between queries for the completion of an address verification request in progress.[br]
[strong]The default polling delay is 3 seconds.[/strong][br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). [/strong]
</address_verify_poll_delay_text>
<address_verify_positive_expire_time>Time after which a successful probe expires</address_verify_positive_expire_time>
<address_verify_positive_expire_time_text>
The time after which a successful probe expires from the address verification cache.[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). [/strong]
</address_verify_positive_expire_time_text>
<address_verify_positive_refresh_time>Time after which a successful address refreshed</address_verify_positive_refresh_time>
<address_verify_positive_refresh_time_text>
The time after which a successful address verification probe needs to be refreshed.[br]
The address verification status is not updated when the probe fails (optimistic caching).[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). [/strong]
</address_verify_positive_refresh_time_text>
<add_routing_relay_domain_rule>Add a domain to relay</add_routing_relay_domain_rule>
<title_postfix_tuning>Postfix Performance Tuning</title_postfix_tuning>
<title_postfix_tuning_text>The hints and tips in this document help you improve the performance of Postfix systems that already work.</title_postfix_tuning_text>
<title_postfix_tuning_1>Doing more work with your SMTP server processes</title_postfix_tuning_1>
<title_postfix_tuning_1_text>With Postfix versions 2.0 and earlier, the smtpd server pauses before reporting an error to an SMTP client.
[br]The idea is called tar pitting.[br]However, these delays also slow down Postfix. When the smtpd server replies slowly, sessions take more time, 
so that more smtpd server processes are needed to handle the load.[br]
When your Postfix smtpd( server process limit is reached, new clients must wait until a server process becomes available.[br]
This means that all clients experience poor performance.[br]
You can speed up the handling of smtpd server error replies by turning off the delay by set [code]0[/code]
</title_postfix_tuning_1_text>
<title_postfix_tuning_2> Slowing down SMTP clients that make many errors</title_postfix_tuning_2>
<title_postfix_tuning_2_text>
 The Postfix smtpd server maintains a per-session error count.[br]
 The error count is reset when a message is transferred successfully, and is incremented when a client request is unrecognized or unimplemented,
 when a client request violates access restrictions, or when some other error happens.[br]
As the per-session error count increases, the smtpd server changes behavior and begins to insert delays into the responses.
[br]The idea is to slow down a run-away client in order to limit resource usage.[br]
[i]IMPORTANT: These delays slow down Postfix, too.[br]
When too much delay is configured, the number of simultaneous SMTP sessions will increase until it reaches the smtpd server process limit, 
and new SMTP clients must wait until an smtpd server process becomes available. [/i]
[ul]
[li]When the error count reaches "soft error limit" (default: 10), the Postfix smtpd server delays all non-error and error responses by "error sleep time" seconds (default: 1 second).[/li]
[li]When the error count reaches "hard error limit" (default: 20) the Postfix smtpd server breaks the connection.[/li][/ul]
</title_postfix_tuning_2_text>

<smtpd_soft_error_limit>Soft error limit</smtpd_soft_error_limit>
<smtpd_soft_error_limit_text>The number of errors a remote SMTP client is allowed to make without delivering mail before the Postfix SMTP server slows down all its responses.[br]
the Postfix SMTP server delays all responses by "error sleep time" seconds.</smtpd_soft_error_limit_text>

<smtpd_error_sleep_time>Error Sleep Time</smtpd_error_sleep_time>
<smtpd_error_sleep_time_text>the SMTP server response delay after a client has made more than "soft error limit" errors, 
and fewer than "hard error limit" errors, without delivering mail.</smtpd_error_sleep_time_text>

<smtpd_hard_error_limit>Hard error limit</smtpd_hard_error_limit>
<smtpd_hard_error_limit_text>The maximal number of errors a remote SMTP client is allowed to make without delivering mail. The Postfix SMTP server disconnects when the limit is exceeded.</smtpd_hard_error_limit_text>


<title_postfix_tuning_3>Measures against clients that make too many connections</title_postfix_tuning_3>
<title_postfix_tuning_3_text>
 The Postfix smtpd server can limit the number of simultaneous connections from the same SMTP client,
 as well as the connection rate and the rate of certain SMTP commands from the same client.[br]
 These statistics are maintained by the anvil server (translation: if anvil breaks, then connection limits stop working).[br]
[i]IMPORTANT: These limits must not be used to regulate legitimate traffic: mail will suffer grotesque delays if you do so.[/i]
[br] The limits are designed to protect the smtpd server against abuse by out-of-control clients. </title_postfix_tuning_3_text>

<smtpd_client_connection_count_limit>Clients connection count limit</smtpd_client_connection_count_limit>
<smtpd_client_connection_count_limit_text>
How many simultaneous connections any client is allowed to make to this service.[br]
By default, the limit is set to half the default process limit value.[br]
[strong]To disable this feature, specify a limit of 0.[/strong]
[i]WARNING: The purpose of this feature is to limit abuse. It must not be used to regulate legitimate mail traffic. [/i]
</smtpd_client_connection_count_limit_text>

<smtpd_client_connection_rate_limit>Client connection rate limit</smtpd_client_connection_rate_limit>
<smtpd_client_connection_rate_limit_text>
The maximal number of connection attempts any client is allowed to make to this service per time unit.[br]
The time unit is specified with the "anvil rate time unit" configuration parameter.[br]
By default, a client can make as many connections per time unit as Postfix can accept.[br]
[strong]To disable this feature, specify a limit of 0.[/strong][br]
[i]WARNING: The purpose of this feature is to limit abuse. It must not be used to regulate legitimate mail traffic
</smtpd_client_connection_rate_limit_text>

<smtpd_client_message_rate_limit>Client message rate limit</smtpd_client_message_rate_limit> 
<smtpd_client_message_rate_limit_text>
The maximal number of message delivery requests that any client is allowed to make to this service per time unit, 
regardless of whether or not Postfix actually accepts those messages.[br]
 The time unit is specified with the the "anvil rate time unit" configuration parameter.[br]
By default, a client can send as many message delivery requests per time unit as Postfix can accept.[br]
[strong]To disable this feature, specify a limit of 0.[/strong]
[i]WARNING: The purpose of this feature is to limit abuse. It must not be used to regulate legitimate mail traffic. [/i]</smtpd_client_message_rate_limit_text>

<smtpd_client_recipient_rate_limit>Client recipient rate limit</smtpd_client_recipient_rate_limit>
<smtpd_client_recipient_rate_limit_text>
The maximal number of recipient addresses that any client is allowed to send to this service per time unit,
 regardless of whether or not Postfix actually accepts those recipients.[br]
 The time unit is specified with the "anvil rate time" unit configuration parameter.[br]
By default, a client can make as many recipient addresses per time unit as Postfix can accept.[br]
[strong]To disable this feature, specify a limit of 0.[/strong]
[i]WARNING: The purpose of this feature is to limit abuse. It must not be used to regulate legitimate mail traffic. [/i]
</smtpd_client_recipient_rate_limit_text>

<smtpd_client_new_tls_session_rate_limit>Client new TLS session rate limit</smtpd_client_new_tls_session_rate_limit>
<smtpd_client_new_tls_session_rate_limit_text>
The maximal number of new (i.e., uncached) TLS sessions that a remote SMTP client is allowed to negotiate with this service per time unit.[br]
 The time unit is specified with the the "anvil rate time" configuration parameter.[br]
By default, a remote SMTP client can negotiate as many new TLS sessions per time unit as Postfix can accept.[br]
[strong]To disable this feature, specify a limit of 0. Otherwise, specify a limit that is at least the per-client concurrent session limit, or else legitimate client sessions may be rejected.[/strong][br]
[i]WARNING: The purpose of this feature is to limit abuse. It must not be used to regulate legitimate mail traffic. [/i]
</smtpd_client_new_tls_session_rate_limit_text>

<smtpd_client_event_limit_exceptions>Client exceptions list</smtpd_client_event_limit_exceptions>
<smtpd_client_event_limit_exceptions_text>
Clients that are excluded from connection count, connection rate, or SMTP request rate restrictions.[br] See the mynetworks parameter description for the parameter value syntax.[br]
By default, clients in trusted networks are excluded.[br]
 Specify a list of network blocks, hostnames or .domain names (the initial dot causes the domain to match any name below it)
</smtpd_client_event_limit_exceptions_text>

<title_postfix_tuning_4>General mail delivery performance tips</title_postfix_tuning_4>
<title_postfix_tuning_4_text>
[ul]
[li]Don't overwhelm the disk with mail submissions.[br] Optimize the mail submission rate by tuning the number of parallel submissions and/or by tuning the Postfix 
[strong]in flow delay[/strong] parameter setting[/li]

[li]Reduce the [strong]connect timeout[/strong] and [strong]helo timeout[/strong] values so that Postfix does not waste lots of time connecting to non-responding remote SMTP servers.[/li]
[li]Use a [strong][a href=postfix.fallback.relay.php]fallback relay host[/strong][/a] for mail that cannot be delivered upon the first attempt.[br]
 This "graveyard" machine can use shorter retry times for difficult to reach destinations[/li]
[li]Speed up disk updates with a large (64MB) persistent write cache.[br]
This allows disk updates to be sorted for optimal access speed without compromising file system integrity when the system crashes.[/li]
[li]Use a solid-state disk (a persistent RAM disk).[br] This is an expensive solution that should be used in combination with short SMTP timeouts 
and a [a href=postfix.fallback.relay.php]fallback relay "graveyard" machine[/a] that delivers mail for problem destinations.[/li]
 [/ul]
</title_postfix_tuning_4_text>

<in_flow_delay>In flow delay</in_flow_delay>
<in_flow_delay_text>
Time to pause before accepting a new message, when the message arrival rate exceeds the message delivery rate.[br]
This feature is turned on by default (it's disabled on SCO UNIX due to an SCO bug).[br]
With the default 100 SMTP server process limit, "in flow delay as 1s" limits the mail inflow to 100 messages per second above the number of messages delivered per second.[br]
[strong]Specify 0 to disable the feature.[br]Valid delays are 0..10.[/strong]
</in_flow_delay_text>


<smtp_helo_timeout>HELO Timeout</smtp_helo_timeout>
<smtp_helo_timeout_text>The SMTP client time limit for sending the HELO or EHLO command, and for receiving the initial server response.[br]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). [/strong][br]
The default time unit is s (seconds).
</smtp_helo_timeout_text>

<smtp_connect_timeout>Connect timeout</smtp_connect_timeout>
<smtp_connect_timeout_text>
The SMTP client time limit for completing a TCP connection, or zero (use the operating system built-in time limit).[br]
When no connection can be made within the deadline, the Postfix SMTP client tries the next address on the mail exchanger list.[br]
[strong]Specify 0 to disable the time limit (i.e. use whatever timeout is implemented by the operating system).[/strong]
[br][strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).[/strong]
</smtp_connect_timeout_text>

<title_postfix_tuning_5>Tuning the number of recipients per delivery</title_postfix_tuning_5>
<title_postfix_tuning_5_text>
The [strong]"default destination recipient limit"[/strong] parameter (default: 50) 
controls how many recipients a Postfix delivery agent will send with each copy of an email message.[br]
You can override this setting for specific Postfix delivery agents.[br]
For example, [strong]"uucp destination recipient limit[/strong] = 100" would limit the number of recipients per UUCP delivery to 100.[br]
If an email message exceeds the recipient limit for some destination, the Postfix queue manager 
breaks up the list of recipients into smaller lists.[br]
Postfix will attempt to send multiple copies of the message in parallel.[br]
[i]IMPORTANT: Be careful when increasing the recipient limit per message delivery;[br]
some smtpd servers abort the connection when they run out of memory or when a hard recipient limit is reached, so that the message will never be delivered.[/i][br]
The [strong]"smtpd recipient limit"[/strong] parameter (default: 1000) controls how many recipients the Postfix smtpd server will take per delivery.[br]
The default limit is more than any reasonable SMTP client would send.[br]
The limit exists to protect the local mail system against a run-away client. 
</title_postfix_tuning_5_text>

<default_destination_recipient_limit>default destination recipient limit</default_destination_recipient_limit>
<default_destination_recipient_limit_text>
The default maximal number of recipients per message delivery.[br]This is the default limit for delivery via the lmtp, pipe, smtp and virtual delivery agents.[br]
Setting this parameter to a value of 1 changes the meaning of the corresponding per-destination concurrency limit from concurrency per domain into concurrency per recipient
</default_destination_recipient_limit_text>

<smtpd_recipient_limit>Recipient limit</smtpd_recipient_limit>
<smtpd_recipient_limit_text>The maximal number of recipients that the Postfix SMTP server accepts per message delivery request.</smtpd_recipient_limit_text>

<title_postfix_tuning_6>Tuning the frequency of deferred mail delivery attempts</title_postfix_tuning_6>
<title_postfix_tuning_6_text>
 When a Postfix delivery agent (smtp(8), local(8), etc.) is unable to deliver a message it may blame the message itself, or it may blame the receiving party.[br]
 [ul]
[li]When the delivery agent blames the message, the queue manager gives the queue file a time stamp into the future, 
so it won't be looked at for a while.[br]
By default, the amount of time to cool down is the amount of time that has passed since the message arrived.[br]
This results in so-called exponential backoff behavior.[/li]
[li]When the delivery agent blames the receiving party (for example a local recipient user, or a remote host), 
the queue manager not only advances the queue file time stamp, but also puts the receiving party on a "dead" list so that it will be skipped for some amount of time.[/li]
[/ul]
This process is governed by a bunch of little parameters.
[ul]
[li][strong]queue run delay[/strong](default: 300 seconds; before Postfix 2.4: 1000s)[br]How often the queue manager scans the queue for deferred mail. [/li]
[li][strong]minimal backoff time[/strong] (default: 300 seconds; before Postfix 2.4: 1000s)[br]
The minimal amount of time a message won't be looked at, and the minimal amount of time to stay away from a "dead" destination.[/li]
[li][strong]maximal backoff time[/strong] (default: 4000 seconds)[br]The maximal amount of time a message won't be looked at after a delivery failure. [/li]
[li][strong]maximal queue lifetime[/strong] (default: 5 days)[br]How long a message stays in the queue before it is sent back as undeliverable.[br]
Specify 0 for mail that should be returned immediately after the first unsuccessful delivery attempt.[/li]
[li]bounce_queue_lifetime (default: 5 days, available with Postfix version 2.1 and later) How long a MAILER-DAEMON message stays in the queue before it is considered undeliverable.
[br] Specify 0 for mail that should be tried only once. [/li]
[li][strong]qmgr message recipient limit (default: 20000)[/li][/strong]
The size of many in-memory queue manager data structures.[br]
Among others, this parameter limits the size of the short-term, in-memory list of "dead" destinations.[br]
Destinations that don't fit the list are not added.[/li]
[/ul]
[i]IMPORTANT: If you increase the frequency of deferred mail delivery attempts, or if you flush the deferred mail queue frequently,
 then you may find that Postfix mail delivery performance actually becomes worse.[/i][br]
 [strong]The symptoms are as follows:[/strong]
 [ul]
[li]The active queue becomes saturated with mail that has delivery problems. New mail enters the active queue only when an old message is deferred.
[br] This is a slow process that usually requires timing out one or more SMTP connections.[/li]
[li]All available Postfix delivery agents become occupied trying to connect to unreachable sites etc.[br]
New mail has to wait until a delivery agent becomes available.[br]
 This is a slow process that usually requires timing out one or more SMTP connections.[/li]
[/ul]When mail is being deferred frequently, fixing the problem is always better than increasing the frequency of delivery attempts.
[br] However, if you can control only the delivery attempt frequency, consider using a dedicated fallback_relay "graveyard" machine for bad destinations,
 so that these destinations do not ruin the performance of normal mail deliveries. 
 [/ul]
</title_postfix_tuning_6_text>


<click_to_expand_or_collapse>Click to expand or collapse</click_to_expand_or_collapse>

<queue_run_delay>Queue run delay</queue_run_delay>
<queue_run_delay_text>
The time between deferred queue scans by the queue manager;[br]
prior to Postfix 2.4 the default value was 1000s.[br]
[i]This parameter should be set less than or equal to "minimal backoff time".[/i][br]
See also "maximal backoff time".
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds)[/strong]
</queue_run_delay_text>

<minimal_backoff_time>Minimal backoff time</minimal_backoff_time>
<minimal_backoff_time_text>The minimal time between attempts to deliver a deferred message; prior to Postfix 2.4 the default value was 1000s.[br]
This parameter also limits the time an unreachable destination is kept in the short-term, in-memory, destination status cache.[br]
[i]This parameter should be set greater than or equal to  "queue run delay".[br] See also "maximal backoff time".[/i]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).[/strong]
</minimal_backoff_time_text>

<maximal_backoff_time>Maximal backoff time</maximal_backoff_time>
<maximal_backoff_time_text>The maximal time between attempts to deliver a deferred message.[br]
[i]This parameter should be set to a value greater than or equal to "minimal backoff time".[br]
See also "queue run delay".[/i]
[strong]Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).[/strong]
</maximal_backoff_time_text>

<qmgr_message_recipient_limit>qmgr message recipient limit</qmgr_message_recipient_limit>
<qmgr_message_recipient_limit_text>The maximal number of recipients held in memory by the Postfix queue manager, and the maximal size of the size of the short-term, in-memory "dead" destination status cache.</qmgr_message_recipient_limit_text>

<qmgr_message_recipient_minimum>qmgr message recipient minimum</qmgr_message_recipient_minimum>
<qmgr_message_recipient_minimum_text>The minimal number of in-memory recipients for any message. This takes priority over any other in-memory recipient limits (i.e., the global "qmgr message recipient limit" and the per "transport recipient limit") if necessary.[br]
[strong]The minimum value allowed for this parameter is 1.[/strong]</qmgr_message_recipient_minimum_text>

<title_postfix_tuning_7>Tuning the number of Postfix processes</title_postfix_tuning_7>
<title_postfix_tuning_7_text>The "default process limit" configuration parameter gives direct control over how many daemon processes Postfix will run.[br]
As of Postfix 2.0 the default limit is 100 smtp client processes, 100 smtp server processes, and so on.[br]
This may overwhelm systems with little memory, as well as networks with low bandwidth.[br]
You can change the global process limit by specifying a non-default "default process limit".
</title_postfix_tuning_7_text>

<default_process_limit>Default process limit</default_process_limit>
<default_process_limit_text>The default maximal number of Postfix child processes that provide a given service. </default_process_limit_text>


<title_postfix_tuning_8>Tuning the number of simultaneous deliveries</title_postfix_tuning_8>
<title_postfix_tuning_8_text>
 Although Postfix can be configured to run 1000 SMTP client processes at the same time, it is rarely desirable that it makes 
 1000 simultaneous connections to the same remote system.[br]
 For this reason, Postfix has safety mechanisms in place to avoid this so-called "thundering herd" problem.[br]
The Postfix queue manager implements the analog of the TCP slow start flow control strategy:
[i]when delivering to a site, send a small number of messages first, then increase the concurrency as long as all goes well; reduce concurrency in the face of congestion.[/i][br]
[ul]The [strong]"initial destination concurrency"[/strong] parameter (default: 5) controls how many messages are initially sent to the same destination before adapting 
delivery concurrency.[br]
Of course, this setting is effective only as long as it does not exceed the process limit and the destination concurrency limit for the specific mail transport channel.[/li]
[li]The [strong]"default destination concurrency limit"[/strong] parameter (default: 20) controls how many messages may be sent to the same destination simultaneously.[br]
 You can override this setting for specific message delivery transports by taking the name of the master.cf entry and appending "_destination_concurrency_limit".[br]
[/ul]
Examples of transport specific concurrency limits are:
[ul]
[li]The [strong]"local destination concurrency limit"[/strong] parameter (default: 2) controls how many messages are delivered simultaneously to the same local recipient.
[br]The recommended limit is low because delivery to the same mailbox must happen sequentially, so massive parallelism is not useful.[br]
Another good reason to limit delivery concurrency to the same recipient:[br] if the recipient has an expensive shell command in her .forward file, 
or if the recipient is a mailing list manager, you don't want to run too many instances of those processes at the same time.[/li]
[li]The default [strong]"smtp destination concurrency limit"[/strong] of 20 seems enough to noticeably load a system without bringing it to its knees.[br]
Be careful when changing this to a much larger number.[/li][/ul]
The above default values of the concurrency limits work well in a broad range of situations.[br]
Knee-jerk changes to these parameters in the face of congestion can actually make problems worse.[br]
Specifically, large destination concurrencies should never be the default.[br]
They should be used only for transports that deliver mail to a small number of high volume domains.[br]
A common situation where high concurrency is called for is on gateways relaying a high volume of mail from between the Internet and an intranet mail environment.[br]
Approximately half the mail (assuming equal volumes inbound and outbound) will be destined for the internal mail hubs.[br]
Since the internal mail hubs will be receiving all external mail exclusively from the gateway, 
it is reasonable to configure the gateway to make greater demands on the capacity of the internal SMTP servers.[br]
The tuning of the inbound concurrency limits need not be trial and error.[br]
 A high volume capable mailhub should be able to easily handle 50 or 100 (rather than the default 20) simultaneous connections, 
 especially if the gateway forwards to multiple MX hosts.[br]
When all MX hosts are up and accepting connections in a timely fashion, throughput will be high.[br]
If any MX host is down and completely unresponsive, the average connection latency rises to at least 1/N * $smtp_connection_timeout, if there are N MX hosts.[br]
This limits throughput to at most the destination concurrency * N / "smtp connection timeout".
[br]For example, with a destination concurrency of 100 and 2 MX hosts, each host will handle up to 50 simultaneous connections.[br]
If one MX host is down and the default SMTP connection timeout is 30s, the throughput limit is [code]100 * 2 / 30 ~= 6[/code] messages per second.[br]
This suggests that high volume destinations with good connectivity and multiple MX hosts need a lower connection timeout, values as low as [code]5s[/code] or even [code]1s[/code]
can be used to prevent congestion when one or more, but not all MX hosts are down.[br]
If necessary, set a higher "transport destination concurrency limit" and a lower "smtp connection timeout" 
(with a "-o" override in master.cf since this parameter has no per-transport name) for the relay transport and any transports dedicated for specific high volume destinations.
</title_postfix_tuning_8_text>

<initial_destination_concurrency>initial destination concurrency</initial_destination_concurrency>
<initial_destination_concurrency_text>The initial per-destination concurrency level for parallel delivery to the same destination.[br]
This limit applies to delivery via smtp, and via the pipe and virtual delivery agents.[br]
[strong]Warning: with concurrency of 1, one bad message can be enough to block all mail to a site.[/strong]
</initial_destination_concurrency_text>

<default_destination_concurrency_limit>default destination concurrency limit</default_destination_concurrency_limit>
<default_destination_concurrency_limit_text>he default maximal number of parallel deliveries to the same destination.
[br]This is the default limit for delivery via the lmtp, pipe, smtp and virtual delivery agents.</default_destination_concurrency_limit_text>

<local_destination_concurrency_limit>local destination concurrency limit</local_destination_concurrency_limit>
<local_destination_concurrency_limit_text>The maximal number of parallel deliveries via the local mail delivery transport to the same recipient 
(when "local destination recipient limit = 1") or the maximal number of parallel deliveries to the same local domain (when "local destination recipient limit > 1").[br]
This limit is enforced by the queue manager.[br]
The message delivery transport name is the first field in the entry in the master.cf file.[br]
[strong]A low limit of 2 is recommended[/strong], just in case someone has an expensive shell command in a .forward file or in an alias (e.g., a mailing list manager).[br]
[i]You don't want to run lots of those at the same time.[/i]
</local_destination_concurrency_limit_text>

<smtp_destination_concurrency_limit>smtp destination concurrency limit</smtp_destination_concurrency_limit>
<smtp_destination_concurrency_limit_text>The maximal number of parallel deliveries to the same destination via the smtp message delivery transport.
[br] This limit is enforced by the queue manager.[br]
 The message delivery transport name is the first field in the entry in the master.cf file.</smtp_destination_concurrency_limit_text>

<relay_domains_table>Relay domains allowed</relay_domains_table>
<routing_rule>Routing rule</routing_rule>
<transport_maps_pattern_explain>
[ul]
[li][strong]user+extension@domain[/strong]: Mail for user+extension@domain is delivered through transport.[/li]
[li][strong]user@domain[/strong]:Mail  for user@domain is delivered through transport to nexthop.[/li]
[li][strong]domain[/strong]:Mail for domain is delivered through transport to nexthop.[/li]
[li][strong].domain[/strong]:Mail for any subdomain of domain is delivered through  transport[/li]
[/ul]
[i]Note 1: the special pattern * represents any address (i.e. it functions as the wild-card pattern)[/i]
</transport_maps_pattern_explain>
<relay_recipient_maps>Relay recipients allowed</relay_recipient_maps>

<routing_relay_recipient>Relay Recipients allowed</routing_relay_recipient>
<relay_recipient_maps_text> Optional lookup tables with all valid addresses in the domains that match "relay domains".[br]
Specify @domain as a wild-card for domains that have no valid recipient list,
and become a source of backscatter mail: Postfix accepts spam for non-existent recipients and then floods innocent people with undeliverable mail.[br]
Technically, tables listed with "Relay recipients allowed" are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from table lookup.[br]
If this parameter is non-empty, then the Postfix SMTP server will reject mail to unknown relay users.[br]
This feature is off by default. </relay_recipient_maps_text>
<smtpd_error_sleep_time>Error Sleep Time</smtpd_error_sleep_time>
<smtpd_error_sleep_time_text>the SMTP server response delay after a client has made more than "soft error limit" errors, and fewer than "hard error limit" errors, without delivering mail</smtpd_error_sleep_time_text>



<smtp_fallback_relay>Fall back relay servers</smtp_fallback_relay>
<smtp_fallback_relay_tiny>You can use a dedicated relay  machine for bad destinations.These destinations will not ruin the performance of normal mail deliveries</smtp_fallback_relay_tiny>
<smtp_fallback_relay_text>When mail is being deferred frequently,
 fixing the problem is always better than increasing the frequency of delivery attempts.[br]
 However, if you can control only the delivery attempt frequency, consider using a dedicated [strong]fallback relay "graveyard"[/strong] machine for bad destinations,
  so that these destinations do not ruin the performance of normal mail deliveries.[br]
This "graveyard" machine could use shorter retry times parameters for difficult to reach destinations. [br]
If you specify multiple SMTP destinations, Postfix will try them in the specified order.[br]
To prevent mailer loops between MX hosts and fall-back hosts, Postfix version 2.3 and later will not use this feature for destinations that it is MX host for.   
  </smtp_fallback_relay_text>
<name>Name</name>
<observations>Observations</observations>
<task_name>Task name</task_name>
<task_command>Task Shell command</task_command>
<run_every>Run every</run_every>
<months>Months</months>
<dayw>DaysOfWeek</dayw>
<add_every>Add every</add_every>
<more_stats>More Statistics</more_stats>
<give_a_number_0_60>Put in this filed a number between 0 to 59 or "*" to set all[br]and press "Enter" key to submit</give_a_number_0_60>
<give_a_number_1_31>Put in this filed a number between 1 to 31 or "*" to set all and press "Enter" key to submit</give_a_number_1_31>
<mailto_task>Notification recipient</mailto_task>
<add_new_task>Add a new task</add_new_task>
<add_artica_tasks>Add predefined tasks</add_artica_tasks>
<add_artica_tasks_text>Select predefined tasks in the field list bellow.[br]</add_artica_tasks_text>

<artica-cron-awstats-mail_text>Execute scripts each 5 minutes in order to generate awstats mails statistics </artica-cron-awstats-mail_text>
<artica-cron-awstats-mail>awstats mails statistics</artica-cron-awstats-mail>

<artica-cron-keepup2date>Kaspersky Anti-virus update databases</artica-cron-keepup2date>
<artica-cron-keepup2date_text>Launch Kaspersky antivirus update program each hours</artica-cron-keepup2date_text>

<artica-cron-watchdog>Watchdog</artica-cron-watchdog>
<artica-cron-watchdog_text>Ensure that the artica service is always up.</artica-cron-watchdog_text>

<artica-cron-kasupdate>Kaspersky Anti-spam Database update</artica-cron-kasupdate>
<artica-cron-kasupdate_text>Launch Kaspersky anti-spam update program each hours</artica-cron-kasupdate_text>

<artica-cron-postfixinet>Postfix change inet interfaces</artica-cron-postfixinet>
<artica-cron-postfixinet_text>Change Inet interfaces values if the configuration file doesn't reflect the reality.[br]This prevent installing Postfix in DHCP mode..</artica-cron-postfixinet_text>

<artica-cron-queuegraph>QueueGraph generation</artica-cron-queuegraph>
<artica-cron-queuegraph_text>Execute each minutes the statistics queueGraph generator</artica-cron-queuegraph_text>

<artica-cron-mailgraph>Mailgraph pictures generator</artica-cron-mailgraph>
<artica-cron-mailgraph_text>Generate graphs and images in the artica folder</artica-cron-mailgraph_text>

<artica-cron-quarantine>Artica quarantine generator</artica-cron-quarantine>
<artica-cron-quarantine_text>Clean users quarantine and generate HTML reports by email for users. </artica-cron-quarantine_text>

<nic_static_dns>Static DNS Servers</nic_static_dns>
<APP_DNSMASQ>DNS forwarder caching</APP_DNSMASQ>
<APP_BOGOFILTER>Bogofilter</APP_BOGOFILTER>
<APP_BOGOFILTER_TEXT>Bogofilter is a mail filter that classifies mail as spam or ham (non-spam) by a statistical analysis of the message's header and content (body).</APP_BOGOFILTER_TEXT>

<SECURITY_MODULES>Security modules</SECURITY_MODULES>
<CORE_MODULES>Core modules</CORE_MODULES>
<STAT_MODULES>Statistics modules</STAT_MODULES>
<MAIL_MODULES>Messaging modules</MAIL_MODULES>
<dnsmasq_settings>dnsmasq settings</dnsmasq_settings>
<dnsmasq_DNS_records>MX Records</dnsmasq_DNS_records>
<dnsmasq_DNS_records_text>Dnsmasq can serve DNS MX records with its database</dnsmasq_DNS_records_text>
<mxexamples>[ul][li]thekelleys.org.uk go to thekelleys.org.uk with weight 5[/li][li]thekelleys.org.uk go to eyas.biff.org.uk with weight 30[/li][/ul]</mxexamples>
<mxrecdomainfrom>Domain</mxrecdomainfrom>
<mxrecdomainto>Targeted domain or computer</mxrecdomainto>
<mxheight>MX priority</mxheight>
<mx-target>MX Target</mx-target>
<others_options>Other options</others_options>
<mx-target_text>Set the default target for MX records created using the "local MX" option</mx-target_text>
<localmx>Local MX</localmx>
<localmx_text>Return an MX record pointing to the MX Target for all local machines.</localmx_text>
<selfmx>Self MX</selfmx>
<selfmx_text>Return an MX record pointing to itself for all local machines</selfmx_text>
<dns_main_settings>DNS settings and tweeks</dns_main_settings>
<nic_static_dns>Static DNS Servers</nic_static_dns>
<nic_static_dns_text>If your ISP provides you with a fixed or static IP DNS address server, and you want to host your own mail server</nic_static_dns_text>
<net_settings>Network IP Settings</net_settings>
<net_settings_text>Change your network configuration IP, add IP aliases and more...</net_settings_text>
<ip_aliases>IP aliases</ip_aliases>
<no_aliases>No aliases</no_aliases>
<nic>Network interface</nic>
<mode>Mode</mode>
<tcp_address>TCP Address</tcp_address>
<netmask>Netmask</netmask>
<gateway>Gateway</gateway>
<broadcast>Broadcast</broadcast>
<basic_configuration>Basic settings</basic_configuration>
<advanced_options>Advanced options</advanced_options>
<ip_aliases>IP aliases</ip_aliases>
<session_expired>Your session as expired</session_expired>
<session_expired_text>You need to logon in order to continue[br]Click on the link below in order to go to the logon page[a href=logon.php]logon[/a][/center]</session_expired_text>
<current_config>Current configuration</current_config>
<saved_settings>Saved configuration</saved_settings>
<add_nic_aliase>Add alias</add_nic_aliase>
<alias>Alias</alias>
<tcp_main_settings>Network cards parameters</tcp_main_settings>
<show_config_file>View generated config file</show_config_file>
<will_deleted_apply_config>Delete after apply configuration</will_deleted_apply_config>
<task_manager>Tasks Manager</task_manager>
<memory>Memory</memory>
<kill_process>Kill process</kill_process>
<reload>Reload</reload>
<postfix_last_errors>Last postfix/cyrus errors</postfix_last_errors>
<give_ip_from_ip_to>Give the from IP and the to IP addresses</give_ip_from_ip_to>
<select_ip_address>Select address</select_ip_address>
<postfix_network>Postfix Network settings</postfix_network>
<postfix_network_text>Specify here your local network and what network IP addresses postfix must bind </postfix_network_text>
<rows>rows</rows>
<search_break>Results of your query exceed maximum rows that the system accept, please specify a query that match more your research</search_break>
<go_back>Go Back</go_back>
<create>create</create>

<create_user>Create an user account</create_user>
<create_user_text>Add a new user/mailbox into your organization</create_user_text>
<name_the_new_account_title>The new unique identifier</name_the_new_account_title>
<name_the_new_account_field>Type the unique identifier of the new account</name_the_new_account_field>
<name_the_new_account_explain>This name will be the unique identifier in the users database, it will be used to access to the mailbox and to the portal</name_the_new_account_explain>

<give_password>Type the user password</give_password>
<give_password_text>This password is used to access to the portal and to the mailbox</give_password_text>
<select_user_group_title>Select the user group</select_user_group_title>
<select_user_group_text>A group is used to define privileges of features and operations permitted in the portal.[br]If you didn't select a group, the user will be a simple user with only access to it's mailbox</select_user_group_text>
<user_email_text>Set the first email address of this user,this email will be the master email address of this account</user_email_text>
<back_to>Back to</back_to>
<global_blacklist>Domains Black List</global_blacklist>
<global_blacklist_text>This feature allows you to deny senders domains for all your organization</global_blacklist_text>

<manage_groups>Manage users groups</manage_groups>
<manage_groups_text>Add and modify groups of your organization, define privileges settings</manage_groups_text>
<add_group>add a group</add_group>
<no_group>No group</no_group>
<manage>Manage</manage>
<maximum>Maximum</maximum>
<normal>Normal</normal>
<high>High</high>
<expired>Expired</expired>
<kas_licence_text>Upload the *.key file about Kaspersky Anti-Spam gateway in order to update the licence.</kas_licence_text>
<manage_groups_antispam>Manage Global antispam rules</manage_groups_antispam>
<manage_groups_antispam_text>Define the default settings of your antispam.This settings could be overrided by users settings</manage_groups_antispam_text>
<quarantine>Quarantine</quarantine>
<query_quarantine>Query your quarantine</query_quarantine>
<query_quarantine_text>Find mails stored in a specific area and release them.</query_quarantine_text>
<mail_events>eMails events</mail_events>
<empty_quarantine>Empty your quarantine</empty_quarantine>
<empty_quarantine_text>Empty your entire quarantine area</empty_quarantine_text>
<empty_quarantine_text_mesgbox>Are you sure to empty your quarantine area ? All mails wille be deleted </empty_quarantine_text_mesgbox>
<global_quarantine_rules>Global quarantine settings</global_quarantine_rules>
<empty_table_confirm>This operation will delete all SQL table rows. Execute this operation ?</empty_table_confirm>
<time>time</time>
<resource>resource</resource>
<client>client</client>
<restart_computer>Reboot</restart_computer>
<restart_computer_text>This operation will reboot this computer </restart_computer_text>
<shutdown_computer>Shutdown</shutdown_computer>
<shutdown_computer_text>This operation will shutdown the computer, it will not be available...</shutdown_computer>
<virus>virus</virus>
<stopped>Stopped</stopped>
<start_service>Start the service</start_service>
<start_service_text>Click on the image in order to start the daemon</start_service_text>
<stop_service>Stop the service</stop_service>
<stop_service_text>Click on the image in order to stop the daemon</stop_service_text>
<config_file>Config file</config_file>
<isnot>is not</isnot>
<is>is</is>
<deny>Deny</deny>
<type>type</type>
<refresh>Refresh</refresh>
<htmlSizeBlocker>HTML Size Manager</htmlSizeBlocker>
<htmlSizeBlocker_intro>HTML Size Manager allows you to define rule to transform messages with a specified size and allow recipients to donwload attached files</htmlSizeBlocker_intro>
<htmlSizeBlocker_text>HTML Size Manager use mhonarc application to transform big messages,defined in rules, to HTML[br]This to prevent sending mails with a big size to pass trought network.[br]
It send notifications to recipients in order to allow them to "download" attached files instead receive them by email</htmlSizeBlocker_text>
<enable>Enable</enable>
<simple_mode>Simple mode</simple_mode>
<advanced_mode>Advanced mode</advanced_mode>
<queue_flow_year>Messages stored per year</queue_flow_year>
<close>close</close>
<dansguardian_main_settings>DansGuardian main config and rules</dansguardian_main_settings>
<squid_events>Squid Events</squid_events>
<start_daemon_events>Start Daemon events</start_daemon_events>
<features_disabled_smtp>These features are disabled, if you want to enable them, go to "GLOBAL Settings" and enable the required level</features_disabled_smtp>
<APP_KAV4PROXY_TEXT>Kaspersky For SQUID provides secure Internet access for all employees in the organization,
automatically removing malicious and potentially hostile programs from incoming HTTP/FTP traffic.</APP_KAV4PROXY_TEXT>
<main_settings>Main settings</main_settings>
<pureftpd_main_settings>Pure-ftpd settings</pureftpd_main_settings>
<pureftpd_satus>Pure-ftpd status</pureftpd_satus>
<sqlgrey_satus>SqlGrey status</sqlgrey_satus>
<APP_SQLGREY>SqlGrey Policy server</APP_SQLGREY>
<APP_CROSSROADS>Crossroads balancing</APP_CROSSROADS>
<sqlgrey_main_settings>SQLGrey Main configurations</sqlgrey_main_settings>
<last_update>last update</last_update>
<or_select>Or select value</or_select>
<postfix_status>Postfix status</postfix_status>
<APP_KAVMILTER>Kaspersky Antivirus Milter</APP_KAVMILTER>
<APP_AMAVISD_NEW>Amavisd-new</APP_AMAVISD_NEW>
<APP_AMAVISD_MILTER>Amavisd Milter daemon</APP_AMAVISD_MILTER>
<APP_ARTICA>Artica Core server</APP_ARTICA>
<APP_CLAMAV>Clam AntiVirus</APP_CLAMAV>
<APP_SPAMASSASSIN>SpamAssassin</APP_SPAMASSASSIN>
<APP_ARTICA_POLICY>Artica Policy server</APP_ARTICA_POLICY>
<APP_MYSQL_ARTICA>Mysql Database engine</APP_MYSQL_ARTICA>
<APP_APACHE>Apache server</APP_APACHE>
<APP_BOA>Boa middleware</APP_BOA>
<APP_SASLAUTHD>Cyrus SASL Auth</APP_SASLAUTHD>
<APP_FRESHCLAM>ClamAV Updater</APP_FRESHCLAM>
<APP_MILTERGREYLIST>Milter-greylist</APP_MILTERGREYLIST>
<services_status_failed>Failed services</services_status_failed>
<services_status>Status of all services</services_status>
<services_status_text>View all services and their status in one page</services_status_text>
<pattern_version>Pattern version</pattern_version>
<QUARANTINE>Quarantine area</QUARANTINE>
<global_whitelist>White & black list admin</global_whitelist>
<global_smtp_rules>Global SMTP rules</global_smtp_rules>
<folders_monitor>Folders monitor</folders_monitor>
<artica_autoupdate>Auto-Update Artica Core</artica_autoupdate>
<view>View</view>
<parameters>Parameters</parameters>
<APP_CYRUS_IMAP>Cyrus-imap</APP_CYRUS_IMAP>
<Administration>Administration</Administration>
<POSTFIX_PLUGINS>Postfix Plugins</POSTFIX_PLUGINS>
<APP_OBM>Open Business Management</APP_OBM>
<APP_OBM_APACHE>Lighttpd for OBM</APP_OBM_APACHE>
<APP_NTPD>Network Time Protocol</APP_NTPD>
<APP_MAILFROMD>MailFromD</APP_MAILFROMD>
<APP_IPTABLES>Iptables Firewall</APP_IPTABLES>
<APP_BACKUP>Artica Backup</APP_BACKUP>
<other_settings>Other settings</other_settings>
<APP_ARTICA_TAIL>Artica-tail</APP_ARTICA_TAIL>
<APP_KAS3_MILTER>Kaspersky Anti-spam Milter</APP_KAS3_MILTER>
<APP_LIGHTTPD>LigHttpd (light and fast webserver)</APP_LIGHTTPD>
<APP_SAMBA_SMBD>Samba TCP/IP Daemon</APP_SAMBA_SMBD>
<APP_SAMBA_NMBD>Samba Resolution Daemon</APP_SAMBA_NMBD>
<APP_CLAMAV_MILTER>Clamav-Milter Daemon</APP_CLAMAV_MILTER>
<APP_SPAMASS_MILTER>Spamassassin-Milter daemon</APP_SPAMASS_MILTER>
<APP_SPFMILTER>SPF mail filter module</APP_SPFMILTER>
<APP_SAMBA>Samba Shares Engine</APP_SAMBA>
<interface_restarted>This user interface will be restarted to change your settings</interface_restarted>
<APP_MIMEDEFANG>MimeDefang</APP_MIMEDEFANG>
<APP_MIMEDEFANGX>MimeDefang Multiplexor</APP_MIMEDEFANGX>
<backup_rules>Backup rules</backup_rules>
<backup>Backup</backup>
<BACKUP>Backup</BACKUP>
<APP_STUNNEL>Universal SSL Tunnel</APP_STUNNEL>
<APP_DKIM_FILTER>DKIM Filter</APP_DKIM_FILTER>
<APP_USB>Usb storage</APP_USB>
<APP_NMAP>nMap Security Scanner</APP_NMAP>
<APP_KAV4SAMBA>Kaspersky For Samba</APP_KAV4SAMBA>
<APP_PRELOAD>Preload Daemon</APP_PRELOAD>
<smartsieve>MailBox rules</smartsieve>
<hourly>hourly</hourly>
<hour>hour</hour>
<year>year</year>
<logs_viewer_text>View application events in realtime</logs_viewer_text>
<APP_CLAMSCAN>Clamav Command Line</APP_CLAMSCAN>
<APP_XFCE>X Freakin Cool Environment</APP_XFCE>
<APP_C_ICAP>C-ICAP Server</APP_C_ICAP>
<APP_BIND9>Bind DNS Server</APP_BIND9>
<APP_BIND9_TEXT>BIND (Berkeley Internet Name Domain or "named") is the most commonly used DNS server on the Internet</APP_BIND9_TEXT>
<APP_GDM>Gnome Display Manager</APP_GDM>
<APP_INETD>OpenBSD Internet Superserver</APP_INETD>
<APP_MAILARCHIVER>Open Mail Archiver</APP_MAILARCHIVER>
<service_info>Service information</service_info>
<no_icap_support>No ICAP Support</no_icap_support>
<APP_FDM>FDM fetch</APP_FDM>
<fetch_mails>Fetch emails</fetch_mails>
<messaging>Messaging</messaging>
<APP_P3SCAN>P3scan email proxy</APP_P3SCAN>
<APP_SYSLOGNG>Syslog-ng daemon</APP_SYSLOGNG>
<memory_usage>memory usage</memory_usage>
<disconnect>disconnect</disconnect>
<license_expired>The license is expired</license_expired>
<new_mail_receive_from>New mail from</new_mail_receive_from>
<more>more</more>
<replace>replace</replace>
<option>option</option>
<upgrade_your_system>Upgrade your System</upgrade_your_system>
<packages_to_upgrade>packages need to be upgraded, it is necessary to perform updates of found packages</packages_to_upgrade>
<system_update>System update</system_update>
<apply_upgrade_text>This operation will upgrade the system with packages below</apply_upgrade_text>
<apply_upgrade>Upgrade your system</apply_upgrade_text>
<apply_upgrade_help>This operation will be executed in background mode, you can check events in "events" section to see if order has been successfully executed</apply_upgrade_help>
<apply_pureftpd>Apply FTP</apply_pureftpd>
<apply_pureftpd_text>Rebuild users database and restart ftp server</apply_pureftpd>
<test>test</test>
<label>label</label>
<hostname>hostname</hostname>
<fs_type>filesystem type</fs_type>
<mounted>mounted on</mounted>
<vendor>vendor name</vendor>
<manufacturer>manufacturer</manufacturer>
<model>model</model>
<speed>speed</speed>
<launch>Launch</launch>
<APP_DAR>Disk Archive (DAR)</APP_DAR>
<browse>Browse</browse>
<restore>restore</restore>
<change>Change</change>
<no>no</no>
<yes>yes</yes>
<graphs>Graphs</graphs>
<tools>tools</tools>
<web_proxy>Web Proxy</web_proxy>
<directory>Directory</directory>
<service_disabled>This service is disabled by artica...</service_disabled>
<for>for</for>
<INSTALL_THIS_SERVICE>Install this service now</INSTALL_THIS_SERVICE>
<APP_BOGOM>Milter-bogom</APP_BOGOM>
<system>system</system>
<session_settings>Session settings</session_settings>
<APP_COLLECTD>System statistics collection daemon</APP_COLLECTD>
<collectd_statistics>Statistics collection</collectd_statistics>
<collectd_statistics_text>View statistics collected by System statistics collection daemon</collectd_statistics_text>
<APP_SIMPLE_GROUPEWARE>Simple Groupware</APP_SIMPLE_GROUPEWARE>
<APP_ARTICA_MAKE>Artica installer</APP_ARTICA_MAKE>
<APP_ATOPENMAIL>@Mail Open</APP_ATOPENMAIL>
<application_setup>Applications setup center</application_setup>
<application_setup_txt>Install new softwares supported by Artica</application_setup_txt>
<APP_MAILSPY>Milter MailSPy</APP_MAILSPY>
<APP_IMAPSYNC>ImapSync (synchronization)</APP_IMAPSYNC>
<APP_MAILSYNC>MailSync (synchronization)</APP_MAILSYNC>
<APP_CONSOLEKIT>ConsoleKit</APP_CONSOLEKIT>
<APP_KRETRANSLATOR>Kav-retranslator</APP_KRETRANSLATOR>
<APP_KRETRANSLATOR_TEXT>Kav-retranslator allow you to transform Artica has an internal update database server</APP_KRETRANSLATOR_TEXT>
<APP_KRETRANSLATOR_HTTPD>Kav-retranslator HTTP</APP_KRETRANSLATOR_HTTPD>
<APP_ARTICA_WATCHDOG>Artica Watchdog daemon</APP_ARTICA_WATCHDOG>
<start_service_in_debug>Start this service in debug mode</start_service_in_debug>
<country>Country</country>
<region>Region</region>
<city>City</city>
<host>Host</host>
<message_id>Message ID</message_id>
<spam>spam</spam>
<first_emails>first emails</first_emails>
<only_with_mysql>This feature works only with mysql enabled</only_with_mysql>
<only_with_amavis>This feature works only with Amavis Enabled</only_with_amavis>
<APP_ISOQLOG>Isoqlog</APP_ISOQLOG>
<postfix_statistics>SMTP Statistics</postfix_statistics>
<folder>folder</folder>
<APP_DOTCLEAR>DotClear web Publish</APP_DOTCLEAR>
<APP_DOTCLEAR_TEXT>Define your multi-Blog settings</APP_DOTCLEAR_TEXT>
<APP_JCHECKMAIL>j-chkmail filter</APP_JCHECKMAIL>
<target>Target</target>
<sources>sources</sources>
<received_mails>Received mails</received_mails>
<backuped_mails>Backuped mails</backuped_mails>
<quarantine_mails>Quarantined mails</quarantine_mails>
<calendar>Calendar</calendar>
<auto_account>Auto-create Accounts</auto_account>
<auto_account_text>Auto-create Accounts is a feature that allow your users to create accounts themself</auto_account_text>
<create_your_user_account>Create an account</create_your_user_account>
<register>Register</register>
<account_already_exists>Account already exists</account_already_exists>
<you_can_close_this_form>You can close this form now</you_can_close_this_form>
<manage_distribution_lists>Manage distribution lists</manage_distribution_lists>
<statusandlicense>Status & License</statusandlicense>
<quarantine_manager>Quarantine Manager</quarantine_manager>
<quarantine_manager_text>Query your user's quarantine and release mails</quarantine_manager_text>
<release>release</release>
<APP_ARTICA_GAYTEWAY>Gayteway Mode</APP_ARTICA_GAYTEWAY>
<APP_ARTICA_GAYTEWAY_TEXT>Transform your Artica server has a gayteway server</APP_ARTICA_GAYTEWAY>
<APP_DHCP>DHCP server</APP_DHCP>
<APP_DHCP_TEXT>Dynamic Host Configuration Protocol define your network to provide dynamically IP addresses</APP_DHCP_TEXT>
<GDPHP_NOT_INSTALLED>GD Library !</GDPHP_NOT_INSTALLED>
<POSTFIX_BUNDLE>Postfix bundles</POSTFIX_BUNDLE>
<POSTFIX_BUNDLE_TEXT>Enable Antivirus/Anti-spam filters connected with postfix</POSTFIX_BUNDLE_TEXT>
<APP_AMAVIS_EXPLAIN>Open filters content checking parameters</APP_AMAVIS_EXPLAIN>
<APP_ALTERMIME>alterMIME</APP_ALTERMIME>
<APP_POMMO>poMMo Mass Mailing</APP_POMMO>
<start_stop>Start Or Stop</start_stop>
<community>Community</community>
<support>Support</support>
<scheduled>Scheduled</scheduled>
<installing>Installing</installing>
<downloading>Downloading</downloading>
<compiling>Compiling</compiling>
<checking>Checking</checking>
<APPLY_SETTINGS_DANSGUARDIAN>Make dansguardian policies in production mode</APPLY_SETTINGS_DANSGUARDIAN>
<single_ip>Single IP address</single_ip>
<range_ip>Entire network</range_ip>
<group_ip>IP range</range_ip>
<ip_address>IP Address</ip_address>
<incremental_backup>Incremental backup</incremental_backup>
<incremental_backup_text>Backup your files using incremental backup in order to reduce backup size</incremental_backup>
<add_new_directory>Add a new directory</add_new_directory>
<advanced_infos>Advanced</advanced_infos>
<normal_infos>Information</normal_infos>
<selected>selected</selected>
<device>device</device>
<query>query</query>
<APP_AMAVIS_STAT>Amavis statistics daemon</APP_AMAVIS_STAT>
<apply_settings_bind9>Compile Bind9 Settings</apply_settings_bind9>
<apply_settings_bind9_text>Make your settings in production mode</apply_settings_bind9_text>
<templates>Templates</templates>
<smtp_notifications>eMail notifications</smtp_notifications>
<upload_max_filesize>Max uploading files size</upload_max_filesize>
<feature_not_installed>This feature is not installed</feature_not_installed>
<format_device>Format this device</format_device>
<format_device_explain>This operation will format this device in order to perform writeable operations</format_device_explain>
<notifications>Notifications</notifications>
<artica_events>Artica Events log</artica_events>
<artica_events_text>Display scheduled job & events about artica operations</artica_events_text>
<UPDATE_ANTIVIRUS>Update antivirus database</UPDATE_ANTIVIRUS>
<UPDATE_ANTIVIRUS_TEXT>perform updating the antivirus databases</UPDATE_ANTIVIRUS_TEXT>
<UPDATE_ANTIVIRUS_DATABASE_PERFORMED>The updating task has been performed in background mode, please refer to the update event log to see results</UPDATE_ANTIVIRUS_DATABASE_PERFORMED>
<display_product_events>Display product's events</display_product_events>
<reserved>reserved</reserved>
<daemon_events>Daemon events</daemon_events>
<update_events>Update events</update_events>
<upload_new_license>Upload a new license</upload_new_license>
<sender>Sender</sender>
<change_label_explain>Change the label name of this device</change_label_explain>
<change_label>Modify the label</change_label>
<dev_point>Dev point</dev_point>
<main_settings_text>Define global parameters of the software, personalize daemons processes and tune performances</main_settings_text>
<APPLY_SETTINGS_MILTERGREYLIST>Save your configuration and change milter-greylist to the server</APPLY_SETTINGS_MILTERGREYLIST> 
<compile_statistics>Compile statistics</compile_statistics>
<compile_statistics_text>Run statistics process in order to obtain last events and graphs</compile_statistics_text>
<APP_OPENVPN>OpenVPN</APP_OPENVPN>
<APP_OPENVPN_TEXT>OPenVPN is a software that allow you to create a Virtual Private Network</APP_OPENVPN_TEXT>
<province>province</province>
<newtork_help_me>Help me to find networks</newtork_help_me>
<you_should_use_one_of_these_network>You should use one of these network parameters</you_should_use_one_of_these_network>
<hosts_number>Hosts number</hosts_number>
<APP_OPENVPN_APPLY_TEXT>Restart OpenVPN server and apply your settings</APP_OPENVPN_APPLY_TEXT>
<APP_OPENVPN_APPLY>Apply OpenVPN settings</APP_OPENVPN_APPLY>
<comment>comment</comment>
<all_quarantines>Global quarantine manager</all_quarantines>
<browse_computers>Browse computers</browse_computers>
<browse_computers_text>Browse your networks & find computers near Artica server or manage yours computers</browse_computers_text>
<computers>computers</computers>
<APP_ARTICA_MYSQMAIL>Artica-Postfix logs watcher</APP_ARTICA_MYSQMAIL>
<postfix_realtime_events>Postfix realtime flow</postfix_realtime_events>
<postfix_realtime_events_text>Display routed mails in realtime</postfix_realtime_events_text>
<received>received</received>
<administrators_allow>Administrators privileges</administrators_allow>
<users_allow>Users privileges</users_allow>
<groups_allow>Group privilege</groups_allow>
<OUT_OF_OFFICE>Out of Office auto-reply</OUT_OF_OFFICE>
<OUT_OF_OFFICE_TEXT>Enable/Modifiy your vacation reply settings</OUT_OF_OFFICE_TEXT>
<APP_GNARWL>GNARWL (Vacation notification via Email)</APP_GNARWL>
<internal_hard_drives>Internal hard drives</internal_hard_drives>
<internal_hard_drives_text>Display and drive your internal hard disks</internal_hard_drives_text>
<partitions_number>partitions number</partitions_number>
<partitions>Partitions</partitions>
<servername>Server name</servername>
<add_ip_address>Add a TCP/IP address</add_ip_address>
<illimited>illimited</illimited>
<APP_MSMTP>msmtp (SMTP client)</APP_MSMTP>
<APP_PFLOGSUMM>Postfix Log Entry Summarizer</APP_PFLOGSUMM>
<APP_CUPS>Open Source printing System</APP_CUPS>
<APP_CUPS_TEXT>Manage, add, delete your shared printers</APP_CUPS_TEXT>
<driver>driver</driver>
<APP_PFLOGSUMM_TEXT>pflogsumm (Postfix Log Entry Summarizer) is designed to provide an over-view of postfix activity, with just enough detail to give the administrator a "heads up" for potential trouble spots.</APP_PFLOGSUMM_TEXT> 
<download>download</download>
<my_address_book>My Address Book</my_address_book>
<APP_CUPS_DRV>Cups drivers package</APP_CUPS_DRV>
<APP_ARTICA_DANSGUARDIAN_TAIL>Dansguardian statistics daemon</APP_ARTICA_DANSGUARDIAN_TAIL>
<quarantine_reports>Quarantine reports</quarantine_reports>
<APP_OBM2>OBM 2.2</APP_OBM2>
<APP_OBM2_TEXT>Open Business Management, is now recognized as the leader of GPL enterprise-class email and Groupware solution face to Microsoft Exchange® or Lotus Notes®</APP_OBM2_TEXT>
<APP_SMARTMONTOOLS>SMART hard disk monitoring</APP_SMARTMONTOOLS> 
<troubleshoot>troubleshoot</troubleshoot>
<troubleshoot_explain>Repair and try to fix corrupted datas</troubleshoot_explain>
<logs_size>Logs size</logs_size>
<rotate_logs>Rotate log file</rotate_logs>
<APP_SARG>Squid Analysis Report Generator</APP_SARG>
<words>words</words>
<xmozillanickname>nickname</xmozillanickname>
<department>department</department>
<electronic_address>Electronic address</electronic_address>
<professional_email>Professional eMail</professional_email>
<personal_email>Home eMail</personal_email>
<homePhone>Home phone</homePhone>
<facsimileTelephoneNumber>Fax</facsimileTelephoneNumber>
<instant_messaging>Instant messaging</instant_messaging>
<nsAIMid>AOL Instant Messenger (AIM)</nsAIMid>
<nsICQid>ICQ</nsICQid>
<nsMSNid>MSN</nsMSNid>
<nsYahooid>Yahoo</nsYahooid>
<websites>Web sites</websites>
<website>Web site</website>
<work>work</work>
<company>Company</company>
<businessRole>Business Role</businessRole>
<working_title>Working title</working_title>
<managerName>Manager name</managerName>
<assistantName>Assistant name</assistantName>
<other>other</other>
<roomNumber>Room number</roomNumber>
<birthDate>birth date</birthDate>
<spouseName>Spouse name</spouseName>
<homePostalAddress>Home Postal Address</homePostalAddress>
<postalCode>Postal code</postalCode>
<state>State</state>
<add_new_contact>Add a new contact</add_new_contact>
<add_new_contact_text>Create a new contact in you address Book</add_new_contact_text>
<UPDATE_CLAMAV>Update ClamAV antivirus</UPDATE_CLAMAV>
<UPDATE_CLAMAV_EXPLAIN>Perform ClamAV pattern files and Scan Engine update</UPDATE_CLAMAV_EXPLAIN>
<debug>debug</debug>
<xapian_packages>Search Engines</xapian_packages>
<APP_XAPIAN>Xapian search library</APP_XAPIAN>
<APP_XAPIAN_OMEGA>Xapian indexer</APP_XAPIAN_OMEGA>
<APP_XAPIAN_PHP>Xapian PHP Library</APP_XAPIAN_PHP>
<APP_XPDF>PDF converter</APP_XPDF>
<APP_UNZIP>Zip decompressor</APP_UNZIP>
<APP_UNRTF>RTF converter</APP_UNRTF>
<APP_CATDOC>DOC reader</APP_CATDOC>
<APP_ANTIWORD>Word converter</APP_ANTIWORD>
<HomeBinding>Home Binding</HomeBinding>
<HomeBinding_text>Link others local folders to Home directory account</HomeBinding_text>
<source>Source</source>
<click_to_mount>Click to mount</click_to_mount>
<mounted>mounted</mounted>
<click_to_dismount>Click to umount</click_to_dismount>
<InstantSearch>InstantSearch</InstantSearch>
<InstantSearch_text>Provides a fulltext search of your documents stored on this server</InstantSearch_text> 
<dmidecode>DMI BIOS Informations</dmidecode>
<dmidecode_text>Contains a description  of  the  system’s  hardware  components,  as well as other useful pieces of information such as serial numbers and BIOS revision</dmidecode_text>
<APP_OBM2_APACHE>OBM2 web server</APP_OBM2_APACHE>
<APP_OBM2_PHP>OBM2 php engine</APP_OBM2_PHP>
<APP_GROUPWARE_APACHE>Apache groupware engine</APP_GROUPWARE_APACHE>
<APP_GROUPWARE_PHP>Php groupware engine</APP_GROUPWARE_PHP>
<APP_OPENGOO>OpenGoo groupware</APP_OPENGOO>
<APP_OPENGOO_TEXT>It is a complete online solution focused on improving productivity, collaboration, communication and management of your teams.</APP_OPENGOO_TEXT>
<APP_CUPS_BROTHER>Brother printers drivers</APP_CUPS_BROTHER>
<ADMIN_CUPS>Manage your printer server</ADMIN_CUPS>
<ADMIN_CUPS_TEXT>Open the administration page that allow you to manage all the Printing system features</ADMIN_CUPS_TEXT>
<manage_your_joomla_text>Install, manage your joomla web services</manage_your_joomla_text>
<APP_JOOMLA>Joomla web service</APP_JOOMLA>
<EXTERNAL_PORTS>Externals ports list</EXTERNAL_PORTS>
<EXTERNAL_PORTS_TEXT>Modify and get a list of all TCP/IP ports used on this computer</EXTERNAL_PORTS>
<APP_DSTAT>Versatile resource statistics tool</APP_DSTAT>
<cpu_usage>CPU Usage (user)</cpu_usage>
<APP_GNUPLOT>GnuPlot</APP_GNUPLOT>
<backup_size>Backup disk size</backup_size>
<change_password>Change Password</change_password>
<server_time>Server time</server_time>
<enable_artica_wbl_robots>Artica White/Black list robots</enable_artica_wbl_robots>
<enable_artica_wbl_robots_icon>Define email addresses that will receive White & Black lists requests</enable_artica_wbl_robots_icon>
<kaspersky>Kaspersky Lab Inc</kaspersky>
<APP_SUGARCRM>SugarCRM</APP_SUGARCRM>
<save_configuration_file>Saving configuration</save_configuration_file>
<POSTFIX_FILTERS>Postfix filters</POSTFIX_FILTERS>
<APP_SA_BLACKLIST>SpamAssassin BlackList</APP_SA_BLACKLIST>
<APP_SA_BLACKLIST_AUTOUPDATE>Update more than 300 000 blacklisted domains pattern file for SpamAssassin</APP_SA_BLACKLIST_AUTOUPDATE> 
<ENABLE_SA_BLACKLIST_UPDATE>Enable/Disable updating blacklisted domains</ENABLE_SA_BLACKLIST_UPDATE>
<ENABLE_SA_BLACKLIST_UPDATE_TEXT>If you turn to green this feature, Artica will update each 2 hours the pattern file for improve your spamassassin detection rate by adding more than 300 000 black listed domains</ENABLE_SA_BLACKLIST_UPDATE_TEXT>
<servers>servers</servers>
<APP_EACCELERATOR>PHP accelerator</APP_EACCELERATOR>
<top_ressources>TOP resources</top_ressources>
<change_antispam_domain_text>Change anti-spam settings for this domain.[br]If users has not set it's own anti-spam settings, this rule will be used</change_antispam_domain_text>
<catch_all>Catch-all</catch_all>
<catch_all_mail_text>A catch-all mailbox will receive all mails when recipients not matching your users stored in local database</catch_all_mail_text>
<POSTFIX_PROCESS_NUMBER>Messaging processes number</POSTFIX_PROCESS_NUMBER>
<flow>flow</flow>
<topten>TOP 10</topten>
<corrupt>corrupt</corrupt>
<quarantine>Quarantine</quarantine>
<last_100_mails>last 100 emails</last_100_mails>
<end>end</end>
<APP_SA_BLACKLIST_AUTOUPDATE_WARNING>Be carreful, this feature will consume around 450M of memory.[br]Verify that you have 450M minimum free memory</APP_SA_BLACKLIST_AUTOUPDATE_WARNING>
<please_wait>Please wait</please_wait>
<log>log</log>
<reject_invalid_hostname>Reject invalid hostname</reject_invalid_hostname>
<reject_invalid_hostname_text>Reject the request when the client has a bad hostname syntax.</reject_invalid_hostname_text>
<EnablePostfixAntispamPack_text>Enable anti-spam Pack is a set of settings that enable restrictions in order to limit SPAM attacks.[br]
The settings applied are :[br]
[b]Disable the SMTP VRFY command.[/b] This stops some processes used to harvest email addresses[br][br]
[b]Allow Postfix to log recipient address information[/b] when rejecting a client name/address or sender address in order to monitor blocks[br][br]
[b]Force remote SMTP computer introduces itself[/b] at the beginning of an SMTP session with the HELO or EHLO command[br][br]
[b]Configure spam black lists[/b] with sbl.spamhaus.org cbl.abuseat.org and dul.dnsbl.sorbs.net[br][br]
[b]set smtpd_error_sleep_time,[br]smtpd_soft_error_limit,[br]smtpd_hard_error_limit[/b] that enforce a number of limits on incoming email. This will stop email flooding attacks.[br] 
</EnablePostfixAntispamPack_text>
<last_mails>Last routing mails</last_mails>
<APP_RSYNC>Remote Synchronization</APP_RSYNC>
<APP_RSYNC_SERVER_TEXT>Configure this server to receive backup from others servers</APP_RSYNC_SERVER_TEXT>
<max_connections>Max connections</max_connections>
<back_system>Back to system</back_system>
<back_system_text>Return back to System & applications area</back_system_text>
<SHARE_FOLDER_TEXT>Share a folder on this system.[br]Browse your hard drives and point a directory to share</SHARE_FOLDER_TEXT>
<SHARE_FOLDER>Share a folder</SHARE_FOLDER>
<APP_RSYNC_STUNNEL>SSL Tunnel</APP_RSYNC_STUNNEL>
<APP_RSYNC_CLIENT_LOG>Rsync Client events</APP_RSYNC_CLIENT_LOG>
<APP_RSYNC_CLIENT_LOG_TEXT>Display your sent backup files events</APP_RSYNC_CLIENT_LOG>
<APP_RSYNC_SERVER_LOG>Rsync receiver events</APP_RSYNC_CLIENT_LOG>
<APP_RSYNC_SERVER_LOG_TEXT>Display events of your storage server</APP_RSYNC_SERVER_LOG_TEXT>
<BACKUP>Backup</BACKUP>
<BACKUP_PARAMETERS>Display backup parameters of this object</BACKUP_PARAMETERS>
<SET_SCHEDULE>Set the schedule task</SET_SCHEDULE>
<SET_SCHEDULE_TEXT>Define when this task will be performed</SET_SCHEDULE_TEXT>
<unselect_all>unselect all</unselect_all>
<NT_STATUS_LOGON_FAILURE>Error:Username/password Failed</NT_STATUS_LOGON_FAILURE>
<NT_STATUS_CONNECTION_REFUSED>Connextion refused</NT_STATUS_CONNECTION_REFUSED>
<NT_STATUS_ACCESS_DENIED>Error:Access Denied</NT_STATUS_ACCESS_DENIED>
<NT_STATUS_HOST_UNREACHABLE>Error: Host unreachable</NT_STATUS_HOST_UNREACHABLE>
<NT_STATUS_INTERNAL_DB_CORRUPTION>Error:Host report corrupted Database</NT_STATUS_INTERNAL_DB_CORRUPTION>
<ADD_COMPUTER>Add a new computer</ADD_COMPUTER>
<ADD_COMPUTER_TEXT>Add a new computer in Artica Database</ADD_COMPUTER_TEXT>
<WHEN_TO_BACKUP>When to backup ?</WHEN_TO_BACKUP>
<WHEN_TO_BACKUP_TEXT>Define the schedule of the backup execution</WHEN_TO_BACKUP_TEXT>
<APP_SAMBA_WINBIND>Samba Winbind Daemon</APP_SAMBA_WINBIND>
<logs_cleaning>Logs files cleaning</logs_cleaning>
<APP_POLICYD_WEIGHT>Policy Daemon for Postfix</APP_POLICYD_WEIGHT>
<APP_POLICYD_WEIGHT_TEXT>Policyd-weight is a policy daemon for the Postfix intended to eliminate forged envelope senders and HELOs (i.e. in bogus mails).</APP_POLICYD_WEIGHT_TEXT>
<EnablePolicydWeight>Enable Policy Daemon for Postfix</EnablePolicydWeight>
<APP_POLICYD_WEIGHT_EXPLAIN>policyd-weight is a Policy daemon for the Postfix MTA intended to eliminate forged envelope senders and HELOs (i.e. in bogus mails).[br]
 It allows you to score DNSBLs (RBL/RHSBL), HELO, MAIL FROM and client IP addresses before any queuing is done.[br]
It allows you to REJECT messages which have a score higher than allowed, providing improved blocking of spam and virus mails.[br]
Policyd-weight caches the most frequent client/sender combinations (SPAM as well as HAM) to reduce the number of DNS queries.</APP_POLICYD_WEIGHT_EXPLAIN>
<ISP_MODE>Internet Provider Mode</ISP_MODE>
<ADD_NEW_TAB_ASK>Give the name of your new tab</ADD_NEW_TAB_ASK>
<COMPUTER_ACCESS>Share credentials access</COMPUTER_ACCESS>
<COMPUTER_ACCESS_TEXT>Set the username and password that have privileges to browse this computer</COMPUTER_ACCESS_TEXT>
<SAMBA_NEWVERSION>New Samba version:</SAMBA_NEWVERSION>
<SAMBA_NEWVERSION_TEXT>It is recommed to upgrade your Samba version to the latest, check the Setup control Center and upgrade your Samba</SAMBA_NEWVERSION_TEXT>
<umount>Disconnect</umount>
<umount_explain>Disconnect this resource from the server</umount_explain>
<waiting>Please wait operation</waiting>
<mount>Connect</mount>
<mount_explain>Connect this resource to this computer for browse directories</mount_explain>
<browse_text>Open this resource and display folders</browse_text>
<external_resource>external resource</external_resource>
<fill_form>Fill the form</fill_form>
<smbclient_not_installed_fill_form>the smblient tool is not installed, the browsing is disabled, fill the form to set informations</smbclient_not_installed_fill_form>
<populate>populate</populate>
<this_server_store>This server store</this_server_store>
<send>send</send>
<web_proxy_text>Configure your web proxy server</web_proxy_text>
<policy>policy</policy>
<MAIL>Messaging</MAIL>
<AMAVIS_NEWVERSION>New amavis version</AMAVIS_NEWVERSION>
<AMAVIS_NEWVERSION_TEXT>a new Amavis version is available in artica update server, it is recommended to upgrade to this version</AMAVIS_NEWVERSION_TEXT>
<SQUID_NEWVERSION>New Squid-cache version</SQUID_NEWVERSION>
<SQUID_NEWVERSION_TEXT>A new squid cache version is vailable in artica update server,it is recommended to upgrade to this version</SQUID_NEWVERSION_TEXT>
<APP_CYRUS_MURDER>Cyrus IMAP Aggregator</APP_CYRUS_MURDER>
<APP_CYRUS_MURDER_TEXT>The Cyrus IMAP Aggregator transparently distributes IMAP and POP mailboxes across multiple servers.[br]
Unlike other systems for load balancing IMAP mailboxes, the aggregator allows users to access mailboxes on any of the IMAP servers in the system.</APP_CYRUS_MURDER_TEXT>
<ERROR_CURL_NOT_INSTALLED>Error unable to stat curl binary file</ERROR_CURL_NOT_INSTALLED>
<NO_CONFIG_FILE>No configuration file found</NO_CONFIG_FILE>
<FEATURE_BETA_MODE>This feature is currently in contruction mode (Alpha/beta), do not try it in production mode, just play with it in testing environment</FEATURE_BETA_MODE>
<could_not_open_infos>Unable to open informations</could_not_open_infos>
<APP_DHCP_MAIN_CONF>DHCP Server main configuration file</APP_DHCP_MAIN_CONF>
<APP_DHCP_MAIN_CONF_TEXT>Display the generated configuration file by artica</APP_DHCP_MAIN_CONF_TEXT>
<ERROR_NO_CONFIG_SAVED>It seems that no configuration file has been saved, please save you first configuration file before</ERROR_NO_CONFIG_SAVED>
<invalid>invalid</invalid>
<INSTALL_UPGRADE_RECOMPILE>re-install or upgrade</INSTALL_UPGRADE_RECOMPILE>
<FETCHMAIL_NEWVERSION>New Fetchmail version</FETCHMAIL_NEWVERSION>
<NMAP_NEWVERSION>New Network security Scanner version</NMAP_NEWVERSION>
<NMAP_NEWVERSION_TEXT>A new NMAP version is available in artica update server, it is recommended to upgrade to this version</NMAP_NEWVERSION_TEXT>
<FETCHMAIL_NEWVERSION_TEXT>A new Fetchmail version is available in artica update server, it is recommended to upgrade to this version</FETCHMAIL_NEWVERSION_TEXT>
<find>Find</find>
<backup>backup</backup>
<DANSGUARDIAN_NEWVERSION>New Dansguardian version</DANSGUARDIAN_NEWVERSION>
<DANSGUARDIAN_NEWVERSION_TEXT>It is recommanded to update your server to the latest DansGuardian version in order to obtain better performances on content filtering</DANSGUARDIAN_NEWVERSION_TEXT>
<ISP>Internet Provider</ISP>
<ERROR_NO_AUTOFS>Error, autofs package is not installed on your system</ERROR_NO_AUTOFS>
<APP_AUTOFS>Automounting removable devices</APP_AUTOFS>
<PHP_EVENTS>PHP traces</PHP_EVENTS>
<PHP_EVENTS_TEXT>display errors generated by web services written in PHP</PHP_EVENTS_TEXT> 
<confirm>Confirm</confirm>
<delete_mailboxes>Delete mailboxes</delete_mailboxes>
<APP_NFS>Network File System server</APP_NFS>
<computer>computer</computer>
<access>Access</access>
<APP_DHCP_EVENTS>DHCP server events</APP_DHCP_EVENTS>
<add_computer_access>Add computer access</add_computer_access>
<read>read</read>
<NFS_CLIENT>Network File System Client</NFS_CLIENT>
<NFS_CLIENT_TEXT>Connect your server to a NFS shared folder on a remote computer</NFS_CLIENT_TEXT>
<write>write</write>
<use_local_storage>Use local storage</use_local_storage>
<use_local_storage_text>Browse this server and select a folder on the local file system</use_local_storage>
<connect>connect</connect>
<add_auto_connection>Add auto-connection</add_auto_connection>
<automount_center>Auto-mount center</automount_center>
<filesystem>File System</filesystem>
<mount_point>Mount path</mount_point>
<add_auto_connection_explain>will auto-mount directly in /automounts/mount-name directory</add_auto_connection_explain>
<automount_center_text>Manage connections service with your external resources.</automount_center_text>
<APP_CYRUS_BACKUP>Mailboxes backup</APP_CYRUS_BACKUP>
<APP_CYRUS_BACKUP_TEXT>backup your mailboxes to a connected resource</APP_CYRUS_BACKUP_TEXT>
<buildSambaSettings>Build profile settings</buildSambaSettings>
<restart_autofs>Restart Auto-connect service</restart_autofs>
<restart_autofs_text>Restart the auto-connect service in order to apply new settings in production mode</restart_autofs>
<during>during</during>
<SUPPORT>Support</SUPPORT>
<Administrator>Administrator</Administrator>
<MYSQL_CLUSTER>Mysql cluster</MYSQL_CLUSTER>
<MYSQL_CLUSTER_TEXT>Increase mysql Database high availability by build a set of mysql clusters nodes</MYSQL_CLUSTER_TEXT> 
<APP_MYSQL_CLUSTER_MGMT>Mysql Cluster management</APP_MYSQL_CLUSTER_MGMT>
<APP_MYSQL_CLUSTER_REPLICA>Mysql Cluster replica</APP_MYSQL_CLUSTER_REPLICA>
<load_avg>Load average</load_avg>
<load>Load</load>
<GROUP_RENAME>Rename this group</GROUP_RENAME>
<GROUP_RENAME_TEXT>Change the name of this group</GROUP_RENAME_TEXT>
<old_name>Old name</old_name>
<new_name>New name</new_name>
<monthly_statistics>Monthly SMTP statistics</monthly_statistics>
<monthly_statistics_text>Display email statistics by month</monthly_statistics_text>
<recipients_domains>recipients domains</recipients_domains>
<mbx_con>Mailboxes connections</mbx_con>
<BACKUP_COMPUTER_TEXT>Backup files on this computer</BACKUP_COMPUTER_TEXT>
<daily_mailboxes_connections_statistics>Daily Mailboxes service statistics</daily_mailboxes_connections_statistics>
<daily_mailboxes_connections_statistics_text>Display remote connections from your users to mailbox services (imap/pop3)</daily_mailboxes_connections_statistics_text>
<delete_not_forget_to_compile>Object has been successfully deleted, do not forget to compile your rules</delete_not_forget_to_compile>
<delete_all_items>Delete all items</delete_all_items>
<ProcessNice>Process priority</ProcessNice>
<VIRUSES_FOUND>Viruse(s) found!</VIRUSES_FOUND>
<VIRUSES_FOUND_TEXT>Viruses are found on your server or computers, check events to display threats</VIRUSES_FOUND_TEXT>
<VIRUS_EVENTS>Viruses events</VIRUS_EVENTS>
<virusname>Virus name</virusname>
<taskname>Task name</taskname>
<mark_has_read>Mak this event has read</mark_has_read>
<mark_all_events_has_read>Mark all events has read</mark_all_events_has_read>
<user_interface>User interface</user_interface>
<user_interface_text>Personnalize Artica Interface for this user</user_interface_text>
<add_a_new_tab>Add a new tab</add_a_new_tab>
<add_a_new_tab_text>Add a new page in order to add more widgets</add_a_new_tab_text>
<index>index</index>
<computers_management>Computers management</computers_management>
<APP_WINEXE>Windows remote execution</APP_WINEXE>
<APP_STORAGE_CENTER>Softwares Storage Center</APP_STORAGE_CENTER>
<APP_STORAGE_CENTER_TEXT>Add packages that will used to perform remote installations tack to your computers</APP_STORAGE_CENTER_TEXT>
<filename>File name</filename>
<debug_mode>Debug mode</debug_mode>
<APP_FRAMEWORK>Artica FrameWork</APP_FRAMEWORK>
<APP_OCSI>OCS Inventory</APP_OCSI>
<APP_OCSI_TEXT>Open Computer and Software Inventory Next Generation is an application designed to help a network or system administrator keep track of the computers configuration and software that are installed on the network</APP_OCSI_TEXT>
<APP_FETCHMAIL_LOGGER>Artica fetchmail logger</APP_FETCHMAIL_LOGGER>
<deploy>deploy</deploy>
<NIC_NAME>Network card name</NIC_NAME>
<WORKGROUP>Workgroup</WORKGROUP>
<timezones>timezones</timezones>
<timezone>timezone</timezone>
<artica_events_status>Engine status events</artica_events_status>
<artica_events_status_text>Display logs generated by processes that generate the web console status</artica_events_status_text>
<fetchmail_recup>Mails downloaded</fetchmail_recup>
<overloaded>overloaded</overloaded>
<error_max_value_is>Error maximum value is</error_max_value_is>
<error_min_value_is>Error Minimum value is</error_min_value_is>
<GENERIC_LDAP_ERROR>OpenLDAP generic error</GENERIC_LDAP_ERROR>
<switch>switch</switch>
<MANAGER_DEFAULT_PASSWORD>Change default password</MANAGER_DEFAULT_PASSWORD>
<MANAGER_DEFAULT_PASSWORD_TEXT>You are using the  Artica Manager default password,everybody know it !![br]it is recommended to change it has soon has possible for security reasons</MANAGER_DEFAULT_PASSWORD_TEXT>
<ERROR_CURL_SO>Error php-curl is not installed</ERROR_CURL_SO>
<ERROR_CURL_SO_TEXT>you need ot install php-curl to enable this feature, execute setup-* or setup-ubuntu to refersh your installation</ERROR_CURL_SO_TEXT>
<APP_ASSP>Anti-Spam SMTP proxy</APP_ASSP>
<ressources_insuffisantes>insufficient resources</ressources_insuffisantes>
<time>time</time>
<task>task</task>
<server_memory>Server memory</server_memory>
<server_swap>server swap</server_swap>
<go>go</go>
<stop_services>Stop services</stop_services>
<select_this_container>Select this container</select_this_container>
<memory_use>Memory use</memory_use>
<groupwares>Groupwares</groupwares>
<APP_LMB>Lundi Matin Business</APP_LMB>
<APP_LMB_TEXT>LUNDI MATIN BUSINESS is an Open Source software that provide a global company management features including[br] 
[li]Commercial management (Quotes, Orders, Shipments, Invoices),[/li]
[li]Directory Management(Customers, Vendors, Employees, Partners, ...),[/li]
[li]Catalog Management,Stock management,Financial Management (Compliance with the rules, reminders, receipts..)[/li]
</APP_LMB_TEXT>
<APP_PDNS>PowerDNS system</APP_PDNS>
<APP_PDNS_TEXT>Manage, add, delete items into your DNS table</APP_PDNS_TEXT>
<APP_PDNS_RECURSOR>PowerDNS recursor</APP_PDNS>
<DNSServer>DNS Server</DNSServer>
<unknown_user>unknown user</unknown_user>
<bad_password>bad password</bad_password>
<sender>sender</sender>
<user_backup_emails_query_text>Search and restore backuped mails directly from messaging router backup feature</user_backup_emails_query_text>
<search_in_message>Search in message</search_in_message>
<release_mail>Release this message</release_mail>
<delete_mailbox>Delete the mailbox</delete_mailbox>
<confirm_deletion_of>confirm deletion of</confirm_deletion_of>
<delete_users>delete users</delete_users>
<delete_group>Delete Group</delete_group>
<APP_MAILGRAPH_ICON_TEXT>Display statistics generated by MailGraph</APP_MAILGRAPH_ICON_TEXT>
<DEF_ICO_POSTFIX_TLS_TEXT>Using SSL in your SMTP communications</DEF_ICO_POSTFIX_TLS_TEXT>
<softwares_install>Softwares install</softwares_install>
<multidomains_icon_text>Each user will have "user@domain.tld" account instead "user" account.</multidomains_icon_text>
<APP_CYRUS_MURDER_ICON_TEXT>Transparently distributes IMAP and POP mailboxes across multiple servers.</APP_CYRUS_MURDER_ICON_TEXT>
<HTTP_FILTER_MONITOR>Web filter monitor</HTTP_FILTER_MONITOR>
<hits_number>Hits number</hits_number>
<websites>Web sites</websites>
<users>users</users>
<filter_stats>Filter statistics</filter_stats>
<filter>Filter</filter>
<dansguardian_statistics>Dansguardian statistics</dansguardian_statistics>
<auto_apt>Automatically upgrade the system</auto_apt>
<find_members>Find members</find_members>
<find_members_text>search your members in the database</find_members_text>
<error_unable_to_create_dir>Error, unable to create directory</error_unable_to_create_dir>
<denied>Denied</denied>
<empty_swap>Empty swap and memory</empty_swap>
<no_memory_free_to_empty_cache>No memory free to perform empty cache, you should reboot or stop some services</no_memory_free_to_empty_cache>
<need>need</need>
<invisible_disk>hidden disk</invisible_disk>
<add_invisible_disk_text>Add a new disk in the collection if your local disk is not correctly displayed</add_invisible_disk_text>
<disk_name>Disk name</disk_name>
<greylisting>GreyListing</greylisting>
<grelisting_text>Your mail server temporarily reject any email from a sender it does not recognize</grelisting_text>
<APP_GLUSTER>Gluster Storage Platform</APP_GLUSTER>
<APP_GLUSTER_TEXT>Gluster Storage Platform is an open source clustered storage solution.</APP_GLUSTER_TEXT>
<enable_backup_email_text>If you set it to green, all mails that will be sent to Internet or sent to mailboxes (excluding blocked mails) will be backuped to Mysql database.
In this case, your users will be allowed to search/resend backuped mails</enable_backup_email_text>