Personalised mails, content very depending on mail client
As I am testing personalized mails from Mailman (2.1.12) I was wondering why various email clients display the content different.
If I send an HTML mail containing only text, both Gmail and Outlook includes personalization in msg_header "Hello %(user_name)s . This is a test"If I send an HTML mail containing an image, Gmail shows "Hello [member's name]. This is a test" on top and the rest of the mail, including image, but Outlook only show the e-mail (including the image), NOT the msg_header not msg_footer.If I use Outlook to email received on Gmail, using IMAP connection, "Hello [member's name]. This is a test" is displayed at the top of the received mail, but the content from the sender and the image is attached.
My content filtering -> pass_mime_types are multipart/mixed multipart/alternative text/plain text/html
but pass_mime_types shouldn't affect the mail as content filtering -> filter_content if off. Also collapse_alternatives or convert_html_to_plaintext doesn't change a thing (as content filtering -> filter_content if off).
Is there something I, as site admin, or the list-admins can do, to get personalized HTML mails, even to Outlook users?
Henrik Rasmussen
On 10/03/2016 07:06 AM, Henrik Rasmussen wrote:
Is there something I, as site admin, or the list-admins can do, to get personalized HTML mails, even to Outlook users?
You can set Non-digest options -> personalize to Full Personalization which will cause delivered non-digest messages to be addressed To: the recipient, and not try to use msg_header for this purpose.
As far as brain dead MUAs not properly rendering multipart messages with msg_header and or msg_footer added, see https://wiki.list.org/x/4030707.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you.
According to the article paragraph "Patching Mailman to solve this problem", a user found a solution to the problem in version 2.1.5, but would Mailman 3 handle this in a better way to work around the problem with some MUAs? Would upgrading be a better option to solve this?
Med venlig hilsen Henrik Rasmussen Systemadministrator, Core Services KØBENHAVNS UNIVERSITET Koncern-it, Drift & Support, Infrastruktur Nørregade 10, postboks 2177 1017 København K
Tel: 35322626 Dir 35322704 Fax 35322707 Email: her@adm.ku.dk Web: it.ku.dk
Har du brug for hjælp eller har spørgsmål af enten faglig og teknisk karakter, er du velkommen til at hendende dig til Servicedesk ved at oprette en sag i KUnet’s selvbetjeningssystem: "KUnet → Selvbetjening → It-service → Min Servicedesk → Opret Sag", eller ringe til Servicedesk på telefon 35 32 27 00. Du er også velkommen til at sende en mail til it-service@adm.ku.dk. KUnet’s selvbetjening findes på adressen http://sd.ku.dk.
-----Oprindelig meddelelse----- Fra: Mailman-Users [mailto:mailman-users-bounces+her=adm.ku.dk@python.org] På vegne af Mark Sapiro Sendt: 5. oktober 2016 06:19 Til: mailman-users@python.org Emne: Re: [Mailman-Users] Personalised mails, content very depending on mail client
On 10/03/2016 07:06 AM, Henrik Rasmussen wrote:
Is there something I, as site admin, or the list-admins can do, to get personalized HTML mails, even to Outlook users?
You can set Non-digest options -> personalize to Full Personalization which will cause delivered non-digest messages to be addressed To: the recipient, and not try to use msg_header for this purpose.
As far as brain dead MUAs not properly rendering multipart messages with msg_header and or msg_footer added, see https://wiki.list.org/x/4030707.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/her%40adm.ku.dk
On 10/05/2016 01:44 AM, Henrik Rasmussen wrote:
According to the article paragraph "Patching Mailman to solve this problem", a user found a solution to the problem in version 2.1.5, but would Mailman 3 handle this in a better way to work around the problem with some MUAs? Would upgrading be a better option to solve this?
Our position is this patch in particular, and probably any patch, is not robust enough for general use. Adding msg_header and msg_footer to a MIME multipart message with possibly multiple text/plain and text/html parts by merging the msg_header and msg_footer into existing text/plain and text/html parts is very difficult to get right which is why we only do it if there is only a single text/plain part to merge into.
Just as MUAs (Outlook) have difficulty determining what's the message body and what's an attachment, we would have the same difficulty in determining to which part(s) to add the header and footer, plus the fact that in general, determining how to add the header and/or footer to an HTML part with styles and multiple <div>s is not easy.
Mailman 3 is not going to be significantly different from Mailman 2.1 is this respect.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Henrik Rasmussen writes:
Is there something I, as site admin, or the list-admins can do, to get personalized HTML mails, even to Outlook users?
There is nothing you can do about the header/footer as admin. Mailman is not changing the mail since you can see the expected in GMail. See Mark's post for other aspects of personalization.
As sender, you can change the MIME structure of the email. Why some MUAs are happy with it but Outlook is not, you would best ask on an Outlook channel. One hint: If you are using Apple Mail, stop that. Apple Mail uses a perfectly conforming MIME structure that makes it difficult for some MUAs to extract attachments anyway, and would probably aggravate this issue, too. Specifically, it uses structure like this:
multipart/alternative
text/plain
multipart/related # or something like that
text/html # refers to content-ids of inline MIME parts
image/jpeg; content-id=1
audio/mpeg-3; content-id=2so that people who have text/plain-only MUAs (or settings) won't "see" the attachments at all in many cases.
I'm not sure what wrapping that in a multipart/mixed:
multipart/mixed # Mailman wrapper for header/body/footer
text/plain # Mailman header text
multipart/alternative
text/plain
multipart/related # or something like that
text/html # refers to content-ids of attachments
image/jpeg; content-id=1
audio/mpeg-3; content-id=2
text/plain # Mailman footer textshould be interpreted as. I know what *I* would do (display the text parts like HTML <P> elements with some default style, and the HTML as HTML), but Microsoft. *shrug*
Good luck, and may your next year have no Microsoft mail software in it!
Steve
participants (3)
-
Henrik Rasmussen -
Mark Sapiro -
Stephen J. Turnbull