Email notification, mail to members and member validation emails are all borked. It looks like mails are coming through in batches. For example, last night I had a batch of 8 thread reply mails arrive at my mail server at 22:06, but they were sent at times from 20:38 to 21:53. Looking at the following extract from a typical mail header:
Received: from [18.104.22.168] (helo=mail2.magicalia.com) by exim11.blueyonder.co.uk with esmtp (Exim 4.68) (envelope-from <email@example.com>) id 1Jo002-0006pq-5E for xxxxxxxxxxxxx; Mon, 21 Apr 2008 18:40:18 +0100Received: from mail pickup service by mail2.magicalia.com with Microsoft SMTPSVC; Mon, 21 Apr 2008 15:20:49 +0100From: <firstname.lastname@example.org>
That's a delay of over three hours.
I know that it's not the blueyonder servers that are causing the problem, as I changed my email address in my forum profile to point to my own mail server. Similar delays are seen. Indeed, it took over three hours for the validation email to arrive. I note from my mail logs that when you enter a new email address the domain is checked by the forum software by doing an SMTP connect to the destination mail host. This is done on the fly, so there's no question that the mail server can be reached.
Please could someone look into this?
I have flagged this up with our tech guys - we've been experiencing problems with this since the close of last week. Unfortunately it's the same for our race confirmation emails too.
Hope to have an update for you soon... thanks for your patience.
Sorry about the continued delays. Our server is just really struggling to keep up with the volume of automated emails at present. Hopefully I'll have news of a proposed upgrade soon to resolve this.
Catherine, I have a suggestion for you to pass to the Magicalia gnomes...
The way it works right now is that the number of mail messages generated is the number of subscribers to the thread for each subscriber to the thread. The total must be quite large. Essentially, though, what we really need is to be notified when a post has been made to a thread we are watching since the last time we looked at the thread. We only need to be told the first time. Here's the suggestion:
The effect of this is that even if 20 posts have been made to the thread since the last time you looked at it, you will only receive one notification. Surely, though, that is all you need. Having read the thread, the notification is ready to be triggered again.
I hope this idea is useful.
Needless to say, when I typed that suggestion my brain was going faster than my fingers. What I meant to type was:
the number of mail messages generated is the number of subscribers to the thread for each new post to the thread.
Note that there would be an additional DB write for each thread view, and for really busy threads -- the ones that resemble real-time chats -- there would not be as much of a reduction of mail to the currently active participants in the thread. I still reckon it could substantially reduce mail load though. There are potential ways of getting round the real-time chat thing, but they make the solution more complex. They would be an option if the simple version didn't produce sufficient benefit though.
Visit the official Runner's World page
Follow Runner's World on Twitter
Other Natmag-Rodale Sites
Run For Charity
About Runner's World
Runner's World is a publication of Hearst Magazines UK which is the trading name of The National Magazine Company Ltd, 72 Broadwick Street, London, W1F 9EP. Registered in England 112955. All rights reserved.
Website powered by: Immediate Media Company Ltd. | © Runner's World 2002-2014 |