#3072: Discourse emails do not contain real sender email
--------------------------------+-----------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Keywords:
--------------------------------+-----------------------
This is something we recently fixed with Mailman by not modifying the From
and thus allowing recipients to check the authenticity of the email
(DKIM).
Instead the Discourse emails are back to hiding the real sender email.
See You're invited to talk on Matrix
uAKfYW2-yINP5uuiMV4ihVT7M?via=osgeo.org&via=matrix.org&via=dend.ro
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3072>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3072: Discourse emails do not contain real sender email
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by robe):
I'm not sure if much can be done about this, but will investigate.
I don't find this to be totally a bad thing. Cause I hate it for example
when someone starts a conversation on a mailing list, and then somehow I'm
the only one being sent the email and it falls off the mailing list. Most
of the time it's not intentional, they just forgot to do reply all or
something. That kind of stuff has been happening more often recently.
I'd much prefer mailing list topics stay on the mailing list/category.
--
Ticket URL: <#3072 (Discourse emails do not contain real sender email) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3072: Discourse emails do not contain real sender email
--------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: |
--------------------------------+------------------------
Comment (by strk):
I think every MUA honours a Reply-To header, we don't need to abuse RFC822
to prevent what you are describing. REF:
RFC 822 - STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
--
Ticket URL: <#3072 (Discourse emails do not contain real sender email) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3072: Discourse emails do not contain real sender email
--------------------------------+------------------------
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: <#3072 (Discourse emails do not contain real sender email) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.