![]() ![]() Syntax: friends_at_rcpt bool friends_pending_name It allows us to check friends at rcpt stage without paying a disk access cost for non-friends users. This setting is automatically added/removed by the web admin when domain level friends defaults are configured. ![]() Whether to check users friends list at rcpt stage Syntax: fallback_domain string friends_at_rcpt Syntax: fallback_force bool fallback_domainįallback domain, rcpt is rewritten this domain name Use fallback address even if user does exist. Use fallback even if user does exist as migration not started yet Syntax: fallback_always bool fallback_force This setting can be used when bringing up a new system if you want to be able to backout. Syntax: fallback_check bool fallback_alwaysĪlso relay to old system even if user does exist – not recommended Syntax: fallback_users string fallback_checkĬheck if user exists on fallback relay host before accepting it. Useful to remove load from backend server as it doesn’t have to be checked for non existent users, the file can contain or just usernames Path to file listing all users to user fallback_relay for Use mx lookup to find ip address for fallback_relay setting Syntax: fallback_relay string fallback_mx There are several options to make this work using servers that only accept mail if they can do a reverse lookup. This allows you to transition between two mail systems, as new accounts are created the emails will be delivered to SurgeMail, and ones that don’t exist will be sent on to the old system automatically. Specifies a default host to send messages to that are not found in the local user database. Setting fallback to “/dev/null” will drop messages (both UNIX and Windows).įallback host to relay non existent accounts to If not defined the Email will be bounced. Specifies a default account to deliver Email to. ![]() Syntax: encrypt_surgeweb_hide bool fallback Syntax: encrypt_ifnew bool encrypt_surgeweb_hide Syntax: encrypt_noconfirm bool encrypt_ifnew Syntax: encrypt_smart bool encrypt_noconfirmĭisable confirmation for encrypted messagesĭisables the automatic confirm reading message This feature is not controlled by this setting, it’s part of the smart features and controlled by the surgeweb options if enabled, instead set encrypt_ifnew and encrypt_smartĮncrypt smart features enabled for this domain This setting is not used, instead use smart and ifnew settings Syntax: encrypt_limitsz int encrypt_token Max size of encrypted msgs per user per day Syntax: encrypt_limit int encrypt_limitsz Per user limit per day, (used to be per hour) Syntax: encrypt_subject string encrypt_limit Subject when encrypted message sent – default is original subject Syntax: encrypt_rule header=string contains=string from=string to=string noconfirm=bool method=string encrypt_subject method=server or inline, we recommend ‘server’ mode as it’s much simpler. If this rule matches then the message will be encrypted before it is sent to the user. This setting has no further documentation currently availableĮxample: blogs_max_per_user 10 broad_sync Syntax: assume_created_epoch bool blogs_max_per_user This setting effect the g_disable_smtp_after and g_delete_user_after settings which, by default, ignore users who have not logged in and have no created field. If user has no ‘created’ field assume they were created an arbitrarily large time in the past Syntax: admin_access_default string assume_created_epoch eg:Īdmin_access_default “all,!users,!reports” It is specified in the same maner as the g_admin_access settings ‘access’ parameter. This setting allows you to specify default access to certain SurgeMail features. Syntax: access_group_default string admin_access_defaultĭefault features granted to domain admins in this domain Specifies the default g_access_group to place users in this domain into. Syntax: alias_max int access_group_default total number of aliases allowed in this domain to the value specified. Maximum number of aliases for this domain This file only exists for backward compatibility. You can create alias files using the same syntax as used in UNIX systems /etc/aliases. In addition each domain has it’s own ‘alias’ file (domain.name/alias.dat). Syntax: abook name=string read=string write=string type=string alias_file The read/write fields should be a list of valid usergroups or * for all users Syntax: comment date=string name=string comment=string abookĭefine surgeweb shared address books for this domain This is a dummy setting that lets you store information in the ini file that will survive setting changes from the web admin tool. Management notes and comments about the domain Syntax: class type=string from=string users=string groups=string name=string comment Define class of user for following commands to apply to ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |