Mark
Thanks for the link to the test archive. That and your information has clarified things a lot.
Jason
On 7/12/2017 11:39 AM, Mark Sapiro wrote:
On 07/12/2017 04:47 AM, Jason Glazer wrote:
Does anyone know if Hyperkitty can be configured to allow for inline images to be maintained so that an HTML file looks like a normal HTML message?
Also, can attachments to a message under Hyperkitty preserve their name rather than being "scrubbed" into "attachment-*.*" files?
The answer to some of this is at <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DCE...>.
One question unanswered by that post is what happens with an inline image in an HTML message body. In the original message, the image is referenced by an IMG tag with "src=" pointing to the image MIME part. Since this structure is not maintained in HyperKitty, inline images probably don't work.
Also, with respect to Mailman 2.1, if you want the scrubber to preserve file names and extensions, set the following in mm_cfg.py
SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True
and if you want scrubbed HTML to not be HTML escaped so it renders rather than looking like raw html, set
ARCHIVE_HTML_SANITIZER = 3
but note this comment from Defaults.py
# 3 - Remove text/html as attachments but don't HTML-escape them. Note: this # is very dangerous because it essentially means anybody can send an HTML # email to your site containing evil JavaScript or web bugs, or other # nasty things, and folks viewing your archives will be susceptible. You # should only consider this option if you do heavy moderation of your list # postings.
This is an issue with HyperKitty as it appears this is what HyperKitty does and there's no way to turn it off.
-- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists