MyBB Community Forums

Full Version: getting subscription emails twice
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
has anyone else been getting all of their thread subscription emails twice today?

at first I thought it was people who delete their reply and then repost a second time, but the mails actually have the same timestamp, but a different message id, so it seems the mail was indeed sent twice at the same time from mybboard.net.

I'll include the relevant mail header of one duplicate mail, replacing all @ signs with Ä to make it a bit harder for the spammers.

Received: by tango.mybboard.net (Postfix, from userid 1001)
        id 89ADF4E0A61; Tue, 26 Jan 2010 11:09:00 -0600 (CST)
To: frostschutzÄmetamorpher.de
Subject: New Reply to MemCache, eAccelerator, files or DB
From: MyBB Community Forums <contactÄmybboard.net>
Reply-To: contactÄmybboard.net
Message-ID: <11de64a9692bc6a59a95ec833ffbd0eaÄcommunity.mybboard.net>
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: MyBB
X-MyBB-Script: community.mybboard.net/search.php
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Date: Tue, 26 Jan 2010 11:09:00 -0600 (CST)

Received: by tango.mybboard.net (Postfix, from userid 1001)
        id 840304E0A64; Tue, 26 Jan 2010 11:09:00 -0600 (CST)
To: frostschutzÄmetamorpher.de
Subject: New Reply to MemCache, eAccelerator, files or DB
From: MyBB Community Forums <contactÄmybboard.net>
Reply-To: contactÄmybboard.net
Message-ID: <65cec55cb5671355f69624e3c1724225Äcommunity.mybboard.net>
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: MyBB
X-MyBB-Script: community.mybboard.net/newreply.php
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Date: Tue, 26 Jan 2010 11:09:00 -0600 (CST)
Not here
Someone recently posted about their board doing this as well. I don't know whatever happened with it, it was unsolved the last I knew.
X-MyBB-Script: community.mybboard.net/search.php

That looks interesting. We will be looking into it.
It doesn't happen anymore though... before I made this thread I got the messages twice, afterwards it was back to normal... Wink
Only thing I can think of is its a race condition or a bug with PHP's shutdown functionality.

Looking at the timestamps I would say a simple race condition: "id 89ADF4E0A61; Tue, 26 Jan 2010 11:09:00 -0600 (CST)"
If it helps any, here's the header of another duplicate mail:

Received: by tango.mybboard.net (Postfix, from userid 1001)
        id 3A9554E04EF; Mon, 25 Jan 2010 13:16:16 -0600 (CST)
To: frostschutzÄmetamorpher.de
Subject: New Reply to Google SEO 1.1.10 (Security Update)
From: MyBB Community Forums <contactÄmybboard.net>
Reply-To: contactÄmybboard.net
Message-ID: <eb0356c3d241f90f5f6c354ee92ba60fÄcommunity.mybboard.net>
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: MyBB
X-MyBB-Script: community.mybboard.net/newreply.php
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Date: Mon, 25 Jan 2010 13:16:16 -0600 (CST)

Received: by tango.mybboard.net (Postfix, from userid 1001)
        id 3B10F4E0512; Mon, 25 Jan 2010 13:16:16 -0600 (CST)
To: frostschutzÄmetamorpher.de
Subject: New Reply to Google SEO 1.1.10 (Security Update)
From: MyBB Community Forums <contactÄmybboard.net>
Reply-To: contactÄmybboard.net
Message-ID: <c81908a170cbc5fdcff349e9144c710eÄcommunity.mybboard.net>
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: MyBB
X-MyBB-Script: community.mybboard.net/archive/index.php/thread-6732.html
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Date: Mon, 25 Jan 2010 13:16:16 -0600 (CST)
Yeah same exact thing. They were sent at the same exact time. This is a simple race condition.
Is there already a solution for this issue? I get some subscription emails twice. The mails have the same timestamp. The message ids are different.

Unfortunately, I have the same problem on my own forum. The mails are sometimes sent twice, or three times. It is exactly the same as described here.
It there no way of preventing this? On big forums it leads to a problem that happens frequently.