allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <d...@brondsema.net>
Subject [allura:tickets] #8191 Remove html-only mailing options
Date Wed, 28 Feb 2018 22:02:01 GMT
- **status**: open --> review
- **assigned_to**: Dave Brondsema
- **Comment**:

Fix on branch db/8191  To review:

* `docker-compose restart taskd` (since it doesn't auto restart like the webapp does)
* `docker-compose logs --follow outmail` to see email output
* check that email goes out as either text only, or multipart text + html, depending on users'
setting
* if someone was on "HTML"-only before, they should now get multipart email and the UI will
show as "HTML" for them.



---

** [tickets:#8191] Remove html-only mailing options**

**Status:** review
**Milestone:** unreleased
**Created:** Tue Feb 27, 2018 06:03 PM UTC by Dave Brondsema
**Last Updated:** Tue Feb 27, 2018 06:03 PM UTC
**Owner:** Dave Brondsema


On /auth/subscriptions/ their are choices for HTML, Plain Text, or Combined emails.  Sending
html-only mails can trigger spam warnings like this one from spamassassin:

    2.3 MIME_HTML_ONLY         BODY: Message only has text/html MIME parts

There's no reason we need to offer HTML-only.  All HTML mail clients can handle multipart
(combined) mails.  So I think we should consider all HTML-only preferences as "Combined".
 And on the preferences page, remove "HTML" and then rename "Combined" to "HTML" (or rich
text / formatted / something better?)


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message