![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
![]() |
Global settings
Note: Most 'matching' settings take wild card lists as parameters, for example "fred*" will match "freddy" and "Fred@bob". And "1.2.*,2.3.*" will match 1.2.4.4 and 2.3.99.100. Many settings will also accept a ! as a "not", and are processed from left to right. eg "!*,127.*,10.*" would first "deny all" then try and match on any 127.* or 10.* domains. Settings using ip's will take ranges also like 10.0.1-120.5
g_access_group - Access groups
Access rules defining groups of IP addresses with certain POP, IMAP and SMTP privileges. When a user is authenticated access is checked against group membership defined in the "mailaccess" field in the authentication database. See accounts for more information.
eg. this could allow you to charge webmail users for pop access privileges:
g_access_group group=paid_user access_pop=* access_imap=* access_smtp=*
g_access_group group=free_user access_pop=webmail.svr.ip access_imap=webmail.svr.ip access_smtp=webmail.svr.ipwith "Access type" set to "free_user" on accounts page or equivalently in nwauth authentication database:
marijn@mydomain.com:{ssha}tVANQo...:created="1060034937" mailaccess="free_user" ...To prevent webmail access for some users you would do this:
g_access_group_default "normal"
g_access_group group="normal" access_pop="*" access_imap=*" access_smtp="*"
g_access_group group="nowebmail" access_pop="*,!webmail.ip" access_imap="*,!webmail.ip" access_smtp="*"And put the users you want to limit in a group called 'nowebmail' e.g.
lookup fred@domain
+OK fred@domaing config 0 mailaccess="nowebmail"See also: g_user_alias, g_user_blogs, g_user_access, g_user_sms_quota, g_user_send_max, g_user_list_quota
g_access_group_default - Access group defaults
Access group defaults for users with no access groups set. (must be used in conjunction with g_access_group)
g_acctlog_authonly - Log sending usage based on authenticated accounts only and ignore "MAIL FROM" address - which may be fake!!
This setting has no further documentation currently available
g_acctlog_noaliases - Don't log redirection & aliases as sending mail as a result of redirection / forwarding (means you will not log account forwarding usage)
This setting has no further documentation currently available
g_acctlog_sum_inactive - Summarise local accounts that have not logged in yet as not_loggedin_yet@domain.com
This setting has no further documentation currently available
g_admin_access - Allow / Restrict domain admin access to features based on g_access_group
g_admin_access group="wildcard" access="list"
This setting matches the g_access_group the admin is in to the wildcard specified and applies the specified access list to that domain admin, giving / restricting thier access to certain features. The list may include any of the following:
Value Result alias Access to domain users "Alias" page and features. aspam Access to the "ASpam" page and features. blog Access to the "Blogs" page and features. bulletins Access to the "Bulletins" page and features. centipaid Access to domain users "Centipaid" page and features. enotify Access to domain users "Email Notification" page and features. exceptions Access to domain users "Exceptions" page. friends Access to domain users "Friends" pages, and system. fwd Access to domain users "Forwarding" features, forwarding, auto-responder. lists Access to the "Lists" page and features. log Access to domain users "Log" page. mailbox Access to domain users "Mailbox" page, view mailbox, setup rules. sms Access to domain users "Sms" page. spam Access to domain users "Spam" page, and SmiteSpam and Aspam processing of messages. spampriv Access to domain users "Spam" pages' spam private feature spf Access to domain users "Spf" page and features. usage Access to the "Usage" button, which shows a domain users usage. users Access to the "Users" page and features. redirect Access to the "Redirect" page and settings. redirect_cc Access to the "Redirect CC" page and settings. In addition you can prefix any of the above with ! to deny access. There are two other special case values, "all" and "none" which mean exactly what they say, access to "all" or "none" of the features.
Example:
g_admin_access group="simple" access="all,!users,!reports"
The above setting gives admins in the 'simple' group access to all the features except the users and reports features.
g_admin_access_default - Default features granted to domain admins
This setting is a default access list for all domain admins on the server, it is specified in the same maner as the g_admin_access settings 'access' parameter. eg:
g_user_access_default "all,!users,!reports"
g_admin_guesses - Number of guesses allowed for admin.
Syntax: g_admin_guesses "number"
This sets the number of guesses allowed for the admin username/password. Once this has been reached the ip is banned.
See also: g_admin_ip, g_admin_localhost, g_admin_access, g_admin_access_default
g_admin_ip - Admin IP access
Mask of valid IP addresses for admin users (default *), this is a security setting you can use to restrict remote web admin access to trusted IP addresses. One is always allowed to use manage SurgeMail using 127.0.0.1 regardless of whether this is explicitly specified.
eg. To restrict to local network as per net mask
g_admin_ip "10.0.0.*,10.1.2.*"g_admin_localhost - Allow localhost web admin without user/pass
Allows a localhost connection to access the web admin port without using the administrator username / password. This is good if you keep forgetting the admin password like I do.
See also: g_admin_ip, g_admin_guesses, g_admin_access, g_admin_access_default
g_allow_bodyless - Allow bodyless email
This will allow bodyless email to be accepted. These are usually spam. In particular Norton Antivirus in autoprotect mode closes the POP link which makes it appear that SurgeMail has terminated the connection when a bodyless email is encountered.
g_allow_passzip_from - A list of addresses to allow unmonitorable archive messages to be sent from
These may of course contain viruses as they cannot be scanned, but some people still need to be able to accept such files.
g_allow_passzip_to - A list of addresses to allow unmonitorable archive messages to be sent to
These may of course contain viruses as they cannot be scanned, but some people still need to be able to accept such files.
g_allow_user_authent_field_get - A space separated list of authent process fields that users are allowed to view for themself using the POP xauthent_field_get command
This provides limited access to the user database for applications like webmail and surgeplus.
See also: g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret
g_allow_user_authent_field_set - A space separated list of authent process fields that users are allowed to set for themself using the POP xauthent_field_set command
This provides limited access to the user database for applications like webmail and surgeplus.
See also: g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret
g_archive - Archive delivered mail
Archive rules allowing all mail delivered to be archived to either:
- Fixed size rotating archive - use this if you want to be able to get back a particular message that has recently passed thorugh the server but you do not want the mail archives to be able to grow too large
- History archive of a fixed (or unlimited) duration that can grow as much as the disk space available. Use this if you need to archive say all mail sent to / from a particular customer for the last year.
The archive is stored as a directory containing bucket files. This allows you to retrieve messages that have been delivered if you need to retrieve a particular message for any reason. To retrieve a message this needs to be extracted manually from the archive files manually using a text editor or your own script. The maximum bucket size (default if 1Mb) of the archive and the maximum individual message size can be set.
Filtering is done based upon wildcard destination and source addresses and subject. These fields provide a logical AND, with a blanks filed matching the default "*". A specific email may match multiple archive rules, and will be archived in each archive in this case. Also note that if a match is part of a larger string the match string should have wildcards surrounding it. eg: to match "important business" in the subject "Very important business for you" you should specify "*important business*".
eg. To catch all email delivered from domain.com you would specify:
g_archive to="*" from="*@domain.com" subject="" path="c:\mailarchive" size="10mb" maxitem="10k"You can also select whether the archiving rule is triggered before or after any filtering that is applied such as virus or spam filtering using the early flag. This can be useful to capture the original source of viruses or spam for testing purposes.
g_archive_bucketsize - Size for archive bucket files. Default is 1mb
Sets the size of the archive buckets used by the circular archives. If set too large then editing the buckets manually is awkward.
See also: g_archive, g_archive_early, g_archive_on_delete, g_archive_on_delete_dir, g_archive_files
g_archive_early - Apply all archive rules before content filtering is applied (obsolete)
This will apply the archive rules before content filtering is applied. This can be user to capture the source message if it is getting stored or bounced unnecessarily by any of the SurgeMail filters. The early flag on individual archive rules should be used instead of this setting.
g_archive_files - Archive attachments to a directory
Each message to the named account will have it's attachments removed and placed in the named directory. The path can contain the symbols $month$ $year$ $day$ $second$. The 'second' is only within this day. Together these variables can be used to ensure a unique path is used for each file if the names might conflict. Use g_redirect_cc to archive email going to an existing account because if you set 'to' equal to a real account then the real account will stop receiving messages!
g_archive_on_delete - Don't delete user files, archive them to g_archive_on_delete_dir
When deleting a user, archive the users files in the g_archive_on_delete_dir archive directory.
g_archive_on_delete_dir - Directory to archive user files to on delete
Directory to archive deleted users files to. Defaults to 'archive' in the SurgeMail installation folder.
g_aspam_headers - Add aspam information messages to messages.
Adds informational aspam headers to all messages.
g_assume_created_epoch - If user has no 'created' field assume they were created an arbitrarily large time in the past
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.
g_atrn_client - Define a rule for fetching email
This is the setting for clients to define to fetch mail from an upstream server. Typically this is done on the special port 366, to specify another port use host:port in the host setting. E.g. host="smtp.upstream.com:25"
See also: g_atrn_server, g_atrn_port
g_atrn_port - Port to listen for 'atrn' (On Demand Relay) requests
See g_atrn_server for more details, the default is port 366, atrn is not obeyed on port 25
See also: g_atrn_server, g_atrn_client
g_atrn_server - On Demand Mail Relay settings to define user/pass for clients to fetch mail
This allows a client on a dynamic IP to connect and request mail for a specific domain after authenticating by using the ATRN command. Typically this is done on the special port 366
See also: g_atrn_client, g_atrn_port
g_auth_hide - Disable SMTP Authentication
Per default SMTP authentication is enabled. If a user matches this IP range/list they will NOT be shown the ESMTP extension for SMTP authentication. This will usually stop the mail client from prompting the user for authentication. We STRONGLY recommend you do NOT use this feature. It is much better to let users authenticate when sending email.
g_auth_norelay - Ignore SMTP auth for relaying purposes
This means relaying only occurs if g_relay_allow_ip matches
g_auth_skipgateway - Skip gateway rules if we get a proxy SMTP auth command
Skip gateway rules if we get a proxy SMTP auth command. This is not for general use. It can be used if you are using SurgeMail in front of another mail server with a wild card gateway to gateway all domains to a back end mail server. Then an authenticated user is a local user trying to send out so the gateway rules are ignored. (this is strongly not recommended)
g_authent_allow_badascii - Allow ascii chars outside the range 32 < 127
By default ascii characters < 32 and >= 127 are blocked as invalid. If you require these characters set this to TRUE.
g_authent_always - Always lookup user, so virtual domains can exist just in authent module
Always lookup user, so virtual domains can exist just in authent module. This allows you to support 10,000 domains on one system without a 'huge' ini file. Be careful to not create/remove real domains with the same name as existing domains that only exist in the authent database as the 'drop files/inboxes' will move when this occurs and existing mail will vanish.
g_authent_cachebad - Cache life of failed authent lookups
Set the life in seconds that the cached failed lookups can be used, default 60 seconds. Best left alone unless your server is being hit by thousands of failed lookups and your authent module is slow.
g_authent_cachelife - Cache life of successful authent lookups
Set the life in seconds that successful cached lookups can be used, default 2 hours. Best left alone.
g_authent_cachesize - Size of the authent cache
Set the size of the authent cache, default is 500 entries. Generally best left alone.
g_authent_domain - Authent domain
If this is 'true', the virtual domain name is appended to the username before it is passed to the authent process. This lets the authent process deal with virtual domains. As a general rule, this should ALWAYS be true.
g_authent_info - Authent info
Defines a piece of information to store about the user in the user database (phone number, name, address etc). Each piece of information is given a name, a field, an access mode, a default and a type. The name defines what appears in the web management display. The field is what is sent to the authent_process. The access mode can be one of the following: user, domadmin, or admin, createonly, none. The default is what value is assigned upon creation of a new user. The type can be one of: date, readonly, encrypt or any custom string which you want to check for or match on the na_details.htm page with a template function like: ||ifequal||user_info_type||custom|| .. do things .. ||endif||
An access mode of 'admin' means that only the system admin can see the information, 'domadmin' means the sysadmin and any domain admin can see the information, 'user' means the user can see the information, 'createonly' means the user sets the information at creation time but cannot see it after that and 'none' ensures that no-one can see or modify the information (used for information that is handled by SurgeMail itself, either through the interface or otherwise)
e.g. g_authent_info name="Phone Number" field="phone" access="user" default="" type=""See here for a complete list of default settings.
g_authent_ip - Authent Lookup IP numbers via authent modules - enables relaying
If enabled each connecting IP address will be looked up in your user database as x.x.x.x@ip eg: "127.0.0.1@ip" and if the user is found then relaying is allowed and if 'send_limit="nn"' is defined then that will set the tarpit send limit for that user.
For per IP tarpit limits to work you need to define the g_tarpit_max and g_tarpit_max_remote settings. And g_tarpit_drop to make the limit effective.
g_authent_last_login - Store users last login time in the database
This setting will cause the authent field 'last_login' to be updated when a user logs in. The field is set to a timestamp which is 'the number of seconds since midnight January 1, 1970'. This field is updated 'at most' once every 24 hours. Other features i.e. delete_user_after and disable_smtp_after will look for this field.
g_authent_logall - Turns on logging of authent requests
If enabled, authentication requests are logged in mail.log as "<day> <time> Authent[<action> <info>]".
g_authent_number - Authent number
The number of concurrent authent processes to run. If you are using a slow external authent module (e.g. sql) then it is probably worth running 3-4, there is no need to have more than 1 when using nwauth.exe. (Default = 1)
g_authent_process - Authent process
The command line of a NetWin authentication module. You can use one of our standard modules for LDAP, ODBCAuth, MySQL etc or write your own. For more information on these modules see the authentication section of the manual .
This will typically be something like:
g_authent_process "E:\surgemail\nwauth.exe -path E:\surgemail"
or
g_authent_process "/usr/local/surgemail/nwauth -path /usr/local/surgemail"
g_authent_restart - Cycle auth modules every 1000 lookups
This is useful if there are resource allocation issues in the authentication module. Eg OBDCAuth
g_authent_single - Allow local users with a single quote char in their name
This let's users exist who contain the single quote ' character. It is not supported with some authent modules though, nwauth does allow it.
g_authent_strip_domain - Strip domain for authent lookups
Use when your database expects one 'primary' domain to do lookups without a domain name then SurgeMail will strip that domain only from lookups. Typically this is only necessary with old DMail authent modules.
g_authent_timeout - Timeout for authent response
Timeout for authent response, default 60 seconds.
g_autologin_file - File to use to share auto login information on NFS based cluster
This allows webmail to autologin when using an nfs based cluster and a load sharing device.
g_autologin_pop - Enables WebMail Autologin using POP when on another server
Webmail needs the ability to automatically login to SurgeMail to changes passwords etc. This setting will do this via an extension to the pop protocol allowing WebMail to autologin whilst running on another server. (Normally this is done using a temporary file)
g_bad_login_allow - Number of consecutive bad logins for a user before blocking that user
Number of consecutive bad logins for a user before blocking that user.
g_bad_login_ip_allow - Number of bad logins from an IP before blocking that IP
Number of bad logins from a single IP before blocking that IP.
g_bad_login_ip_ignore - IP address(es) to ignore bad logins from
Use for webmail system or other local gateway to stop bad login counter from locking out all users.
See also: g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_badfrom_noip, g_badfrom_check, g_badfrom_stamp, g_badfrom_badmx, g_badfrom_from, g_badfrom_whitelist
g_bad_login_mins - Minutes to block login for, if consecutive bad ones received
Minutes to block login for, if consecutive g_badlogin_allow or g_badlogin_ip_allow bad logins received=.
g_badfrom_badmx - Drop message if this MX
If mx host is one of these addresses then drop the message, it's definitely spam (e.g. 127.*).
g_badfrom_check - Check if 'from' envelope can be delivered to
If this is set to "true" then SurgeMail will connect back to the envelope 'from' address and check that the address is valid, a cache is used to improve performance, if it cannot connect then the message is bounced as probable spam. It's nicer to use the following setting "g_badfrom_stamp" as well, then if SurgeMail cannot connect back or the user is invalid then a header is added to indicate this, and our SmiteSpam rules will use this to increase the spam weighting.
You can use g_spam_allow to exempt an IP from this check as well as g_badfrom_whitelist for a domain. Please note that by default SurgeMail uses a blank mail from to do its check.
MAIL FROM: <>
Some servers might reject this, though they shouldn't because its a standard bounce, however if they do you can use g_badfrom_from to set a mail from address to be used for this check.g_badfrom_from - Mail from account for g_badfrom_check
From to use when doing the g_badfrom_check check, not normally needed, if set must be set to valid account.
g_badfrom_noip - Check envelope from domain exists and is a valid IP number
Check envelope from domain exists and is a valid ip number, if not bounce message.
g_badfrom_stamp - If 'g_badfrom_check' is bad then stamp a header on the message
g_badfrom_check must also be set to true. If this is set to "true" then SurgeMail will connect back to the envelope 'from' address and check that the address is valid, a cache is used to improve performance, if it cannot connect then a header is added to indicate this, and our SmiteSpam rules will use this to increase the spam weighting.
g_badfrom_whitelist - Whitelist of domains to skip from checks
Whitelist of "from" address domains to skip g_badfrom_* checks.
eg.
g_badfrom_whitelist "specialdomain.com"g_ban_blackhole - Leave connected but reject all recipients without looking them up
Leave connected but reject all recipients without looking them up. This is good of dealing with high volume spammers without wasting resources doing user lookups.
g_ban_from - Ban any matching MAIL FROM: envelope
Same as 'ban_helo' but applies to the from (return address) part of the mail envelope. This is NOT the same as the from/sender header in the message itself!!! This equates to the 'Return-path:' header that the mail server adds.
g_ban_helo - Ban any machine that gives a matching 'helo' string
This is a simple spam protection system to block known spam/problem users based on the 'helo' name they send to your system. This name is recorded in the 'received' header along with the IP address. This name is very easy to 'fake' so is not a high security level of protection, but it is simple for stopping stupid robots etc, that have gone insane.
Example: *junkmail.com
g_ban_rcpt - Ban any matching RCPT TO: envelope
Same as 'ban_helo' but applies to the recipient part of the envelope (destination users) this is NOT the same as the 'To:' header in the message itself!!! This can sometimes be used to block really simple spamming programs that always send to the same invalid users.
g_bank_debug - Log request to bank server
Use when trying to debug the g_bank_url post/response
See also: g_bank_url, g_bank_user, g_bank_pass, g_bank_ok, g_bank_reason, g_bank_log, g_bank_group
g_bank_group - Map groups to prices and a description
See g_bank_url for details
See also: g_bank_url, g_bank_user, g_bank_pass, g_bank_ok, g_bank_reason, g_bank_log, g_bank_debug
g_bank_log - Log lines matching this in response.
See g_bank_url for details
See also: g_bank_url, g_bank_user, g_bank_pass, g_bank_ok, g_bank_reason, g_bank_debug, g_bank_group
g_bank_ok - Find this in response, if found then charge was successful
See g_bank_url for details
See also: g_bank_url, g_bank_user, g_bank_pass, g_bank_reason, g_bank_log, g_bank_debug, g_bank_group
g_bank_pass - Password for authenticated web request to banks system
See g_bank_url for details
See also: g_bank_url, g_bank_user, g_bank_ok, g_bank_reason, g_bank_log, g_bank_debug, g_bank_group
g_bank_reason - This line is returned to user if it is found
See g_bank_url for details
See also: g_bank_url, g_bank_user, g_bank_pass, g_bank_ok, g_bank_log, g_bank_debug, g_bank_group
g_bank_url - URL to charge a credit card (experimental)
This allows automated monthly charging of users
See also: g_bank_user, g_bank_pass, g_bank_ok, g_bank_reason, g_bank_log, g_bank_debug, g_bank_group
g_bank_user - Username for authenticated web request to banks system
See g_bank_url for details
See also: g_bank_url, g_bank_pass, g_bank_ok, g_bank_reason, g_bank_log, g_bank_debug, g_bank_group
g_bind_from - Bind outgoing SMTP connections based on 'from' envelope
Bind outgoing SMTP connections based on the IP of the virtual domain in 'from' envelope. This is only useful if you are using IP based virtual domains.
g_bind_out - Bind outgoing smtp connections to IP
Bind outgoing smtp connections to this IP number.
g_black_above - Level for spam detection for g_black_count
Level for spam detection for blacklisting IP number e.g. 7.
g_black_count - Blacklist sender IP based on spam sent
Number of spam in a row before IP blacklisted for 30 minutes eg: 30 (default = disabled)
g_black_to - Blacklist sender IP based on catch addresses
Blacklist senders IP address for 30 minutes if they deliver to these spam catch email addresses.
eg. g_black_to "smith@mydomain.com,catcher@myotherdomain.com"
g_block_files - Block certain attachments
Allow you to block any mail with certain files attached.
g_block_files "*.exe,*.cmd,*.com"
See also: g_block_wild, g_block_skip, g_block_longok, g_debug_block
g_block_longok - If true allow long file names (more than 180 char)
By default files names over this length are ALWAYS blocked if g_block_files is used, in rare situations these are not just viruses attempting to get around the filter.
See also: g_block_wild, g_block_files, g_block_skip, g_debug_block
g_block_skip - From or To address to bypass g_block_files
Some users will need to send various attachments, these users are excempt to the g_block_files rule
See also: g_block_wild, g_block_files, g_block_longok, g_debug_block
g_block_wild - Block wildcards in usernames
Block the '*' wildcard character in usernames.
g_blogs_default_template - Default template set that is used by newly created blogs
This setting can have a value of the name of any directory in the SurgeMail blogtpl directory
g_blogs_enable - Surgemail blogs
Allow users to create blogs
g_blogs_max_per_user - Maximum number of blogs per user
Maximum number of blogs per user, default is 5
See also: blogs_max_per_user, g_user_blogs
g_blogs_maximum_image_width - Default maximum image width
Images larger than this that are posted to blogs are scaled down, default is 390, per blog setting can overide this.
g_blogs_maximum_items_in_top_page - Maximum number of items on the top blog page
Maximum number of post bodies to appear on a blog top page, default is 10
g_blogs_no_suffix - Shortens URL, url_blogs must be defined for each domain
This shortens http://a.com/blog/juggling to http:/a.com/juggling, but does require that you define a specific name for the blogs in the domain based url_blogs setting
g_blogs_not_unique - Allow the same blog name in multiple domains
If set you can create different blogs with the same name in different virtual domains, this is not recommended.
g_blogs_ping - Sites to ping on each post
Host and path to ping on each blog post. egs: host=rpc.technorati.com path=/rpc/ping or host=rpc.weblog.com path=/RPC2
g_blogs_sub_domain_prefix - Prefix to use instead of blogs. for blog subdomains. use ! to have no prefix.
Experimental feature do not use
g_blogs_use_sub_domains - Make blogs accessible at http://blog_name.domain/
If you're DNS entry supports it, turn on this setting to make blogs accessible at http://blog_name.blogs.domain/ instead of http://domain/blogs/blog_name
g_body_filter - Enable user email body filtering
Allows the user to configure filters which filter the body of incoming messages
g_bomb_max - Max messages to a single address per hour
Simple system to prevent intentional or more likely, accidental mail loops or mail bombs where thousands of Emails are sent to a single user. A setting in the range of 100-1000 is generally good depending on your sensitivity to incorrectly blocking real mail. We suggest 1000 is a good setting if you are unsure.
This counts the messages from a single IP address to a single recipient. If a single IP sends more than this many messages to any single recipient then they will be tarpitted (slowed down and rejected).
Use spam_allow ip.address.list to over-ride the limit for known local systems that might exceed this limit (unlikely anything will).
g_bomb_max_from - Max msgs from a single email address/hour
Max msgs from a single email address/hour.
g_bounce_bind - Use a specific ip address for outgoing bounces
Some RBL sites blacklist machines for sending bounces, which is probably a good thing. But even with spf running your server may occasionally send a bounce to a forged address, and so you can use an alternate ip address for these bounces to avoid blacklisting your main mail server address. First you must assign the ip address to your network interface etc
g_bounce_disable - Bounce Disable
Disable all bounces. This is particularly useful when under spam attack. This is for outgoing bounces it stops SurgeMail generating bounces it won't affect incomming bounces from other servers.
example:
g_bounce_disable "true"g_bounce_limit - Max size of bounce messages
Max size in bytes of message to send back as bounce message is truncated if necessary.
g_bounce_nodrop - Enables locally generated bounces for non local users
This setting makes bounces occur normally, the reason bounces are normally dropped for non local users is that they are almost always spam bouncing off another server due to forwarding settings, and as such sending a bounce email will get your server black listed, so we decided it was best to drop them by default since they are rarely useful. Turn this setting on at your own risk :-). Instead use g_bounce_to to list domains that it is safe to bounce to.
g_bounce_redirect - Send all bounces to a local address
This can be used to avoid 'back scatter' which can get your server listed in various black listed sites. In general your server should not generate bounces so if you get lots you may find changing config settings can stop them. Note this only redirects bounces to non local recipients, so your users sending outgoing mail will still get their own bounce messages.
g_bounce_reject - Reject bounces by ip address from known dumb mail servers
Some mail servers (exchange) will accept email, then bounce it, this is now considered a 'crime' and will get your server black listed, so if you have surgemail running as a gateway for such servers you can tell it to reject any bounce that server is foolish enough to send you.
g_bounce_some - Enables locally generated bounces for partial message failure
Don't turn this on it risks getting your server black listed as it will generate more back scatter
g_bounce_to - Domains to treat as local and send bounces to
This setting makes bounces occur normally, the reason bounces are normally dropped for non local users is that they are almost always spam bouncing off another server due to forwarding settings, and as such sending a bounce email will get your server black listed, so we decided it was best to drop them by default since they are rarely useful. Turn this setting on at your own risk :-). Instead use g_bounce_to to list domains that it is safe to bounce to.
g_centipaid - see CentiPaid.htm
Authentication server and port for CentiPaid.
g_comment - Management notes and comments about the server
This is a dummy setting that lets you store information in the ini file that will survive setting changes from the web admin tool.
g_con_perip - Connections per IP
Maximum number of connections allowed per IP address. Primarily this is used to prevent simple denial of service attacks where one user could otherwise use up all the channels your system can support and then do nothing with them.
g_con_perip_except - Connections per IP exception
IP list of exception addresses to g_con_perip.
g_con_persubnet - Maximum concurrent connections per subnet
Maximum number of concurrent connections per subnet. This limits concurrent connections from a sub net, great for automatically stopping professional spammers who use multiple addresses. A typical setting might be 20. Subnet is /24.
g_convert_percent - Convert % signs top @ in recipient addresses
Some Spam tests send mail user%spamdomain.com@localdomain.com to see if a server is an open relay. If a default address is set up for the local domain this will be delivered to this local address and the test assumes the mail server is an open relay. This setting prevents this.
g_create_allow - List of characters allowed in usernames/passwords
Defaults to A-Za-z0-9\-_. meaning usernames/password may contain letters, numbers, -, _ and . and nothing else.
g_create_allow_pass - List of characters allowed in passwords
Settting overriding g_create_allow just for passwords.
g_create_apply - List of user groups to apply create_* settings for.
This setting allows you to apply create_* settings to domain admin accounts. Specify g_access_group names and domain admins in these groups will have create_* settings applied to them when adding users in the domain admin interface.
g_create_badnames - List of illegal usernames
Comma separated list of illegal usernames, may contain wild cards, if username contains part of a non-wild card or matches a wildcard it is disallowed.
g_create_cleanup - Cleanup existing data before adding a user
This causes a delete to be actioned for a user before/as they are created. This ensures the new user does not end up with any files, on any mailing lists, with any aliases etc from a previous user of the same name/address. If you delete users from the authent database directly i.e. not using the surgemail web admin or calling 'tellmail delete_user' then this setting will cleanup the users files when their address is re-used.
g_create_dictionary - File containing dictionary words to compare passwords to
Text file containing one word per line, passwords are compared to all words longer than 4 characters in this file, if a username or password contains a word in this file it is not allowed. Only takes effect if g_create_strict is checked.
g_create_pass_length - Limit the length of user passwords
This is applied during user self creation and when users change passwords. Set admin to true to restrict the domain and global admin also.
g_create_record_ip - Causes surgemail to store ipnum in the authent database
This setting has no further documentation currently available
g_create_strict - Whether to apply strict rules to usernames/passwords
Checking this causes surgemail to check passwords do not contain words longer than 4 characters from g_create_dictionary as well as requiring the password to be 6+ characters, and usernames/passwords to contain more than 1 character.
g_create_user_length - Limit the length of usernames
This is applied during user self creation. Set admin to true to restrict the domain and global admin also.
g_dbabble_links - Add web links to DBabble from other web interfaces (and vice versa)
This causes links to appear in the DBabble interface to switch to using WebMail (and SurgePlus if you have the g_surgeplus_links setting on).
See also: g_dbabble_smtp_port, g_dbabble_smtp_prefix
g_dbabble_smtp_port - DBabble SMTP port (do not manually change this setting - it should be set from the DBabble section of the web admin interface only)
This setting specifies the port that DBabble listens on. DBabble looks at surgemail.ini and if it sees this setting, overrides it's own setting with this value. When you save changes to this setting from within the SurgeMail DBabble admin interface, SurgeMail automatically sets appropriate values for the g_redirect_iflocal and g_gateway settings.
See also: g_dbabble_smtp_prefix, g_dbabble_links
g_dbabble_smtp_prefix - DBabble SMTP prefix (do not manually change this setting - it should be set from the DBabble section of the web admin interface only)
This setting is used in conjunction with the dbabble_smtp_port setting to forward all mail with the specified prefix on to DBabble.
See also: g_dbabble_smtp_port, g_dbabble_links
g_debug_ini - Debugging, don't use this
This is a temp setting used for testing
g_debug_vanished - Name of file to check for, if file vanishes, crash
This is for tracking a particular bug, not for general use
g_delete_exclude - Field and value that excludes an account from g_delete_user_after
If the authent response includes this field/value pair then the user account will not expire
Example: field="noexpire" value="true"
See also: g_acctlog_authonly, g_authent_always, g_authent_allow_badascii, g_authent_prefix_sep, g_authent_process, g_authent_cachelife, g_authent_cachebad, g_authent_cachesize, g_authent_domain, g_authent_number, g_authent_info, g_authent_ip, g_authent_path_broken, g_authent_single, g_authent_strip_domain, g_authent_restart, g_authent_logall, g_authent_fwdfile, g_authent_timeout, g_authent_last_login, g_auth_hide, g_auth_norelay, g_auth_skipgateway
g_delete_user_after - Number of days an account can remain unread before it is deleted
DO NOT USE THIS SETTING IN A MIRROR/CLUSTER SETUP
Number of days an account can remain unread before it is deleted. This setting cannot be used on an authent_domain FALSE domain unless it has a prefix setting.
g_delete_user_mode - Instead of deleting an unread account you can perform another action
DO NOT USE THIS SETTING IN A MIRROR/CLUSTER SETUP
You can set this to "file" or "suspend". "file" causes accounts to be written to the users_delete.rec file, which you can action by running "tellmail delete_user FILE" or "tellmail delete_user FILE users_delete.rec" (optionally specify the file). "suspend" causes accounts to be suspend, it does this by setting the field and value specified in the g_delete_user_suspend setting.
g_delete_user_suspend - If suspending an unread account set this field/value
DO NOT USE THIS SETTING IN A MIRROR/CLUSTER SETUP
Set the field and value to use when suspending an account due to g_delete_user_after and the g_delete_user_mode "suspend" settings.
g_deny - Deny users from some IP ranges
Block known spammers etc by IP address. You can use wild cards and 'not' signs, e.g. "!*,127.*,10.*"
g_deny_msg - Deny message
Message to give to users who are disconnected due to the above 'deny' setting.
g_deny_smtp - Deny SMTP based on IP address
Block users from some IP ranges connecting to SMTP only.
g_disable_exclude - Field and value that excludes an account from g_disable_smtp_after
If the authent response includes this field/value pair then the user account will not be disabled from receiving messages
Example: field="noexpire" value="true"
See also: g_disable_smtp_after
g_disable_smtp_after - Number of days an account can remain unread before delivery is disabled
DO NOT USE THIS SETTING IN A MIRROR/CLUSTER SETUP
Number of days an account can remain unread before delivery is disabled.
g_disable_surgeplus - Disable SurgePlus Calendar and File Sharing client
Disable users from logging in using the SurgePlus Calendar and File Sharing client. See SurgePlus
See also: xfile_url, disable_surgeplus, surgeplus_pop_server_name, surgeplus_smtp_server_name, g_xfile_allow, g_surgeplus_links, g_disable_surgeplus_updates, g_surgeplus_log_level, g_surgeplus_port, g_surgeplus_secure_port, g_surgeplus_web_port, g_surgeplus_web_url, g_surgeplus_hide_client_downloads, g_surgeplus_pop_server_name, g_surgeplus_smtp_server_name, g_surgeplus_delay_tell_upgrade, g_surgeplus_delay_tell_upgrade_exempt
g_disable_surgeplus_updates - Disable automated downloading of new versions of SurgePlus client from netwinsite.com
New versions of the SurgePlus client are automatically downloaded from netwinsite.com and made available for download form your server by your users. See SurgePlus
See also: disable_surgeplus, g_disable_surgeplus, g_surgeplus_delay_tell_upgrade, g_surgeplus_delay_tell_upgrade_exempt
g_dlist_nostart - Disable dlist
If set disable (do not attempt to start) dlist for DMail compatibility mode..
g_dlist_path - Path for dlist
DList Path normally defaults to $g_home/dlist.
g_dns_cache_size - Set size of forward dns cache, default 7000
Best not to change this normally
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_host - DNS host(s) for MX lookups
This setting can normally be left blank as the mail server will find your system DNS settings. However, you can specify one or more DNS servers for the mail server to use instead to lookup names.
DNS lookups are cached to disk so SurgeMail will generally continue to work even if your dns server is temporarily unavailable.
Test your dns server with this command. If working it should return two ip addresses for that domain.
tellmail dns_test "netwinsite.com"If you change the dns_host settings a 'reload' is not sufficient, restart surgemail.
Prior to SurgeMail 2.0h dns lookups were done using tcp instead of udp, they are now down with UDP unless the response exceeds UDP packet size (as per RFC).
NOTE: All dns servers listed in this setting must be fully recursive, a non recursive dns server will create many dns lookup failures!
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_match_msg - Message for stamp or bounce if forward and reverse lookup don't match
The message given to the user when the forwar/reverse dns lookup doesn't match
Example: "Sorry your ip address doesn't translate into a name that translates into your ip address"
See also: g_dns_paranoid, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_nlookup - Concurrent MX lookups
Concurrent DNS lookups to send to DNS server (Default=20) (not used after version 2.0h)
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_nocache - Disables DNS cache for spf lookups (20 minute life)
This setting disables the small cache used for SPF lookups to improve performance.
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_noptr - Set to reject or retry, for ip addresses with no reverse dns entry (rdns)
If the ip number of a connecting user has no associated name in the reverse dns database then the connection is rejected or told to retry later.
Example: "retry"
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_noptr_msg - Message for stamp or bounce if DNS lookup fails on ip address
See short description.
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_paranoid - Compare sender forward and reverse dns lookup and see if they match
Does a forward DNS lookup on the sender's domain and matches this with a reverse lookup of the senders IP address. If these do not match the message is either bounced or stamped with the header "X-DNS-Paranoid: <explanation>". Valid values for this field are "STAMP","RETRY" and "REJECT".
STAMP = Add the X-DNS-Paranoid header if it fails
RETRY = Bounce the message with a 450 error. (so if the failure was temporary the sending server will retry)
REJECT = Bounce the message with a 550 error
Set g_dns_lookup_msg or g_dns_match_msg to define the reject/stamp strings respectively.
g_dns_require - Require reverse DNS names match
Require MAIL FROM header to match the reverse dns lookup based of the sender based on the sender's IP.
eg. from=*@hotmail.com hosts=*hotmail.com
See also: g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_require - Require MAIL FROM header matches senders ip reverse dns
This setting predates SPF which does the same sort of thing on a grander scale, no longer needed.
Example: from=*@hotmail.com hosts=*hotmail.com
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_system - Use system code to do reverse lookups
If all channels hang in a state 'lookup' then turn this on so it will use the surgemail code for reverse dns lookups. This setting used to be g_dns_lookup and had the opposite meaning, we reversed it because the system dns code was faulty so often
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_dns_translate - If mx response is x.x.x.x translate to y.y.y.y:port
Useful for translating ip numbers inside a local intranet and doing other fancy routing of various sorts.
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_old, g_dns_new, g_spf_dns_timeout
g_domain_default - Default domain when POP/IMAP user does not specify one
This is probably not what you think it is, generally the 'first' domain in surgemail.ini is used in this situation, but in some instances, when using domuser.dat for example to translate users back to virtual domains, you will want the default domain to be a 'generic' made up domain that doesn't really exist.
For example lets say you have users fred@a.com, bob@b.com, then in domusers.dat you have
fred@a.com fred@a.com
bob@b.com bob@b.com
bob@xxx bob@b.com
fred@xxx fred@a.comAnd the result is that users who login to pop as bob or fred, will be correctly mapped to the correct virtual domain user even though the actual domain is different in those two cases.
Clear as mud I expect?
g_domain_list_max - Maximum number of domains to list at once
Maximum number of domains to list at once in the admin user interface.
g_domain_separator - Separator characters for virtual POP
For POP logins where your virtual domain is NOT distinguished by IP address users can login with 'user@domain' or user/domain.name etc and the mail server will pickup the domain name correctly. By default only 'user@domain.name' is accepted unless this setting is used which can be useful for brain dead mail clients which don't allow the user to specify 'user@domain.name' as the username eg:
g_domain_separator "/"
g_domuser_file - Domain users to thousands of virtual domains easily
Specifies a file which contains lines that translate an email address to the username that should be looked up in the database. This file can contain a domain name not previously specified in surgemail.ini allowing you to create unique sub-domain addresses. eg:
g_domuser_file "c:\surgemail\domuser.dat"
Example entries...
*@domain.com postmaster@domain.com
userA@domain.com userB@domain.com
firstname@lastname.domain.com firstname@lastname.domain.comg_dotlock_minutes - NFS lock waits
Minutes to wait for nfs lock file, default 20 minutes.
g_dotstuff_fix - Convert the way mail is stored on disk from dotstuffed to non dot stuffed (beta)
In the dotstuffed format any attachments that have content (in encoded format) starting with a . get corrupted, as all single '.' characters at the start of a line are converted to '..'. This is only very seldomly an issue as encoded text doesn't usually have . characters. This feature can only be enabled and still need furhter production level testing to make sure there are no side effects... so if you play with it consider yourself adequately warned :-)
g_download - Fetch an http file and do an ini reload
Can be used with g_include to have settings fetched from a central location, the file is fetched once an hour.
g_drop_use_len - Use the content-len header for drop file processing
For use on Solaris when using sendmail for incoming mail delivery.
g_dsn_enable - Enable DSN (Delivery Status Notification) esmtp extension.
Not recommended. Delivery Status Notification is used by spammers to find addresses to spam to.
See also: g_dsn_nofinal
g_dsn_nofinal - Try not to show real final recepients but just original recipients
This setting helps hide internal addresses in bounce messages (after forwarding etc). Not recommended.
See also: g_dsn_enable
g_encrypt_key - Encryption key for ccnumber auth field
Not for general use currently, used to partially obscure credit card info when stored in the authent module.
g_enotify_from - From address to use in email notification messages
This setting has no further documentation currently available
g_eof_fix_off - Turns of auto stripping of control+Z
These characters can break some mail clients and should not appear in normal emails
g_expire_silent - Don't send users emails telling them what was expired.
Some users get upset when they find messages have expired, this setting makes the expiration silent so the users don't even notice. I think this is a bit nuts myself but some admins prefer it
See also: expire_age, expire_size, expire_rule, g_expire_trash, g_user_utoken_expire
g_expire_trash - Expire any messages found in trash folders
Expires any messages more than 7 days old found in the 'trash' folder.
See also: expire_age, expire_size, expire_rule, g_expire_silent, g_user_utoken_expire
g_external_ip_disable - Disable adding of external IP to message headers
As subject says :-)
g_fallback - Fallback address
Default address for all local domains. If a local delivery is not to any valid user Emails will be delivered to this address. There is also a per domain default.
We want to stress that this is a dangerous setting, you use at your own peril.
Spammers will turn up to your server and test sending to accounts, they will just run through a dictionary of names, with a fallback setting you will be telling the spammer that all these accounts exist. The spammer will then deliver spam to these addresses in volumes that can cripple a server almost.g_fallback_relay_if_exists - Use FALLBACK_RELAY if not logged in but user exists (OLD_POPHOST_CREATEUSER_DISABLE)
This can be used to relay users where you have a user database that can be checked on the front end system directly (odbcauth, tcpauth, etc)
See also: surgewall, surgewall_options, surgewall_capa_local, g_surgewall_split
g_filter_max - Max size of messages to send through the filter pipe
Messages over this size (in bytes) are skipped. default = no limit
g_filter_n - Number of filters to run simultaneously
Default is 20, when this limit is reached the incoming thread waits a few seconds then skips the filter if necessary, this is intended to prevent a log jam/melt down effect.
g_filter_pipe - Filter pipe allowing external message processing
This allows external applications to filter and modify incoming messages. Example: Integration with Spam Assassin (on UNIX) could be achieved as follows:
g_filter_pipe "/usr/local/bin/spamassasin -P"
g_filter_pipe_skip - Skip filter if ip matches this
Set this for local servers that don't need filtering, e.g. mailing list servers, local trusted robots.
g_filter_timeout - Filter pipe timeout
Filter timeout (g_filter_pipe) in seconds, default is 360.
g_fix_crcrlf - Fix email messages containing crcrlf for line termination
This is best not used, it's best to fix the faulty email application, results are not gauranteed.
g_footer_file - Footer file
Footer file which is appended to all plain text mail messages.
g_footer_html - Footer file (HTML mail)
Footer file which is appended to all HTML mail messages.
g_footer_send - Footer file (outbound only)
Plain text footer file which is appended to all outbound mail messages only.
g_footer_sendonly - Enable outbound footer
Add g_footer_send to all messages when sending to non local users.
g_footer_skip - Skip footers for these users
This skips the footer for matching users (e.g. cell phones etc)
g_forward_illegal - Ban forwards to these addresses
A wildcard list of addresses to prevent forwarding to. Can be applied to 'user', 'domadmin' or 'admin'. eg *@yahoo.com,*@hotmail.com
g_friends_at_rcpt - Whether to check users friends list at rcpt stage
This setting is automatically added/removed by the web admin when global friends defaults are configured. It allows us to check friends at rcpt stage without paying a disk access cost for non-friends users.
g_friends_check_spf - Disable friends bounces if SPF headers missing/failed.
If the incoming message may be forged it will bounce messages using an smtp error code to deny delivery.
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_quota_friends, g_user_friends_domain_log_disable
g_friends_confirm_subject - String to use as the subject of a friends confirmation email
String to use as the subject of a friends confirmation email.
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_ignore - List of addresses considered friends for all users on the system
List of addresses considered friends for all users on the system eg: the system manager email address
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_latest_headers - Friends system re-read message headers
Causes friends to re-read message headers, allowing rules based on headers added during delivery
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_name - What to call the friends system
This specifies what to call the friends system when referring to it on web pages and in email to our users, you can call it whatever you like
See also: friends_at_rcpt, g_friends_only, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_only - Friends system
An anti-spam feature which screens incoming mail to ensure it comes from a human. For incoming mail from unknown addresses a message is sent to this person requesting them to reply to confirm they are human and the original message will be delivered. See this page for more details.
See also: friends_at_rcpt, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_pending_keep - Time to keep friend pending messages
How long to store users friends pending messages before deleting them (days)
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_pending_novanish - Disable auto-vanish of pending messages on confirmation bounce
When a bounce for a confirmation message is received the message it was sent for is deleted. This setting disabled the delete, leaving the pending message until it expires or the user decides to delete, release or allow it.
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_silent - Disable friends responses to users
This setting is to simply disable the confirm emails, not generally recommended as this makes friends a bit pointless.
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_friends_spf_fail_bounce - Bounce SPF failures, do not send friends confirmations
The default behaviour is to only send confirmations if SPF checks pass, if they fail friends checking is skipped, no confirmation request is sent and the email is not blocked by friends.
g_from_allow - From header allow
From headers to allow bypassing the g_from* checks. e.g. "*@x.y.com,*@b.com,fred@bb.com"
g_from_bl - Domain Based Blacklist Zones, lookups FROM domain in dns
The 'from' domain is checked against the specified RBL which must be a special 'FROM' based rbl which lists spammers by from address. Most spammers fake from addresses so this is a fairly marginally useful method.
See also: g_spam_allow_rbl, g_surbl
g_from_bounce - Bounce if from is probably faked
Bounce if from address is probably faked.
This check is activated for any mail with a local domain in the from address but not using SMTP authentcation, relay allow IP address or spam allow IP address.
g_from_check - Check from matches valid local domain
Check from domains match valid local domains if user is authenticated, or g_from_allow.
g_from_exact - Check from matches authenticated user
Check from matches authenticated user.
g_from_header - From header used in delivery bounces
From header used in delivery bounces.
g_from_relay - If not authenticated and g_relay_allow_ip matched then block if not local domain or whitelisted
This one helps prevent a local virus sending out spam. It basically says non authenticated users who can relay due to a g_relay_allow_ip rule must send from one of your domains or use smtp authentication or be in a white list. Note this test is performed on the message envelope not the body. We recommend insisting on smtp authentication to reduce your risk of this type of problem.
g_from_relay_white - White list of domains for g_from_relay setting
This is domains that can be used as a 'from' address for non authenticated users, in addition to local domains
g_from_rewrite - Rewrite from header, e.g. *@this.domain -> %1@another.domain
This lets you change the 'from' address from an internal domain name to a valid public domain name.
g_from_stamp - Stamp if from is probably faked
Stamp message with "X-Verify-Failed:" header if from address is probably faked.
eg: X-Verify-Failed: <user@mydomain.com> From mydomain.com is local but user not authenticated or from g_relay_allow_ip
This check is activated based on the same conditions as g_from_bounce.
g_from_timeout - Timeout on g_badfrom_* checks
Timeout in seconds of g_badfrom_* checks. Default = 60 seconds. If this timeout is reached the g_badfrom check will be classed as having failed.
g_gateway - Gateway messages to a particular domain (Or smarthost)
Used to gateway messages to another local mail server. Typically this other server is inside a fire wall so it's local IP address is not known by the DNS server. You specify the domain and IP address to send messages to and this server is treated as 'local' rather than remote in terms of open relay restrictions. eg: nonauthenticated users are able to send in mail. Open relay restrictions do not apply to messages sent to this domain because they are considered as if they were local users and not 'relaying'.
This setting has the fields domain(required), to(required), user(optional), pass(optional), relay=true/false(optional),check=true/false (optional)
Normally "domain" and "to" are the only fields that need to be filled in. eg. To relay mail from anyone to user accounts in the domain somedomain.com to the host 1.2.3.4.
g_gateway domain="somedomain.com" to="1.2.3.4"user="username" pass="password"
If SMTP authentication is required on the destination server the user and pass fields need to be completed.
check=trueThe check=true setting tells surgemail to actually connect to the server and check that recipients exist before accepting an incoming email for that user, this is STRONGLY recommended, as it stops the server having to bounce thousands of messages when spammers send to invalid addresses on your server. If SurgeMail cannot connect it will assume the user does exist so nothing is bounced except when the connection is successful.
relay="true"
As a safety measure to prevent accidental openrelays, SurgeMail will not relay for non authenticated users if the domain is "*". This can be overridden by placing "true" in the "relay" field. eg: To relay all mail for all users to host 1.2.3.4:
g_gateway domain="*" to="1.2.3.4" relay="true"
(The above gateway rule is equivalent to the 'Smart Host' feature other servers offer, allows open relaying to the server).
It is possible to use domain="c:\domains.txt" where domains.txt is a file listing the domains to be gatewayed, this should only be done for one gateway rule, and is only worth doing if you have thousands of domains to gateway.
local="true"
?
Gateway after user lookup
When gatewaying to a domain which accepts all email regardless of address (e.g. exchange) you are best to define the users in your local user database, this is the only way to prevent nasty bounces and get rid of all the spam cleanly.
1) remove the gateway setting for the domain
2) add a virtual domain
3) In the virtual domain add surgewall settings, e.g. in this example I'm gatewaying the domain 'netwin.co.nz' to a
backend server called 'backend.netwin.co.nz"vdomain address="" name="netwin.co.nz"
...
surgewall "backend.netwin.co.nz"
surgewall_options strip_domain="" proxy_failover="" auth_local="TRUE" pop="" smtp="" imap="" usercgi=""
You can find more gateway examples in our FAQ here http://www.netwinsite.com/surgemail/help/faq.htm#gateway
g_gateway_allow - Known hosts that act as incoming SMTP or surgewall servers for us
Some spam prevention mechanisms which use the ip address of the incoming system must be disabled for incoming SMTP servers/surgewall/firewall boxes so that stupid limits don't block all the incoming messages from your backup mx server etc. Settings this affects: g_tarpit_max, g_tarpit_max_remote, g_con_perip, RBL checks,
See also: g_smtp_delay_stamp, g_smtp_welcome_delay
g_gateway_always - Always send to gateway even if local domain exists
Always send to gateway even if local domain exists. Not sure why you would want to use this setting other than to temporarily send mail on to another server whilst keeping the local domain and accounts intact and untouced.
g_gateway_auth - Send SMTP auth requests to another host
Send SMTP auth requests to another host.
g_gateway_data - Gateway at the data stage (beta)
To allow bounces to be handled cleanly gateway messages before responding to the data comman so bounces can go direct without being generated and creating back scatter.
g_gateway_helo - Header that must exist in incoming bounces (g_send_helo) or bounces are dropped
An incoming filter can discard the majority of incoming bounces by using this setting to figure out if a bounce is valid without having to do a user lookup first! Usually this would be the setting g_send_helo from your 'outgoing' mail server
See also: g_ban_helo, g_helo_optional, g_send_helo, g_send_helo_from, g_verify_helo
g_gateway_ifnot - Send mail to gateway in preference to local delivery unless IP matches
The use of g_gateway_ifnot will deliver mail to the g_gateway rule in preference to local delivery unless the IP number matches. This would typically be used to pass mail through an external SMTP server for certain or all domains for scanning purposes etc.g_gateway_orcpt - Writes an original receipt header when forwarding a message, this may disclose multiple recipients, cc/bcc etc use only for tracking faults
This writes a header X-Rcpt-Original: ..., when forwarding a message to another server, good for tracking problems. This may disclose multiple hidden recipients, it should not be used normally
g_group_field - Group Field from authentication database
Based upon a match on an arbitrary field in the authentication database a user can be defined as being part of an access_group. All fields (field, value, group) are required. eg: To add the user to the access_group "paid_user" if the field "mystatus" has the value "fullaccess":
g_group_field field="mystatus" value="fullaccess" group="paid_user"
g_header_out - Header to add to outgoing posts
Mail header to add to outgoing mailing list posts.
g_header_strip - Strip listed headers from incoming messages
Useful for stripping headers that you don't trust or don't want for some reason
g_helo_optional - Make the SMTP Helo optional
Helo is optional for SMTP protocol (not recommended).
g_home - Root directory of the mail server
This setting controls where the mail server runs including the many sub directories it creates below this directory for work files and log files for each domain. Not something you should generally change.
g_http_proxy - Proxy web server for fetching files via HTTP
Proxy web server for fetching files if direct access fails. (mainly for updates to the spam prevention rules from netwinsite.com and for downloading the latest version of the SurgePlus Windows client to make available to your users.)
g_imap_acl - Enable ACL (shared folders) in imap
Experimental setting, This setting allows folders to be shared between users. We are still testing this, do not use it :-)
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_log_flush, g_imap_port, g_imap_secure_port, g_imap_no_internal_date, g_imap_timezone, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_capa - Where to get the CAPABILITY value from
When you have suffix based domains and you're using SurgeWall the CAPABILITY request comes before the domain of the user is known. As such SurgeMail cannot determine whether to send the real servers CAPABILITY or it's own. This setting will choose the default behaviour, valid values are: Local,
. By default SurgeMail defaults to the behaviour of the primary domain, if it's surgewall then it obtains the real server capability. "Local" defaults to SurgeMails own capability, and defaults to the real server capability. g_imap_capa_strip - Capability values to hide
In some situations you might not want to advertise server capabilities, for example SURGEMAIL and XFLDDATA when they cause problems with SurgeWall operations. Or perhaps the IDLE capability. Specifying the capability strings to hide here will cause SurgeMail to stop advertising those capabilies.
g_imap_cram_enable - Enable CRAM-MD5 authentication (requires nwauth 4.0h or greater)
Please note that CRAM-MD5 does have security implications, specifically it means that the local users password must be stored in a semi reversable state in the authent database. Also you must be using the new version of the NWAuth module.
See also: authent_info_grp, g_acctlog_authonly, g_allow_user_authent_field_get, g_allow_user_authent_field_set, g_authent_always, g_authent_allow_badascii, g_authent_prefix_sep, g_authent_process, g_authent_cachelife, g_authent_cachebad, g_authent_cachesize, g_authent_domain, g_authent_number, g_authent_info, g_authent_ip, g_authent_path_broken, g_authent_single, g_authent_strip_domain, g_authent_restart, g_authent_logall, g_authent_fwdfile, g_authent_timeout, g_authent_last_login, g_auth_hide, g_auth_norelay, g_auth_skipgateway, g_mirror_nwauth, g_gateway_auth, g_smite_skip_auth, g_smtp_portauth, g_smtp_etrn_auth, g_smtp_noauth, g_spam_check_auth, g_xauthuser_hide
g_imap_idle_nsf - The number of seconds before a complete directory rescan. To be use on NSF network drives
Number of seconds for IMAP IDLE to do directory rescan
g_imap_log_flush - IMAP log flush
Flush IMAP log on every write (for debugging).
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_port, g_imap_secure_port, g_imap_no_internal_date, g_imap_timezone, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_log_protocol - Log IMAP protocol
Log IMAP protocol and other IMAP information to the mail.log file.
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_flush, g_imap_port, g_imap_secure_port, g_imap_no_internal_date, g_imap_timezone, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_no_internal_date - Disable the internal date output on IMAP commands
The RFC implementation of internal dateis broken wiht MS outlook. SurgeMail has been modified to conform to the outlook inplementation of internal date making this setting redundant..
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_log_flush, g_imap_port, g_imap_secure_port, g_imap_timezone, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_port - IMAP Port (default 143)
Specifies the PORT to listen for IMAP connections on. IMAP is an alternative to POP protocol where the messages and folders all exist on the server. This is ideal when sharing a mail account between several users or when using Email from more than one computer. Use the keyword 'disabled' to disable this part of the surgemail service.
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_log_flush, g_imap_secure_port, g_imap_no_internal_date, g_imap_timezone, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_secure_port - IMAP Port (default 993)
Specifies the PORT to listen for dedicated SSL IMAP connections.
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_log_flush, g_imap_port, g_imap_no_internal_date, g_imap_timezone, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_size_fetch - If true, will display message sizes on fetch command. (ie * 123 EXISTS)
Displays message size in IMAP responses
g_imap_timeout - Time, in minutes for imap timeout, RFC required default is 30
You may in some cases wish to reduce this below the RFC required default if your server is under very heavy load. Results may be unexpected when breaking RFC behavior!
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_log_flush, g_imap_port, g_imap_secure_port, g_imap_no_internal_date, g_imap_timezone, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_timezone - Timezone to display - for testing purposes only
as per title :-)
See also: imap_public, old_imaphost, old_imaphost_always, old_imaphost_createuser_disable, old_imaphost_nodomain, old_imaphost_nodelete, old_imaphost_prefix, old_imaphost_file, old_imaphost_user, old_imaphost_pass, old_imaphost_lowercase, old_imaphost_skip, g_imap_acl, g_imap_cram_enable, g_imap_capa, g_imap_capa_strip, g_imap_log_protocol, g_imap_log_flush, g_imap_port, g_imap_secure_port, g_imap_no_internal_date, g_imap_timeout, g_imap_uidl_nofix, g_imap_size_fetch, g_imap_idle_nsf, g_old_imap_headbody, g_ssl_allow_imap, g_ssl_require_imap
g_imap_uidl_nofix - Disable UIDL auto repair of duplicate entries
If true disable auto repair of identical UIDL entries.
g_include - Include another ini file global settings only
Unlike the include command this setting will allow editing of the ini file in web admin, but settings included via this setting will not appear in the admin interface
g_iplimit - Untrusted local ip addresses e.g. web servers, special sending limits applied.
These limit settings let you control untrusted sources which may get viruses or cgi scripts that open them up to abuse. By throttling the remote addreses limit this will prevent any significant abuse. Authenticated sessions are 'not' limited!.
g_iplimit_islocal - Add domains to list of domains considered local for limit counting
See explanation of g_iplimit
g_iplimit_local - Max sends from untrusted ip to local domains per 30 minutes.
See explanation of g_iplimit
g_iplimit_remote - Max sends from untrusted ip to local domains per 30 minutes.
See explanation of g_iplimit
g_iplimit_whitelist - List of 'from' addresses that should bypass limits
This lets you bypass the iplimit restrictions for a known trusted user/form that needs to send a lot of local/remote emails
g_keepalive - Attempts to use keepalive for the web sessions (experimental & faulty currently)
Don't use this yet, we are still working on it.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_key_manual - Try and activate automatically when the key expires
When you purchase updates you must activate to get the expire date reset in surgemail, if this setting is not turned on then surgemail will try and do this automatically for you.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_language_default - Default language for user web interface
If the user has not yet selected a language then this language is used as a default. If the language specified here does not exist in the language files, or nothing is specified here then English is used as the default language.
g_last_login - Create last_login.time files
If true then when users login via pop or imap or webmail the file last_login.time is created/touched, this can then be used by local scripts to determine which user directories are not in active use.
g_ldap_forward - Remote ldap server to forward requests to (only for testing do not use)
Forwards all ldap requests to another host, primarily intended for testing, use at your own risk.
See also: ldap_disable, ldap_anydomain, g_ldap_port
g_ldap_port - LDAP Port (normally 389)
If specified this enables the mini ldap server inside surgemail which allows users with email clients that can do 'ldap' directory lookups to search for other users on the system. Obviously this should NEVER BE turned on for a public mail server, it is only appropriate with private mail servers where all users who can access the system are trusted.
There are additional 'domain' settings ldap_anydomain, which lets users search for users outside their own domain name. And ldap_disable which can disable ldap for specific domains.
See also: ldap_disable, ldap_anydomain, g_ldap_forward
g_lf_fix_off - If input contains naked 'lf' characters then reject with error instead of stripping as usual
This setting has no further documentation currently available
g_local_skipgateway - Skip gateway rule for local messages
If true skip gateway rule for local messages (bounces etc).
g_log_bounce_disable - Stop bounce reject entries filling up log (typically from spam bounces)
Disables useless logging in msg*.rec files, only recommended for busy servers
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_dns - Log dns responses in gory detail
Useful when debugging unexpected DNS results, search for 'dns' in mail.log to find the results.
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_log_flush - Flushing log - flush on every write
This makes the server flush log data after every write to the file. This affects performance but can sometimes be the only way to track down an unusual fault eg: if the server dies the log is completely up to date and shows the last thing the server did before dying.
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_fwd - Log fwd/redirection rules associated in msg.rec
Log fwd/redirection rules associated with g_log_rcpt in msg.rec files.
g_log_level - Set logging level
Set the logging level. This is primarily intended for finding faults with the server. Info level logging is the default. Alternatives are 'error' and 'debug'
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_norcpt - Don't log individual recipients in msg.rec files
Log individual recipients in msg.rec files
g_log_path - Path for log files
Sets the path for all SurgeMails generated logfiles. (except the delivery record logs)
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_pid - Log pid
Log PID along with thread-id in the UNIXlog files.
g_log_reject_disable - Disable the logging of rejected mail
SurgeMail will normally log failed deliveries due to MFilter / SmiteSpam / etc in the delivery logs. This setting will restrict this logging to accepted mail only.
g_log_size - Size of the mail.log files before they are rotated
The mail.log files are a fixed size rotating log of what is happening inside SurgeMail. Dependant on the load of your server this may contain a few days worth of activity or a few minutes worth. This setting allows you to change the default 2MB before rotation size.
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_slow - Do slower logging system
Forces logging to disk even if it may slow things down. Not recommended.
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_start_norotate - Don't rotate log on startup
By default the mail.log is rotated to mail2.log... on startup.
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_tcp_read,g_log_tcp_write - Log actual data for a specific IPThese settings let you 'trace' the data going 'to' and or 'from' a specific IP address (or list, or wild card) Lets say you have a client on a specific address that has a problem where the fault could be server/client or network related. To track it down add this to surgemail.ini
g_log_tcp_read "2.3.4.5"
g_log_tcp_write "2.3.4.5"Then try whatever is 'failing' and examine 'mail.log' to see what was read/written to that client.
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_log_user, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_log_thid - Log thread id in .rec files
Logs the thread id in the msg*.rec files, this is good for some types of debugging.
See also: redirect, redirect_max, redirect_cc, redirect_hash, g_create_record_ip, g_bounce_redirect, g_orbs_rec, g_received_name, g_received_names, g_received_skip, g_received_skip_all, g_recent_bypass, g_record_days, g_record_hash, g_record_path, g_redirect, g_redirect_cc, g_redirect_from, g_redirect_from_cc, g_redirect_hide, g_redirect_iflocal, g_spam_allow_recent, g_virus_recent_skip
g_log_user - Log pop/imap/smtp protocol for specified user
Creates a file for each user that matches this list, user_user@domain.log
See also: blogs_max_per_user, loginfails, url_blogs, g_acctlog_sum_inactive, g_acctlog_authonly, g_acctlog_noaliases, g_bad_login_mins, g_bad_login_allow, g_bad_login_ip_allow, g_bad_login_ip_ignore, g_bank_log, g_authent_logall, g_authent_last_login, g_autologin_pop, g_autologin_file, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping, g_imap_log_protocol, g_imap_log_flush, g_last_login, g_log_flush, g_log_fwd, g_log_level, g_log_path, g_log_pid, g_log_thid, g_log_reject_disable, g_log_bounce_disable, g_log_tcp_read, g_log_tcp_write, g_log_norcpt, g_log_size, g_log_dns, g_log_slow, g_log_start_norotate, g_perflog_disable, g_perflog_flush_interval, g_perflog_lowres, g_perflog_logall, g_perflog_surgeonly, g_smtp_log_protocol, g_smtp_log_size, g_spawn_log, g_spflog_enable, g_ssl_require_login, g_surgeblog, g_user_blogs, g_user_friends_domain_log_disable, g_surgeplus_log_level
g_lookup_names - Lookup names for connecting IP addresses
This is one of those things that you very likely do not want to turn on. It makes the mail server lookup the IP name of any connecting user, however lookups can take 30-90 seconds so it can negatively impact apparent performance. Most of the access rules in the server can accept IP names if this setting is enabled, e.g. instead of specifying local users are 153.2.3.* you can say '*.netwinsite.com"
g_lookup_reject_fails - If lookup cannot get a name, reject user (not generally recommended)
If lookup cannot get a name, reject user (not generally recommended)
g_lowdisk_warning - Disk space level below which to warn the manager
SurgeMail checks available disk space on startup and every half hour whilst running on all the mail, temp and home directories. If any is found to be low an email is sent to the system manager. The recommended level is at least 100MB (default is 10MB).
g_mailbox_path - Default directory to store mail
Default directory to store mail this is used to set mailbox_path when creating domains.
g_maildir_max - Max messages in a folder, do not adjust
The default is 30,000. When exceeded additional messages are invisible until some are deleted. We strongly recommend you don't change this limit as large folders are gemoetrically inefficient and users should take steps to avoid this limit rather than increasing it.
See also: g_maildir_netwin, g_maildir_standard
g_maildir_netwin - Use NETWIN proprietry storage format, STILL TESTING, DO NOT USE THIS
This changes the storage format from one message per file, to a proprietry format, the spool is converted automatically when you restart surgemail, THIS FEATURE IS CURRENTLY BEING TESTED, DO NOT USE IT!!!!
g_maildir_standard - Use more standard maildir format
The maildir format is flawed in that it is not designed to be used on Windows systems. This setting will force SurgeMail to use a more standard maildir format, but does mean you cannot just copy mail from a UNIX box to a Windows box as the ":" character is a reserved character on Windows systems.
g_mailstatus_message - Error message to give when mailstatus is set to specified state
This allows you to specify the error message given to the user when they are set to certain states, you may use other authent fields in the message, for example:
g_mailstatus_message state="payup" message="Payment is due $full_name$, please pay here: http://your.site/path/file.htm"
g_manager - Email address of manager
Email address to send reports to.
g_manager_port - Manager port (default 7026)
This is the port the web manager and web mail access will run on. By default it is port 7026. Use the keyword 'disabled' to disable this part of the surgemail service.
g_manager_secure_port - Manager secure port (default 143)
This should be the main server management port and provides a secure server management connection. By default it is port 7025. https://your.mail.server:7025. Use the keyword 'disabled' to disable this part of the SurgeMail service.
g_manager_smtp - SMTP server for manager Emails about failures
For obvious reasons, if the server is not working it cannot use itself to send the manager an Email message, so for highest reliability you may want to define another mail server for fault reports to be Emailed to.
g_manager_username - Global domain managers username (for web based domain administration)
Specifies the local users which have manager rights for all domains. These users can login to the user self management interface and will recieve special domain manager options. This setting works slightly different to the domain level 'manager_username' setting in that if you specify an account without the @domain part i.e. 'admin' it gives all admin users in all domains domain rights over all domains.
g_max_bad_nolookup - Max bad recipients in a row if exceeded skip user lookup
Max bad recipients in a row if exceeded skip user lookup - useful when tarpitting a spammer.
g_max_bad_to - Max bad recipients in a row
If a system sending your system Email sends more than the specified number of bad addresses in a row then it is assumed to be incoming spam and further messages are rejected.
g_mdir_hash - SurgeMail hashing mode
Hashing mode for SurgeMail, default is 5, for compatibilty with /b/o/bob use 2.
g_mdir_prefix - Maildir folder prefix
Prefix for maildir folders defaults to 'mdir', use '.' for compatibility with qmail.
g_mfilter_addonly - Add headers only
If true then only allow 'adding' headers, not changing them.
g_mfilter_file - Path to mfilter.rul spam rule processing
This is the full path to the Mfilter rule file which provides advanced message filtering capabilities. See Mfilter.htm for more details.
g_mfilter_localonly - Only filter local deliveries
If true then only run Mfilter on local deliveries.
g_mfilter_maxlen - Mfilter Max message length
Size to truncate messages to before processing with Mfilter.
g_mfilter_noisey - Do log anything in mfilter
Logs the real details of mfilter, never user on a live busy system this is only intended for debugging an mfilter script. It logs every line of the script!
See also: g_mfilter_file, g_mfilter_maxlen, g_mfilter_addonly, g_mfilter_localonly, g_mfilter_trace, g_mfilter_skip_ip, g_user_mfilter
g_mfilter_skip_ip - Skip mfilter for messages from these ip's
This allows you to add a comma separated list of ip's to skip running mfilter on. This is based on the ip of the sender. Wild cards and ranges can be used.
Example:
g_mfilter_skip "10.0.0.2,210.56.43.*,193.1.16-24.0-255"g_mfilter_trace - Log trace lines in Mfilter
Log trace lines in Mfilter for debugging .
g_mirror_config - Mirror surgemail.ini
Syntax: g_mirror_config "true/false"
You put this on both machines and it will attempt to mirror the surgemail.ini. There will be some settings that you do not wish to mirror and these can be exempted by using:
g_mirror_config_except "setting,setting,setting"
Some settings are not mirrored by default these are: g_mirror_host, g_mirror_nwauth*, g_mirror_mode, g_authent_path, g_dlist_path, g_log_path, g_record_path, g_home, g_authent_process, g_mfilter_file, g_webmail_work, g_work, g_virus_cmd, g_atrn_port, g_imap_port, g_imap_secure_port, g_ldap_port, g_manager_port, g_manager_secure_port, g_monitor_port, g_pop_port, g_pop_secure_port, g_ppd_port, g_smtp_port, g_smtp_secure_port, g_webmail_port, g_webmail_secure_port, g_surgeplus_port, g_surgeplus_secure_port, g_surgeplus_web_port, g_bind_out, g_virus_avast, dmail_drop_path, dmail_bin_path, web_path, webmail_work
(it is possible we will update this list over time)
* g_mirror_nwauth is obsolete don't use it.See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_prune_age, g_mirror_threads, g_mirror_live, g_mirror_config_except
g_mirror_config_except - Mirror surgemail.ini
Syntax: g_mirror_config "setting,setting,setting"
This will tell the server not to import the specified settings from the other mirror.
Example:
g_mirror_except "g_spam_allow"This will tell the server not to change this setting. This only affects the machine its on, if the other server does not have this set, it will continue to mirror the setting. This setting accepts wildcards. This setting accepts a special case value "address" that will prevent mirroring of existing domain ip addresses, allowing different ips on each mirror machine. There are a number of settings which are not mirrored by default these are specified above in g_mirror_config.
In addition the mailbox_path setting is not mirrored, unless, the existing setting is a sub directory of the g_mailbox_path and the new setting is a sub directory of the g_mailbox_path from the other server, in which case the mailbox_path is set to the same sub directory using the existing g_mailbox_path setting eg.
[recieving server]
g_mailbox_path "c:\surgemail\mbox"
mailbox_path "c:\surgemail\mbox\domain"[sending server]
g_mailbox_path "d:\surgemail\mbox"
mailbox_path "c:\surgemail\mbox\domain_moved_here"[result on recieving server]
g_mailbox_path "c:\surgemail\mbox"
mailbox_path "c:\surgemail\mbox\domain_moved_here"See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_prune_age, g_mirror_threads, g_mirror_live, g_mirror_config
g_mirror_host - Mirror host
This unique SurgeMail feature allows you to setup two identical mail servers across a local or widearea network. The waiting mail messages & folders etc are duplicated continuously between the two systems, so users can use either system. If either system fails for any hardware reason the other acts as an instant on line replacement without any interruption to the user. In addition when the faulty system is replaced the two automatically re-synchronize.
See this page for Mirror overview
See also: g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_prune_age, g_mirror_threads, g_mirror_live, g_mirror_config, g_mirror_config_except
g_mirror_live - Mirror: Send incoming messages immediately
Enables a faster mirroring mechanism, strongly recomended, this setting will be the default in a future release
See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_prune_age, g_mirror_threads, g_mirror_config, g_mirror_config_except
g_mirror_mode - Master / slave mirror system
Certain actions may only be run on the mirror master system (such as expire processing) or are different in behaviour between the master and slave (such as NWAuth mirrorring and dlist mirorring). This setting must be set to MASTER on one system and SLAVE on the other system for correct operation. (Note basic mirrorring of delivered mail will happen if this setting is the same on both systems it is just some of the special mirrorring functionality that this is required for)
See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_secret, g_mirror_prune_age, g_mirror_threads, g_mirror_live, g_mirror_config, g_mirror_config_except
g_mirror_nossl - Disable SSL for mirror protocol connection
This is best turned off unless your servers are talking over a wide area untrusted network.
See also: g_mirror_host, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_prune_age, g_mirror_threads, g_mirror_live, g_mirror_config, g_mirror_config_except
g_mirror_prune_age - Mirror minimum age for items to be pruned during sync_prune
Mirror minimum age for items to be pruned during sync_prune, default 14 days.
See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_threads, g_mirror_live, g_mirror_config, g_mirror_config_except
g_mirror_secret - Mirror secret shared password
This password is required to prevent the mirroring mechanisms being abused. We recommend a random string of letters at least 10 characters long. e.g. "urcajfielsjfs"
See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_prune_age, g_mirror_threads, g_mirror_live, g_mirror_config, g_mirror_config_except
g_mirror_threads - Max threads we can use during resync_fast, default 6
During resync fast four threads are used, this is usually sufficient, more may overload your system and result in failures, if your system is not under load you could set it as high as eight, but this would only be sensible if your disk array has more than 4 drives in it!
See also: g_mirror_host, g_mirror_nossl, g_mirror_nwauth, g_mirror_mode, g_mirror_secret, g_mirror_prune_age, g_mirror_live, g_mirror_config, g_mirror_config_except
g_monitor_disable - Disable the monitor process
This allows the monitor process to be completely disabled. The monitor process is the swatch executable and can be setup to monitor and automatically restart SurgeMail if it crashes. The monitor process is also used to start SurgeMail from the using the web interface if it has been shutdown.
g_monitor_port - SurgeMail monitor port (default 7027)
The port SurgeMail monitor runs on allowing SurgeMail to be remotely started. Typically you won't need to change this, however you can specify an IP address to bind to or a list of alternate ports, e.g. 10.3.2.3:7027 or 7027,8027 etc...
g_msg_hops_max - Maximum received lines or message is bounced, default 30
If there are more received lines than this the message is bounced.
g_msg_max - Max size of a single message
Max size, in bytes, of a message, eg: 20,000,000 for a 20mb limit. This setting is useful to prevent a single large message jamming up your system.
g_mx_tryall - Try all mx hosts even if lower than own mx priority
This breaks the standard RFC behavior, but can be sensible in certain rare situations which currently escape me.
g_naked_msg - Text to display if message body contains naked LF characters
Default is: "Naked LF see http://netwinsite.com/surgemail/help/smtplf.htm"
g_newui_advanced - Always run new admin ui in advanced mode
This setting has no further documentation currently available
g_newui_disable - Disable swanky new admin ui
This setting has no further documentation currently available
g_notag_notascii - Don't add x-notascii: charset to any non ascii message
This can be used by user exception rules for users that don't expect any foreign language messages
g_notag_url_forgery - Don't add x-UrlForgery when a ref urls seem to not match
Many scam's will use legit urls with aref links to their own site, this tries to tag such messages which can then be scored as spam via aspam_mfilter.rul
g_old_imap_headbody - Get head and body seperately
This is just the way it used to do it, I can't see any good reason for it, but I'm leaving this setting incase there is a reason :-)
g_old_pophost_debug - Log extra info when doing old pophost logins
Log extra info when doing old pophost logins for debugging.
g_old_user_check - Disable the account status enabled check on rcpt lines
Normally the account status field is checked at the recipient stage, this setting disables this check.
See also: authent_info_grp, g_allow_user_authent_field_get, g_allow_user_authent_field_set, g_authent_always, g_authent_allow_badascii, g_authent_prefix_sep, g_authent_process, g_authent_cachelife, g_authent_cachebad, g_authent_cachesize, g_authent_domain, g_authent_number, g_authent_info, g_authent_ip, g_authent_path_broken, g_authent_single, g_authent_strip_domain, g_authent_restart, g_authent_logall, g_authent_fwdfile, g_authent_timeout, g_authent_last_login
g_orbs_cache_life - Sets the amount of time to keep RBL entries cached.
Syntax: g_orbs_cache_life "seconds"
Default: 7200 secondsThis allows you to control how long the RBL lookups are cached for.
Example:
g_orbs_cache_life "100"
g_orbs_check_all - Keep doing lookups even if found in a RBL, this is slower of course!
This checks all the ORBS/RBL servers listed even if the connecting ip address is found in one server, this is slower but can mean you can score more accurately when an ip is listed in multiple RBL databases.
See also: g_spam_allow_rbl, g_surbl
g_orbs_exception - Exceptions to Open Relay / Known Spam sites
This allows you to over-ride a response from an ORBS/RBL database. For example, if a site you wish to do business with is in the RBL database you can add their IP address to this setting and then they can send you Email again.
g_orbs_force - Forces RBL lookup even if they are in an exception.
Syntax: g_orbs_force "true/false"
This allows you to force RBL lookups on users that would normally not be checked due to being in an allowed relay ip (g_allow_relay_ip).
g_orbs_late - Disconnect user only if they fail to authenticate
Sometimes your customers will be using dial in lines that are banned by RBL databases, in this situation this setting will help as it will keep the connection alive long enough for a valid user to send an smtp authentication in.
Can also be used wth g_spf_skip_to "user@domain" this will allow you to add exceptions for users or domains that do not want RBL checks done on their accounts.
g_orbs_list - Multiple Open Relay Blocking System RBL databases
Allows enforcement of a servers blacklisting or whitelisting in one or more RBL databases with a different action for each database. In addition this can be used to mark messages with a header which can then be taken into account in the SmiteCRC"SpamDetect rating" calculation. A RBL database is simply a DNS server that returns a positive response if a server is listed in the database. A variety of services are available online that can maintain blacklist databases. Normally you would maintain your own whitelist database that overrides the blacklist listings.
name=service action=deny,accept,stamp stamp="string to add to header ||remoteip||"
Where the stamp option adds the header:
X-ORBS-Stamp: string to add to header 1.2.3.4
The variable ||remoteip|| can be used to create a url to go directly to a spam database web site and give details on the offending ip address. e.g. stamp="Spamcop, http://spamcop.net/w3m?action=checkblock&ip=||remoteip||"
eg 1 - A simple deny mail from blacklisted servers could be achieved with:
g_orbs_list name="relays.ordb.org" action="deny"eg 2 - A smarter setup with exceptions for certain IP ranges and a whilelist exception database, a blacklisted deny database and with useful header based tagging could be achieved as follows:
g_orbs_exception "127.0.0.*,12.34.56.*"
g_orbs_list name="mywhitedatabase.none" action="accept"
g_orbs_list name="relays.ordb.org" action="deny"
g_orbs_list name="relays.osirusoft.com" action="deny"
g_orbs_list name="bl.spamcop.net" action="stamp" stamp="spamcop, http://spamcop.net/w3m?action=checkblock&ip=||remoteip||"
eg 3 - To use the output of header based ORBS stamping in the SmiteCRC calculation the following could be used:
g_orbs_list name="relays.ordb.org" action="stamp" stamp="open relay"
g_orbs_list name="my.dialup.databse.none" action="stamp" stamp="dialup"
These entries have the following rules in filter.rul. If you used your own stamp text you would place appropriate entries in the local.rul file.
if(rexp_case("X-ORBS-Stamp", "open relay")) then
call spamdetect(4.0, "Sender's IP was on an open relay RBL")
endifif(rexp_case("X-ORBS-Stamp", "dialup")) then
call spamdetect(4.0, "Sender's IP was on a dialup RBL")
endifSome RBL lists return a numeric code to give extra meaning, for example 127.0.0.4 might mean an open relay, and 127.0.0.5 might mean the site has no postmaster address. You can specify multiple stamp messages using this format, stamp="4=Open Relay~5=No postmaster address~Default message goes here"
See Also: RBL's
g_orbs_rec - Log to record file if orbs deny action occurs
Log to record file if ORBS deny action occurs (can fill logs up).
g_orbs_report - List of IP's to check in orbs
Use this setting to test your own ip addresses, as soon as one is found in orbs you will be sent an email to alert you. The test is performed hourly. To test add 127.0.0.2 to the comma seperated list
g_orbs_service - Open Relay Blocking System RBL, service name (superceeded by g_orbs_list)
Set the name of the RBL service you want to use. A RBL service is a DNS database that has a record of all known spamming sites. If the server finds the connecting users IP address in this database all Email from their system is rejected. Also see the setting g_orbs_exception. Here are a few known RBL services, some charge and some are free!
- www.ordb.org
- inputs.orbs.org
g_orbs_system - Use system DNS lookups instead of SurgeMails for ORBS (not recommended)
If true use system DNS lookups instead of surgemails for orbs (not recommended).
g_orbs_testing - ORBS testing
If true ORBSlookups are recorded but not blocked.
g_orbs_timeout - Orbs timeout
ORBS lookup timeout in seconds (default=10). If the timeout is reached the message is accepted and the failure is logged to mail.log.
g_perflog_disable - Disable perflog logging
Completely disable the logging of historica performance data for the status graphs.
g_perflog_flush_interval - Flush interval
Interval in seconds to flush the performance log files to disk. Default is 3600 s (ie once per hour)
g_perflog_logall - Log all counters
Log all counters including the currently undisplayed counters. This is useful if in the future you suddenly think, Oh I would really like to see the historic information on one of the undisplayed counters - which would normally not have been logged to file.
g_perflog_lowres - Log in low resolution
Normally data is logged avery 10 seconds and 5 display scales are available hour, day, week, month and year. If this is set samples are taken every 5 minutes and 4 display scales are avbailable: day, week, month, year.
g_perflog_surgeonly - Only log surgemail counters
On Windows systems surgemail's performance logging will gather counters from surgemail and from the system "Perfmon" performance logging. This disables the collection of system counters.
g_pipelining - Show pipelining in ehlo response
Show pipelining in ehlo response - not recommended - has no behavior affect.
g_pop_add_size - Improves pop performance on nfs slightly
This renames inbox messages to include the size of the file so that an lstat call is not needed.
g_pop_blocksize - Size of packets to read POP messages (best left alone)
Size of packets to read POP messages (best left alone).
g_pop_delay - Send POP packets after waiting for more data to send
This setting replaced g_pop_nodelay, as the default has been changed. It was changed as this can improve performance.
g_pop_lock - Lock out duplicate POP users with the file system
Use this setting if you are sharing a file system between multiple mail servers. This will make the mail server lock the users files to prevent a second user of the same name logging in and reading mail from one of the other systems.
g_pop_max - Max total POP & IMAP users at any one time
This limits the channels that will be used at any one time for incoming POP and IMAP connections. The purpose of this setting is to prevent a sudden burst of users reading mail from using up all available channels. Generally setting this is a bad idea as there is a sensible default (dependent on the system resources available).
See FAQ section on session limits
g_pop_nolock - Allow concurrent POP logins (experimental)
Allows concurrent POP logins, very bad, use entirely at your own risk..
g_pop_port - Port to listen for POP connections (default 110)
Typically you won't need to change this, however you can specify an IP address to bind to or a list of alternate ports, eg: 10.3.2.3:110 or 110,6110 etc... By default the mail server listens to port 110 on all adapters/addresses. Use the keyword 'disabled' to disable this part of the SurgeMail service.
g_pop_secure_port - Port to listen for secure POP connections (default 995)
Dedicated secure port to listen on for POP connections. Use the keyword 'disabled' to disable this part of the SurgeMail service.
g_popfetch - Fetch incoming mail from another POP server
POPfetch will retrieve mail from POP accounts on another server and store it locally. The POP fetch interval can be set using g_popfetch_interval. The parameters for this setting are host(required), user(required), pass(required) or localuser(required).
eg:
g_popfetch host="netwin.co.nz" user="marijn" pass="secret" localuser="marijn@anydomain.com"Alternatively POPfetch is able to attempt local delivery based on headers. Delivery is attempted to "X-Rcpt-To:" with fallback of "To:" and "Cc:" headers. To enable this the local user needs to be defined as "*,userxxx". Fetched mail will be delivered as specified in the headers or if no valid user is identified in the header to the default user "userxxx".
g_popfetch_interval - Interval between POPfetch attempts
The interval (in seconds) between successive attempts to fetch mail from remote mailserver POP accounts (as per g_popfetch rules). (default is 5 minutes = 300)
g_popfetch_kick - POPfetch will try and open the link for 10 seconds, then retry, this should bring up ISDN lines.
If true then POPfetch will try and open the link for 10 seconds, then retry, this should bring up ISDN lines.
g_popfetch_nodup - Drop duplicate messages
Drop duplicate messages based on "Message-id:" header.
g_ppd_port - POPPassD port (default 106)
Port to listen for POPPassD connections. Typically you won't need to change this, however you can specify an IP address to bind to or a list of alternate ports, eg: 10.3.2.3:106 or 106,6106 etc... By default the mail server listens to port 106 on all adapters/addresses. Use the keyword 'disabled' to disable this part of the SurgeMail service.
g_proxy - Proxy mode (or mailhost)
This enables the SurgeMail proxy mode, using 'tohost=xxx' received from the authentication to determine real host for SMTP/POP connections. Any incoming SMTP, POP or IMAP connections will be passed on directly to the specified server. This allows you to split a domain over several separate systems. This method is outlined in general terms here.
To setup a proxy server system with 4 machines (2 proxy, 2 backend) use the following steps, lets assume your hosts are PROXY1, PROXY2, SERVER1, SERVER2
1) Set on the proxy servers in surgemail.ini g_proxy "true"
On the back end server use g_pop_nlock "true" (to avoid timing issues)
2) Configure your authent database to return 'tohost=xxx' for each user on your system, e.g. in nwauth
nwauth
set testuser1@test.com test tohost=SERVER1
set testuser2@test.com test tohost=SERVER2
lookup testuser1@test.com
+OK testuser1@test.com config 0 tohost=SERVER13) Configure your load balancing router to send users to PROXY1 & PROXY2, ...
4) When new users are added always define the 'tohost' setting to define which system they are added to as load increases you can add more backend or frontend servers as needed.
This is very similar to the 'mailhost' setting some systems use in LDAPAuth to translate mailhost to 'tohost' you would use: info_fields mailhost,tohost in ldapauth.ini
g_proxy_default - Default proxy host
Default host to forward to if 'tohost' is not defined in user database for this user.
g_proxy_to_gateways - Proxy pop/imap connections to matching gateway settings
This setting has no further documentation currently available
g_pstat_disable - Disable pstat per user accounting (for debugging)
Used for debugging only, do not play with this.
g_queue_limit - If on disk queue exceeds this block incoming mail
If you send email in faster than it can be sent, the queue grows forever until the server fails due to huge directories or insufficient disk space, this setting stops the incoming messages so you are alerted to the problem before it becomes critical. Note that this stops all incoming mail, including local deliveries. This is the number of items
Example: g_queue_limit "100000"
g_queue_max - Size of internal queue file cache
Size of internal mail queue file cache, range 500-3000.
g_quota - Disk quota for users in specified g_access_group
If the user is in the specified group they get the specified disk quota. This is applied if no quota is specified in the authent module.
See also: quota_default, quota_domain, user_sms_quota, user_list_quota, g_quota_warning_disable, g_quota_rcpt_disable, g_quota_try_later, g_quota_friends, g_quota_skip, g_quota_disable, g_share_quota, g_user_sms_quota, g_user_list_quota
g_quota_disable - Disable quota system
Disables quota processing completely
g_quota_friends - Count stored spam as part of quota
Count friends pending messages and spam store as part of the per user quota.
See also: quota_default, quota_domain, user_sms_quota, user_list_quota, g_quota_warning_disable, g_quota_rcpt_disable, g_quota_try_later, g_quota_skip, g_quota, g_quota_disable, g_share_quota, g_user_sms_quota, g_user_list_quota
g_quota_rcpt_disable - Disables quota check at rcpt stage
SurgeMail now does quota checking at rcpt stage (Quota checking used to be done after data arrived) This setting disables the quota checking at rcpt stage if the above causes problems (not intended for general use).
See also: quota_default, quota_domain, user_sms_quota, user_list_quota, g_quota_warning_disable, g_quota_try_later, g_quota_friends, g_quota_skip, g_quota, g_quota_disable, g_share_quota, g_user_sms_quota, g_user_list_quota
g_quota_skip - Skip quota checks for matching ip addresses
Skips the quota checking. Use this if you have a high priority robot (like your billing system) that must be able to deliver email to users (or students) even if the user is over quota.
See also: quota_default, quota_domain, user_sms_quota, user_list_quota, g_quota_warning_disable, g_quota_rcpt_disable, g_quota_try_later, g_quota_friends, g_quota, g_quota_disable, g_share_quota, g_user_sms_quota, g_user_list_quota
g_quota_try_later - Retry responses for over quota
Give 450 response if user is over quota so message will be resent.
See also: quota_default, quota_domain, user_sms_quota, user_list_quota, g_quota_warning_disable, g_quota_rcpt_disable, g_quota_friends, g_quota_skip, g_quota, g_quota_disable, g_share_quota, g_user_sms_quota, g_user_list_quota
g_quota_warning_disable - Disables the 80% quota warning message
Disables the 80% quota warning message.
See also: quota_default, quota_domain, user_sms_quota, user_list_quota, g_quota_rcpt_disable, g_quota_try_later, g_quota_friends, g_quota_skip, g_quota, g_quota_disable, g_share_quota, g_user_sms_quota, g_user_list_quota
g_rcpt_bang - Allow bang characters in addresses
Allow exclamation marks in addresses. ie '!'
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_rcpt_colon - Allow colon characters in addresses
Allow colon characters in addresses. ie ':'
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_rcpt_max - Max recipients per message, default is 1000
Max recipients per message, default is 1000, can only be lower than 1000.
See also: rcpt_msg, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_rcpt_max_in - Limit for recipients of untrusted channels, default g_rcpt_max
This limit is only applied to untrusted sessions (incoming mail)
See also: rcpt_msg, g_rcpt_max, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_rcpt_msg - Invalid recipient response
Response given for invalid recipient errors message is prefixed by email address..
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_rcpt_nodup - Ignore duplicate recipients to the same user
When enabled this prevents a message being delivered more than once to a single person, it's a fairly good setting to use and will get rid of some spam for people using fallback addresses.
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_rcpt_quote - Allow quote character(s) in addresses
By default quotes are blocked at the SMTP level, this is because some of the authent modules don't handle quotes in addresses so it's best not to let them through. There is no known reason for ever turning this setting on.
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout
g_received_name - Name shown in received headers
Name shown as received "by" in the received headers this defaults to server name but can be specified if required:
eg "myservername"
Received: from netwin.co.nz (unverified [10.0.0.5]) by myservername (SurgeMail 1.5f) with ESMTP id 1140619 for <marijn@netwin.co.nz>; Fri, 07 Nov 2003 10:25:59 +1300g_received_names - List of valid received names for incoming email
This list is used when processing vanish_bad_bounces, vanish_virus_bounces and vanish_any_bounce. It defines the valid received names to expect quoted in a properly formed bounce message for a message from this server/system.
g_received_skip - Don't write a received header for local trusted users
This setting can be used to hide sensitive local ip addresses from outgoing mail headers. This will make tracking abuse more difficult, we do not recommend using this setting generally.
g_received_skip_all - Skip local received header for messages that have non local recipients
Note that in the case of a message that is to a local and remote recipeient, it will skip the headers for both, even though the desire is to skip them for the remote recipient only. This not quite right, ideally one should skip this for outgoing only but since the header is added at delivery time we thought this was close enough.
g_recent_bypass - Bypass recent login failure checking
This allows you to disable recent login failure checking for certain IP addresses. Normally there up to a maximum of 9 login attempts are allowed per connection.
g_record_days - Period delivery logs are stored
The number of days SurgeMail message delivery logs are stored.
g_record_hash - Hash delivery logs
Message delivery logs may be stored in hashed format within g_record_path as <surgemail dir> \recYYMM\msgYYMMDD.rec
g_record_path - Path for mail delivery logs
Sets the path for the SurgeMail delivery logs. Delivery logs contain entries for mail received and delivered in a single file per day. See Searching the Log Files for more information.
g_redirect - Redirect messages to 'was' to the 'new' address
Specifies global redirection rule. These rules are applied to local and remote addresses so should be used with 'care', for domain based redirection use the redirect rules within a domain. An example rule would be: fred@xx.com --> bob@yy.com or *@xx.com --> joe@xx.com
Wild cards can be used and replaced, e.g.
g_redirect from="*@gadget.net" to="%1@gadget.com"
g_redirect from="*@*.gadget.com" to="%1-%2@gadget.com"Would make
bob@gadget.net --> bob@gadget.com
fred@cool.gadget.com --> fred-cool@gadget.comThese rules are processed 'before' the domain is identified, therefore you cannot use host_alias domain values in them. Use a domain redirect rule if this is required.
g_redirect_cc - Carbon Copy redirect message
Same as 'redirect' but the message is still delivered to the original address as well. For g_redirect_cc there are two special names defined "$localdomain$" and "$remotedomain$", which can be used in the 'was' paramater (requires SurgeMail 2.3).
g_redirect_from - Redirect message if from matches
Redirect a message to another address if the from matches.
g_redirect_from_cc - Carbon Copy redirect message if from matches
Redirect a copy of the message to another address if the from matches still delivering to the original address as well.
g_redirect_hide - Hide the redirection in the SMTP output
Hide the redirection in the SMTP output
g_redirect_iflocal - If local domain, then apply redirect
This is for doing fancy redirection where the rule is only applied if the domain of the destination is a local domain. For example to redirect all messages to postmaster at any local domain to one particular admin user.
Example: g_redirect_iflocal was="postmaster@*" to="john@main.domain"
See also: redirect, redirect_max, redirect_cc, redirect_hash, g_bounce_redirect, g_redirect, g_redirect_cc, g_redirect_from, g_redirect_from_cc, g_redirect_hide
g_relay_allow_from - Allow relaying for known from addresses
This setting allows users to send outgoing Email if their envelope 'from' address is a known local address. This is a very bad idea in general as spammers can do this too. So in general don't use this setting except as a lesser of two evils. It will be detected by some open relay checking systems and your site can then end up listed as an open relay. If this happens your Emails will be rejected by other peoples systems. e.g.
g_relay_allow_from "*@my.domain,*@second.domain,fred@third.domain"
g_relay_allow_ip - Allow relaying from these users
List the IP ranges of local users that you will allow to send 'OUTGOING' Email without using SMTP authentication, e.g. "127.0.0.1,10.0.*". In the past, mail servers used to permit this from any IP address, but since this was abused by 'spammers' all modern mail servers only allow this from known local IP addresses. Remote users should use 'smtp authentication' or login via POP protocol before sending Email, then SurgeMail will trust them. Do NOT set this to '*' If you do your system will be blocked as it will be assumed that spammers are using your system even if they are not!!!
g_relay_dom_and_ip - Relay based on domain and IP
Allow relaying if the domain in the from envelope and IP address both match.
g_relay_ifnot - Accept locally only if not from this ip
This lets you send all email to 'mx' destination, even if the account is local, unless it is coming from a known ip address range.
g_relay_message - Message to display to users who try to relay
Text string displayed to users who try and relay.
Default (blank) is: "Relaying blocked, read new mail, add <sender.ip> to forwarding or enable smtp authentication in your mail client"
g_relay_process - Relay process, e.g. testip.exe $WHOIP, return 1 to allow relaying, 0=deny
Allows you to run an external program to lookup an ip address and decide if it is one of your users who should be allowed to relay. This can be used when your users login via some type of shared system so the ip ranges are not known but you do have a way of checking if a user of yours is 'currently' connected on an ip address
Example: g_relay_process "c:/surgemail/testip.exe $WHOIP"
See also: fallback_relay, lookup_relay_on_from, g_auth_norelay, g_fallback_relay_if_exists, g_from_relay, g_from_relay_white, g_relay_allow_ip, g_relay_allow_from, g_relay_dom_and_ip, g_relay_window, g_relay_to, g_relay_to_user, g_relay_ifnot, g_relay_message, g_spf_rewrite_relay
g_relay_to - Relay to this domain from anyone
This setting allows mail from anyone to be relayed to the specified domain. The relaying is unconditional.
g_relay_to_user - Relay to specific user from anyone
This setting has no further documentation currently available
g_relay_window - Allow relaying after valid POP login
This sets the time after a valid POP login that you will allow a user on the same IP to send outgoing mail. In general it is safe to set this setting large and it can allow people using old mail clients (that do not know how to do SMTP authentication) to still send through your server without making your server an open relay.
g_rename_files - Files to apply virus renaming to
Only takes effect if g_virus_rename is checked. Default is: "*.exe,*.pif,*.bat,*.com,*.cmd,*.jav,*.vbs,*.scr,*.wsh"
g_responder_delay - Delay between responses to the same address.
This setting has no further documentation currently available
g_responder_safer - Only respond if the sender can be verified in some way (spf/domainkeys)
This setting makes the server less likely to be black listed by accidentally responding to a forged email.
g_restart - Auto restart server
If turned on Swatch (a spawned second process) checks every 30 seconds to see if the server is still running. If it isn't running but it's pid file still exists (so if it died) this second process restarts the missing server and sends the manager account an Email reporting the fault.
For this to work on NT you need to set Dr Watson NOT to show visual notification of faults:
This sets Dr Watson to be the default debugger) c:/> drwtsn32 /i This brings up the Dr Watson settings, un-tick "Visual Notification" c:/> drwtsn32Generally this setting is not needed and could be left off, but if an odd problem should develop, this setting can give you peace of mind for a few days while you wait for a problem resolution from NetWin.
g_retry_bounces - Max hours to keep trying to bounce messages
Max hours to keep trying to deliver a bounce the default is 48hrs
g_retry_dns - Hours to keep trying if dns response suggested invalid domain name, default 0
By default, if the DNS server says a domain doesn't exist, the message is immediately bounced so the sending user can take action. In some rare cases this will occur with a valid domain name because the actual DNS of the domain you are sending to is temporarily down. In this situation making SurgeMail retry for 1 hour can prevent these false bounces. I don't recommend this setting as mostly the DNS response and cache etc is very very reliable because SurgeMail keeps a local cache of DNS lookups that worked on disk. So for a failure like this to occur it must be the first time the server has EVER looked up the domain, so the odds are extremely remote. Delaying a useful response to the user for 1 hour just for this remote chance is not wise in my opinion.
Example: g_retry_dns "1"
See also: g_dns_paranoid, g_dns_match_msg, g_dns_noptr, g_dns_noptr_msg, g_dns_nocache, g_dns_cache_size, g_dns_system, g_dns_host, g_dns_nlookup, g_dns_require, g_dns_translate, g_dns_old, g_dns_new, g_spf_dns_timeout
g_retry_limit - Max hours to keep trying to deliver messages
Every hour the mail server will attempt to deliver any messages that fail for a reason that may be a temporary fault (for example the destination mail server doesn't respond). This setting limits how long these retries continue for. The default is 48 hours (2 days).
g_retry_minutes - Time between attempted retries
Time in minutes that SurgeMail will try and resend a message that has failed to be delivered.
(default = 60 minutes).g_retry_rule - Retry rules overriding g_retry_limit
Rules that allow you to specify the retry_limit in hours on a per destination domain basis.
Example:
g_retry_rule domain="test.com" hours="48"That will make it keep retrying to send to the domain test.com for 48 hours.
g_retry_warn - Send user a warning if first send fails
I like this setting myself but it can confuse users as the first send attempt will often fail and the user will mis read the bounce and think it's failed completely. It does mean when a message is urgent the user gets told right away, instead of 2 days later, that there is a problem sending the message so for a business it's a nice setting to enable.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_retry_warn_n - Send user a warning if nth send fails
Similar to the above setting but this one reduces the false warnings as messasges often fail on the first attempt
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_route - Wildcard route mail to specified server
Route messages matching particular wildcard "from address" and wildcard "to address" to specified server. This is not a gatweay rule and is only applied to mail that has already been accepted via SMTP authentication, relaying rules or gateway rules.
This would typically be used to route all mail for a particular user on a domain to another mailserver or to route all mail from a local domain through another server:
Case 1: Route mail for one user to another server
g_route from="*@*" to="user@localdomain.com" dest="1.2.3.4" user="" pass=""
Case 2: Route all mail from local domain through other server
g_route from="*@localdomain.com" to="*" dest="1.2.3.4" user="" pass=""
g_route_except gets applied allowing you to prevent mail coming in from certain IP addresses to be routed.
g_route_by_tohost - Route based on authent 'tohost' field
Use routing to a particular server based on 'tohost' setting in authentication database. This is particularly useful if you have users spread over several physical locations and want to be able to route mail for different users to particular servers.
g_route_except - IP exception to g_route and g_route_by_tohost
IP exception to g_route and g_route_by_tohost.
g_sample_get - Sample account to check if deliveries work
The idea is to create several accounts on various public mail servers. Then send a test message using a mailing list or g_redirect rule to these test accounts, then use the command tellmail sample_get CODE DELETE to check if the messages have arrived. The first paramter of tellmail sample_get is a code it expects to find in the message headers (or subject) and the second paramter should be the keyword 'delete' if you want it to delete the sample messages.
g_sample_show - Headers to show from sample messages
Typicall you will list headers that are added by spam filters
g_scan_action - Converts return value from g_scan_cmd to action on email
Converts return value from g_scan_cmd, action=drop,accept,bounce.
g_scan_cmd - Run command on message, and return integer
Run command on message, and return integer, see g_scan_action.
g_sched_utoken_timeout - Timeout for sched utokens in minutes
Timeout for sched utokens in minutes.
g_send_backoff - Backoff slow hosts
Seconds to leave slow responding host alone (default 900).
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_body_end_retry - Try again if connection fails after entire body sent
This setting will tend to result in 'duplicate' messages being received, so should not be used, but strictly speaking it is valid to retry in this situation, the trouble is the receiving mail server 'may' have a real copy of the message so may deliver it even though the connection was dropped.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_body_noretry - Don't try and resend if failure during body send
By default SurgeMail retries to send messages if the tcp connection is lost during the body send part of sending an email message. In rare situations this may cause problems, for example while sending a large file if the receiving software is faulty and is dieing rather than responding with 'don't try again' error code. This behaviour was reversed before version 2.0h (e.g. it never retried)
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_delay - Wait this many seconds after sending each item.
This is a simple throttle to limit sending speed to any single domain, a value of 2 seconds is probably reasonable. In general you would also set G_SEND_MAX_PERDOM to 1.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_helo - Domain to use for all outgoing SMTP helo commands
Fully qualified domain to use for all outgoing SMTP helo commands.
See also: g_ban_helo, g_gateway_helo, g_helo_optional, g_send_helo_from, g_verify_helo
g_send_helo_from - Use the sending domain for the helo command
If the senders domain name (in return path envelope) is a valid local domain, then it is used in the 'helo' command.
Not generally recommended. The correct use of the helo is to identify the sending machine, not the domain, so although this makes the headers look pretty it doesn't make them more correct in my opinion.
See also: g_ban_helo, g_gateway_helo, g_helo_optional, g_send_helo, g_verify_helo
g_send_lines - Send single line packets
Send messages in single line packets, slow! (for debugging)
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_max - Max concurrent sending sessions
Maximum concurrent outgoing SMTP connections . You should not have to change this. The default is 100.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_max_perdom - Max concurrent sending sessions to a single domain
Maximum concurrent outgoing SMTP connections to a single domain. The default is 6.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_nolimit - Don't apply g_max_perdom limit when sending to this domain
Use this on incomng mx severs for the local domain so it can use lots of channels to send the data through.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_noskipslow - Don't skip slow hosts
Normally surgemail remembers hosts that are slow to open, fail and doesn't retry for 60 minutes.
g_send_onpopfetch - Only send outgoing while doing a POPfetch
Only send outgoing while doing a POPfetch (For dialup use).
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_open_timeout - SMTP link open timeout
Timeout, in seconds when opening an SMTP link.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_retry_552 - Retry on 552 responses (typically quota exceeded)
Some faulty hosts return a 552 error when a user is over quota, this means that by the RFC SurgeMail must not try again to deliver the message. However this is clearly not a permanent error and so it's often wise to retry in this situation, This setting makes SurgeMail attempt retries when faced with this odd response.
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_rewrite - Rewrite envelope recipient at send stage, does not change destination server
This rewrites the recipient envelope, you can use wild cards, e.g. *@this.domain %1@another.domain, to rewrite 'from' addresses use g_from_rewrite
g_send_speed - max outbound bandwidth
Bytes per second to limit each outgoing channel to. eg: 10k
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_delay, g_send_timeout, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_timeout - Send timeout
Timeout, in seconds when sending mail, default is 540 (9 minutes)
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_tolimit, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_send_tolimit - Limit speed to send to one or more domains.
Some large providers will assume you are a spammer if you send too many messagse in an hour. If you have a large mailing list it's easy to break these limits, in which case some rules like this can prevent this problem.
Example: g_send_tolimit domain="hotmail.com,*hotmail.com" perhour="60"
See also: user_status_send, user_send_max, g_footer_send, g_footer_sendonly, g_send_helo, g_send_helo_from, g_send_backoff, g_send_lines, g_send_max, g_send_max_perdom, g_send_nolimit, g_send_onpopfetch, g_send_retry_552, g_send_rewrite, g_send_noskipslow, g_send_speed, g_send_delay, g_send_timeout, g_send_open_timeout, g_send_body_noretry, g_send_body_end_retry, g_user_status_send, g_user_send_max, g_user_send_rule
g_server_name - Wildcard "SERVER_NAME" translation for domain identification
The vdomain a user connects on is normally identified automatically for "user account self management" and for "webmail". In the event that the domain name is not the same as the host name (eg hostname = mail.domain.com, domainname = domain.com) the WebMail web server can automatically translate the SERVER_NAME variable.
This setting specifies a wild card list of URLs 'URL' with associated translated host name for "SERVER_NAME". If the URL matches then SERVER_NAME is set to the second part of this setting 'name'. eg: to host the domains domain.com and mail.domain.com on host mail.domain.com:
g_server_name url="*.domain.com" name="domain.com"
Note: If your server name is not the same as your domain name also check the per domain setting URL_host.
g_server_stamp - Replaces SurgeMail and version string in "Received" headers
Replaces SurgeMail and version string in Received headers of process mail
g_share_home - Allow sharing of home directory
This allows sharing of the home directory in the unlikely situation that you might want to run separate surgemail processes. eg one process to cope with SMTP and another to cope with POP access.
g_share_mail - Allow sharing of mail directory
Set true if mail area is shared (by nfs or other mechanism)
g_share_quota - Do quota on disk (e.g. when using nfs shared spool)
Normally SurgeMail keeps track of quota for all users in memory, this is efficient, but means if your are using a shared mail spool the quota figures are completely wrong, so use this setting to make surgemail keep track of quota's on disk, it increases disk load a bit of course but not too much.
g_smite_all - Add smite headers to all messages passing through server
Normally SmiteSpam headers are only added for locally delivered messages. This setting to all messages passing through this server.
g_smite_gateway - Add smite headers to gatewayed messages
Normally SmiteSpam headers are only added for locally delivered messages. This setting adds the headers for gatewayed messages too. This also adds headers to messages that are redirected by forward rules as well.
g_smite_level - Smite level to discard message
If SmiteSpam gives a message a "smite score" above this, throw it awayl. This setting is best never used. If used it should be set to '1 or 2'. A value of 1 = "has been reported", 2 = "has been reported multiple times". If smite match score is above this drop message. This is applied when the user downloads the email not at delivery time. What you probably want is 'g_spam_bounce' described elsewhere on this page.
g_smite_skip - Skip smitecrc processing for messages from these domains
This will skip running SmiteCRC for messages whose from address matches these domains. This is the mail from envelope header NOT the from header in the message (you can check the return path header in the message to check what you need to add for this setting).
Note this is a wildcard field so to match any mail claiming to be from safedomain.com you would have to set:
g_smite_skip "*@safedomain.com"
g_smite_skip_auth - Skip spam scanner if user logged in
Skips spam checks and spam header generation for any authenticated local user.
g_smite_skip_ip - Skip smite based on sender IP
Skip smite scanner if sender IP matches this wild card list.
g_smite_skip_to - Skip smite based on <to>
Skip smite scanner if to matches this wild card to <address>.
g_smite_tag - Tag message if in SmiteSpam database
If set to true will tag messages already in the SmiteSpam database. A value of 1 = "has been reported", 2 = "has been reported multiple times".
g_sms_gateway - Address and port of your SMS gateway
This is the ip and port of an 'email to sms gateway'. The gateway should accept SMTP messages on this port and convert the email into an sms message then deliver to the phone number in the 'to' address. SMSGate is our 'email to sms gateway' and is FREE with SurgeMail. Setting user_sms to "true" for a domain allows users to specify a phone number (or email address) and rules for when to notify them.
g_sms_gateway_force - Force sms notifications to go to g_sms_gateway
If a user sets their sms number to an email address, perhaps to make use of an existing gateway, then surgemail will send the message to the domain in that address. If you set this you can force the email to go to g_sms_gateway. NOTE: It is possible to configure SMSGate with 'send_mode smtp', 'recv_mode none' and no GSM modem. In this setup it simply reformats messages passing them on to the configured smtp_outserver for delivery as email messages.
g_sms_gateway_msgbytes - Maximum amount of message to send to g_sms_gatway (bytes)
Defines the maximum number of bytes of 'body' text to send to the g_sms_gateway. All headers are sent, then the defined number of bytes of 'body' text. Defaults to 160. May be set larger than the default if you have a lot of html messages or multipart html and text messages. Should not be set too large as there is no point sending binary attachments and the like to an sms gateway.
g_smtp_big - Slow down incoming SMTP reads to get bigger packets (experimental)
This setting tries to prevent thrashing by making the server slow down the speed it reads data in an attempt to get larger packets. This seemed to have no affect when I tested it, but play with it if you want, It is only intended to be useful when you have hundreds of incoming connections all very slowly sending in data, and the server is short of CPU.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_fast_bounce
g_smtp_bounce_nslow - Number of handles to use for doing slow rejections of smtp connections
If external servers are over loading your server so much that it ends up in a cpu loop rejecting connections then increaseing this might help. But beware your system must not run out of file handles so don't set it too large, The default is 100
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_cmd_timeout, g_smtp_data_timeout
g_smtp_cmd_timeout - SMTP command timeout
Seconds to wait after getting a message for next command (workaround for sendmail bug)
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_data_timeout
g_smtp_cram_enable - Enable CRAM-MD5 authentication (requires nwauth 4.0h or greater)
Please note that CRAM-MD5 does have security implications, specifically it means that the local users password must be stored in a semi reversable state in the authent database. Also you must be using the new version of the NWAuth module.
See also: authent_info_grp, g_acctlog_authonly, g_allow_user_authent_field_get, g_allow_user_authent_field_set, g_authent_always, g_authent_allow_badascii, g_authent_prefix_sep, g_authent_process, g_authent_cachelife, g_authent_cachebad, g_authent_cachesize, g_authent_domain, g_authent_number, g_authent_info, g_authent_ip, g_authent_path_broken, g_authent_single, g_authent_strip_domain, g_authent_restart, g_authent_logall, g_authent_fwdfile, g_authent_timeout, g_authent_last_login, g_auth_hide, g_auth_norelay, g_auth_skipgateway, g_mirror_nwauth, g_gateway_auth, g_smite_skip_auth, g_smtp_portauth, g_smtp_etrn_auth, g_smtp_noauth, g_spam_check_auth, g_xauthuser_hide
g_smtp_data_timeout - SMTP data timeout
Seconds to wait for SMTP data input.
See also: rcpt_msg, g_rcpt_max, g_rcpt_max_in, g_rcpt_msg, g_rcpt_bang, g_rcpt_colon, g_rcpt_quote, g_rcpt_nodup, g_smtp_bounce_nslow, g_smtp_cmd_timeout
g_smtp_delay_stamp - Stamp message if sender doesn't wait for welcome
If true then if any smtp commands arrive before the 'helo' greeting is sent then a header is added to messages which will result in a higher spam score.
See also: g_gateway_allow, g_smtp_welcome_delay
g_smtp_etrn_auth - etrn if authenticatd
Only do etrn processing if user is authenticated.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_fast_bounce - Reject bad connections immediately
Normally SurgeMail waits 1-10 seconds before rejecting a bad connection (rbl/limits,...), this reduces cpu usage and prevents some DOS attacks, this setting disables this behaviour.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big
g_smtp_help_disable - disable smtp help command
Disable SMTP help command (minor security percaution).
g_smtp_log_protocol - Log SMTP protocol
If enabled, the SMTP protocol is logged to the mail.log file as "smtp: In" and "smtp: Out" entries.
g_smtp_log_size - Size of smtp.log file
This sets the smtp.log file size, default is 2mb
See also: g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_max - Max total incoming SMTP connections
This limits the channels that will be used at any one time for incoming SMTP connections. The purpose of this setting is to prevent a sudden burst of spam from using up all available channels. Generally you do not need to change this. (Default = 250). Use the related setting g_smtp_max_reason to over-write the detailed error if you don't want spammers to know what your limits are set to.
See also: g_smtp_log_size, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_max_nolimit - IP based exceptions to g_smtp_max
This lets you specify IP based exceptions to g_smtp_max, so if you need a certain IP to open up many connections you would add that IP here.
eg. g_smtp_max_nolimit "10.0.0.50"
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_max_reason - Reason to give to user if g_smtp_max is exceeded
This is most useful when the host in question is being used for the wrong purpose (incoming when it's intended for outgoing etc), or simply to advise the user of a potential solution
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_maxbad - Max bad SMTP commands
The maximum number of bad commands accepted per session before SurgeMail will drop the connection.
Example: g_smtp_maxbad "10"
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_no_brackets - Allow from/rcpt without angle brackets
Some faulty mail clients forget to put the brackets <> around the recipient, this setting allows such faulty behavior. Not generally recommended.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_big, g_smtp_fast_bounce
g_smtp_noauth - Accept incoming SMTP from these IPs (other IPs allowed if authenticated), default is *
Mail sent from other IP addresses is only accepted if user is authenticated. Typically used if your server is behind a firewall of some kind and should only allow incoming email from a particular IP address. Users will be able to send as from any IP address if they use smtp authentication.
See also: disable_smtp_after, old_smtphost, old_smtphost_skip, smtp_welcome, surgeplus_smtp_server_name, g_disable_smtp_after, g_dbabble_smtp_port, g_dbabble_smtp_prefix, g_deny_smtp, g_manager_smtp, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout, g_smtp_delay_stamp, g_smtp_welcome_delay, g_smtp_log_protocol, g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_help_disable, g_smtp_cram_enable, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce, g_smtp_thread, g_verify_smtp, g_surgeplus_smtp_server_name
g_smtp_port - Port to listen for SMTP connections (default 25)
Typically you won't need to change this however you can specify an IP address to bind to or a list of alternate ports, eg: 10.3.2.3:25 or 110,2110 etc... By default the mail server listens to port 25 on all adapters/addresses. Use the keyword 'disabled' to disable this part of the SurgeMail service.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_portauth - SMTP ports which require smtp authentication, typically 587
It is recommended (by some) that users send email to port 587, and it requires smtp authentication, and port 25 be blocked from client ip addresses to prevent viruses etc using email servers. Be sure to add ,587 to the g_smtp_port setting too!
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_secure_port - Port to listen for secure SMTP connections (default 465)
Port to listen on for dedicated SSL SMTP connections.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_thread - Use seperate thread for incoming SMTP connections
This makes the server run a seperate thread just to process incoming smtp connections, this can help on a busy system to stop a huge load of smtp connections clogging up the pop/imap connection processing, it is rarely needed.
See also: disable_smtp_after, old_smtphost, old_smtphost_skip, smtp_welcome, surgeplus_smtp_server_name, g_disable_smtp_after, g_dbabble_smtp_port, g_dbabble_smtp_prefix, g_deny_smtp, g_manager_smtp, g_smtp_bounce_nslow, g_smtp_cmd_timeout, g_smtp_data_timeout, g_smtp_delay_stamp, g_smtp_welcome_delay, g_smtp_log_protocol, g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_vrfy_msg, g_smtp_etrn_auth, g_smtp_help_disable, g_smtp_cram_enable, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce, g_smtp_noauth, g_verify_smtp, g_surgeplus_smtp_server_name
g_smtp_vrfy_msg - VRFY response
Change Response to VRFY, e.g. 252 Not telling.
See also: g_smtp_log_size, g_smtp_max, g_smtp_max_reason, g_smtp_max_nolimit, g_smtp_maxbad, g_smtp_port, g_smtp_portauth, g_smtp_secure_port, g_smtp_etrn_auth, g_smtp_no_brackets, g_smtp_big, g_smtp_fast_bounce
g_smtp_welcome_delay - delays welcome message
Syntax: g_smtp_welcome_delay "seconds"
This delays the welcome message sent by SurgeMail to a connecting server. If the server sends data to SurgeMail during this waiting time SurgeMail will drop their connection. The theory is that any well behaved server will wait for prompts and check them, but a lot of spamming software never takes any notice of prompts/responses and sends blindly. We believe a value of 1-3 seconds is ideal. You can also exempt ip's from this setting by using g_spam_allow "ip". Settings too high will cause real mail to be lost.
Examples:
g_smtp_welcome_delay "3"
g_spam_allow "127.0.0.1"So above, delay giving the welcome message for 3 seconds, anyone that sends data in that 3 seconds will be dropped, but anything connecting from 127.0.0.1 will be able to send immediately (you should make sure webmail is exempt).
See also: g_gateway_allow, g_smtp_delay_stamp
g_spam_allow - IP wild card of sites to exempt from spam limits
Typically use this to allow known mailing list servers that use your system to send messages in without being tarpitted. e.g. "127.0.0.1,local.ip.number". This same setting is an exception to the other spam rules.
g_spam_allow_disable - Disable allow bounce messages
Normally when SurgeMail detects an SPF failure it will give the sending an opportunity to send an email to a special address, If the sender does this then their IP address is permitted in future, this saves a lot of hassle generally, in rare situations you may not want this system, this setting will just simply bounce the message instead.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spam_allow_known - Unblock IP address if we have received messages from it for 3 days (so it's not a transient spammer)
This setting makes the SPF strict settings much softer, basically it says any IP address we've known about for 3 days, is considered safe. This will still stop most spammers, particularly when used in combination with RBL/ORBS lists which will block the 'repeat' offenders.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spam_allow_msg - Template for unblock messages, use ||reason|| and ||allow|| and maybe a url
This lets you tailor the message given to incoming messages that fail the SPF checks.
Example: g_spam_allow_msg "SPF ||reason||, please send to ||allow|| then resend original email."
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spam_allow_rbl - Give unblock message to RBL/ORBS bounces too
This setting extends the 'allow' email system used by SPF to the RBL style of failures. This makes it much safer to use RBL lists is block mode instead of stamping mode.
See also: g_surbl
g_spam_allow_recent - Exempt recent POP from spam limits
Skip spam rules if recent POP IP number (see g_relay_window).
g_spam_aspam - Aspam rating
Scale for Aspam default is 1.0. Valid range is zero to two.
The aspam matching based on it's database of known spam and non spam produces a score in the range -5 --> 5. Tthe g_spam_aspam setting lets you 'scale' this score to increase/decrease the importance of the aspam rating. The result is then applied (added to) the spamdetect header.
g_spam_autotrain - Autotrain "good" filter
Auto train spam filter good messages based on first 1,000 outgoing emails.
g_spam_block - Block spam (as decided by spf etc), if not set then user or domain can set
This setting has no further documentation currently available
g_spam_block_gateway - Block spam gatewayed messages too
Use this setting on incoming mail servers or servers that relay to servers that implement SPF. Without this SPF blocking will not work as the back end server cannot perform the SPF checks/blocking.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spam_block_msg - Template for spf blocked message if allow is disabled
This error is given for SPF failures when the allow system is disabled. You are probably looking for the setting g_spam_allow_msg, as it is the one that is normally used when a user is 'blocked' by spf.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spam_body - Add SpamDetect header in body
If spamdetect score is above this, add spamdetect header at top of message body (in addition to the header). This allows mail clients that are not able to filter mail based on headers to filter out spam email. This can be set on a per user basis too. A value of 3 or 4 would be reasonable. The only real reason for this setting is some common mail clients are unable to scan non standard headers so cannot automatically file spam in a folder unless this is used. My recommendation is for such users to use the web interface to set actions individually.
g_spam_body_url - Text part of info to add to body, usually a url to your site
On this page you should explain to your users why this tag was added to their message, and how they can adjust their spam settings etc.
g_spam_bounce - Bounce local delivery based on spamdetect score
If spamdetect score (number of '*'s) is above this, bounce message if local delivery. e.g. 7 or 8 would be reasonable, 3 would be very strict, and less than 3 would certainly bounce real emails. I recommend you don't set this below 5.
g_spam_bounce_all - Bounce local and remote delivery based on spamdetect score
If spamdetect score (number of '*'s) is above this, bounce message, this applies to all messages regardless of user settings. e.g. 7 or 8 would be reasonable, 3 would be very strict, and less than 3 would certainly bounce real emails. I recommend you don't set this below 5. This rule is applied as soon as the message is submitted, user spam settings do not override it.
g_spam_bounce_text - Error text when message is bounced due to g_spam_bounce setting
As per description. Default is: "554 Failure Message looks like spam, sorry not wanted here q=311", where q is the message queue id.
g_spam_bounce_trusted - If spamdetect score is above this, bounce message if trusted (spam_allow or authenticated)
Normally trusted users (spam_allow or smtp authenticated users) are never bounced due to spam content, this setting forces those users to also be checked for spam content.
g_spam_catcher - Spam catcher addresses
Addresses on web pages that shouldn't get any email (robot bait), only for use with Aspam.
Any email going to the specified address will be sent to the isspam address for processing and the message will also be dropped. If the message has multiple rctp's and some are valid users, but one matches the catcher address, it is not delivered to anyone. If you need to enter a lot of spam catcher addresses then the best way is to just setup a single spam catcher address and then use g_redirect to redirect other addresses to the spam catcher address.eg
g_spam_catcher "johnsmith@mydomain.com"g_spam_char - Character to use instead of '*' for smitespam headers (best left alone if possible)
Changing this will cause no end of problems, so only do this when initially installing SurgeMail
g_spam_check_auth - Enable spam rules for authenticated users
Normally authenticated users are exempt from spam rules when sending mail. This enables all spam checking rules for authenticated users.
g_spam_content_disable - Disable aspam_content.txt rules
The file aspam_content.txt is fetched from netwinsite and used to identify certain common spam messages based on content. Each line in the file gives a list of words or phrases, if most of the words are found, then the rule matches. You can add your own rules to aspam_content_local.txt. In a message that matches a rule you will see in the spamdetect header, Content: cid=NNN cid=NNN, you can then match the NNN with the unique id of each rule in aspam_content.txt
See also: g_aspam_headers, g_spam_aspam
g_spam_grey - Enable greylisting for spf instead of 'allow' rejections, messages are bounced with 451 from unknown ip addresses for 55 minutes
The grey listing mechanism relies on the principle that spammers are not using real mail servers but using dumb robots that won't 'retry'. So if all incoming messages are asked to 'retry' then the spam will not be received but the non spam will get in eventually. This does create a delay on all incoming mail, and may stop some stupid mail servers from successfully delivering. I would tend not to use this setting myself.
g_spam_grey_bounce - Bounce if message was allowed due to grey listing, and spam score is above this, default 4
Since messages which are allowed in due to grey listing generally can't accept friends bounces (as the sender is unverified) it's important to bounce them with an allow message instead if they look like spam
See also: g_spam_grey, g_spam_grey_dflt, g_spam_grey_dflt_bad, g_spam_grey_size
g_spam_grey_dflt - Enable greylisting for spf default accept events (recommended for block or strict)
This settings is quite useful, if a message is going to be accepted due to the spf default rule (so there was no real spf record), then this comes into play. If the message is not from a trusted person, or a domain that we have previously checked using grey listings. Then the message is bounced. If the sender then tries again to send the same message (from/to pair) within a few hours, but not within 1 minute, then that ip address is marked as 'good' and future messages from them are accepted.
See also: g_spam_grey, g_spam_grey_dflt_bad, g_spam_grey_size, g_spam_grey_bounce
g_spam_grey_dflt_bad - Enable greylisting instead of allow in some cases (recommended for block or strict)
This setting enables grey listing for spf default failure events only, and only if it's the first message from that ip address if more arrive before the grey listing succeeds then allow bounces are sent instead
See also: g_spam_grey, g_spam_grey_dflt, g_spam_grey_size, g_spam_grey_bounce
g_spam_grey_size - Size of grey listing table, default is 3000
On busy servers set this to a larger figure, e.g. 9000 so it can remember more grey listing events
See also: g_spam_grey, g_spam_grey_dflt, g_spam_grey_dflt_bad, g_spam_grey_bounce
g_spam_header_trust_ip - List of IP addresses from which to trust/accept existing X-SpamDetect headers in emails
Use this setting to specify the filter machines which perform spam scanning for this machine. Use this on the filter machine, to specify itself so that mailing list messages do not get scanning/tagged twice. Ensure your users are sending messages via the filter machine.
g_spam_hold_keep - Spam hold timeout
How many days to store users spam hold messages before deleting them.
Default is 14 days.
eg. g_spam_hold "14"g_spam_info - Info line explaning aspam system
Info line and url to explain aspam system.
g_spam_info_hide - Remove x-spamdetect-info header line
Removes the x-spamdetect-info header line.
g_spam_internal - Enable internal Aspam spam processing system
Enable new 'internal' spam processing system, note this disables SmiteCRC too!
g_spam_isspam_kind - Allow isspam from recent pop, gateway to etc
Allow ASPAM training messages to (isspam) from any trusted source (e.g. any source that would be allowed to relay/send outgoing email). This setting is recommended.
g_spam_notrain - Disable isspam and notspam addresses
Disable isspam and notspam addresses for user training.
g_spam_notspam - Spam collection address
Address that non authenticated users can send non spam to.
Example: g_spam_notspam "notspam@domain.com"
g_spam_noupdate - Disable aspam updates
Disable fetch of aspam filter rules etc from netwinsite.
g_spam_poly - Scale for poly word matching
Scale for poly word matching, default is 0.1, Valid range is zero to two, Use 1.0 to enable.
g_spam_poly_disable - Disable poly code.
Disables the poly statistical scoring feature which is part of Aspam. Poly tries to analyze the frequency of word combinations in spam and not spam to identify if a message is likely to be spam or not. We don't consider the poly system to be very useful, it has two faults, it's behaviour is not 'understandable' and it is 'content based', SPF is a much superior system!
g_spam_private - Enable private email addresses for users to avoid spam
Note: The user will define these settings, after turning on this global setting the user can use the Web Self administration interface, press the 'Spam' button and the private email address is defined on that page.
This setting adds the ability for each user to create a private email address to bypass SPF/ Spam filters. The user would then typically increase the spam settings for their non private account to 'friends mode' and enable SPF. So only known friends will be able to contact them via the old address.
This allows the user to live 'spam free' without the risk of blocking email from real people.
The user must be careful with their new private address, it should only be used with humans, when entering an address in a web form or mailing list a special variant should be used e.g. user--from-WEBDOMAINNAME@users.domain
The user defines their private address, in the form user--PRIVATE@domain.com, e.g. if the users public address is joe@cool.com, and the user defines a private extension of "juggle" then the private address would be:
joe--juggle@cool.com
Email addressed to joe--juggle@cool.com is delivered without SPF or SPAM filtering / tagging.
In addition the user can enable 'from' matching which must look like this: username--KEYWORD-STRING@cool.com, the user specifies a keyword e.g. "match". Then anything addressed to the user in this form:
joe--match-STRING@cool.com
Will only be delivered if 'STRING' is found in the 'from' envelope address, otherwise it will bounce. So when entering an email address in a web page called "toys.com" the user would enter:
joe--match-toys@cool.com
Any -- extension that is not recognized will return a bounce suggesting they remove the extension and try again.
g_spam_subject - Modify message subject line based on spam rating
If spamdetect score is above this add spam rating Spam:**** to subject.
g_spam_subject_gateway - Modify message subject lime based on spam rating for gatewayed messages
If true then spam_subject setting applies to gatewayed messages too
g_spam_subject_word - Allow arbitrary modification of message subject line
This is a string that is prefixed to the subject of incoming mail caught by g_spam_subject. You can use ||score|| and ||stars|| which will contain the actual spam rating. Good examples might be: "[SPAM]" or "SPAM(||score||), "
g_spam_url - Scale for url word matching
Scale for URL word matching, default is 0.3, Valid range is zero to two (recommend 1.0)
g_spam_user_max - Max messages for authenticated users
Max messages an authenticated user can send per 30 minutes, eg: 5000
g_spam_userconfig - Enable per user spam settings
Allow users to opt in / out of specific anti spam features. If this is enabled this will add a "Spam" button on the users account self management pages.
The most useful antispam feature is that user's mail that is suspected spam, can be stored on the server so that these messages do not need to be downloaded to your normail email client over what could well be a low bandwidth connection.
g_spam_vanish - Vanish local delivery based on spamdetect score
If spamdetect score (number of '*'s) is above this, vanish message if local delivery. eg: 12 would be reasonable.
g_spam_vanish_all - Vanish local and remote delivery based on spamdetect score
If spamdetect score (number of '*'s) is above this, drop message, applies to all messages regardless of user settings. e.g. 14. This rule is applied as soon as the message is submitted, user spam settings do not override it.
g_spamdetect_always - Always add spamdetect header
Always show spamdetect header even for low and negative scores.
g_spawn_log - If true the spawns are logged to lib_spawn.log
Useful for finding obscure problems with spawned modules of various kinds, webmail, nwauth, virus checkers etc.
g_spf_baddns_skip - If spf dns failure then allow message through (instead of giving retry error)
Normally on a DNS failure SPF should give a 'retry' message, this is because spammers often have faulty DNS servers so that SPF checks always fail for their domain, so letting the message through will let some spam into your system. But in some situations the normal behavior might loose you real email so then using this setting at least until your dns problems are resolved might be wise.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spflog_enable
g_spf_default - (strict only) Default spf record if none found default 'mx/16 a ptr:%{d2} -all'
The example shown isn't entirely true, we adjust the 'd2' depending on the domain, so it's usually unwise to change this.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_default_noblock - (strict only) Only stamp headers if default spf record fails when no real spf header
This setting makes blocking occur only for REAL spf records, not for the default one applied to domains that have no SPF record defined.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_dns_timeout - Seconds to wait for dns lookups for spf, best not to change
Generally a ten or twenty second timeout is reasonable. Adjusting the default is probably not necessary.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_domain - Domain for SPF rewrite and allow messages (defaults to first domain on server)
When SurgeMail relays/forwards a message the 'from' address is rewritten (g_spf_rewrite should be true). The new address is 'from' your domain and this setting tells surgemail which local domain to use for these from addresses.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_mode - Sender Permitted From
See http://netwinsite.com/spf.htm for details.
g_spf_nocache - Disable SPF cache
There is a small cache used for SPF results, This setting disables it.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_norewrite - Exceptions to rewrite rule, e.g. *@my.domain,bob@this.domain
Where you allow users to send through your server you may want to stop rewriting for their domains so that their from address is not munged. Local domains are automatically excempt from 'rewriting'.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_rev_skip - Skip SPF checks if reverse ip name matches in this list, e.g. *.yahoo.com
Where you identify a domain that does not support SPF and is often used in a manner which breaks SPF default rules this setting can safely allow the problem domain. This setting is probably not needed now most large mail systems are using SPF.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_rewrite - Rewrite 'from' envelope in redirected mail (SRS)
When messages are redircted/forwarded to another server from you server, the 'from' address of the existing message envelope will no longer obey SPF rules as it will be coming from your server rather then the original server. So to fix this enable this rewrite setting and then the from envelope is rewritten to point to your system using a short life token. The 'from' header of the message is not modified.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_rewrite_relay - Rewrite even if from ip is a host to relay for
In some cases you will want SRS rewriting for relay hosts, In which case you should turn this on.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_share - List of hosts to share allow ips with. Must all have same srs.secret file
List your other incoming mail servers (which must be running surgemail). This lets SurgeMail share the list of known IP addresses which have sent 'allow' emails. You must copy your srs.secret file across all of the servers in question so they can verify each other correctly.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_baddns_skip, g_spflog_enable
g_spf_skip - Skip spf checks for these ip addresses, e.g. other mx hosts
List the ip addresses of your other MX servers so SPF checks wont fail when a message comes in via an mx host instead of directly. The SPF checking must therefore be done on all the MX servers.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_skip_from - Skip based on from, e.g. noreply@*paypal.com,..., Also skips RBL
Good for skipping SPF checking if a domain is in some way incompatible with SPF checking
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_skip_to - Skips SPF checks based on rcpt address and RBL checks.
Syntax: g_spf_skip_to "user@domain.com"
This setting can be used to skip spf checks based on the rcpt address, if used with g_orbs_late "true" then it can also be used to skip rbl checks if the rcpt matches this setting.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spf_very_strict - (strict only) Only give 'allow' option for default spf rule failures not real ones
In this mode real SPF failures are hard failures, but if there is no SPF record for a domain then the friendly 'allow' system is used to let the user send mail with only mild difficulty.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip, g_spflog_enable
g_spflog_enable - Enable this if this server is a frontend for a SurgeMail server users log into.
Enable this if this server is a frontend for a SurgeMail server users log into.
See also: g_friends_spf_fail_bounce, g_friends_check_spf, g_spf_mode, g_spf_nocache, g_spf_rewrite, g_spf_rewrite_relay, g_spf_norewrite, g_spf_dns_timeout, g_spf_domain, g_spf_very_strict, g_spf_default, g_spf_default_noblock, g_spf_skip, g_spf_skip_from, g_spf_skip_to, g_spf_rev_skip, g_spf_share, g_spf_baddns_skip
g_spool_path - Allows SurgeMail to scan a directory for messages to send.
Syntax: g_spool_path "directory of spool"
SurgeMail will scan this directory every few seconds and check for any messages in this directory if found SurgeMail will then send them the messages (must end in the extension .msg). The format of the messages is as follows (without the quotes).
filename: test.msg
"
To: you@domain.com
From: blah@domain.com
Subject: blah blahThis is a test
"
g_ssl_allow - IP Wild card of connections to allow to use SSL
This setting controls which connecting IP numbers are permitted to use SSL on POP and IMAP. They will see TLS in the protocol extension command (ETRN for SMTPor CAPA for POP). Typically, to enable SSL you set this to "*" after getting a certificate. If you don't have a valid certificate then turning this on can cause problems as mail clients will try to use SSL and fail.
g_ssl_allow_imap - IP Wild card list to allow SSL encryption from for imap
This setting controls which connecting IP numbers are permitted to use SSL on IMAP.
g_ssl_per_domain - Create/use an SSL certificate for each domain
SurgeMail can be set to use a single SSL certificate for the server or individual certificates on a per domain basis. Per domain SSL certificates can only be used with IP based vdomains.
SurgeMail will create private key / certificate pairs if required on startup. Alternatively these can be created using the 'SSL Config' link on the global settings page. These can be replaced with your own trusted signed certificates using the web admin interface or by placing the appropriate private key and certificate pem files in the following location: <surgemail>/ssl for a single certificate for the whole server and under <surgemail>/ssl/<vdomain> for per vdomain certificates.
Some mail clients and web browsers will complain if the certificate domain does not match the domain they are connecting to.
Changing g_ssl_per_domain will require surgemail to be restarted to take affect. Changes to certificates using the web admin interface now take affect immediately.
g_ssl_require - IP Wild card of connections to require to use SSL
This forces all matching IP addresses to use SSL for SMTP, POP and IMAP connections. Typically you would use this for non local connections to increase security local connections might be comparatively safe in un-encrypted mode.
g_ssl_require_imap - IP Wild card of connections to require to use SSL for IMAP
This forces all matching IP addresses to use SSL for IMAP connections.
g_ssl_require_login - IP wildcard of connections fur users needing to use SSL
This setting forces all matching IP addresses to use SSL for any action that requires a user login. eg: POP, IMAP and SMTP authentication but not plain SMTP. So this is ideal if you want all users to use SSL but still want email to come in from non SSL SMTP servers.
g_ssl_require_out - Other machines we only send to using SSL
This forces all matching IP addresses to use SSL for SMTP outgoing connections. Typically you would use this for outgoing connections to increase security.
See also: ssl_pop_domain, g_mirror_nossl, g_ssl_allow, g_ssl_allow_imap, g_ssl_require, g_ssl_require_imap, g_ssl_require_login, g_ssl_try_out, g_ssl_per_domain
g_ssl_try_out - Try and start ssl mode to these hosts, may cause failures!
If the hosts match then SurgeMail tries to start SSL security on the SMTP session. Note that this may cause failures if the link is dropped by the receiving server.
See also: ssl_pop_domain, g_mirror_nossl, g_ssl_allow, g_ssl_allow_imap, g_ssl_require, g_ssl_require_imap, g_ssl_require_login, g_ssl_require_out, g_ssl_per_domain
g_startup_delay - Startup delay
Seconds to wait before accepting inbound connections when starting SurgeMail .
g_surbl - SURBL Spam URI Realtime Blocklists
This looks up each url found in each mail message and checks it against the SURBL database of your choice, the multi database can be used. See http://www.surbl.org/, adds headers of the form: X-Surbl: stamp urlfound nameofsurbl.
Example: g_surbl name="multi.surbl.org" stamp="sc.surbl.org,ws.surbl.org,phishing,ob.surbl.org,ab.surbl.org,jp"
See also: g_spam_allow_rbl
g_surgeblog - Specialize SurgeMail as a Blog server
This setting causes SurgeMail's interface to specialize itself for the purposes of being a Blog server.
g_surgeplus_delay_tell_upgrade - Delay informing existing users about new SurgePlus versions for
Delay informing existing users about new versions of SurgePlus for this long after the new version is downloaded to your server. SurgePlus clients poll the server once an hour so they won't be informed about the new version for up to an hour longer than the value of this setting. Use this setting combined with the g_surgeplus_delay_tell_upgrade_exempt setting so that only administrator users are informed about new versions at first so you can confirm the new version works fine with your existing server configuration before everyone upgrades. Example values: "3 hours" or "2 days"
See also: g_disable_surgeplus, g_disable_surgeplus_updates, g_surgeplus_delay_tell_upgrade_exempt
g_surgeplus_delay_tell_upgrade_exempt - Users exempt from delayed new version informing
See the above setting for information. Example value: "user1@domain.name,user2@domain.name"
See also: g_disable_surgeplus, g_surgeplus_delay_tell_upgrade
g_surgeplus_hide_client_downloads - Hide the links to download and install SurgePlus Windows client
Use this setting if you don't want your users to know about the SurgePlus Windows client. All this setting does is to hide the download links from the web interface.
See also: g_disable_surgeplus
g_surgeplus_links - Add web links to SurgePlus from other web interfaces (and vice versa) for users allowed to use SurgePlus.
This causes links to appear in the SurgePlus interface to switch to using WebMail (and DBabble if you have the g_dbabble_links setting on).
See also: g_dbabble_links, g_disable_surgeplus
g_surgeplus_log_level - SurgePlus log level. 'none', 'info', or 'debug'. Default is 'info'
Sets the amount of logging done for SurgePlus. When using 'debug' level, data is logged to surgeplusd.log in addition to surgeplus.log
Example: debug
See also: g_log_level, g_disable_surgeplus
g_surgeplus_pop_server_name - Default pop server to set SurgePlus client download to connect to.
SurgePlus Windows client downloads are set to connect to this POP server by default. This setting only applies if the user is downloading the client from a URL that does not match a valid domain on the server. If the URL does match a domain on the server, the domain specific version of this setting applies instead.
See also: surgeplus_pop_server_name, surgeplus_smtp_server_name, g_surgeplus_smtp_server_name
g_surgeplus_port, g_surgeplus_secure_port - SurgePlus port and SurgePlus secure port.
SurgePlus uses the POP protocol to communicate with SurgeMail. However, some virus scanners running on the clients machine prevent the SurgePlus client from using POP commands that the virus scanner does not know about. In order to avoid this problem, SurgePlus uses port 7110 by default instead of port 110. However, clients not using a virus scanner (or clients using some virus scanners we have made SurgePlus work with - e.g. Norton) can safely use port 110 if they would otherwise be prevented from connecting to SurgeMail by a firewall. The SurgePlus client will quietly switch to using port 110 if it is not able to connect to the server using port 7110.
See also: xfile_url, g_pop_secure_port, g_xfile_allow, g_disable_surgeplus, g_surgeplus_port
g_surgeplus_smtp_server_name - Default smtp server to set SurgePlus client download to connect to.
SurgePlus Windows client downloads are set to connect to this SMTP server by default. This setting only applies if the user is downloading the client from a URL that does not match a valid domain on the server. If the URL does match a domain on the server, the domain specific version of this setting applies instead.
See also: surgeplus_pop_server_name, surgeplus_smtp_server_name, g_surgeplus_pop_server_name
g_surgeplus_web_port - SurgePlus web port.
If you want your SurgePlus users to view shared files over a different port than WebMail uses give this setting a value.
See also: xfile_url, g_webmail_port, g_disable_surgeplus, g_surgeplus_web_url
g_surgeplus_web_url - Direct SurgePlus users to access shared files at this url
Use this to override the default location that users are directed to to view shared SurgePlus web files. If you don't specify a value for this setting then it defaults to using the non-secure webmail port.
Example: https://||domain||:7443
See also: xfile_url, g_disable_surgeplus, g_surgeplus_web_port
g_surgewall_split - Split up surgewall messages, one per recipient
Split up incoming messages so subject tagging should work
g_tarpit_badrcpt - Delay rejection of bad recipients
Delay rejection of bad recipients (in seconds, default 4s).
g_tarpit_blackhole - Reject email one recipient at a time to make spammers go away
If tarpit_blackhole is true then if it was going to drop the connection to that user. Instead it will keep it and let the user talk and try and send messages, but will reject all recipients, it only does this for a max of 200 channels, any more are dropped.
g_tarpit_drop - Max recipients per hour from one IP
Drop link and ban for 1 hour if g_tarpit_max or g_max_bad_to has been exceeded.
g_tarpit_max - Max number of local recipients per hour from one IP
If this limit is exceeded, the offending client is "tarpitted". This means the mail server starts pretending to go slowly. This is better than simply closing the connection as that will not stop the sending system from trying to reconnect rapidly or send to other systems rapidly, but tarpitting jams the sending system and limits the damage they can do to you and others. Cool huh?
Unlike G_BOMB_MAX, the g_tarpit_max setting counts the total of all recipients to all addresses from this IP address.
A setting of about 200-10,000 is probably good but be careful with mailing lists it will break them. Use an exclusion for IP addresses of known mailing lists or set the limit higher than known mailing lists, eg: 2,000 is probably a good setting just to avoid disasters without disrupting many real users.
Use spam_allow ip.address.list to over-ride the limit for known systems (eg: mailing list servers) that would be exceed the limit.
g_tarpit_max_remote - Max remote recipients from one IP
The maximum number of remote recipients before slowing down.
g_tarpit_retry - Send retry error, 450 if tarpit limits exceeded
This setting has no further documentation currently available
g_tcp_read_timeout - Timeout in 'seconds' on POP connections (do not adjust)
Timeout in 'seconds' on POP connections, do not adjust. (default 600).
g_tellmail_ip - Tellmail IP restriction
Restrict remote tellmail commands to these IP addresses.
g_thread_max - Total maximum number of threads allowed
Total maximum number of threads allowed on this system. This should not normally be changed. If you do increase it start small, eg: 400 is a safe number on most systems. Generally if you need to increase it more than that then you have a performance problem that needs fixing and increasing it more is unlikely to be a good idea. On Linux if your thread_max setting is above 500 then you must modify surgemail_start.sh to increase the handle limit from 1024 to 2048 (at least twice the g_thread_max value). If you get crashes with 'handle_limit' recorded in the logs then it's likely that your operating system handle limit is too small for your g_thread_max setting. On Solaris you will need the 64 bit build of SurgeMail to increase this limit as the Solaris 32 bit 'c' libraries are limited to 256 file handles (I kid you not :-)
See FAQ section on session limits
g_thread_reuse_real - Thread reuse
If enabled the server will reuse existing threads instead of creating and destroying threads for each incoming/outgoing message. This has no affect on performance but does avoid a bug in some UNIX threading libraries which leak handles and cause problems if threads are not reused. Generally best disabled except on early Linux systems.
g_timezone - Timezone text
Text to be placed in the timezone part of the date string. e.g. +1200 NZT
g_tohost_local - Tohost entries to deliver locally
Authentication database tohost name entry to deliver locally. This setting only applies if g_proxy or g_route_by_tohost is enabled. This is useful to allow the configuration of multisite systems using g_route_tohost with a single shared authentication database.
g_toscan_path - Path used for mime parts for virus scanner
The default is the toscan directory under the home path, using this setting can help sometimes if permissions are a problem
g_unique_name - A unique name for this server
This name is used in place of the machine hostname in message filenames and thus friends confirmation message subjects
g_url_alias - Allows translation from one URL to another
Allows translation from one URL or beginning of a URL to another. eg:
g_url_alias from="/cgi-bin/" to="/scripts/"
will cause the URL http://localhost:7025/cgi-bin/fred.cgi to reference the same file as http://localhost:7025/scripts/fred.cgi would have, the fred.cgi in the SurgeMail 'scripts' directory. The domain url_alias settings are checked before these, the first matching rule is used, settings are checked in the order specified.
g_url_enable - Enables widearea url database
Syntax: g_url_enable <true/false>
If set then SurgeMail fetches the url database and updates from netwinsite.com every few hours. Messages which contain matches will get a header X-SpamUrl:... which will be used in the spam score. Once enabled you will contribute to Netwin's central server and also download from their once every couple of days.
Additions to your isspam/notspam training addresses are also sent to netwinsite.com (just the url's for white list/blacklist)g_url_host_noscan - Disable the scan for url_host settings matching the domain in an incoming web request
SurgeMail uses g_server_name and url_host settings to determine the default domain to select for web requests, this setting stops it using the url_host settings (which may be slow on systems with a large number of domains)
g_url_master - Not for general use
Used by netwin to manage the master server. Sorry this doesn't allow you to run your own master.
Should be left blankg_url_master_to - Not for general use
Not for general use. Used by netwin for testing.
g_user_access - Allow / Restrict user access to features based on g_access_group
g_user_access group="wildcard" access="list"
This setting matches the g_access_group the user is in to the wildcard specified and applies the specified list to that user, giving / restricting thier access to certain features. The list may include any of the following:
Value Result alias Access to the "Alias" page and features. blog Access to the "Blogs" page and features. centipaid Access to the "Centipaid" page and features. delete Access to the "Delete" button, which deletes the email account. enotify Access to the "Email Notification" page and features. exceptions Access to the "Exceptions" page. filter Access to filtering of messages. (g_filter_pipe, g_mfilter_file, g_dmail_filter) friends Access to the "Friends" pages, and system. fwd Access to the "Forwarding" features, forwarding, auto-responder. lists Access to the "Lists" page and features. log Access to the "Log" page. mailbox Access to the "Mailbox" page, view mailbox, setup rules. main Access to the "Main" page containing user details. pass Access to the "Password" features, change password, password retrieval. sms Access to the "Sms" page. spam Access to the "Spam" page, and SmiteSpam and Aspam processing of messages. spampriv Access to the "Spam" pages' spam private feature spf Access to the "Spf" page and features. surgeplus Able to connect to SurgeMail using the SurgePlus client. virus Access to virus scanning of messages. (g_virus_cmd, g_virus_filter, g_virus_avast, g_scan_cmd) webmail Access to the "WebMail" button which logs the user into WebMail. In addition you can prefix any of the above with ! to deny access. There are two other special case values, "all" and "none" which mean exactly what they say, access to "all" or "none" of the features.
Example:
g_user_access group="simple" access="all,!spam,!virus"
The above setting gives users in the 'simple' group access to all the features except spam and virus features.
g_user_access_default - Default user features granted to users
This setting is a default access list for all users on the server, it is specified in the same maner as the g_user_access settings 'access' parameter. eg:
g_user_access_default "all,!spam,!virus"
g_user_access_from - When sending use from for useraccess rules
When sending a message the user access rules which are applied can be based on the 'from' header, this is not secure but is sometimes useful.
See also: authent_info_grp, g_acctlog_authonly, g_allow_user_authent_field_get, g_allow_user_authent_field_set, g_authent_always, g_authent_allow_badascii, g_authent_prefix_sep, g_authent_process, g_authent_cachelife, g_authent_cachebad, g_authent_cachesize, g_authent_domain, g_authent_number, g_authent_info, g_authent_ip, g_authent_path_broken, g_authent_single, g_authent_strip_domain, g_authent_restart, g_authent_logall, g_authent_fwdfile, g_authent_timeout, g_authent_last_login, g_auth_hide, g_auth_norelay, g_auth_skipgateway, g_mirror_nwauth, g_gateway_auth, g_smite_skip_auth, g_smtp_portauth, g_smtp_etrn_auth, g_smtp_noauth, g_spam_check_auth, g_xauthuser_hide
g_user_alias - Number of aliases accounts can create
This setting specifies the maximum number of account aliases an account (optionally in specified group) can create. The format of these aliases is specified in the file specified by the g_user_alias_file setting. eg.
g_user_alias quota="10" group=""
g_user_alias quota="20" group="grp1"
g_user_alias quota="30" group="grp2"g_user_alias_file - User aliases configuration file
This setting specifies the configuration file for user aliases. This file is in the following format:
domain alias_domain,access[,access]...
where domain is the domain name eg: email.com, alias_domain is the domain in which aliases can be created, and access specifies who is allowed to create these aliases, it can have one of the following values:
user Users can create these aliases. domadmin Domain administrators can create these aliases. admin The Administrator can create these aliases. private Same as domadmin,admin. The Administrator and the Domain administrators can create these aliases. public Same as user,domadmin,admin. Everyone can create these aliases. Example alias.dat file:
email.com *.email.com,public email.com sport.email.com,public internal.email.com email.com,private internal.email.com internal.email.com,adming_user_blogs - Number of blogs accounts can create
Specifies blog limit based on user group.
Example: g_user_blogs group=premium quota=15
See also: blogs_max_per_user, url_blogs, g_access_group, g_blogs_enable, g_blogs_maximum_image_width, g_blogs_maximum_items_in_top_page, g_blogs_max_per_user, g_blogs_default_template, g_blogs_use_sub_domains, g_blogs_sub_domain_prefix, g_blogs_not_unique, g_blogs_no_suffix, g_blogs_ping
g_user_cookies - Enable browser cookies for user self management
Enable browser cookies for user self management.
g_user_domainlist - Show domains list on user pages
This setting decides who will see the drop-down list of domains on the user check, add, login, and management pages. It has three possible values: user, domadmin and admin. A value of 'user' allows everyone to see the list, 'domadmin' allows domain admins and the admin to see the list, and 'admin' allows only the admin to see the domains list.
g_user_filter_early - Process user exceptions/filters before tagging message as spam
Causes the users exception rules to be processed before tagging the message as spam, meaning, if a rule matches to 'accept' a message, that message not to be tagged as spam.
g_user_friends_domain_log_disable - Disable domain level friend.log file
By default a friend.log file is written to each domain mailbox_path. This file is a collection of all users friends.log entries that rotates when it reaches 2mb in size.
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends
g_user_list_quota - Number of mailing lists users can create
g_user_list_quota group="" quota="100"
This setting configures the number of mailing lists a user can create on this server. The group field is optional, specifying none effects all users globally, otherwise it matches this against the users access group. See also user_list_quota which can set quota per domain. Also the list_quota authent field can set quota per user.
g_user_mfilter - Local delivery Mfilter rules
Mfilter rules to run late in the delivery process after the email messages have become "user specirfic", In particular this allows filtering based on the output of g_user_pipe.
g_user_pipe - Local delivery filter pipe
Pipe run on file just before delivery to user, $USER$ available on command line. This allows the message to be modified (also see g_filter_pipe).
g_user_send_rule - Define valid recipient addresses for users in a group (requires SMTP AUTH)
This rule allows you to define which domains users in the specified group can send email to.
g_user_send_rule group="wildcard" to="number"
If 'group' is set to '*' then it applies to users who are not in a group (see g_access_group), and/or whose group does not match another g_user_send_rule setting. The 'to' field contains a wildcard list of allowed email addresses.
g_user_send_rule - Define valid recipient addresses for users in a group (requires SMTP AUTH)
This setting has no further documentation currently available
g_user_sms_quota - SMS quota
Number of SMS messages accounts can send.
g_user_status_send - Number of days after which to send user status messages (0 = never)
When the user enables friends then this setting will send them a regular report on what is pending and what filter rules have done.
See also: friends_at_rcpt, g_friends_only, g_friends_name, g_friends_silent, g_friends_ignore, g_friends_confirm_subject, g_friends_latest_headers, g_friends_pending_keep, g_friends_pending_novanish, g_friends_at_rcpt, g_friends_spf_fail_bounce, g_friends_check_spf, g_quota_friends, g_user_friends_domain_log_disable
g_user_utoken_days - Length of time a user self management login token is valid
Length of time a user self management login token is valid for. Length of time a user self management cookie is valid for. After this time period the login token will stop allowing the user access and they will need to login again.
g_user_utoken_expire - Length of time a user self management login token is valid for
This setting has no further documentation currently available
g_user_virus_scan - Allow users to enable / disable virus scanner for themselves
This setting adds a tickbox to the Spam page in user self administration that allows the user to enable and disable the virus scanner for them selves.
g_vanish_any_bounce - Vanish all bounces are not bounces to messages from this machine (requires g_received_name)
This setting will vanish spam pretending to be a bounce, it is possible it will vanish a real but badly formed bounce (badly formed as it contains no indication that it came from this server).
g_vanish_bad_bounces - Vanish suspected spam bounces
Vanish suspected spam bounces (requires g_received_name).
g_vanish_virus_bounces - Vanish suspected virus bounces (requires g_received_name)
This setting gets rid of most of those stupid virus bounces you get from emails you haven't sent. It works by checking incoming virus bounces for the received header that must exist if it was sent with your mail server. If the header is not found, the message is dropped. Recomended.
g_verify_helo - Verify helo name translates to same network as sending system.
Syntax: g_verify_helo "true/false"
It will skip this check for any trusted connection (smtp authenticated, or any ip it would allow to forward)
It adds this header:
X-Verify-HeloIt simply takes the helo name, and turns it into a number a.b.c.d, then it checks that the connection is coming from 'a.b.*.*'
if it isn't it adds a header saying as much.See also: g_verify_smtp, g_verify_timeout, g_verify_mx, g_verify_mx_skip
g_verify_mx - Verify sender IP by MX
Verify MX records contain senders IP address (also see g_verify_mx_skip).
See also: g_verify_smtp, g_verify_timeout, g_verify_mx_skip, g_verify_helo
g_verify_mx_skip - Skip verify sender IP by MX
Use to define incoming mail gateway IPs so the MX verify doesn't fail on them.
See also: g_verify_smtp, g_verify_timeout, g_verify_mx, g_verify_helo
g_verify_smtp - Verify SMTP port
Verify we can talk back to the SMTP port on incoming IP address.
See also: g_verify_timeout, g_verify_mx, g_verify_mx_skip, g_verify_helo
g_verify_timeout - Seconds to wait for SMTP response, default is 10 seconds
As the verification of incoming addresses is done while the message is arriving at the 'data' stage, it is critical that it not take more than 30-60 seconds or the sending server will give up and the message will be lost. Generally this setting should not be changed.
See also: g_verify_smtp, g_verify_mx, g_verify_mx_skip, g_verify_helo
g_virus_allow_unmonitorable - Allow unmonitorable content (avast antivirus)
By default messages that cannot be scanned (eg as they contain password protected archive files) are blocked by the avast virus scanner. This setting allows unmonitorable contect to be sent.
g_virus_avast - Enable Avast virus scanner integration
Enable Avast virus scanner integration. Avast should first be licensed and installed before this is enabled. Installation is done by pressing the install button next to this setting in the global settings page. Licensing is part of the SurgeMail key. During the SurgeMail evaluation period full Avast license is available. Subsequent to that the Avast integration must be purchased.
Status of the progress of installation and the whether Avast is currently uptodate is displayed in the main status page.
g_virus_avast - Set Avast update time
This is a string based setting that allows you to specify when Avast updates are attempted.
eg: to update at 12 midnight, 6am,12noon and 6 pm.
g_virus_avast_hour "0,6,12,18"
g_virus_cmd - Command line virus checker to run on MIME parts
If defined the mail server will extract MIME parts in a multi part message and run the virus scanner over the extracted file. The command line can include $FILE$ which will be replaced with the actual file name of the extracted part. An intelligent cache is used so mailing lists, etc, will not require running the virus scanner on every message sent. If you set this to "do_not_run" then SurgeMail will extract the MIME parts but not actually run any program, some virus scanners scan all files on the system so the file is deleted magically and SurgeMail will notice and bounce the message. If your scanner supports the returning of return codes if a virus is found then you should use g_virus_cmd_codes with this setting as this is more reliable than having to detect if a file is deleted and also means also will work on viruses in archives which a lot of scanners won't delete.
g_virus_cmd_codes - Return codes to bounce message
Accept return codes from virus scanner as a confirmation that the scanned file is infected, eg: 1,2,3,4,5.
Lets SurgeMail check the return code from g_virus_cmd and if the code matches
one in the above setting assumes its a virus and bounces it.g_virus_cmd_codes "10,12"
This would assume its a virus if the scanner returns return code 10 or 12 and then will bounce the message.
g_virus_cmd_drop - Drop silently instead of reject at data stage - not recommended
This should only be used when your front end server is not scanning for viruses and your back end server then rejects the message generating back scatter on the front end server.
g_virus_cmd_max - Maximum number of concurrent threads to use for scanning
Syntax: g_virus_cmd_max "number of threads"
This sets the maximum number of threads that be used for running the virus scanner set by g_virus_cmd. Some scanners can take a while to scan a message and if the server is very busy this can tie up many channels and drain the cpu slowing down the entire mail server. When the maximum has been reached any messages coming in will be passed on without being run through the scanner - although this is not the best, it's better than the mail server grinding to a halt.
g_virus_cmd_nodel - Do not delete scanned files
Disables cleanup of scanned files, so you can test manually. The files are extracted to the "toscan" directory inside the SurgeMail directory. You should never normally need this on unless for debugging purposes.
g_virus_cmd_sleep - Wait after g_virus_cmd incase delete is not immediate
Milli seconds to wait after g_virus_cmd incase delete is not immediate, eg: 500 = half a second.
g_virus_disable_remote - Disable virus scans for non-local addresses
By default SurgeMail scans incoming messages from non-local senders, this disables that behaviour so scans will only occur if any recipient has virus scan access.
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_filter, g_virus_filter_require, g_virus_fprot, g_virus_recent_skip, g_virus_rename, g_virus_report, g_virus_restart
g_virus_filter - Virus checker or filter that takes commands on stdin and response on stdout
Virus filters use the following protocol the process is run continuously and sent on STDIN a command of the form, "nnn CHECK fullfilename envelopefilename\r\n" and in response it must send back is "nnn OK|REJECT|ERROR reason text\r\n"
It can modify the file directly and then respond with 'ok', however if it does this it must maintain the crlf line terminated and dot stuffed nature of the file.
Here is an example test of a virus filter
c:\surgemail> vfilter.exe 1 check c:\surgemail\work\a.itm c:\surgemail\work\a.hdr 1 REJECT Found something bad in that file 2 check c:\surgemail\work\a.itm c:\surgemail\work\a.hdr 2 OK send message alonga.hdr would contain:
From: bob@domain.com To: xyz@thisdomain.com To: xyz3@thisdomain.comSee also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter_require, g_virus_fprot, g_virus_recent_skip, g_virus_rename, g_virus_report, g_virus_restart
g_virus_filter_require - Require filter pipe
If any g_virus_filter pipe fails bounce messages rather than allow to continue.
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter, g_virus_fprot, g_virus_recent_skip, g_virus_rename, g_virus_report, g_virus_restart
g_virus_fprot - Set F-PROT port for mail scanning
Typically set this to 11200
First install f-prot virus scanner, exact steps will vary depending on platform so follow your F-Prot install instructions, but as an example on Linux we did this:
cd /usr/local gunzip DISTRIBUTION.tar.gz tar -xvf DISTRIBUTION.tar cd f-prot ./install-f-prot.pl cd tools# Now start mail scanner as user 'mail' su mail -c"/usr/local/f-prot/tools/scan-mail.pl -server -daemon"Your will also need to start the scanner as above in your startup scripts (e.g. rc.local)
Then lastly in surgemail.ini set
g_virus_fprot 11200
When a message is scanned a header X-Fprot: ... is added giving some informational status.
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter, g_virus_filter_require, g_virus_recent_skip, g_virus_rename, g_virus_report, g_virus_restart
g_virus_recent_skip - Skip recent virus cache
Skip virus recent cache which attempts to speed up virus scanners.
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter, g_virus_filter_require, g_virus_fprot, g_virus_rename, g_virus_report, g_virus_restart
g_virus_rename - Rename attached executables to prevent autorun
If enabled SurgeMail will rename dangerous executable files by replacing the '.' with an '_'. This will stop many autorun viruses. This is name
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter, g_virus_filter_require, g_virus_fprot, g_virus_recent_skip, g_virus_report, g_virus_restart
g_virus_report - Report detected viruses to someone
Sends an email report to the specified address when a virus comes in.
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter, g_virus_filter_require, g_virus_fprot, g_virus_recent_skip, g_virus_rename, g_virus_restart
g_virus_restart - Restart vpipe virus scanners
Restart vpipe virus scanners every this many items.
See also: g_user_virus_scan, g_vanish_virus_bounces, g_virus_avast, g_virus_avast_hour, g_virus_allow_unmonitorable, g_virus_cmd, g_virus_cmd_codes, g_virus_cmd_nodel, g_virus_cmd_sleep, g_virus_cmd_max, g_virus_cmd_drop, g_virus_disable_remote, g_virus_filter, g_virus_filter_require, g_virus_fprot, g_virus_recent_skip, g_virus_rename, g_virus_report
g_vpipe_concurrent - Concurrent requests to vpipe process
Concurrent requests to vpipe process, default is 7, set to 1 to debug vpipe issues
g_vpipe_notag - Disable vpipe result headers
Disable headers showing vpipe results in messages.
g_vpipe_skip - Skip virus filter checks per IP address
Disable virus and crc checking for known safe bulk mailers that would otherwise overload the server. This setting affects the virus checker.
Example: g_vpipe_skip "20.0.0.2"
- g_virus_cmd
- virus filters (g_virus_filter)
- filter program (g_filter_pipe)
- F-Prot in daemon mode (g_virus_fprot)
g_vpipe_timeout - Timeout for firus filters (default 60s)
The timeout in second that SurgeMail will wait for a virus filter (defined by g_virus_filter) to complete. If after this time the virus filter has not responded the message will be let through and the following line logged in mail.log:
"Virus filter not responding, stuck on <msg file> allowing message through"
g_web_charset - Charset for html pages
Sets the charset to use for each language i.e. e.g. iso-8859-1
g_web_hide_source_names - Hide the name of the source template page in output web pages.
To aid tailoring each web page in the web admin shows it's own address so you can find it to modify it. Some admins consider this a security issue, or just a bit ugly, so use this setting to hide this information when you don't need it.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_url_path, g_web_title
g_web_max - Max concurrent web connections, default is 100
This includes web admin, webmail etc...., The default limit should be sufficient for most systems. Although a limit of 10 would be tons for most systems we had to set the default high as this setting was added recently.
g_web_max_perip - Max concurrent web connections, default is 30
This includes web admin, webmail etc...., The default limit should be sufficient for most systems unless all your users are coming through a common proxy
g_web_ref_path_extension - Path extension to add to web page image/css references.
This setting is used for caching purposes. See SurgeMail template caching for details
g_web_timeout - Timeout for web requests
Timeout for web requests, the default is 180 seconds, generally it should not be set below 61 seconds
g_web_title - Title to use on specified web page
This lets you customize the title of each management web page.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path
g_web_url_path - Url to path translation with access specifier
This lets you setup aliases and translations of urls partly based on the access rights of the user.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_title
g_webmail_limit - Maximum number of concurrent webmail requests
This should not generally be adjusted, it is simply a limit to prevent DOS attacks or overloading from web requests. A value of 10-300 would be reasonable. The default is 200
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_port - WebMail port (default 7080)
This is the port that WebMail users should connect through (unless you want better security, then use the secure port and HTTPS protocol listed below) By default it is port 7080, but if you are not running a web server you probably want to change it or add port 80, eg:"7025,80" so that people can get to it with a URL like this: http://your.mail.server instead of http://your.mail.server:7080. Use the keyword 'disabled' to disable this part of the SurgeMail service.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_secret - Secret string used by webmail when sending the ip address of connecting users
This is used with webmail when you want surgemail access rules to apply to webmail users, webmail has a matching setting which makes it pass the ip address through
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_secure_port - WebMail secure port (default 7443)
This is the port that WebMail users should connect through.. By default it is port 7443, but if you are not running a web server you probably want to change it or add port 443, eg:"443" so that people can get to it with a URL like this: https://your.mail.sever Instead of https://your.mail.server:7443. Use the keyword 'disabled' to disable this part of the SurgeMail service.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_select_domain - Send select_domain instead of host in webmail autologins
Recommended. This uses the select_domain method of auto-logins with WebMail, it often works where the old method fails.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_timeout - Timeout for webmail or any cgi process (in seconds, default 360)
If he webmail cgi fails to respond this limits how long SurgeMail will wait before killing the process.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_url - Url to the WebMail cgi
If WebMail is not in the default place and/or is not on the SurgeMail machine then this setting tells SurgeMail where it is so links to WebMail from SurgeMail function correctly.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_urladd - Url data to append to WebMail auto-login link
This setting allows you to specify additional information and settings which are passed to WebMail when SurgeMail links to it.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_useip - Use the ip address in g_webmail_port setting
By default it will use the same url as the user connects on which is generally better.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_url, g_webmail_urladd, g_webmail_workarea, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_webmail_workarea - Path to WebMail workarea
If WebMail is not installed in the default location on this SurgeMail machine this setting tells SurgeMail where to find it.
See also: webmail_url, webmail_urladd, webmail_workarea, webmail_host, web_url_path, g_keepalive, g_key_manual, g_webmail_limit, g_webmail_port, g_webmail_secure_port, g_webmail_timeout, g_webmail_useip, g_webmail_url, g_webmail_urladd, g_webmail_select_domain, g_webmail_secret, g_web_hide_source_names, g_web_url_path, g_web_title
g_wmail_backend - Backend machine to connect to
This specifies the backend machine where WMail connects for email and to store user settings. WMail will cache data here but store the master copy of anything on the backend machine.
g_wmail_work - Path to WMail cache/work files
This is where WMail stores it's temporary or working files, default I_G_HOME\wmail\work
g_work - Workarea Path
Work area for SurgeMail temporary work files.
g_xauthuser_hide - Hide X-Authenticated-User header
The header X-Authenticated-User is added to all local deliveries for users that login using SMTP authentication. This is the most reliable way to determine who actually sent this email. This setting will disable the addition of this header.
g_xfile_allow - IP address to allow xfile and WebMail features from
Allow xfile & web upload features for users. Set to '*' or the WebMail servers IP address.
See also: xfile_url
g_xrcpt_hide - Hide X-Rcpt header
The X-Rcpt header is added indicating which local account this message was delivered to. This setting will disable the addition of this header.
g_xrcptoriginal_hide - Hide X-Rcpt-Original header
The X-Rcpt header is added indicating which local account this message was delivered to. If the mail has been redirected for any reason the original delivery address is added as an X-Rcpt-Original header. This setting will disable the addition of this header.
g_xserver_hide - Hide XServer header
This wil hide the X-Server header.
spamlist - Spam Filter Rules
These rules allow simple filtering of Email messages for common or repetitive spam message. The form lets you specify whether a string is found in a specified header that all such messages be bounced or redirected. This form will write or modify your mfilter.rul file to include an auto generated section which obeys the rules you have defined, e.g.
D:\>type \surgemail\mfilter.rul # BEGIN_AUTO Generated section do NOT EDIT this bit if (isin("Subject","bad words")) accept "fred@remote.domain" if (isin("To","bad words")) accept "fred@remote.domain" # END_AUTO Generated section do NOT EDIT this bitYou can write much more complex rules yourself manually, see mfilter.htm for more details.
Compatibility settings
g_authent_prefix_sep - Authent Prefix Separator (deprecated - for backward compatibility only)
Prefix separator for prefix based separator. Only relevant if enabled on a per vdomain basis using the "prefix" setting.
g_authent_fwdfile - Use DMail forward files (deprecated - for backward compatibility only)
Allows old style DMail forward files to be read.
g_dmail_filter - Run DMail compatible filter files (deprecated - for backward compatibility only)
Run DMail compatible filter files. Mfilter rule files should be used instead.
g_mirror_nwauth - Mirror NWAuth data files (deprecated - for backward compatibility only)
This setting is no longer used (as of SurgeMail 1.7d), the g_mirror_mode setting is used instead to decide whether do mirror the NWAuth database.
Specialist / debugging settings
g_backtrace_disable - Backtrace Disable
Disable backtrace information for unix systems.
g_crash_normal - Crash without catching exceptions
Crash without catching signals 10,11. In particular this will generate correct core files on FreeBSD systems.
g_debug_block - For catching bugs in block file processsing
For catching bugs in block file processsing.
g_mutex_timeout - Crash without catching exceptions
Default mutex timeout period in seconds (default=600 ie 10minutes). This is a self monitoring feature that if it has not received a mutex for some reason (usually a bug, but could be server overloading) SurgeMail will shut itself down. If g_restart is enabled this would restart surgemail.
g_shutdown_slow - Delay shutdown
Add 20 second delay to shutdown for testing purposes only.
g_slow_welcome - Delay the welcome message
Add 20 second delay to welcome message for testing purposes only.
g_vpipe_fail_crash - Crash if vpipe fails
Crash SurgeMail if vpipe fails. This is for debugging purposes only.