You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Roy T. Fielding (JIRA)" <ji...@apache.org> on 2007/09/06 21:16:32 UTC
[jira] Created: (INFRA-1356) JIRA comment loop due to watcher email
autoresponder
JIRA comment loop due to watcher email autoresponder
----------------------------------------------------
Key: INFRA-1356
URL: https://issues.apache.org/jira/browse/INFRA-1356
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: JIRA
Reporter: Roy T. Fielding
Priority: Critical
See JCR-940. https://issues.apache.org/jira/browse/JCR-940
The loop resulted in a new comment every two minutes. Fortunately, our developers
are in Europe and were able to cut the loop in less than an hour.
Please turn off the ability to comment on an issue by responding to the jira mail, at least
until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525514 ]
Henri Yandell commented on INFRA-1356:
--------------------------------------
I've turned it off (pretty much... made the period of checking 99999999 minutes).
Jeff, any thoughts on this? It's not something I've run in JIRA before. I thought there was an email server involved in it for both receiving and sending, so I don't get why said server isn't handing the looping.
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525946 ]
Joe Schaefer commented on INFRA-1356:
-------------------------------------
Not on our jira- one of our admins saw fit to disabling the "Precedence: bulk" header.
FWIW, here is the text of the original email, since the comments
have since been deleted from the Jackrabbit issue:
======
Bedankt voor uw bericht - helaas ben ik op dit moment niet in staat mijn
email te lezen maar zal reageren wanneer ik terug ben. Voor dringende
zaken kunt u contact opnemen met XXXXXXX op nummer DDDDDD.
Thank you for contacting me - unfortunately I am away from my email
right now but I will reply to you on my return. In the meantime, if you
need some assistance, please call XXXXXXX at DDDDDD.
======
What phrases do you suggest we target in the procmail rule?
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525788 ]
Sebb commented on INFRA-1356:
-----------------------------
Presumably the auto responder is also ignoring the Reply-To header?
I assume it must have used the From: address to reply...
Could JIRA be set to use a different From address for outgoing mails?
Or perhaps that's a lot of work - or would cause other problems.
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Jeff Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537206 ]
Jeff Turner commented on INFRA-1356:
------------------------------------
> Should the header be turned back on?
Who turned the Precedence: Bulk header off, and why?
The only reason I can think of for turning it off is if some mailing lists reject emails with "Precedence: bulk". I don't think that's been the case at Apache. Is there an easy way to check the list setups for bulk-friendliness? Otherwise I guess we just turn it back on and see who complains. I'll do this in the next few days if nobody shouts.
The autoreply that caused all this chaos is pasted below. There is not a damn thing we can filter on, except perhaps "X-MimeOLE: .*Microsoft" or "From:.*@gx.nl". We can't complain too loudly if Precedence: bulk was off, as we're at least partly at fault for the loop.
Return-Path: bramk@gx.nl
X-Original-To: jira@brutus.apache.org
Delivered-To: jira@brutus.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.2])
by brutus.apache.org (Postfix) with SMTP id 71B75714035
for <ji...@brutus.apache.org>; Wed, 5 Sep 2007 23:37:16 -0700 (PDT)
Received: (qmail 228 invoked by uid 500); 6 Sep 2007 06:37:02 -0000
Delivered-To: apmail-jira@apache.org
Received: (qmail 221 invoked by uid 99); 6 Sep 2007 06:37:02 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2007 23:37:02 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of bramk@gx.nl designates 193.173.25.11 as permitted sender)
Received: from [193.173.25.11] (HELO boba.gx.nl) (193.173.25.11)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2007 06:36:57 +0000
Received: from darth-vader.nijmegen.gx.nl (vpn.gx.nl [193.173.25.2])
by boba.gx.nl (8.13.1/8.13.1) with ESMTP id l866aYjG025761
for <ji...@apache.org>; Thu, 6 Sep 2007 08:36:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C7F050.44FA9D29"
Subject: RE: [jira] Commented: (JCR-940) add db connection autoConnect for BundleDbPersistenceManager.
Date: Thu, 6 Sep 2007 08:36:34 +0200
Message-ID: <34...@darth-vader.nijmegen.gx.nl>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [jira] Commented: (JCR-940) add db connection autoConnect for BundleDbPersistenceManager.
Thread-Index: AcfwUETZHj3OPQWxRw+xFDGhWqk1yQAAAAG0
From: Bram de Kruijff <br...@gx.nl>
To: "Martijn Hendriks (JIRA)" <ji...@apache.org>
X-Virus-Scanned: by amavisd-new
X-Virus-Checked: Checked by ClamAV on apache.org
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Bedankt voor uw bericht - helaas ben ik op dit moment niet in staat mijn
email te lezen maar zal reageren wanneer ik terug ben. Voor dringende
zaken kunt u contact opnemen met Marieke Smit op nummer +31
(0)24-3888261.
Thank you for contacting me - unfortunately I am away from my email
right now but I will reply to you on my return. In the meantime, if you
need some assistance, please call Marieke Smit at +31 (0)24-3888261.
--
Bram de Kruijff
<GX> creative online development B.V.
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525780 ]
Joe Schaefer commented on INFRA-1356:
-------------------------------------
I've looked at the raw emails which caused this,
and they appear to be sent from some Microsoft
product which makes no attempt to mark the
email as being auto-replies. I'm not sure what can
be done to remedy the situation.
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525807 ]
Joe Schaefer commented on INFRA-1356:
-------------------------------------
What we could do is configure jira to
set the "Precedence: bulk" header,
which should tell any decent autoresponder
to ignore jira emails.
This will likely break jira notifications
to a few of our mailing lists, but I think
we should be able to cope with that.
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Jeff Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525891 ]
Jeff Turner commented on INFRA-1356:
------------------------------------
JIRA already does set Precedence: bulk on outgoing mails.
The world is full of useless autoresponders that don't set _any_ headers indicating the mail is an autoreply. The only solution to this is procmail filtering of mail before JIRA sees it. The current setup is described at https://svn.apache.org/repos/asf/infrastructure/trunk/jira/replybyemail/README
To fix the current problem, we need to a) update the procmailrc at https://svn.apache.org/repos/asf/infrastructure/trunk/jira/replybyemail/procmailrc with a rule matching whatever mail got through, b) make it live by running:
jira@brutus:~/infrastructure/jira/replybyemail$ svn up
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-1356) JIRA comment loop due to watcher
email autoresponder
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525982 ]
Henri Yandell commented on INFRA-1356:
--------------------------------------
Should the header be turned back on?
> JIRA comment loop due to watcher email autoresponder
> ----------------------------------------------------
>
> Key: INFRA-1356
> URL: https://issues.apache.org/jira/browse/INFRA-1356
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Roy T. Fielding
> Priority: Critical
>
> See JCR-940. https://issues.apache.org/jira/browse/JCR-940
> The loop resulted in a new comment every two minutes. Fortunately, our developers
> are in Europe and were able to cut the loop in less than an hour.
> Please turn off the ability to comment on an issue by responding to the jira mail, at least
> until jira is smart enough to recognize mail loops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.