1108698 - Sending email to mailing lists does not show up (except if you're subscribed directly)

Status: NEW

(mozilla.org :: Discussion Forums, task)

Description

[Armen [:armenzg]]

With Thunderbird I sent an email to:
* mozilla.tools
* mozilla.dev.b2g
* mozilla.dev.platform
* mozilla.release.engineering

however, the email is not showing up under Google Groups or my Thunderbird subscription to news.mozilla.org

Nevertheless, it seems that people subscribed directly to lists.mozilla.org did receive the email straight to their inbox.



Delivered-To: [e-mail]
Received: by 10.50.95.133 with SMTP id dk5csp670592igb;
        Mon, 8 Dec 2014 11:14:10 -0800 (PST)
X-Received: by 10.236.7.42 with SMTP id 30mr31648272yho.58.1418066050414;
        Mon, 08 Dec 2014 11:14:10 -0800 (PST)
Return-Path: <[e-mail]>
Received: from mail.mozilla.com (zmmta1.corp.phx1.mozilla.com. [63.245.216.72])
        by mx.google.com with ESMTPS id 68si17797414yhj.205.2014.12.08.11.14.10
        for <[e-mail]>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 08 Dec 2014 11:14:10 -0800 (PST)
Received-SPF: softfail (google.com: domain of transitioning [e-mail] does not designate 63.245.216.72 as permitted sender) client-ip=63.245.216.72;
Authentication-Results: mx.google.com;
       spf=softfail (google.com: domain of transitioning [e-mail] does not designate 63.245.216.72 as permitted sender) smtp.mail=[e-mail];
       dkim=pass header.i=@gmail.com;
       dmarc=pass (p=NONE dis=NONE) header.from=gmail.com
Received: from mail.mozilla.com (localhost6.localdomain [127.0.0.1])
	by zmmta1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPS id 9ECAC1060FC;
	Mon,  8 Dec 2014 11:14:09 -0800 (PST)
Received: from psmtp.com (exprod5mx252.postini.com [64.18.0.47])
	by zmmta1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPS id 5D4791060D5
	for <[e-mail]>; Mon,  8 Dec 2014 11:14:09 -0800 (PST)
Received-SPF: pass (google.com: domain of [e-mail] designates 209.85.213.181 as permitted sender) client-ip=209.85.213.181;
Received: from mail-ig0-f181.google.com ([209.85.213.181]) (using TLSv1) by exprod5mx252.postini.com ([64.18.4.10]) with SMTP;
	Mon, 08 Dec 2014 19:14:09 GMT
Received: by mail-ig0-f181.google.com with SMTP id l13so3543092iga.2
        for <[e-mail]>; Mon, 08 Dec 2014 11:14:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=buD8oZdJvEnm1U6WTjM+dLKu7uqI8eFp/XZQeL1QyFc=;
        b=kwGGCeuWoXSmzEYvkKIU4RrkzlY4WJ0HRQF2SA3buxB4jZnvXW+KLmgIlL9cNxW8FQ
         RRIq9YTmDE2f1mnIgiYKpWTddojhxF8KXKa8TdbG4lshAXgNzLB/MSnZo+ZZa7PO937d
         OuhF6SfDBdeODj+ALE+/EO1JOdA8ld8+x4F4+IdVY5YhCVHRf/UHo4OlOrYPk1kQHhpv
         NtfjmJTQj7jzKRG5dLu6dEEMmPUEayK3bev2ecmrmTTjWglWk1K8/Yi9L9pmWUmBibWR
         YM31cb4g3IP7cuBiSSPBAa3OSfa3mXlY/882ZK3fFIkf7UKZtI5g0wK29Q6qq9OmfrzB
         QM9w==
X-Received: by 10.107.165.75 with SMTP id o72mr11833496ioe.33.1418066048754;
 Mon, 08 Dec 2014 11:14:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.156.8 with HTTP; Mon, 8 Dec 2014 11:13:48 -0800 (PST)
In-Reply-To: <[e-mail]>
References: <[e-mail]>
From: Christopher Manchester <[e-mail]>
Date: Mon, 8 Dec 2014 14:13:48 -0500
Message-ID: <[e-mail]>
Subject: Fwd: You can now test mozharness changes on try
To: [e-mail]
Content-Type: multipart/alternative; boundary=001a114150ec1aa86a0509b93bc9
X-pstn-mail-from: <[e-mail]>
X-pstn-neptune: 0/0/0.00/0
X-pstn-levels:     (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-dkim: 1 skipped:not-enabled
X-pstn-settings: 3 (1.0000:0.0100) s cv gt6 gt5 gt4 GT3 gt2 gt1 r p m c 
X-pstn-addresses: from <[e-mail]> [242/12] 

--001a114150ec1aa86a0509b93bc9
Content-Type: text/plain; charset=UTF-8

---------- Forwarded message ----------
From: Armen Zambrano <[e-mail]>
Date: Mon, Dec 8, 2014 at 1:39 PM
Subject: You can now test mozharness changes on try
To: [e-mail]


tl; dr; if you want to test mozharness changes on try you can do so by
modifying testing/mozharness/mozharness.json [1] and pointing it to your
own repository. This currently *only* applies to desktop, mobile and b2g
test jobs.

Hello all,
As many of you know, mozharness [2] drives most of our build and test
jobs on treeherder/tbpl.

We now can point to a different repository/revision/branch than the
official mozharness repository.

This is handy because you can push to try and point to your own
repository and test your mozharness changes in isolation.

With this feature, we will also be able to pin mozharness from any tree
and prevent backward compatibility issues.
This will make mozharness changes easy to backout and visible in
tbpl/treeherder.
In other words, Mozharness code changes will be able to ride the trains.

To learn more about it:
* The blog post [3]
* The code [4]
* The bug [5]

If you want to help with Mozharness visit these links [6][7].
This is part of a series of proposed changes [8]

regards,
Armen

-- 
Zambrano Gasparnian, Armen
Automation & Tools Engineer
http://armenzg.blogspot.ca


[1]
https://hg.mozilla.org/mozilla-central/file/default/
testing/mozharness/mozharness.json
[2] https://wiki.mozilla.org/ReleaseEngineering/Mozharness
[3]
http://armenzg.blogspot.ca/2014/11/pinning-mozharness-from-in-tree-aka.html
[4]
http://hg.mozilla.org/build/tools/file/default/buildfarm/
utils/repository_manifest.py
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=791924
[6] https://wiki.mozilla.org/Auto-tools/Projects/Mozharness
[7]
https://bugzilla.mozilla.org/buglist.cgi?resolution=---&
emailtype1=exact&query_format=advanced&emailassigned_to1=1&
email1=nobody%40mozilla.org&component=Mozharness&product=
Release%20Engineering&list_id=11694466
[8]
https://wiki.mozilla.org/User:Armenzg/Proposals/Mozharness_
changes#Lock_mozharness.27_repository_and_version_used_from_the_tree




-- 
Zambrano Gasparnian, Armen
Automation & Tools Engineer
http://armenzg.blogspot.ca

_______________________________________________
tools mailing list
[e-mail]
https://lists.mozilla.org/listinfo/tools

--001a114150ec1aa86a0509b93bc9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote">---------- Forwarded messag=
e ----------<br>From: <b class=3D"gmail_sendername">Armen Zambrano</b> <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:[e-mail]">[e-mail]=
m</a>&gt;</span><br>Date: Mon, Dec 8, 2014 at 1:39 PM<br>Subject: You can n=
ow test mozharness changes on try<br>To: <a href=3D"mailto:mozilla-tools@li=
sts.mozilla.org">[e-mail]</a><br><br><br><div class=
=3D"HOEnZb"><div class=3D"h5">tl; dr; if you want to test mozharness change=
s on try you can do so by<br>
modifying testing/mozharness/mozharness.<u></u>json [1] and pointing it to =
your<br>
own repository. This currently *only* applies to desktop, mobile and b2g<br=
>
test jobs.<br>
<br>
Hello all,<br>
As many of you know, mozharness [2] drives most of our build and test<br>
jobs on treeherder/tbpl.<br>
<br>
We now can point to a different repository/revision/branch than the<br>
official mozharness repository.<br>
<br>
This is handy because you can push to try and point to your own<br>
repository and test your mozharness changes in isolation.<br>
<br>
With this feature, we will also be able to pin mozharness from any tree<br>
and prevent backward compatibility issues.<br>
This will make mozharness changes easy to backout and visible in<br>
tbpl/treeherder.<br>
In other words, Mozharness code changes will be able to ride the trains.<br=
>
<br>
To learn more about it:<br>
* The blog post [3]<br>
* The code [4]<br>
* The bug [5]<br>
<br>
If you want to help with Mozharness visit these links [6][7].<br>
This is part of a series of proposed changes [8]<br>
<br>
regards,<br>
Armen<br>
<br>
-- <br>
Zambrano Gasparnian, Armen<br>
Automation &amp; Tools Engineer<br>
<a href=3D"http://armenzg.blogspot.ca" target=3D"_blank">http://armenzg.blo=
gspot.ca</a><br>
<br>
<br>
[1]<br>
<a href=3D"https://hg.mozilla.org/mozilla-central/file/default/testing/mozh=
arness/mozharness.json" target=3D"_blank">https://hg.mozilla.org/<u></u>moz=
illa-central/file/default/<u></u>testing/mozharness/mozharness.<u></u>json<=
/a> <br>
[2] <a href=3D"https://wiki.mozilla.org/ReleaseEngineering/Mozharness" targ=
et=3D"_blank">https://wiki.mozilla.org/<u></u>ReleaseEngineering/Mozharness=
</a><br>
[3]<br>
<a href=3D"http://armenzg.blogspot.ca/2014/11/pinning-mozharness-from-in-tr=
ee-aka.html" target=3D"_blank">http://armenzg.blogspot.ca/<u></u>2014/11/pi=
nning-mozharness-<u></u>from-in-tree-aka.html</a><br>
[4]<br>
<a href=3D"http://hg.mozilla.org/build/tools/file/default/buildfarm/utils/r=
epository_manifest.py" target=3D"_blank">http://hg.mozilla.org/build/<u></u=
>tools/file/default/buildfarm/<u></u>utils/repository_manifest.py</a> <br>
[5] <a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3D791924" targe=
t=3D"_blank">https://bugzilla.mozilla.org/<u></u>show_bug.cgi?id=3D791924</=
a><br>
[6] <a href=3D"https://wiki.mozilla.org/Auto-tools/Projects/Mozharness" tar=
get=3D"_blank">https://wiki.mozilla.org/Auto-<u></u>tools/Projects/Mozharne=
ss</a><br>
[7]<br>
<a href=3D"https://bugzilla.mozilla.org/buglist.cgi?resolution=3D---&amp;em=
ailtype1=3Dexact&amp;query_format=3Dadvanced&amp;emailassigned_to1=3D1&amp;=
email1=3Dnobody%40mozilla.org&amp;component=3DMozharness&amp;product=3DRele=
ase%20Engineering&amp;list_id=3D11694466" target=3D"_blank">https://bugzill=
a.mozilla.org/<u></u>buglist.cgi?resolution=3D---&amp;<u></u>emailtype1=3De=
xact&amp;query_format=3D<u></u>advanced&amp;emailassigned_to1=3D1&amp;<u></=
u>email1=3Dnobody%40mozilla.org&amp;<u></u>component=3DMozharness&amp;produ=
ct=3D<u></u>Release%20Engineering&amp;list_id=3D<u></u>11694466</a> <br>
[8]<br>
<a href=3D"https://wiki.mozilla.org/User:Armenzg/Proposals/Mozharness_chang=
es#Lock_mozharness.27_repository_and_version_used_from_the_tree" target=3D"=
_blank">https://wiki.mozilla.org/User:<u></u>Armenzg/Proposals/Mozharness_<=
u></u>changes#Lock_mozharness.27_<u></u>repository_and_version_used_<u></u>=
from_the_tree</a> <br>
<br>
<br>
<br>
<br>
-- <br>
Zambrano Gasparnian, Armen<br>
Automation &amp; Tools Engineer<br>
<a href=3D"http://armenzg.blogspot.ca" target=3D"_blank">http://armenzg.blo=
gspot.ca</a><br>
<br>
______________________________<u></u>_________________<br>
tools mailing list<br>
<a href=3D"mailto:[e-mail]" target=3D"_blank">[e-mail]=
zilla.org</a><br>
<a href=3D"https://lists.mozilla.org/listinfo/tools" target=3D"_blank">http=
s://lists.mozilla.org/<u></u>listinfo/tools</a><br>
</div></div></div><br></div>

--001a114150ec1aa86a0509b93bc9--

Comment 1

[Ashish Vijayaram [:ashish]]

Triaging this out of Server Operations, relevant folks have been CC'd.

Comment 2

[Gervase Markham [:gerv]]

Surely mail not showing up where it should is a server-ops issue?

Gerv

Comment 3

[Ashish Vijayaram [:ashish]]

"server-ops" is very vague given the size and sub-divisions in IT these days. The old Server Operations queues don't have much visibility at all, which is why I cc'd people who are most relevant with this bug.