bwinton@mozillamessaging.com unable to send mail to tb-planning mailing list

RESOLVED INVALID

Status

mozilla.org Graveyard
Server Operations
--
critical
RESOLVED INVALID
8 years ago
3 years ago

People

(Reporter: dmose, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
He's on the list, and as far as I can tell it's configured so that his mail should go through.  He's tried a few times, and it's gone into the ether.  Nothing in the moderator queue (though the moderation bit is unset for his address anyway). Other people have successfully sent mail to the list without a problem.

As far as I can tell, the Mailman Web UI doesn't expose the logs I'd need to tell if Mailman ever saw the message, and if not, presumably access to the Mozilla MTA logs would be required to diagnose further.

Setting this bug to critical in part because I don't know the actual scope here.  We're in the middle of launching tb-planning and trying to persuade people to use it for day-to-day work, and if it's failing for more than just him, that's likely to affect adoption non-trivially.  If it's truly just a problem for Blake, then this is slightly less critical, but still important.  In either case, I'm hoping it will be straightforward to diagnose, given the inclusion of the message here:

Message-ID: <4B9689F7.6080307@mozillamessaging.com>
Date: Tue, 09 Mar 2010 12:48:39 -0500
From: Blake Winton <bwinton@mozillamessaging.com>
Organization: Mozilla Messaging.
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a3pre) Gecko/20100308 Shredder/3.2a1pre
MIME-Version: 1.0
To: tb-planning@mozilla.org
Subject: Re: Policy change for the blocking next release flag
References: <4B94E662.4030104@mozillamessaging.com>
In-Reply-To: <4B94E662.4030104@mozillamessaging.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 10-03-08 6:58 , Ludovic Hirlimann wrote:
> We are looking at ways to drive bugs into releases more efficiently one
> of these ways is ton control the size of bug list. One such bug list the
> bug list based on the blocking request flag. In order to be more
> efficient, we are going to restrain access to who can set the flag.
>
> I've posted a draft policy at
> https://wiki.mozilla.org/Thunderbird:Blocking_Flag_Policy with a initial
> list at https://wiki.mozilla.org/Thunderbird:Blocking_Flag_Policy:List.
>
> Comments welcome before we start actually implementing this.

My only thought is that we might want to separate "Core developers" and 
"People being paid to work on TB." into two different items, because 
they may not be the same set of people.

Other than that, it seems like it'll be extra work for people like me, 
when folks try to convince me to ask for blocking, but less work on the 
triagers, and I think that's a fair trade, or at least worth a try.

Later,
Blake.
User error.  Sorry about that.  (My ISP forces me to verify new email addresses before I can send from them, and I didn't get a bounce message from them for some reason.)

Thanks,
Blake.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Updated

8 years ago
Resolution: FIXED → INVALID
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.