Closed
Bug 756468
Opened 13 years ago
Closed 13 years ago
dev.* list is not sending new messages
Categories
(mozilla.org Graveyard :: Server Operations, task, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: justdave)
Details
eom
![]() |
||
Updated•13 years ago
|
Assignee: nobody → catlee
Priority: -- → P2
![]() |
||
Comment 1•13 years ago
|
||
actually, I haven't gotten any dev.tree-management e-mail since may 16.
![]() |
||
Updated•13 years ago
|
Assignee: catlee → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → phong
Summary: Wait times reports last reported on May 16th → dev.tree-management list is not sending new messages
Comment 2•13 years ago
|
||
1) this is happening with multiple lists, not just dev.tree-management. Tweaking subject and bumping priority to match.
2) Is this fallout from the mail server outage? The timelines are about right. See bug#755520 and bug#755447 for details on that outage.
Severity: normal → major
OS: Mac OS X → All
Summary: dev.tree-management list is not sending new messages → dev.* list is not sending new messages
![]() |
||
Updated•13 years ago
|
Assignee: server-ops → afernandez
Assignee | ||
Comment 3•13 years ago
|
||
Is new mail to these lists working? This was supposedly fixed yesterday afternoon.
Assignee | ||
Comment 4•13 years ago
|
||
(and yes, it was a victim of the mail outage, and the mail that didn't deliver was lost :( - but new mail should be working now)
Comment 5•13 years ago
|
||
There are Wait reports generated 6am Pacific on the 18th, 19th 20th, and 21st now visible in mozilla.dev.tree-management newsgroup. Some of them are marked '***SPAM***' in the subject, which isn't desirable.
Comment 6•13 years ago
|
||
Comment 7•13 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #5)
> There are Wait reports generated 6am Pacific on the 18th, 19th 20th, and
> 21st now visible in mozilla.dev.tree-management newsgroup.
Great!
> Some of them are
> marked '***SPAM***' in the subject, which isn't desirable.
ummm. That is new and that is not good.
Is that "***SPAM***" coming from within Mozilla mail servers, or is it being added by others externally after the email leaves Mozilla?
![]() |
||
Comment 8•13 years ago
|
||
A lot of release automation emails sent to release@mozilla.com was marked as spam:
***SPAM*** [release] Tagging started for Thunderbird 13.0b3 build1
Full headers:
Return-Path: release@mozilla.com
Received: from zmmta1.mail.corp.phx1.mozilla.com (LHLO
zmmta1.mail.corp.phx1.mozilla.com) (10.20.77.21) by
zmmbox3.mail.corp.phx1.mozilla.com with LMTP; Tue, 22 May 2012 16:32:08
-0700 (PDT)
Received: from mx1.mail.corp.phx1.mozilla.com (zlb1.mail.corp.phx1.mozilla.com [10.20.77.200])
by zmmta1.mail.corp.phx1.mozilla.com (Postfix) with ESMTP id 2168310666E
for <release@mozilla.com>; Tue, 22 May 2012 16:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mozilla.org
X-Spam-Flag: YES
X-Spam-Score: 7.199
X-Spam-Level: *******
X-Spam-Status: Yes, score=7.199 required=6.31 tests=[BAYES_50=2,
MISSING_MID=1.199, TO_EQ_FM_DIRECT_MX=0.001, TO_NO_BRKTS_DIRECT=3.999]
autolearn=no
Received: from buildbot-master34.srv.releng.scl3.mozilla.com (v-1030.fw1.releng.scl3.mozilla.net [63.245.214.82])
by mx1.mail.corp.phx1.mozilla.com (Postfix) with SMTP id E7D54F2804
for <release@mozilla.com>; Tue, 22 May 2012 16:32:07 -0700 (PDT)
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Content-Type: text/plain; charset="utf8"
Date: Tue, 22 May 2012 16:32:07 -0700
subject: ***SPAM*** [release] Tagging started for Thunderbird 13.0b3 build1
From: release@mozilla.com
To: release@mozilla.com
Message-Id: <20120522233208.2168310666E@zmmta1.mail.corp.phx1.mozilla.com>
![]() |
||
Updated•13 years ago
|
Assignee: afernandez → justdave
Assignee | ||
Comment 9•13 years ago
|
||
OK, I'll consider this fixed then. The ***SPAM*** in the subject thing is bug 756259.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•