Access Keys:
Skip to content (Access Key - 0)

How large an attachment can be sent to Request Tracker (RT)?

  • How large an attachment can be sent to Request Tracker (RT)?
  • How big a file can I send to RT?
  • Why is my attachment in an RT ticket truncated?
  • Why is the picture in my RT ticket cut off?

Context:

  • Request Tracker (RT) on help.mit.edu
  • Attachments in RT tickets

Answer:

  • The current message size limit remains 2 MB (two megabytes). This is the maximum allowed size for a message, including encoded attachments.
  • Files (including image files) that are larger will be dropped and an error message will appear in the ticket.
  • You will still see a list of attachments in the ticket so you know what files were dropped and can request they be sent to an alternate address, or shared via Dropbox

This limit is in place because RT stores attachments in the database as objects, and with a very large instance like ours, overly large attachments can cause system-wide problems and issues with service stability.

MIT offers several other tools designed for robust file sharing and exchange, such as Dropbox, that can be used as alternatives to sending them via email.

If this size limit is a serious problem for your work please tell us why by reporting it to the Tooltime Team at tooltime@mit.edu.

IS&T Contributions

Documentation and information provided by IS&T staff members


Last Modified:

July 28, 2021

Get Help

Request help
from the Help Desk
Report a security incident
to the Security Team
Labels:
rt rt Delete
request_tracker request_tracker Delete
c-request-tracker c-request-tracker Delete
c-rt-enduser c-rt-enduser Delete
c-rt-user c-rt-user Delete
c-rt-enduser-attachment-merging c-rt-enduser-attachment-merging Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
Feedback
This product/service is:
Easy to use
Average
Difficult to use

This article is:
Helpful
Inaccurate
Obsolete
Adaptavist Theme Builder (4.2.3) Powered by Atlassian Confluence 3.5.13, the Enterprise Wiki