Emails being sent by WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ & WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. WordPress instances are currently SPF softfail’ing, I suspect that’s what has caused Gmail to mark all contact requests from a WordCamp site to me (and the rest of the team) as spam.
This is happening as the bounce reply address is currently set to
firstname.lastname@example.org which doesn’t accept w.org IP ranges as SPF permitted senders (as expected).
WordPress.org emails are DKIM signed (where as WordCamp ones are not), so i suspect that’s why they don’t get marked as spam.
Relevant part of a WordCamp email:
Received-SPF: softfail (google.com: domain of transitioning email@example.com does not designate 184.108.40.206 as permitted sender) client-ip=220.127.116.11;
spf=softfail (google.com: domain of transitioning firstname.lastname@example.org does not designate 18.104.22.168 as permitted sender) email@example.com
Received: from [22.214.171.124] (port=20977 helo=wordcamp1.lax.wordpress.org)
by marx.multipattern.com with esmtp (Exim 4.85)
for *brisbane wc email removed*; Sat, 04 Apr 2015 03:49:16 +0000
And that of a Make blog:
Received-SPF: softfail (google.com: domain of transitioning firstname.lastname@example.org does not designate 126.96.36.199 as permitted sender) client-ip=188.8.131.52;
spf=softfail (google.com: domain of transitioning email@example.com does not designate 184.108.40.206 as permitted sender) firstname.lastname@example.org;
Received: from mail.wordpress.org (localhost.localdomain [127.0.0.1])
by mail.wordpress.org (Postfix) with ESMTP id 3DAEA206CA9;
Fri, 27 Mar 2015 04:05:43 +0000 (UTC)
@nacin, the new Training team would like to use training@ in conjunction with SupportFlow. Could you please setup the address for them? Once it’s active I can setup SupportFlow.
We have a handful of @wordpress.org email addresses set up as forwards. For the teams that need an official email address and a supportpress/supportflow setup, we have been doing addresses on wordcamp.org (which has mailboxes) or setting up one-off gmail addresses to handle the mailbox, the owner of which might get lost over time. I talked to Barry at the team meetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. days at WCSF about this and he said we should put wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ on gmail for email. Matt said this was okay.
I’ve reclaimed the Foundation account for google apps for non-profits (a WC organizer had used the tax id to claim it without asking first, so we had to jump through some hoops). I’ve set up the account and gone through the steps with Ashish Shukla to have it recognize wordpress.org as the domain. The next step would be to modify the MX record to start routing email through the google apps account, but that gets complicated when it comes to ensuring no disruption to existing forwards, which is why Ashish and I were waiting for Barry to be available. When I spoke to Barry today, he said that @nacin is doing something around email too, so now he’s not super comfortable making changes at all lest we inadvertently step on each others’ toes.
@nacin: what is the thing you are doing with email, and does it preclude a shift to having actual mailboxes that are official? Let’s coordinate with whomever else is working on this to make sure everyone’s needs are met. I’m happy to share the google credentials with the appropriate people to get it going. We also get stuff like official hangouts the teams can use, calendar, etc. as part of the google apps account. If there’s a reason *not* to take Barry’s advice about using google apps/gmail for the team emails, I can remove wordpress.org from the google account (if so, please explain).
@andreamiddleton would like to setup a mailbox (not just a forward) for email@example.com, but we’re not sure what the current setup is and don’t have access to it. Could you please either give me access, or setup the account?
Hey @barry and @stankea. Can you set up an email address (not a box, just an alias) of firstname.lastname@example.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and have it forward to me at email@example.com? At some point we’ll probably want to set up a supportpress instance or something, but for now I just need an active address to satisfy the meetup.com contract. Thanks.
security/wordpress/org gets a ton of spam. Many of us use Gmail, but we’ve had to disable the Gmail spam filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. because it was causing legitimate messages to be missed (don’t know why).
Most of the spam is really obvious… VIAGRA, foreign languages (a lot of Russian), other pharma spam.
Ultimately, I think we’d like to move away from e-mail, and have some sort of private Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or ticketing system. But until then, some SpamAssassin or other measures would really help us find the wheat among the chaff.