Closed Bug 472463 Opened 16 years ago Closed 16 years ago

No longer receiving my own emails to mailing lists

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: samuel.sidler+old, Unassigned)

Details

I sent an email to r-d and, while it was received by people on the mailing list (including people on qa@ and build@ which are mailing lists themselves that are subscribed to r-d), I never received my own email. I used to, however. This was confusing because I wasn't sure if my email had gone through.

Whimboo mentioned he had the same issue with one of the other qa mailing lists. Did a configuration change?
There's a user setting in Mailman for this, did you check it?  Not aware of anything changing recently on the server end other than Zimbra being told to remove duplicate messages again a month or so ago.  But if that's what you hit, you probably still would have gotten it, it just might not have filtered to the right folder.
This setting is enabled for me for each of the subscribed mailing lists. I've already checked this yesterday. As I can remember it started on Monday (at least for me). No idea if that has been caused by the email address update.
The user setting has always been set for me. I've never changed it. Something else must have changed. I feel like we've had this problem before...
I'm not aware of any changes to mailman's configuration for the last several weeks.

(In reply to comment #2)
> No idea if that has been caused by the email address update.

The LDAP mailing lists are Zimbra-controlled and are completely separate from mailman, so that wouldn't be the case.
So, what would cause this? I definitely received my r-d email on December 31...
I suspect postini.
I wouldn't suspect postini.  Mailman mozilla.org lists don't go through postini and either of the two mailman instances would deliver mozilla.com email locally, not back out through postini.
So, email to r-d, for me, would go through this path:
  from ss@m.c -> r-d@m.o -> qa@m.o -> ssidler@m.c

Postini doesn't check all email coming into my mozilla.com email address? We've added exceptions for mailing list mail?

(And, as of today, I've subscribed personally to r-d so I don't need to go through qa@ every time.)
There is no exception for mailing list mail, it just doesn't go through postini to begin with, because it's already behind our firewall.  Only stuff coming in from outside goes through postini.
(In reply to comment #9)
> There is no exception for mailing list mail, it just doesn't go through postini
> to begin with, because it's already behind our firewall.  Only stuff coming in
> from outside goes through postini.

Yeah, we found that's not true. It seems somebody changed the internal MXs to point to postini, too. Should fix that...
(In reply to comment #10)
> Yeah, we found that's not true. It seems somebody changed the internal MXs to
> point to postini, too. Should fix that...

Fix that because it's a problem?  Or because it's not ideal?  

Is that the reason for Sam's issue?
What happens when you turn off nodupes for yourself?
I works again. Some seconds I've sent a message to the qa mailing list and got my message too. Where there made any changes yet? Sam, can you verify?
Mine started working randomly again as well, but I also subscribed myself directly to r-d instead of going though the qa mailing list. I can close this bug (or you can!) but it appears to happen sporadically for no apparent reason, except that there must be a reason and it's almost certainly an IT issue.
I won't do that. Means there is still a remaining issue, which should be solved completely. Leaving open for now.
(In reply to comment #10)
> (In reply to comment #9)
> > There is no exception for mailing list mail, it just doesn't go through
> > postini to begin with, because it's already behind our firewall.  Only stuff
> > coming in from outside goes through postini.
> 
> Yeah, we found that's not true. It seems somebody changed the internal MXs to
> point to postini, too. Should fix that...

Actually, it was true, because both mailman servers have mozilla.com hardcoded to go to the zimbra server, and ignore the MX records.
mconnor mentioned on IRC that he did something regarding the QA and release-drivers mailing lists... mconnor, care to explain what you did?
qa@ got unsubscribed somehow recently, but it was after this bug was filed because others received the email I sent to r-d (like Al) who weren't subscribed directly to that list (but were subscribed to qa@).
qa@ wasn't subscribed anymore.  I don't know why, but since the QA people weren't aware, I added it back for the time being.
I this still happening at all?  The qa subscription thing sounds like the most logical explanation, and I can't find any other problems that might contribute to this (other than duplicate-removal happening on Zimbra if you're subscribed from an @mozilla.com address, and that's not going to go away for a while).
OK, I'll assume the amount of quiet means adding the qa list back fixed the problem.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.