www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Pocock (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11721) spam from Jenkins
Date Thu, 21 Apr 2016 08:26:25 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251549#comment-15251549
] 

Daniel Pocock commented on INFRA-11721:
---------------------------------------

If you are going to run a mailer, you need to take responsibility for it.  Don't expect random
users on the internet to come and log in and start configuring things because somebody else
made a mistake.

You say "not much can be done about it" - well, yes, something can be done: turn off the email
notifications for the whole site until somebody can be bothered thinking it through and coding
a proper solution.

Abusing people with email notifications like this is just wrong and bad for the future of
open source development, many people are volunteers and want to spend their time on quality
things rather than administrivia like this.

If this isn't fixed in another 8 hours then my own site is going to blacklist builds.apache.org


> spam from Jenkins
> -----------------
>
>                 Key: INFRA-11721
>                 URL: https://issues.apache.org/jira/browse/INFRA-11721
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Daniel Pocock
>            Priority: Critical
>
> Jenkins has started spamming me about a project I am not involved in.  The spamming started
on 17 April 2016.
> If you can't control the emails to stop spam, please disable email from Jenkins.
> Here is an example:
> Return-Path: <jenkins@builds.apache.org>
> Received-SPF: None (no SPF record) identity=mailfrom; client-ip=140.211.11.3; helo=mail.apache.org;
envelope-from=jenkins@builds.apache.org; receiver=daniel@pocock.pro 
> Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
> 	by mail1.trendhosting.net (Postfix) with SMTP id 787FD1509D
> 	for <daniel@pocock.pro>; Sun, 17 Apr 2016 02:01:27 +0100 (BST)
> Received: (qmail 13774 invoked by uid 99); 17 Apr 2016 01:01:24 -0000
> Received: from crius.apache.org (HELO crius.apache.org) (140.211.11.14)
>     by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Apr 2016 01:01:24 +0000
> Received: from crius.apache.org (localhost [127.0.0.1])
> 	by crius.apache.org (ASF Mail Server at crius.apache.org) with ESMTP id 1036A9C0097;
> 	Sun, 17 Apr 2016 01:01:16 +0000 (UTC)
> Date: Sun, 17 Apr 2016 01:01:16 +0000 (UTC)
> From: Apache Jenkins Server  <jenkins@builds.apache.org>
> To: commits@beam.incubator.apache.org, bchambers@google.com, daniel@pocock.pro, 
> 	davor@google.com, dhalperi@google.com, lcwik@google.com, 
> 	tgroh@google.com
> Message-ID: <913957783.6890.1460854876064.JavaMail.jenkins@crius>
> In-Reply-To: <293699841.6881.1460851670118.JavaMail.jenkins@crius>
> References: <293699841.6881.1460851670118.JavaMail.jenkins@crius>
> Subject: Jenkins build is still unstable:
>  beam_PostCommit_RunnableOnService_GoogleCloudDataflow #134
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
> X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkqVKZPv7YyHBB3FvWfV7XQehwe/Ga3aadzSNknt8g382X3uN8A3SOQ+Ixq9HxS+ZlN6XR4TECySmSRy2JN5Rx8svxAD0TjtSF9LuU98dD+LniNDP7Lq6gvRFuJhbMHoS0nuTizDZLsK4X8TW5MyV9w+jFbdoZfRE5O/Mse0fkOeL5uoIS/3Vvu/W+x9QSjDkB7CaU56bPFlQjqqJBl3Cn9r34CkXQZYnLb/NjW4vcpw0+TgMUAPTIVEr5BTPZRshz19g7huwg3zANT5HBIZnzV4hsVY9w4JHkceFdKi/ibNnjPjsFs9pm0HSGJ/RDxjIvSTYT02eH4+m1RAYaj2E9QIDAQAB
> X-Jenkins-Job: beam_PostCommit_RunnableOnService_GoogleCloudDataflow
> X-Jenkins-Result: UNSTABLE
> See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message