Setup Other: Difference between revisions

Jump to navigation Jump to search
Line 57: Line 57:
* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.
* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.


* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add the constant MAIN_FIX_FOR_BUGGED_MTA. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email be be modified and become correct during sending, solving any problem. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com
* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add this constant to 1. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email be be modified and become correct during sending, solving any problem. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com


== Module Tiers ==
== Module Tiers ==

Navigation menu