General System Settings

Below are the configuration options available when viewing the General Settings section of SmarterMail. These settings apply server-wide, across every domain hosted on the server, unless a specific setting is explicitly called out as something domain administrators can override.

• Server Info
• Paths
• Webmail Login
• Webmail
• Reports
• Folder Auto-Clean
• Calendar Auto-Clean
• Notification Auto-Clean
• File Storage
• Cloud Storage
• File System
• External Senders
• Spool
• Message Archiving
• Footer
• Block Authentication by Country
• Mailbox Migration

Server Info

• Hostname - The hostname the server identifies itself with. This value is used, among other things, as the EHLO/HELO name SmarterMail presents during outbound SMTP sessions, so it should be a fully-qualified, resolvable name — not just a bare server name. SmarterMail validates whatever is entered here against standard domain-name syntax rules, so it must look like a real hostname rather than an arbitrary label.
  Note: Hostnames should be in the format computername.domain.com — for example, mail01.example.com. Using a name that does not resolve back to the server's IP address (or that doesn't match the PTR/reverse-DNS record for that IP) can cause receiving mail servers to view the EHLO/HELO greeting with suspicion, which can hurt deliverability.
• DNS IP Address #1 and DNS IP Address #2 - These fields configure the actual DNS resolver(s) SmarterMail itself uses when performing mail-related DNS lookups — not just a fallback used by the underlying operating system. Once populated, every DNS query the mail engine issues (MX record lookups during outbound delivery, SPF/DKIM/DMARC record checks, RBL/DNSBL queries against spam block lists, and reverse-DNS/PTR lookups used for spam and connection checks) is sent to whichever server is listed here first, falling back to the second if the first doesn't respond. If both fields are left blank, SmarterMail falls back to whatever DNS servers are configured at the operating-system level (pulled from Windows Networking settings via WMI on a Windows install). Because so much of SmarterMail's spam- and delivery-related logic depends on fast, reliable DNS resolution, pointing these fields at a DNS server the administrator controls and trusts (rather than relying on whatever the OS happens to be configured with) is recommended for production mail servers, particularly if the default resolver is slow, rate-limited, or untrusted for RBL lookups.

Paths

By default, SmarterMail stores certain information in pre-defined paths. However, there may be times when system administrators want certain things stored in separate locations. A perfect example of this is the SmarterMail Spool: for many servers, having the Spool process on a separate drive on the server can increase performance and server reliability, not to mention save disk i/o. That's because the Spool for any mail server can tax a drive due to all the file reads and writes. Having the Spool on a separate drive — we recommend putting it on an SSD drive — can help the overall lifetime of a mail server.

In this section, system administrators can specify which drive paths to use for the following:

• Spool Path - Having the Spool on a separate drive is recommended for any mail server due to the i/o required. If you are using a real-time virus scanner, this is the path that must be scanned in order to properly handle viruses. Unlike the Log Files path below, SmarterMail reads the current Spool Path setting fresh each time it processes a message, rather than caching it once at startup, so moving the Spool Path takes effect immediately and does not require a service restart. Do, however, make sure the new location exists and that the SmarterMail service account has full read/write permissions to it before saving the change, since any in-flight mail will start writing to the new path right away.
• Log Files - Storing SmarterMail log files on a separate drive means that more space is available for users. Depending on how log files are set up — the level of detail stored for each — having a separate, large hard drive specifically for log files means less potential for disk space issues for users.
  Note: Changing the log path will not take effect until you restart the SmarterMail service. Unlike the Spool Path and Quarantine Path, the logging subsystem opens its log files once when the service starts and does not re-check this setting while running, so a restart is required before new log entries are written to the updated location.
• Quarantine Path - This is the directory used for files caught by SmarterMail's antivirus and antispam integrations. Having quarantined items stored on a separate drive can further protect a mail server from issues caused by viruses. As with the Spool Path, this setting is re-read on each use rather than cached at startup, so changing it takes effect immediately without needing to restart the SmarterMail service.

