• Recently I started getting emails from noreply@wordpress.org with subject that starts with “Re: [WordPress Plugin Repository] ” (Yes it starts with Re). The “to” field is empty.

    A typical email looks like this

    #9: new kind of spam, which looks almost normal
    ———————–+————————-
    Reporter: researcher | Owner: kitten
    Type: defect | Status: closed
    Priority: normal | Component: spaminator
    Severity: normal | Resolution: fixed
    Keywords: spaminator |
    ———————–+————————-

    Comment (by ruhanirabin):

    In [changeset:”903847″]:
    {{{
    #!CommitTicketReference repository=”” revision=”903847″
    this resolves #6 and closes #7, also fixes #8 and close #9. Additionally
    close #10 and fix #11. Also, close #12 and fix #13. That is also close #14
    }}}


    Ticket URL: </ticket/9#comment:7>
    WordPress Plugin Repository <http://wordpress.org/plugins/&gt;
    A WordPress community development project

    I guess this is from some ticketing system used in wordpress.org, but it doesn’t provide any link or any information apart from it and I am not sure why I am receiving it as well.

    The fact that the subject starts with “Re: ” and the fact that it doesn’t have any to address makes me wonder whether they are spam or generated because of a bug somewhere.

    Does anyone know why I am getting these messages and also how to stop them?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    https://plugins.trac.wordpress.org//ticket/9#comment:7

    Dear god, someone’s actually USING that? Oh, wait, no, HAH! Okay, so this is funny. He used #s in his comments to mark his internal to-do. Only TRAC decided that meant itself and .. well emailed you. Since you’d left a comment on that ticket. I’ll ask him not to do that 🙂

    Thread Starter Sudar Muthu

    (@sudar)

    I think there is more to it and part of the blame lies with me as well.

    I use github to develop my WordPress plugins and when they are ready to be released, I just combine all the commit messages of all the commits which went in the release in a single message and make a single commit to WordPress repo. I use this script for this https://github.com/sudar/wp-plugin-in-github

    In the individual commit messages, I refer to issues in my github repo (eg: Fix #4 etc) and when this commit message goes into trac, it think that I am referring to issue #4 in trac. Going forward I guess I have to strip out these issues numbers from my commit messages.

    I think it’s not just me, but all the people who posted the comment in that particular ticket in the last few years have made the same mistake.

    I’ll ask him not to do that 🙂

    Did you mean TRAC or the person who did the commit?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    The person who made the commit, though really you’d only get those emails if you signed up and/or replied in trac for plugins in the first place, so you can just unsubscribe from that topic in plugin trac and never get another alert.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Getting emails from noreply@wordpress.org’ is closed to new replies.