Last modified: 2013-05-05 11:52:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49196, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47196 - New langcom@ mailing list
New langcom@ mailing list
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Thehelpfulone
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-13 13:40 UTC by MF-Warburg
Modified: 2013-05-05 11:52 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MF-Warburg 2013-04-13 13:40:01 UTC
Per langcom consensus, Langcom wishes to switch a publicly logged mailing list. The archives of the old, private langcom-l list should be kept [privately]; so please create a new langcom@ list, which will have public archives & be open to public subscription (though the non-LC members on it should be moderated).
Comment 1 Thehelpfulone 2013-04-13 13:47:59 UTC
Thanks, list created at <https://lists.wikimedia.org/mailman/listinfo/langcom>. I'll share the list admin password with the existing list admins, I've set the list to be publicly logged and subscribed all the old members of the langcom and langcom-observers list, setting the old Langcom Observers and new members to have their posts automatically moderated. I'll keep this open for a while as a place to report any potential problems with the migration.
Comment 2 Seb35 2013-04-17 11:10:32 UTC
Related to the config, Nickanc reports a phishing warning by Gmail
http://lists.wikimedia.org/pipermail/langcom/2013-April/000002.html

From my experience of list manager (for WMFR), it could be a problem in SPF (or DKIM?), although it is quite unlikely to be this issue since it doesn’t happen on other WMF lists (although spf=neutral).
Comment 3 Thehelpfulone 2013-05-05 11:52:49 UTC
I don't think we are seeing this issue any more so I'm happy to close this bug as fixed.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links