Webmail Login

Small businesses using SmarterMail on their own servers, or even companies using SmarterMail from their hosting provider, will benefit from the ability to customize the SmarterMail login page to add a company logo, provide additional branding text, or simply adjust the default 'Login to SmarterMail' text to be more in line with an overall brand message.

• Logo Image - Upload an image, like a company logo, by dragging and dropping a file in the highlighted area or clicking to browse for a file (max file size of 3mb). Uploading an image using this upload control will host the image publicly on the server and enter the <img src="URL" /> tag in the HTML section.
  Note: Uploading an image here alone will NOT display the image on the login screen. The HTML must remain in the Login Page HTML section. This upload control can be used by those who don't have their logo publicly hosted or who wish the image source to point back to their mail server. Furthermore, regardless of the image uploaded, the image's source URL will remain the same; only one image may be hosted at a time.
• Custom Login Text - Use this setting to customize the login page header to something more in line with an overall brand message. If Custom Login Text is left blank, SmarterMail's login page will show the default text "Welcome to SmarterMail". For example, a hosting provider might change this to "Welcome to Contoso Hosted Email" so their own branding, rather than SmarterMail's, is the first thing a user sees.
• Custom Title Text - Use this setting to customize the title of the login page to something more in line with an overall brand message. If Custom Title Text is left blank, SmarterMail's login page will show the default text of "SmarterMail" in the browser tab title. Note: When a system administrator is logged in, the custom title text will appear on all pages. If the login display for a domain is not set to default or overridden, users will see this text on the login page only, with their email address displayed as the browser title for all other pages.
• Login Background - Use this option to select the background image(s) that displays on your login screen. Use the default images that come with SmarterMail, point to your own path on the server or select a solid color background. For custom images, the following image formats are supported: SVG, PNG, JPEG/JPG and GIF. Minimum size is dependent upon the image type being used. However, you can use 1920 x 1280 as a general guideline.
• Enable custom login page HTML - Check this box to enable the ability to use HTML to further modify the login screen to add additional text or adjust the layout.
• Login Page HTML - Enter the custom HTML that will be used to further modify the login screen (in-line custom CSS can be used as well).
  Note: To include white space around the Image on Login Screen, the div id "companyinfo" must be included.

Webmail

• Logout URL - By default, users are presented with the login page for their mail server when they log out of webmail. Entering a full URL here means the added URL will open in the user's window once they log out instead of the login page. For example, a business might set this to its own corporate intranet page (https://intranet.example.com) so employees land somewhere useful after signing out rather than back at the login screen.
• Replace online help with custom URL - When enabling custom help, whatever is entered as the Custom Help Text, and the URL that text redirects to, will replace the standard, default Online Help link that is displayed. That means you'll be redirecting users of the SmarterMail server to your OWN help documentation and away from the documentation created by SmarterTools. This is useful for hosting providers or enterprises that maintain their own internal knowledge base or support portal (e.g., "Contact IT Support" pointing to an internal ticketing site) and don't want end users referred to SmarterTools' public documentation.
• Hide external email avatars - This allows system administrators the ability to block email avatars from services like Gravatar or other external image sources. Enabling this is a privacy and security consideration: without it, simply opening or previewing a message can cause webmail to reach out to a third-party avatar service, which reveals to that third party that the message was opened. Administrators in privacy-sensitive environments (legal, healthcare, government) commonly enable this to prevent that kind of external callback.

Reports

Use this tab to specify how long historical statistics are retained on the server before being purged. Each of the three retention settings below can be turned on or off independently, and each has its own retention period in months.

