You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OSM user usera leaves a private message to OSM user userb.
userb receives an email message from OSM with the content of the message that usera sent
userb replies using email client to the message, email client send the email to usera <[email protected]>. The email is successfully sent, as reported by MTA.
usera never receives the message. userb never sees their message in the outbox on OSM web site.
Screenshot(s) or anything else?
I have unsuccessfully tried to reproduce the issue locally, by hand-crafting the email content and piping it to script/deliver-message.
Here are the headers of one reply message as sent by the email client (some portions are replaced with word "redacted")
Date: Fri, 05 Jan 2024 12:51:42 +0100
From: <redacted>
To: redacted <[email protected]>
Subject: Re: [OpenStreetMap] <redacted>
User-Agent: K-9 Mail for Android
In-Reply-To: <redacted>
References: <[email protected]> <redacted>
Message-ID: <001551C3-090C-4D7F-ABE0-D489222AD88E@redacted>
MIME-Version: 1.0
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
body
The text was updated successfully, but these errors were encountered:
milan-cvetkovic
changed the title
Replying to emails does not deliver message to OSM user
Replying to message email does not deliver message to OSM user
Jan 5, 2024
URL
No response
How to reproduce the issue?
usera
leaves a private message to OSM useruserb
.userb
receives an email message from OSM with the content of the message thatusera
sentuserb
replies using email client to the message, email client send the email tousera <[email protected]>
. The email is successfully sent, as reported by MTA.usera
never receives the message.userb
never sees their message in the outbox on OSM web site.Screenshot(s) or anything else?
I have unsuccessfully tried to reproduce the issue locally, by hand-crafting the email content and piping it to
script/deliver-message
.Here are the headers of one reply message as sent by the email client (some portions are replaced with word "redacted")
The text was updated successfully, but these errors were encountered: