1): Can we confirm that email@example.com is the same distribution list as firstname.lastname@example.org? (Not just consisting of the same members, but also that sending from one sends to the other, and vice-versa?) 2): More importantly, can we have these two aliases both take and receive posts (via an SMTP -> NNTP gateway) to and from mozilla.dev.quality? Thanks!
I confirmed Step #1. email@example.com & firstname.lastname@example.org are sending to one another. Pushing to Server-Ops for Step#2.
Assignee: aignacio → server-ops
Component: Server Operations: Account Requests → Server Operations
QA Contact: tfairfield → jdow
QA@mozilla.com and .org have been subscribed to the dev-qualtiy list  (which sync with mozilla.dev.quality). Email from either address (.org or .com will be allowed on the list. I believe I disabled it to not send duplicate mail, but let me know how you find it.  https://lists.mozilla.org/listinfo/dev-quality/
Status: NEW → ASSIGNED
email@example.com is no longer subscribed. Let me know if you're getting duplicate mail still.
(In reply to Michael Burns [:mburns] from comment #5) > firstname.lastname@example.org is no longer subscribed. Let me know if you're getting duplicate mail > still. Yeah, we still are :-(
After a couple subscription tweaks, I think this duplication problem is resolved. I'll let you confirm before I close.
Closing. Let me know if you are experiencing any problems.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Sorry for the delay; reopening :-( I hadn't had a chance myself to test this in-the-wild until today, really, when I posted to email@example.com, and didn't see the message come through to mozilla.dev.quality  -- in fact, the last message in the newsgroup is from 14 hours ago. I meant to mention that firstname.lastname@example.org was unsubscribed from dev-quality on October 12; seems like a likely candidate, but I don't know why what was?  https://groups.google.com/forum/?fromgroups#!forum/mozilla.dev.quality
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
* email@example.com is a Zimbra distribution list * firstname.lastname@example.org is a Mailman mailing list * email@example.com is a Mailman discussion forum As of right now: firstname.lastname@example.org forwards to email@example.com firstname.lastname@example.org is a white_listed sender to dev-quality@ .. New emails to email@example.com will forward to firstname.lastname@example.org members only email@example.com is subscribed to dev-quality@ .. New emails to firstname.lastname@example.org will go to members of the qa@ mailing list email@example.com .. incoming emails will go to members of the newsgroup, including firstname.lastname@example.org HOWEVER, emails to email@example.com (or firstname.lastname@example.org) do not go to dev-quality@, which would create a mail routing loop. If that is an acceptable caveat, splendid. Another option would be to move the members of email@example.com wholesale to dev-quality@, and make firstname.lastname@example.org and email@example.com *just* forward to dev-quality@, which is where all the discussion would take place. That would avoid any duplicating or cross-subscription issues.
Stephen, sending you this bug so it shows up on your radar. Let me know if #comment11 is satisfactory behavior, or if you would like different behavior and we can figure that out. Otherwise, feel free to Resolve. Cheers!
Assignee: mburns → stephen.donner
Sorry, Boot2Gecko called, and we had the longest chat ever (it's still on the phone!) The 1st part of comment 11 isn't ideal, actually -- we do need emails to firstname.lastname@example.org and email@example.com to get posted to mozilla.dev.quality (and its associated mailing list). I'll need to bring up the 2nd option to the team at large, and come to an agreement with them; I don't think it'll be what we need, though we'll discuss. Are there any other clean options to get what we initially requested? At a minimum, if we can get firstname.lastname@example.org <-> dev-quality@/mozilla.dev.quality going, that'd be a great interim step. Thanks!
:justdave, is there anything we can do better WRT the questions in comment 13?
The last option in comment 11 is most likely to actually work. Have both qa@ addresses just forward to dev-quality, and put all of the subscribers on dev-quality.
fwiw, we do exactly this with email@example.com and firstname.lastname@example.org, where both lists are subscribers to each other. And the only reason it works is because email@example.com is in Majordomo, not Mailman, and has duplicate message detection server-side to filter the messages that come back to it. It's a pain in the ass, it's broken multiple times because various automatic messages will trigger one or the other of them to automatically unsubscribe the other thinking it bounced, and the developers@ list is going away and becoming an alias as soon as I get off my butt and get a round tuit.
I think the last option mentioned is by far the best.
Component: Server Operations → Infrastructure: Mail
Product: mozilla.org → Infrastructure & Operations
QA Contact: shyam → limed
(In reply to Dave Miller [:justdave] (firstname.lastname@example.org) from comment #15) > The last option in comment 11 is most likely to actually work. Have both > qa@ addresses just forward to dev-quality, and put all of the subscribers on > dev-quality. That sounds excellent. Can we just move ahead with that suggestion?
:justdave: would you be interested in helping us with this? Or can you assign/know whom might? Thanks!
Yes. I've headed to the list server with the intention of doing this twice now and managed to get myself distracted by some other task before getting this done. Hopefully with it assigned to me I'll see it and remember :)
Assignee: stephen.donner → justdave
All subscribers to email@example.com that weren't already on firstname.lastname@example.org have been subscribed there. email@example.com mailing list has been deleted. firstname.lastname@example.org alias created which forwards to email@example.com firstname.lastname@example.org alias changed to point at email@example.com instead of firstname.lastname@example.org email@example.com and firstname.lastname@example.org have been added as valid recipients in the dev-quality list configuration.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.