Closed Bug 1303132 Opened 9 years ago Closed 5 years ago

Trying to find source of duplicate emails.

Categories

(Infrastructure & Operations :: Infrastructure: Mail, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Dolske, Unassigned)

References

Details

Attachments

(2 files)

Attached file email headers
I admin/moderate the firefox-dev@mozilla.org list. Recently I've noticed that when a particular person is posting an update, the list is getting 2 duplicate messages. The author is sending a single message in Thunderbird, to firefox-dev@mozilla.org and the newsgroups mozilla.dev.platform and mozilla.tools. The email headers (attached) of one of the duplicates seems to indicate it's coming in by way of the mozilla.tools group. There's a "To: mozilla-tools@lists.mozilla.org" header that's not in the other (which looks like a normal email to firefox-dev). jlin took a look, but doesn't see firefox-dev subscribed to the mozilla-tools@ list (which was my guess), so I'm not sure what's causing this duplicate to be sent to firefox-dev. Ultimately I would like to stop this. :)
Attached file normal headers
Oh, and just in case it's useful, here are the normal headers from the expected email.
aryx wrote on irc "the sheriffs mailing list" had multiples. I don't know details
See Also: → 1302978
This is still occurring on at least one list (enterprise@mozilla.org): ``` Received: from mail-qt0-f197.google.com (mail-qt0-f197.google.com [209.85.216.197]) by mailman1.mail.scl3.mozilla.com (Postfix) with ESMTPS id 3AA5EC0216 for <enterprise@mozilla.org>; Mon, 3 Oct 2016 22:01:56 +0000 (UTC) Received: by mail-qt0-f197.google.com with SMTP id 38so130477065qte.0 for <enterprise@mozilla.org>; Mon, 03 Oct 2016 15:01:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-original-authentication-results:x-gm-message-state:subject:to :references:from:message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=UdgXynNLIjsSr9HkFTXPOu9qHDbUFxmR4XWWmCba4p0=; b=aFBMLPfDSb1kxDwqFB5QLu6VgJKtjhV/EH2/eDI88oV/Hwc9xPneZ3XxP4Zh5EjKc8 wkmYGVmreDmJHBA3zcNkr+GDdy3wi1LAzQHYSbXIRlCGpw4VOdvx1HXSS1Pi+WlKtHux ejYl3T06MIzxyZ2Qzu82FC5r8c5rtQesKptzmCDW3YAkSKwfhMeMkLi77bQzwDr7vhwX 94o+fYfPciRyJo9kLhcLqCJORi7woTCinLBHuHcrTeChOtvOVvXz2ReNTLyeCpEa7f44 jWpHCQph+CFg/BpSxLIq4ijK+KCEnGQ3Haryh62lPL9Ttw0YuZjLnnZtPanKLmpnHVVu cCmw== X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of tiago.delboni@almg.gov.br designates 177.86.143.130 as permitted sender) smtp.mailfrom=tiago.delboni@almg.gov.br X-Gm-Message-State: AA6/9RnTdq+snpBhGo397PcBV2TFaEio/oBpI0n4tBQ2jIrozycIL8xpGPZc0S7mhp1CtCM2dr/DMfTL7qR8G8mDROAUkUf/HKN3qYkZjPTkZ/PdEdRooTOnYqH0g4xED6a+cXesyVgvS9fa+lcuCDSSuEEQ6rPGiILQMJpdiVUfOErxzR7fq6ZTs/GCwNqLc8aQnVoa+sPJCBQKFKpG X-Received: by 10.55.111.2 with SMTP id k2mr307317qkc.188.1475532115224; Mon, 03 Oct 2016 15:01:55 -0700 (PDT) X-Received: by 10.55.111.2 with SMTP id k2mr15054685qkc.188.1474023259168; Fri, 16 Sep 2016 03:54:19 -0700 (PDT) Received: from hades.almg.gov.br (hades.almg.gov.br. [177.86.143.130]) by mx.google.com with ESMTPS id y34si7882506qta.127.2016.09.16.03.54.18 for <enterprise@mozilla.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 16 Sep 2016 03:54:19 -0700 (PDT) ... Message-ID: <8e75f700-6112-d5eb-f6fc-7172cef07b70@almg.gov.br> ``` Looks like messages are bouncing within Google's infrastructure (MX for mozilla.org is Google), finally ending at the Mailman server. This may need to be addressed at Google's end (unless something like https://mail.python.org/pipermail/mailman-users/2002-January/016687.html is implemented)
I think comment 4 might be referring to bug 1302978 (which is also happening for "List-Id: WebVR Discussion <web-vr-discuss.mozilla.org>") which seems to be a different problem than comment 0. Comment 0 sounds like a multi-path problem that results in duplicates immediately rather than messages being duplicated 2+ weeks later.
(In reply to Andrew Sutherland [:asuth] from comment #5) > I think comment 4 might be referring to bug 1302978 (which is also happening > for "List-Id: WebVR Discussion <web-vr-discuss.mozilla.org>") At first glance, both bugs looked about the same issue, so because this one mentioned the source of the duplicates, I posted here. I'll post this there as well, if it's where it should go.
Yeah, this bug is about a specific issue with messages to mozilla-tools immediately duping on firefox-dev. Getting dupes unrelated to mozilla-tools weeks later is a different issue. (Although, FWIW, that issue _also_ hit firefox-dev over the weekend. Service Desk had me file INC0021401, but there have not yet been any updates there.)
So it looks like there are 2 messages that I managed to track down that is causing the duplicates and in both cases the header looks like this: to: firefox-dev@mozilla.org X-Original-To: mozilla-tools@lists.mozilla.org As you mentioned or at least what I'm seeing is mail is intended to go to tools@lists.mozilla.org but also ends up to firefox-dev@mozilla.org. All other emails seem to be sending normally? CC'ing sender of emails, :armenzg I'm curious how are you sending these emails? "Subject: Usability improvements for Firefox automation initiative - Status update #4" and "Subject Usability improvements for Firefox automation initiative - Status update #5". I'm curious as to why your header looks like that
Flags: needinfo?(armenzg)
I use Thunnderbird. In the email I set the field "Newsgroup" for mozilla.tools and mozilla.platform while firefox-dev@ I use the "To" field. I could use "To" for all the fields if prefered (and use instead firefox-dev@, tools@ and dev-platform@)
Flags: needinfo?(armenzg)
(In reply to Armen Zambrano [:armenzg] (EDT/UTC-4) from comment #9) > I use Thunnderbird. > > In the email I set the field "Newsgroup" for mozilla.tools and > mozilla.platform while firefox-dev@ I use the "To" field. > > I could use "To" for all the fields if prefered (and use instead > firefox-dev@, tools@ and dev-platform@) If thats possible yea, it seems like its sort of causing duplicate emails (although duplicate isn't a big issue) it does cause some confusion.

Since mailman and the nttp gateway have been decom'ed (AND it sounds like it was sorta-resolved before), closing this out.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: