openstreetmap / operations

OSMF Operations Working Group issue tracking
https://operations.osmfoundation.org/
98 stars 13 forks source link

Replying to message email does not deliver message to OSM user #1017

Closed milan-cvetkovic closed 6 months ago

milan-cvetkovic commented 6 months ago

URL

No response

How to reproduce the issue?

  1. OSM user usera leaves a private message to OSM user userb.
  2. userb receives an email message from OSM with the content of the message that usera sent
  3. userb replies using email client to the message, email client send the email to usera <m-dddd-cccc@messages.openstreetmap.org>. The email is successfully sent, as reported by MTA.
  4. 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 <m-1155857-VpmyK4S3@messages.openstreetmap.org>
Subject: Re: [OpenStreetMap] <redacted>
User-Agent: K-9 Mail for Android
In-Reply-To: <redacted>
References: <6597e31f6a8d9_20882e1a902757c4@spike-01.openstreetmap.org.mail> <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
tomhughes commented 6 months ago

This is an operational issue with the correct secret key base not being used when deliver-message is invokved.

tomhughes commented 6 months ago

Actually that wasn't the problem - the problem was that exim was mangling the local part to lower case.

Fixed in https://github.com/openstreetmap/chef/commit/d7e14243b1f2d6e63ea5d6bad5f6578844ac705c.