[03:20:40] 10Phabricator, 10MediaWiki-extensions-CentralAuth, 10MediaWiki-extensions-OAuth, 10MobileFrontend: Loging into Phabricator with MediaWiki account on mobile device can cause endless loop - https://phabricator.wikimedia.org/T146122#2654867 (10SamanthaNguyen) [07:36:47] 10Phabricator, 10MediaWiki-extensions-CentralAuth, 10MediaWiki-extensions-OAuth, 10MobileFrontend: Loging into Phabricator with MediaWiki account on mobile device can cause endless loop - https://phabricator.wikimedia.org/T146122#2655234 (10Schnark) Long version: 1. Open Firefox on desktop, install the ad... [10:08:51] 10Phabricator, 06Operations: phabricator: can't search for RT tickets (reference field) anymore - https://phabricator.wikimedia.org/T146116#2655516 (10Aklapper) Could reproduce locally; created https://secure.phabricator.com/T11675 [12:59:26] 10Phabricator: Good bug reports - https://phabricator.wikimedia.org/T146266#2655794 (10Paladox) [13:00:04] 10Phabricator: Good bug reports - https://phabricator.wikimedia.org/T146266#2655797 (10Paladox) 05Open>03Invalid This has nothing to do with labs or ops I am not sure if this is invalid since we already have docs on this. [13:00:17] 10Phabricator: Good bug reports - https://phabricator.wikimedia.org/T146266#2655800 (10Paladox) 05Invalid>03Open [13:03:53] 10Phabricator: Good bug reports - https://phabricator.wikimedia.org/T146266#2655803 (10Aklapper) Thanks for reporting this! > 1.Having a clearly specified bug number Automatically done. T146266 in this very case. :) > 2.Reproducible > 3.Be Specific Covered by https://www.mediawiki.org/wiki/How_to_report_a_bu... [13:04:05] 10Phabricator: Good bug reports - https://phabricator.wikimedia.org/T146266#2655804 (10Aklapper) 05Open>03Invalid [14:54:42] Hello ALL ! [15:07:17] hi newbyy [15:09:09] andre [15:09:14] how are you ? [15:09:23] newbyy: fine, thanks. [15:11:19] newbyy: Anything that we can help with or any questions regarding Wikimedia's development infrastructure? [15:12:07] i had a question for Phabricator but i find an answer thanks for you help [15:13:01] ah, nice :) [16:30:25] andre__ solves another one! :P [17:14:54] :D [17:30:26] hey all — I noticed my latest phab email update failed spf. I’m getting a little warning in my inbox that the email might be spam [17:30:47] thought I should flag this in case it seems like a concern [17:31:01] can you paste the full email with headers somewhere? [17:31:14] sure, should I create a new task? [17:35:00] Krenair I cc’d you on the task, hope that was appropriate [17:35:08] https://phabricator.wikimedia.org/T146299 [17:35:19] that's fine, I don't mind being cc'd on things [17:36:26] Received-SPF: fail (google.com: domain of no-reply@phabricator.wikimedia.org does not designate 2620:0:861:103:10:64:32:150 as permitted sender) client-ip=2620:0:861:103:10:64:32:150; [17:36:44] interesting, that's iridium's internal v6 ip [17:37:18] er, or not [17:39:56] yes, it's internal [17:40:03] shouldn't google use the ip of the mx server? [17:40:50] 10Phabricator, 10MediaWiki-extensions-CentralAuth, 10MediaWiki-extensions-OAuth, 06Reading-Web-Backlog, 07Mobile: Loging into Phabricator with MediaWiki account on mobile device can cause endless loop - https://phabricator.wikimedia.org/T146122#2656730 (10Jdlrobson) [17:40:50] say SPF one more time and I'll stop stalking that ;) why is it using it's internal IP [17:41:13] ccogdill, something interesting is happening here [17:41:38] I received that same notification on my @gmail.com address [17:41:41] But in mine: [17:41:49] Received-SPF: pass (google.com: domain of no-reply@phabricator.wikimedia.org designates 208.80.154.76 as permitted sender) client-ip=208.80.154.76; [17:42:08] (that's mx1001's ip, which you would expect) [17:42:11] 10Phabricator, 10MediaWiki-extensions-CentralAuth, 10MediaWiki-extensions-OAuth, 06Reading-Web-Backlog, 07Mobile: Loging into Phabricator with MediaWiki account on mobile device can cause endless loop - https://phabricator.wikimedia.org/T146122#2651458 (10Jdlrobson) After research, if you find this is s... [17:43:14] ok [17:45:17] 10Phabricator, 10Mail, 06Operations: Phabricator emails failing spf - https://phabricator.wikimedia.org/T146299#2656753 (10Krenair) Something strange is going on here, I got an SPF pass on that message to my @gmail.com address - why does google use the origin server's IP for the SPF check instead of the rela... [17:46:19] how weird Krenair! could it be that the bug is only impacting @wikimedia addresses? [17:46:34] ccogdill, possibly [17:46:45] well that’s less concerning at least [17:47:12] there is some mail routing going on to allow some @wikimedia.org addresses to be controlled by the foundation's OIT and those go through google apps [17:47:31] I don't know if that's causing this problem [17:47:54] yeah [17:48:31] I've been getting that randomly as well, I'll look deeper at the task after this meeting [17:49:22] yep [17:49:35] Just checked another email sent to my WMF phab account (and so my @wikimedia.org address in google apps) [17:49:39] It has the same problem as ccogdill [17:49:51] No DKIM signature on these either [17:49:56] yeah I noticed that! [17:50:00] thought the lack of DKIM was odd [17:50:28] whereas my @gmail.com got a DKIM signature [17:51:06] hmm anyone else have a phab acount with an email at a different domain than @wikimedia.org or @gmail.com? [17:55:02] Krenair could it be related to the need for mx1001 needing a certificate renewal? [17:55:05] and hi [17:55:18] I very much doubt it paladox [17:55:21] Oh [17:55:29] It works for me in yahoo anyways [17:57:32] The cert is valid for like another 24 hours ish [17:57:47] Not Before: Sep 22 18:01:13 2015 GMT [17:57:47] Not After : Sep 22 18:01:13 2016 GMT [17:58:11] Oh [17:58:27] Well 23 hrs now [18:01:08] Krenair could the fix be to do something internally to verify it. [18:01:43] By that i mean on iridium [18:01:44] for gmail users [18:01:44] about 24 really [18:01:49] what? [18:02:21] Well maybe if we internally verify it and send it, it may help, but i am really guessing [18:02:24] sorry about guessing [18:02:50] http://serverfault.com/questions/655326/gmail-spf-fail-based-on-client-ip [18:11:16] Krenair could you try http://vamsoft.com/support/tools/spf-policy-tester since it passed for me? [18:11:18] please [18:13:24] Oh it fails [18:14:00] Krenair it works in yahoo but is broken in gmail, i guess we will need to workaround it. And it is a known problem with gmail if you search for it on google [18:14:07] no [18:14:08] it works in gmail [18:14:17] it fails in gmail-hosted wikimedia.org [18:14:26] Oh [18:14:29] Strange [18:14:38] Oh yeh [18:14:47] gmail buisness and normal gmail [18:14:47] are [18:14:50] different [20:02:44] 10Phabricator, 10Mail, 06Operations, 13Patch-For-Review: Phabricator emails failing spf - https://phabricator.wikimedia.org/T146299#2656694 (10BBlack) ping [20:03:40] 10Phabricator, 10Mail, 06Operations, 13Patch-For-Review: Phabricator emails failing spf - https://phabricator.wikimedia.org/T146299#2657255 (10BBlack) 05Open>03Resolved a:03BBlack The email sent from my ping nows says `Received-SPF: pass (google.com: domain of no-reply@phabricator.wikimedia.org desig... [21:30:23] 10Phabricator, 10Mail, 06Operations, 13Patch-For-Review: Phabricator emails failing spf - https://phabricator.wikimedia.org/T146299#2656694 (10greg) I bet this was a dupe of {T144381}