31,003
edits
Setup Other: Difference between revisions
Jump to navigation
Jump to search
m
→For SaaS / Cloud hosting integrators
Tags: Mobile edit Mobile web edit |
Tags: Mobile edit Mobile web edit |
||
| Line 1,044: | Line 1,044: | ||
*'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)'' | *'''MAILING_LIMIT_WARNING_PHPMAIL''' ► Set this value to a translation key. Then add translation keys into the instance so user will see a message when into the email setup page. For example, you can set a message to say ''Warning: To avoid abuse, when using default setup, you are restricted to 500 emails per day for all your application (account may be suspended in case of violation of this rule. You can setup application to use your own SMTP server for sending email so you want have no restriction at all (see menu Home-Setup-Emails)'' | ||
*'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock so the administration tools like install.php and repair.php can't be used on your customer instance (until the lock file is deleted). | *'''MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE''' ► If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock and remove the upgrade.unlock so the administration tools like install.php and repair.php can't be used on your customer instance (until the lock file is deleted). | ||
*'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email: | *'''MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS''' ► (A better name of this option should be MAIN_EXTERNAL_MAIL_CLIENT_IP_ADDRESS). Set here the list of IPs where your Dolibarr instances are hosted. So when your customer go into the setup area of email: | ||