• Delete Server Stats After (Months) - The length of time server-wide stats should be kept before being deleted. The retention value defaults to 13 months, though automatic deletion of server-wide stats is not turned on by default — a system administrator who wants server stats purged automatically needs to enable this switch explicitly.
• Delete Domain Stats After (Months) - The length of time per-domain stats should be kept before being deleted. This defaults to 13 months and is enabled out of the box.
• Delete User Stats After (Months) - The length of time per-user stats should be kept before being deleted. This defaults to 13 months and is enabled out of the box. For example, on a server with thousands of mailboxes, leaving this enabled keeps the statistics database from growing indefinitely as user-level send/ receive counters accumulate month after month.

Folder Auto-Clean

Folder Auto-clean is a method for limiting how much of a user's disk space is used by the Junk EMail, Sent Items, and Deleted Items folders. By placing limits on the size of these folders, system administrators can help ensure that user accounts do not fill up unnecessarily. Messages are deleted from the folders in the order that they were received so that older messages get deleted first.

• Allow domains to override auto-clean settings - Enable this setting to allow domain administrators to create their own auto-clean policies for their domain.
• Allow users to auto-clean Inbox - Enable this setting to allow users to create auto-clean policies on the Inbox folder.

Any existing auto-clean rules will be listed. To add a new folder auto-clean rule that will apply to all users across all domains, click on the New Rule button.

If the Rule Type is set to Size, the following options will be available:

• Folder - The folder that will be auto-cleaned: Deleted Items, Junk Email or Sent Items.
• When size greater than (MB) - The maximum size of the folder, in megabytes. Once the folder reaches this size, the auto-clean process is started and older messages (messages that were received the longest time ago) are deleted.
• Reduce to (MB) - The size the folder should be after the auto-clean process has completed, in megabytes. When auto-cleaning, SmarterMail will delete older messages first until the folder reaches this size.
  Note: This number should always be lower than the previous field. For example, a rule might trigger cleanup once the Deleted Items folder exceeds 500 MB, then delete the oldest messages until the folder is reduced back down to 250 MB.

If the Rule Type is set to Age, the following options will be available:

• Folder - The folder that will be auto-cleaned: Deleted Items, Junk Email or Sent Items.
• Days - The maximum number of days mail will stay in the selected folder before deletion. For example, setting Junk E-mail to 14 days means any spam message older than two weeks is purged automatically, even if the user never manually empties that folder.

Auto-Clean Timings

Size-based auto-clean rules are run whenever an action is performed on a particular folder. For example, moving a message into the folder. Once that action occurs, the auto-clean rule is run, and it runs each time an action is performed. Age-based rules, however, run once per day, on the FIRST folder action for that day. For example, deleting an email first thing in the morning. When you delete an email, it's moved to the Deleted Items folder, which is a folder action. At that point, if there's an age-based auto-clean rule for the Deleted Items folder, the rule is run and then is silent until an action is performed on the next day. If no action is performed on a folder with an age-based rule, the rule still runs automatically shortly after midnight, server time. This distinction matters when troubleshooting: an administrator who expects an age-based rule to fire the instant a message crosses the age threshold will instead see it clear out during the next folder action (or at the latest, shortly after midnight) rather than in real time.

Calendar Auto-Clean

Having a system-wide setting for all domains that limits past calendar appointments is another way to help prevent disk drives from filling up. Just as with messages, calendar appointments are deleted in the order they were created or accepted.

• Calendar Auto-Clean Months - The max age of a calendar appointment before it is permanently deleted. The available options are Never, or 3, 6, 12, 18, or 24 months — this is a fixed dropdown rather than a free-form number of months. Out of the box, this defaults to Never, meaning calendar appointments are not automatically cleaned up unless a system administrator explicitly picks one of the numeric options. For example, choosing 12 Months means an appointment from more than a year ago is purged automatically, which can be useful on servers with very large shared calendars that accumulate years of recurring events.
• Allow domains to override auto-clean settings - Enable this setting to allow domain administrators to create their own auto-clean policies for their domain.

Notification Auto-Clean

