[OSGeo] #3073: Discourse email having malformed text

#3073: Discourse email having malformed text
--------------------------------+-----------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Keywords:
--------------------------------+-----------------------
I see backslashes in discourse emails, see
You're invited to talk on Matrix

I noticed those emails are multipart with TEXT and HTML versions, the
broken one is the TEXT version which I instruct my MUA to prefer.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* Attachment "screenShotMalformed.png" added.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):

See how bad it is:

[[Image(screenShotMalformed.png)]]
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by robe):

I assume this must be what you are getting via email?

Cause the mirror record looks fine -
https://discourse.osgeo.org/t/osgeo-3039-problems-with-sending-overflow-
attachments/4711

Maybe it's the setting on discourse to prefer html send doing it. It was
set that way and I was tempted to change it to plain text, but there
doesn't seem to be a setting for that per category, just a global one.
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by robe):

The settings I am referring to are here -
https://discourse.osgeo.org/admin/site_settings/category/email

Incoming email prefer html: yes

I should also add, the default behavior of discourse for

**trim incoming emails**
Trim part of the incoming emails that isn't relevant.

Was set to true. Having this be true, made all trac emails have the body
chopped off, cause I guess the ----- that trac uses in email was some sort
of signaling to it to ignore the rest of the message.

I also had changed the osgeo trac mail encoding when I was troubleshooting
the above issue to quoted-printable. I've changed that back to base64 to
see if that fixes this issue.
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by robe):

@strk are you seeing problems in other emails besides trac? I know there
are issues with trac mail which I haven't figured out. I'd be more
concerned if you are seeing issues with other mail.
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* Attachment "mutt-mail-good.png" added.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* Attachment "mutt-mail-bad.png" added.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* Attachment "mutt-mail-bad.png" added.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* Attachment "mutt-mail-good.png" added.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):

Yes, see the difference:

[[Image(mutt-mail-good.png)]]
[[Image(mutt-mail-bad.png)]]

I clearly don't need all that markdown or HTML in the text/plain version
of the email from Discourse.

BTW: I receive a multipart/alternative both from Mailman and from
Discourse (I guess that's how Vicky sent that mail), but the Mailman
version of the text is correctly formatted
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* Attachment "mutt-mail-bad.png" added.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by robe):

Ah I see what it's doing. Looks like it's trying to markdownify the
email.

Maybe If we turn off prefer html incoming or something that will help.

#this by default is on. I just turned it off.

incoming email prefer html
Use HTML instead of text for incoming email.
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):

I think my problem is with outgoing, not with incoming ?
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by robe):

Well I didn't see a setting for outgoing so thought it maybe formats the
incoming and sends it outgoing. So it's the incoming formatting that is
causing the outgoing format to be screwy.
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):

The thing is that the original email is the same that goes into Mailman
too, but following that path lands to me in perfect shape. I guess we
should report this upstream. Now it would be nice if those who proposed
Discourse in the first place took on some responsibility to make it
behave...
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: defect | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* type: task => defect

--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: defect | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):

Upstream ticket (a topic in the upstream "bug" category):
https://meta.discourse.org/t/html-entities-and-escape-characters-in-text-
plain-outgoing-email-alternative/290637
--
Ticket URL: <#3073 (Discourse email having malformed text) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse email having malformed text
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: defect | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):

The upstream ticket is unanswered for 4 days now, I suspect neither
Discourse dev nor Discourse proponent care about email mediated
communication, making this problem's only possible fix being a "scratch
your own itch" project.

I'd rather avoid Discourse for anything I rely upon (trac tickets being
one of those things) so hopefully I can be selective about what I want or
don't want to receive by mail from it.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3073#comment:12&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3073: Discourse text/plain email use html entities, markdown and backslash-
escapes for no reason
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
     Type: defect | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Changes (by strk):

* summary: Discourse email having malformed text =>
     Discourse text/plain email use html entities, markdown and backslash-
     escapes for no reason

--
Ticket URL: <#3073 (Discourse text/plain email use html entities, markdown and backslash-escapes for no reason) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.