Issue #9028 duplicate

Issue notifications all use the same message id, resulting in dropped emails

Martin Eden
created an issue

Hi Bitbucket,

We are not receiving all email updates to issues in your issue tracker. We have investigated this and the cause seems to come down to duplicated message id's. Normally all emails have a unique message id, and many mail servers have a filter on them which prevents messages with the same id being delivered multiple times to an individual.

It seems that when issues on BitBucket are updated, the update emails for a particular issue are sent out with the same id, which means that our email system only delivers the first one. Please could you investigate and see whether this behaviour can be altered so that all update emails get unique ids.

As an example, we created this issue. We added 2 updates to it, and between them, we changed Stuart's email address to a different LShift account, which allowed us to avoid the email being dropped due to duplication.

We then examined the headers which are included below. You can see that the Message ID is the same in both messages, which should not happen.

Message 1 headers:

Return-Path: <issues-reply@bitbucket.org>
Received: from agentj.lshift.net (localhost [::1])
     by agentj (Cyrus v2.2.13-Debian-2.2.13-19squeeze3build0.10.04.1) with LMTPA;
     Mon, 24 Feb 2014 16:42:02 +0000
X-Sieve: CMU Sieve 2.2
Received: from lb01-ash.bitbucket.org ([131.103.20.165] helo=lb01.bitbucket.org)
    by agentj.lshift.net with esmtp (Exim 4.71)
    (envelope-from <issues-reply@bitbucket.org>)
    id 1WHybR-0005Rx-Tc
    for stuart@lshift.net; Mon, 24 Feb 2014 16:42:02 +0000
Received: from app18.ash-private.bitbucket.org (app18.ash-private.bitbucket.org [172.17.10.38])
    by lb01.bitbucket.org (Postfix) with ESMTP id 8CA171B4168F
    for <stuart@lshift.net>; Mon, 24 Feb 2014 16:41:56 +0000 (UTC)
Received: from app18.ash-private.bitbucket.org (localhost [127.0.0.1])
    by app18.ash-private.bitbucket.org (Postfix) with ESMTP id 844B59C0055
    for <stuart@lshift.net>; Mon, 24 Feb 2014 16:41:56 +0000 (UTC)
Content-Type: multipart/alternative;
 boundary="===============6524968487279699052=="
MIME-Version: 1.0
Subject: Re: [Bitbucket] Issue #27: A test issue to demonstrate email issue
 (MartinEden/framelog)
From: "Martin Eden" <issues-reply@bitbucket.org>
To: stuart@lshift.net
Date: Mon, 24 Feb 2014 16:41:56 -0000
Message-ID: <issues-a5c1880fcc03b341f23410217aae31b1/updated@bitbucket.org>
References: <issues-a5c1880fcc03b341f23410217aae31b1@bitbucket.org>
In-Reply-To: <issues-a5c1880fcc03b341f23410217aae31b1@bitbucket.org>
X-SA-Score: 0.0

Message 2 headers

Return-Path: <cyrus@agentj>
Received: from murder ([unix socket])
     by agentj (Cyrus v2.2.13-Debian-2.2.13-19squeeze3build0.10.04.1) with LMTPA;
     Mon, 24 Feb 2014 16:52:37 +0000
X-Sieve: CMU Sieve 2.2
Received: from lb01-ash.bitbucket.org ([131.103.20.165] helo=lb01.bitbucket.org)
    by agentj.lshift.net with esmtp (Exim 4.71)
    (envelope-from <issues-reply@bitbucket.org>)
    id 1WHylh-0005an-1t
    for noc@lshift.net; Mon, 24 Feb 2014 16:52:37 +0000
Received: from app18.ash-private.bitbucket.org (app18.ash-private.bitbucket.org [172.17.10.38])
    by lb01.bitbucket.org (Postfix) with ESMTP id DDFC21B41540
    for <noc@lshift.net>; Mon, 24 Feb 2014 16:52:30 +0000 (UTC)
Received: from app18.ash-private.bitbucket.org (localhost [127.0.0.1])
    by app18.ash-private.bitbucket.org (Postfix) with ESMTP id DDB099C0055
    for <noc@lshift.net>; Mon, 24 Feb 2014 16:52:30 +0000 (UTC)
Content-Type: multipart/alternative;
 boundary="===============3217501506750673135=="
MIME-Version: 1.0
Subject: Re: [Bitbucket] Issue #27: A test issue to demonstrate email issue
 (MartinEden/framelog)
From: "Martin Eden" <issues-reply@bitbucket.org>
To: noc@lshift.net
Date: Mon, 24 Feb 2014 16:52:30 -0000
Message-ID: <issues-a5c1880fcc03b341f23410217aae31b1/updated@bitbucket.org>
References: <issues-a5c1880fcc03b341f23410217aae31b1@bitbucket.org>
In-Reply-To: <issues-a5c1880fcc03b341f23410217aae31b1@bitbucket.org>
X-SA-Score: 0.0

Comments (1)

  1. Log in to comment