Long name of the attachemnets in mailman list
Hello everyone,
Recently, when I sent to our mailing list (using mailman) a message with a attachment with a long name ("VEF Annual Conf 2009 - Announcement - Fellows & Visiting Scholars.pdf") . As a recipient, I received the attachment with the name that has been changed to ATT00462.pdf. The content of the attachment had not been changed. So, I have some questions that I hope someone can answer:
Does the mailman automatically rename the attachment due to thelong name of the attachment?
If yes, how long should the name of the attachment be so that itwould not be changed by mailman?
If no, could you please explain to me the reason why the name hadbeen changed?
I would appreciate your reply soon.
Thanks,
Tu Ngo
Tu Ngo wrote:
Does the mailman automatically rename the attachment due to thelong name of the attachment?
If yes, how long should the name of the attachment be so that itwould not be changed by mailman?
If no, could you please explain to me the reason why the name hadbeen changed?
This is all controlled by configuration settings. The default settings are
SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = True
SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = False
which means that all stored attachments will have a "made up" name and an extension based on the MIME Content-Type of the attachment.
In order to preserve the original name and extension of the attachment when it is stored, you need to set
SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True
in mm_cfg.py, but this can allow attachments to be stored with names that might not be valid on all systems and with extensions that might disguise the actual content type.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Tu Ngo