One other way to help limit disk space is by automatically cleaning out old notifications for a user's account. When notifications are dismissed, they're still logged by SmarterMail. Therefore, unless old notifications are actually deleted, that log file can grow rapidly, especially if a user has a number of notifications. When notifications are automatically cleaned, they're cleaned in the order they were created or dismissed.

• Notification Auto-Clean Days - The max age of a notification before it is permanently deleted. The available options are 15, 30, or 45 days — again a fixed dropdown rather than an arbitrary number. By default, this is set to 30 Days.

File Storage

SmarterMail's file storage feature allows users to upload files to the server and share them via public links. One benefit of using file storage is that it reduces the stress on the server by keeping large files out of the spool.

• Max File Size (KB) - The maximum size a file can be in order to be uploaded to the File Storage area. This has a relationship to the file size limits for attachments, and any files uploaded to Online Meetings and/or Chats as all of those items are stored in a user's File Storage area. Out of the box, this limit is enabled and set to 10,240 KB (10 MB) per file. For example, raising this to 51,200 KB (50 MB) would allow users to attach larger design files or recordings through chat and meetings, but administrators should weigh that against available disk space across all mailboxes, since every uploaded file counts against the user's overall quota.
• Root Webmail URL - The base URL of any file stored and shared in file storage. By default, the base URL corresponds to the domain the mail server is set up on (i.e., http://mail.example.com). If SmarterMail is configured on an external IP that allows a network address translation (NAT) to an external IP, the system administrator may need to modify the root URL so that shared file links resolve correctly for recipients outside the local network.

Cloud Storage

SmarterMail's cloud file storage feature enables users to upload files to the server and share them via public links. By storing large files separately, this feature helps reduce server load and keeps the spool optimized. System Administrators can integrate various add-ons with SmarterMail to enhance file storage capabilities, connecting user file storage to a supported third-party cloud provider instead of (or alongside) local disk-based storage.

Visit the Marketplace to explore available Cloud File Storage add-ons.

File System

• Inbound Extension Blacklist - This list allows you to limit the file types that are allowed INTO the mail server as attachments. Out of the box this list is empty — nothing is blocked by default. For example, many email administrators choose to add executable files (EXE) since they can cause issues on the mail server, and possibly across an entire network. To add a blacklisted file type, simply type in the file extension, one per line. (E.g., .exe or EXE)
• Outbound Extension Blacklist - This list allows you to limit the file types that users are allowed to send OUT OF the mail server as attachments. Like the inbound list, this is empty by default. For example, many email administrators choose to add batch files (.BAT) since they can cause issues on the recipients' mail server, and possibly across their entire network. To add a blacklisted file type, simply type in the file extension, one per line. (E.g., .bat or BAT) If a user attempts to send an email or create a calendar appointment invitation that contains a blacklisted file extension, the outbound delivery of that message or invite is blocked.
• Extension Blacklist for Uploads - Unlike the two lists above, this one ships with a substantial default list of roughly five dozen extensions already blocked — covering executables and installer formats (.exe, .msi, .msix, .app, .appx), shell and script files (.bat, .cmd, .ps1, .sh, .vbs, .js, .py, and similar), and a handful of web/server script types (.php, .asp, .aspx, .cgi). It's possible to add more extensions on top of that default list, and anything in this list cannot be uploaded to the server across any area. This includes files uploaded to File Storage, attachments to calendar appointments, contacts, contact groups, tasks, and notes, as well as files added to signatures or uploaded via chat or in Online Meetings. Essentially, any area that allows a file upload. (This list does not apply to standard email attachments — those are governed separately by the Inbound/Outbound Extension Blacklist above.) System administrators may want to add further extensions here to limit the capabilities of users to upload certain file types that can possibly be used to cause problems on the server. To exclude the ability to upload files without a file extension at all, check the box labeled Block files without an extension, which is enabled by default.
• File System Restrictions - These are generally file, folder, and user restrictions for Windows Server as the items listed are reserved device names, etc. that carried over to Windows from MS-DOS. While most aren't used anymore, the restrictions still apply to Windows. Linux admins can potentially clear out this list as needed, though it remains part of the default installation of SmarterMail.

External Senders

SmarterMail has the ability to notify users when an email they receive has originated from an account outside of their organization and/or their domain. For example, financial institutions like to be notified if an email comes from someone outside of their own company, and that's where the External Sender text comes in handy.

It's important to understand exactly how SmarterMail decides a message is "external," since the feature does not inspect SPF, DKIM, or DMARC results. Instead, the check is a domain-match comparison performed at delivery time: if the message was submitted over an authenticated SMTP session (the sender logged in with a valid username and password), it is always treated as internal, regardless of the sender address used. Otherwise, SmarterMail looks at the sender's domain (from the Sender header, falling back to the From header, and cross-checked against the Return-Path domain) and compares it against the recipient's own domain, that domain's configured aliases, and any domains added to the External Senders whitelist. If the sending domain matches any of those, the message is considered internal and no external-sender text is added; if it doesn't match, the message is flagged as external. In practice this means a spoofed message that simply forges a From address at the recipient's own domain, but isn't authenticated and doesn't otherwise match, will still be flagged as external — which is exactly the scenario (look-alike or forged internal senders) this feature is most useful for catching.

That said, some organizations like for their users to be able to manage the accounts this text appears on, without disabling it entirely. For those organizations, SmarterMail allows system administrators to give domains the ability to override this setting. In addition, system administrators can select where to add external sender text: It can be appended to the body of the message or the subject line.

• Allow domains to override external sender settings - When enabled, domain administrators can modify the settings made by system administrators, customizing them for their own users.
• Add text to body - When enabled, this will add a text box to the body of the message that cautions the recipient that the email originated outside their own domain, and to take caution when clicking links or opening attachments. By default this reads: "CAUTION: This email originated from outside of this organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe." Note that calendar invitations are exempt from having this text added to the body.
• Add text to subject - When enabled, this adds the text "[EXTERNAL SENDER]" to the subject line of the message — for example, an email with the subject "Invoice Due" would arrive as "[EXTERNAL SENDER] Invoice Due".

Spool

• SubSpools - SubSpools are within the spool path and allow SmarterMail to work around the NTFS limitation of 30,000 objects in an individual folder. SmarterMail will utilize subspools by evenly distributing mail among the subspools, allocating up to 10,000 messages per subspool. If the subspool count is set to 1, the Spool folder will be used.
  Note: If the subspool count is lowered, the old subspool folders will not be automatically deleted; however, you may manually delete the unused subspool folders if you wish. This design is to accommodate for situations where the subspool count is lowered while mail is still processing in those folders. (Default value is 10)
• Delivery Delay (Seconds) - This number of seconds mail will be held in the spool before it is delivered. A delivery delay is beneficial when you are running a secondary service (such as a virus checker) that needs access to messages prior to delivery, as it provides ample time for the secondary service to interact with the message. By default, the delivery delay is 1 second.
• Retry Intervals (Minutes separated by commas) - When the mail server is unable to contact the receiving server, the email attempting to be sent is held for a period of time before the mail server attempts to resend it. This is the time between retries. Users can specify multiple retry attempts to resend emails before it is bounced. By default, this is set to 16 attempts - at 1, 5, 5, 15, 30, 30, 30, 30, 60, 90, 120, 240, 480, 960, 1440, 2880.
• DNS Errors Before Bounce - The maximum number of attempts SmarterMail should make before the message is bounced due to a DNS error. The most common cause of a DNS error is a misspelled domain. Limiting the number of attempts before DNS errors are bounced is beneficial because messages will not sit in the queue for long periods of time taking up processing on the mail server and possibly slowing the system down. This will be helpful to users because messages will be bounced sooner and will give users the opportunity to fix any mistakes and get a message resent. By default, the server will make 2 attempts. Note: Setting this at 1 retry can be dangerous if the DNS server fails or if there is a loss of Internet connectivity. To disable this feature, set the number of bounces equal to the number of retry intervals — for example, if there are 16 retry intervals configured, setting DNS Errors Before Bounce to 16 means a DNS error will never bounce a message early; it will simply keep retrying on the normal schedule until the retries are exhausted like any other delivery failure.
• Notify Senders of Delay After (Attempts) - Sets the number of delivery attempts before the sender is notified that the email delivery is delayed. This can be beneficial as it lets the sender know that the mail server is still attempting to deliver the message but that the recipient has not received it yet. (Default value is 0.)
• Max Local Delivery Threads - Enter the maximum number of messages that can be sent at one time to email addresses that are on the local server. If a message cannot be sent, the server's multi-threading capabilities will move on to the next message and eventually get back to the one it skipped. This action can save tremendous amounts of time when compared to some other mail servers that stall the spool if a message cannot be sent right away. (Default is 50)
• Command Line File - Move the slider to the right to enable this option. Then enter the name of the file used to process incoming messages. Use %filepath as an argument to pass the path of the email file to the executable. It is allowable for the executable to delete the message to prevent delivery. Example: If you set this field to "c:\program files\myexe.exe %filepath" on Windows, the program myexe.exe will be launched with the full path to the spool file as its first argument.
• Script Arguments - As with any command-line action, arguments can be added to provide more context or to tell the command line how you want it to act. NOTE: Not all command-line areas support the use of arguments.
• Command-Line Timeout (Seconds) - The number of seconds that the server will wait for the command-line executable to finish running before giving up on it. By default, the timeout is set to 5 seconds.

Message Archiving

By default, SmarterMail does not archive messages for new installations. System administrators need to set up rules for archiving domains — either all domains or for individual domains, depending on need. To specify which domains on the SmarterMail are archived, the system administrator will need to create archiving rules on each domain's Configuration card when the domain is added to the server. (Or edit each domain individually if it's already been added to the server.)

