Knowledgebase
Application Settings
Review application settings and tweak it according to the requirement.
Menu Navigation: Settings - Application Settings
Menu Navigation: Settings - Application Settings
General Settings
Fields
| Field | Description |
|---|---|
| Force Secure URL | Enable it if you want all links to be forcibly redirected to https
Warning! It will redirect to your primary domain in any case. e.g. https://yourmumaradomain.com. This means your primary domain will be exposed if even if you are using CNAME redirection method.
|
| Application URL | The URL of Mumara installation. Mumara will automatically set this URL itself and you don't need to manually set it |
| Server IP | The IP address of the server where Mumara is installed. Mumara will automatically detect the IP address itself |
| Time Zone | Set the default timezone of the application. It is the reference timezone for all internal time-based system operations |
| Number of Messages per Connection | It is the number of emails to be sent before re-establishing the connection with the MTA server. In other words, it's the batch size of the emails per persistent connection |
| Delete Campaign Logs After (Days) | The number of days you want the campaign logs to retain. To keep database optimized and light, you may need to delete old and unnecessary campaign logs |
| Hourly Sending Speed | The maximum number of cumulative emails to be sent per hour. (It is an application-level sending rate)
Hourly Speed: Hourly speed is throttling of the emails going out and calculated over nanoseconds. For example, if you have set hourly speed to 60, it means the system will push the emails out at the rate of 1/s. And if Mumara has parallel campaigns running or multiple clients sending campaigns at the same time, Mumara will not exceed the hourly rate combining all campaigns.
|
| Daily Sending Limit | The maximum number of cumulative emails that can be sent from Mumara per day |
| Monthly Sending Limit | The maximum number of cumulative emails that can be sent from Mumara per month |
Mail Settings
Fields
| Field | Description |
|---|---|
| Mail Method | Select PHP default mail function or use SMTP to send systematic/notification emails |
| Sender Name | Name that the email will appear to be sent from |
| Sender Email | The email address that the email will appear to be sent from |
| Reply-to Email | The email address where the replies will be sent, in case if the user replies |
| Email Global Header | HTML codes that will be automatically inserted at the top of every email going out |
| Email Global Footer | HTML codes that will be automatically inserted at the bottom of every email going out |
| Force Unsubscribe Link | If you want to make unsubscribe link insertion into broadcasts mandatory to your clients |
Sending Domain Settings
Fields
| Field | Description |
|---|---|
| Default DKIM selector | The default selector for the domain keys that appears after adding a sending domain |
| Default Tracking Domain Prefix | The default subdomain for tracking purpose after adding a sending domain |
| Domain Key Size in Bits | Size of the domain keys generated after adding a sending domain |
| Require Domain Ownership Verification | Enable if you want Mumara to verify the ownership of the sending domain name before it can be used Verify Ownership: In this case, the user will need to verify the ownership of the domain by uploading a file that Mumara randomly creates or by adding a txt record in the domain's DNS.
When you enable this option, Mumara will further ask you about the previous domains i.e if you want the already added domains to be set as verified or unverified. |
Broadcast Settings
Fields
| Field | Description |
|---|---|
| Auto resume broadcasts upon connection reestablishment | When the connection with a sending node fails during a running broadcast, Mumara auto pauses the broadcast. Enable it if you want Mumara to auto-resume the system-paused broadcasts if the connection with sending node has been restored |
| Recheck auto-inactive sending node connection after every | After how many minutes Mumara should recheck the connection with a failed sending node
Auto-Inactive: Any sending node that has failed during a running broadcast will be set as Auto-Inactive and Mumara will just try to re-check connection for auto-inactive sending nodes.
|
| Recheck auto-inactive sending node connection for | How long Mumara should keep trying to re-establish the connection for auto-inactive sending nodes |
| Ignore Duplicate Opens for | In some cases, you'll need to ignore duplicate opens if occured too rapidly. e.g bot opens |
| SMTP Driver | Select the SMTP Module i.e. PHPMailer or SwiftMailer |
Segment Settings
Fields
| Field | Description |
|---|---|
| Chunk Size | To avoid overloading the system, Mumara processes segments in parts/chunks. Define here the number of records to process per chunk. |
| Delay Between Chunks | For optimal performance, define the sleep time in seconds between two chunks |
| Delete Exported Segments After | Number of days after the exported segments files from the server should be deleted |
Trigger Settings
Fields
| Field | Description |
|---|---|
| Number of executions per cronjob | The maximum number of executions that a single cronjob should handle. Set -1 for unlimited |
| Number of records to process per execution | The number of records to process per execution. Default is 20 to keep server load optimized |