User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

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 revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
mantisbt:plugins:emailreporting [2018/06/05 17:57] – [MantisBT Configuration options] SL-Gundammantisbt:plugins:emailreporting [2020/01/24 13:15] SL-Gundam
Line 102: Line 102:
 It's possible to run into database query errors if you've incorrectly setup some maximum size settings in PHP, and MantisBT It's possible to run into database query errors if you've incorrectly setup some maximum size settings in PHP, and MantisBT
  
-EmailReporting and MantisBT uses the following to decide what the maximum attachment size is that should be supported (MySQL variable is not used for this decision)+EmailReporting and MantisBT use the following to decide what the maximum attachment size is that should be supported (MySQL variable is not used for this decision)
  
 ^ Where    ^ Configuration option     ^ Help information                                                ^ ^ Where    ^ Configuration option     ^ Help information                                                ^
Line 114: Line 114:
 As for the MantisBT $g_max_file_size. That one is very important if you've setup EmailReporting to save attachments in the database instead of on the disk. MySQL/MariaDB for example also have limits on the amount of data that is allowed in one insert statement which could generate an error (see max_allowed_packet above). If max_allowed_packet is set too low, this could result in the error [[https://dev.mysql.com/doc/refman/8.0/en/gone-away.html|"MySQL server has gone away"]]. As for the MantisBT $g_max_file_size. That one is very important if you've setup EmailReporting to save attachments in the database instead of on the disk. MySQL/MariaDB for example also have limits on the amount of data that is allowed in one insert statement which could generate an error (see max_allowed_packet above). If max_allowed_packet is set too low, this could result in the error [[https://dev.mysql.com/doc/refman/8.0/en/gone-away.html|"MySQL server has gone away"]].
  
-Make sure you set $g_max_file_size to a slightly lower value then your server setup supports (alternatively increase the other mentioned values to be higher then $g_max_file_size). If you need to handle big attachments, make sure MantisBT stores them on the disk, not in the database.+Make sure you set $g_max_file_size to a slightly lower value then your server setup supports (alternatively increase the other mentioned values to be higher then $g_max_file_size and adjust any not mentioned requirements for your setup to handle the increased size). If you need to handle big attachments, make sure MantisBT stores them on the disk, not in the database.
  
 === "From" address for MantisBT Notification emails === === "From" address for MantisBT Notification emails ===
Line 149: Line 149:
  
 Description: Whether or not to delete processed emails from the mailbox. See "[[#mailbox_type|Mailbox type]]" for some more info about its effects Description: Whether or not to delete processed emails from the mailbox. See "[[#mailbox_type|Mailbox type]]" for some more info about its effects
 +
 +Do keep in mind that this option was not meant for archiving purposes. The more emails there are in the mailbox, the higher the run-time for the script everytime it is run. This is especially true for IMAP
  
 === mail_max_email_body === === mail_max_email_body ===
 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 214: Line 216:
  
 Description: With this you can disable MantisBT internal disposable email checker. This will only be changed for EmailReporting, not for the rest of MantisBT Description: With this you can disable MantisBT internal disposable email checker. This will only be changed for EmailReporting, not for the rest of MantisBT
 +
 +=== mail_respect_permissions ===
 +Name: Check user permissions
 +
 +Description: Whether or not EmailReporting should check the permission of the user for adding new issues, notes or attachments.
 +
 +The email will be ignored if a permission check fails for notes or issues, not for attachments. When processing finishes [[#mail_delete|Delete processed email from the mailbox]] will be respected.
 +
 +The default is to ignore permissions because EmailReporting works with the intend to "Process at all costs". If you turn this on it is possible that you will lose emails so should only consciously be turned on.
  
 === mail_add_bug_reports === === mail_add_bug_reports ===
-Name: Create new issues+Name: Add new issues
  
-Description: Whether or not to allow the creation of new issues by EmailReporting. If this is disabled and an email cannot be added as a note, the email will be deleted from the mailbox without further processing+Description: Whether or not to allow the creation of new issues by EmailReporting. If an email cannot be added as a new issue, the email will be ignored without further processing and respect [[#mail_delete|Delete processed email from the mailbox]]
  
 === mail_add_bugnotes === === mail_add_bugnotes ===
Line 320: Line 331:
 Name: Strip signature from email body Name: Strip signature from email body
  
-Description: Strip an email signature from the issues and notes. It will search for a delimiter (see "[[#mail_strip_signature_delim|Delimited by]]") which will mark the start of the signature. Anything below it will be deleted (this includes any other email parts)+Description: Strip an email signature from notes. It will search for a delimiter (see "[[#mail_strip_signature_delim|Delimited by]]") which will mark the start of the signature. Anything below it will be deleted (this includes any other email parts)
  
 === mail_strip_signature_delim === === mail_strip_signature_delim ===
Line 338: Line 349:
  
 Description: Self explanatory i believe. Some users just want to add some attachments to an existing issue. In that case a note is not added but the attachments are. But if this happens for a newly created issue you might wonder what caused it since you would expect the user to inform you of what the problem... maybe he wrote it all in the subject line? Description: Self explanatory i believe. Some users just want to add some attachments to an existing issue. In that case a note is not added but the attachments are. But if this happens for a newly created issue you might wonder what caused it since you would expect the user to inform you of what the problem... maybe he wrote it all in the subject line?
 +
 +=== mail_ignore_auto_replies ===
 +Name: Ignore auto-reply emails
 +
 +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 383: Line 406:
  
 === mail_debug_show_memory_usage === === mail_debug_show_memory_usage ===
-Name: Show the memory usage in different stages of the email processing process+Name: Show the memory usage at various stages of the email processing process
  
 Description: This will show memory usage during several stages of the email processing. This was mostly added to improve memory usage and should normally be disabled Description: This will show memory usage during several stages of the email processing. This was mostly added to improve memory usage and should normally be disabled
mantisbt/plugins/emailreporting.txt · Last modified: 2022/10/23 09:12 by SL-Gundam

Driven by DokuWiki