Alternatively, a rule can be created that will archive messages for all domains on the server. To create a rule for archiving all domains, use the Settings button.

By default, SmarterMail will set an archive path, which will match the default data path set up when SmarterMail was installed. (This is generally c:\SmarterMail\Archive.) However, that path can be edited as needed. Then, it's possible to select which messages are archived: all messages, inbound messages, or outbound messages. Finally, set the Archive Auto-Clean rules.

Creating Message Archiving Rules

When adding or editing a message archive settings, the following settings will be available:

• Archive Path - The directory on the hard drive in which archived messages are saved.
• Direction - Set the direction of the messages you want added to the Archive. The following Rules are available:
  • Save All Messages
  • Save Inbound Messages
  • Save Outbound Messages
• Archive Auto-Clean - How long to store messages in the archive before they're automatically deleted from the server.

Once email archiving is set up, both system administrators and domain administrators can search the archives.

Archive Auto-Clean Defaults

Regarding auto-clean rules, this is purely dependent on need and business rules. Administrators can elect to purge messages in yearly increments, from 1 to 10 years. They also have the opportunity to disable auto-clean entirely by selecting "Never". Realize, however, that never cleaning out the archive can take up quite a bit of space, so plans should be made accordingly.

The default that gets applied depends on how the rule came to exist. Brand-new archive rules, created fresh on a new installation (or added for the first time on an existing server), default their Archive Auto-Clean value to five (5) years. Rules that were already in place before an upgrade, however, are deliberately left set to Never during the upgrade process, specifically so that an administrator's existing, un-cleaned archive doesn't suddenly start having older messages purged out from under them as a side effect of applying an update. In other words: new installs and brand-new rules start at 5 years; pre-existing rules carried forward through an upgrade start at Never, and an administrator who wants those older rules to actually start expiring old messages needs to go in and set a specific retention period explicitly.

