User Tools

Site Tools


mantisbt:plugins:emailreporting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mantisbt:plugins:emailreporting [2019/09/07 16:16]
SL-Gundam [Configuration options]
mantisbt:plugins:emailreporting [2020/04/07 15:28]
SL-Gundam
Line 155: Line 155:
 Name: Maximum size of the description or note being added to the issue Name: Maximum size of the description or note being added to the issue
  
-Description: This is the maximum size allowed for the description or a note. The choice was made to make the default 65535 bytes because that used to be the default for old MantisBT versions prior to mid 2007 using MySQL. __New__ MantisBT installations after mid 2007 will be able to store upwards of 1 million bytes. Even more depending on which database backend you use. As updating the schema does __not__ update the column size in question this would be a good default that would not cause problematic issues+Description: This is the maximum size allowed for the description or a note. The choice was made to make the default 60000 bytes because 65535 used to be the default column length for old MantisBT versions prior to mid 2007 using MySQL. Since we need some overhead we lowered 65535 to 60000. __New__ MantisBT installations after mid 2007 will be able to store upwards of 1 million bytes. Even more depending on which database backend you use. As updating the schema does __not__ update the column size in question this would be a good default that would not cause problematic issues
  
-Of course you can increase this if you want. Just make sure that your MantisBT database is using a column type in which this will fit+Of course you can increase this if you want. Just make sure that your MantisBT database is using a column type in which this will fit. This is usually the case if you MantisBT installation was created using MantisBT 1.1.x or later
  
 === mail_max_email_body_text === === mail_max_email_body_text ===
Line 353: Line 353:
 Name: Ignore auto-reply emails Name: Ignore auto-reply emails
  
-Description: Ignore auto-reply emails like out-of-office replies+Description: Ignore auto-reply emails like out-of-office replies
 + 
 +Check if the email is an out of the office auto reply by checking the following fields: 
 +   * X-Autoreply 
 +   * X-Autorespond 
 +   * auto-submitted with a value of "auto-replied" 
 + 
 +Based on: https://www.jitbit.com/maxblog/18-detecting-outlook-autoreplyout-of-office-emails-and-x-auto-response-suppress-header/
  
 === mail_remove_replies === === mail_remove_replies ===
Line 455: Line 462:
  
 Description: PHP 5.6 enables by default SSL verification when encryption is applied to the connection. With this you can manipulate that behavior as its not guaranteed that this works properly. Most likely reason that it does not work is if PHP is unable to access the OS-managed cert stores and the OpenSSL variables (openssl.cafile OR openssl.capath) in PHP configuration file are not properly set Description: PHP 5.6 enables by default SSL verification when encryption is applied to the connection. With this you can manipulate that behavior as its not guaranteed that this works properly. Most likely reason that it does not work is if PHP is unable to access the OS-managed cert stores and the OpenSSL variables (openssl.cafile OR openssl.capath) in PHP configuration file are not properly set
 +
 +Please read this "[[https://www.saotn.org/dont-turn-off-curlopt_ssl_verifypeer-fix-php-configuration/|Don’t turn off CURLOPT_SSL_VERIFYPEER, fix your PHP configuration]]"
  
 === erp_username === === erp_username ===
mantisbt/plugins/emailreporting.txt · Last modified: 2020/04/07 15:28 by SL-Gundam