@Joel I was just using gmail on my phone and according to gmail the reply went to the correct address…
Ummmmm, could have been picked up by the spam filter. Can you get a timestamp for when the email was sent, I’ll check the logs to see what happened.
reply-<insert a load of characters here>@filmsoc.warwick.ac.uk?
from:Andrew Maddison firstname.lastname@example.org
to:Filmsoc Forums email@example.com
date:5 May 2015 at 14:05
subject:Re: [Filmsoc] [Shadow the Exec] Outdoor screening replacement
2015-05-05 14:06:00 1YpcXs-0005h0-Nr <= firstname.lastname@example.org H=mail-relay-4.csv.warwick.ac.uk [18.104.22.168] P=esmtp S=8797 id=CAKBdugpBBmO25yXk2TZReUr9-LCo0YKZBJ9SGpVo-AMUW7ArZQ@mail.gmail.com from <email@example.com> 2015-05-05 14:06:00 1YpcXs-0005h0-Nr => 11eef31506c3f28393e2b14bc83df889 <firstname.lastname@example.org> F=<email@example.com> R=discourse_reply_router T=discourse_transport 2015-05-05 14:06:00 1YpcXs-0005h0-Nr Completed
Just pulled that log from the email server, its claiming that your email had a from header of
firstname.lastname@example.org, for discourse would have rejected it.
MIME-Version: 1.0 Sender: email@example.com Received: by 10.96.94.228 with HTTP; Tue, 5 May 2015 06:05:51 -0700 (PDT) In-Reply-To: <firstname.lastname@example.org> References: <email@example.com> <firstname.lastname@example.org> Date: Tue, 5 May 2015 14:05:51 +0100 Delivered-To: email@example.com X-Google-Sender-Auth: QU-i1gY7DWfqZbN60Sn0oEntWRw Message-ID: <CAKBdugpBBmO25yXk2TZReUr9-LCo0YKZBJ9SGpVo-AMUW7ArZQ@mail.gmail.com> Subject: Re: [Filmsoc] [Shadow the Exec] Outdoor screening replacement From: Andrew Maddison <firstname.lastname@example.org> To: Filmsoc Forums <email@example.com>
Right, it looks like the mail server had a moment and locked up. This stopped discourse picking up any of the emails, (which have now arrived).
I’m gonna see if there is something that can be done to prevent this in the future.