Footer

System administrators can configure server-wide message footers that SmarterMail will append on all incoming and outgoing messages. Messages that a SmarterMail user forwards that already has a footer will not have the system footer appended as well. Although similar to signatures, message footers are typically used to convey disclaimers or provide additional information. For example, a system administrator may want every message to include a notice that the message was scanned for viruses or the text "Sent by SmarterMail."

• Enable footer for all messages - Move the slider to the right to turn on the message footer for all incoming and outgoing messages. This setting does not need to be enabled to allow domain administrators to override. If domain admins do override this setting and it's enabled for all messages, emails will have the domain footer on outgoing messages but still have the system footer on incoming messages.
• Apply to mailing lists - Move to slider to the right to enable this setting and append the message footer to mailing list messages.
  Note: Mailing lists have their own configurable footers. If a custom mailing list footer is already configured, enabling this option will append a second footer at the end of each message posted to the mailing list subscribers. Because this may be confusing for mailing list moderators and recipients, most administrators will choose to keep this option disabled.
• Allow domains to override footer - Move the slider to the right to enable this setting and allow domain administrators to configure a unique message footer for their domain.
• Footer - Use this section to create the message footer text. Clicking the edit icon will open a modal that includes an HTML-based editor, allowing admins to create footers that seamlessly fit into any email message.
  Note: The message footer does not support the use of variables.

