Paul Arenson writes:
The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful.
The user's MUA probably used embedded content in the HTML, while yours used a MIME attachment. I don't think our email package looks inside the HTML. It's also possible that the user's image was an embedded link to a network resource.
As well, links were weird.
It came out double as
https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">")
I believe that this is an MUA issue, not Mailman. Mailman doesn't touch content at that level. It optionally
(1) removes MIME parts as wholes, (2) converts whole text/html parts to text/plain (3) adds a header before the main content part without touching the main content, or (4) adds a footer after the main content part without touching the main content.
None of these can affect the main content except (2), but I believe you have this feature configured OFF.
I don't know much about these problems. It's really not possible to diagnose either of these problems without access to the emails.
QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients?
It's a client question.
One client that is always available with Mailman is HyperKitty. The most recent versions of HyperKitty will format Markdown in plain text mail. I'm not familiar with the particular flavor of Markdown used though.
Note: Markdown is only relevant to plain text mail, not HTML or other kinds of "rich text". It also is *only* useful in HyperKitty (and a few other clients used by a few programmer types).
So are there guidelines one whether/how to attach an image so that it makes it?
No. It should just work. It's possible you need to add the string 'image' to the mailing list's 'pass_types' attribute, or delete strings starting with 'image' from the mailing list's 'filter_types' attribute. Unfortunately, as far as I can see those are not accessible from the web interface.
Steve