Block Authentication by Country

Part of a system administrator's job is making sure bad actors can't attempt to brute force logins to user accounts. Blocking authentication attempts from specific countries, or ONLY ALLOWING authentication from specific countries, is one way of doing this. Adding a country to the setting will just block authentication attempts, it won't impact sending or receiving messages from the country. It will simply prevent anyone from the country(-ies) logging into the server, regardless of protocol. Use this card to specify the following:

It's worth noting that if an entire country is blocked, but an IP within that country is added to the server's Whitelist, that IP will NOT be blocked as the Whitelist takes priority over any country-based rule — this is enforced before the country check even runs, so a whitelisted IP is never evaluated against the blocked-country list at all. For example, if you blocked the entirety of Albania, but added a single IP address that falls within Albania's block to the Whitelist, that IP will be able to authenticate to the server. No other Albanian IPs will be able to authenticate. (No offense meant to Albania — it simply appears towards the top of the list of countries.)

Also note that country blocking is only ever evaluated for connections arriving from a public IP address. Authentication attempts coming from a private, intranet-range IP address (for example, a LAN client connecting directly to the server) are never subject to country blocking, regardless of how this card is configured, since there's no meaningful "country" for a private address to be blocked from. Because this feature is entirely IP-geolocation based, a practical safeguard before blocking a country you administer from is to first add your own known administrative IP address (or IP range) to the Whitelist — that way, even if your own location's country later gets added to (or is already part of) a block list, your specific access is preserved.

• Countries to Block - Use this dropdown to select "Specified Countries" or "All But Specified Countries". When selecting "Specified Countries", authentication attempts attempted from the country(-ies) that are selected will be blocked. When selecting "All But Specified Countries", only authentication attempts from the selected country(-ies) will be allowed. Attempts from any other country will be blocked. For example, a small business that only ever expects staff to log in from one country could pick "All But Specified Countries" and select just their own country, blocking authentication attempts from everywhere else in the world.
• Country - Use this dropdown to select one or more countries, based on the block type selected.

Mailbox Migration

The ability to set the number of threads used when migrating a mailbox can help speed up that migration (more threads = faster processing), but it can also impact the performance of the mail server if too many threads are dedicated to migrations. This setting allows the system administrator to manage the number of threads used for migrating accounts over to SmarterMail. For example, migrating hundreds of mailboxes from an old mail platform overnight might call for a higher thread count to finish faster, while a server that also needs to keep serving live user traffic during business hours would want a lower thread count so migrations don't compete too heavily for CPU and disk i/o with everyday mail delivery.