You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2011/01/29 22:17:46 UTC
[jira] Created: (INFRA-3403) procmail e-mail processing (JIRA mails
and gmail threads issue).
procmail e-mail processing (JIRA mails and gmail threads issue).
----------------------------------------------------------------
Key: INFRA-3403
URL: https://issues.apache.org/jira/browse/INFRA-3403
Project: Infrastructure
Issue Type: Wish
Security Level: public (Regular issues)
Components: Infra Wishlist, JIRA, Mail (qmail)
Reporter: Dawid Weiss
Priority: Minor
LONG(ISH) INTRODUCTION
Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
PROBLEM/QUESTION
Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Dawid Weiss (JIRA) wrote on Sat, Jan 29, 2011 at 16:17:46 -0500:
> LONG(ISH) INTRODUCTION
>
> Hi. There's been an exchange of e-mails on the Lucene mailing list
> (started by me) about the issue gmail has with grouping (creating
> threads) out of JIRA notification e-mails. Apparently, gmail does not
> make use of standard e-mail headers and groups by e-mail subject ONLY
Then make gmail respect standards? They're about 30 years old by now.
> PROBLEM/QUESTION
>
> Is it possible/ allowed for apache committers (those having
> @apache.org e-mails) to use procmail on people.apache.org? What is the
> "correct" way of setting up a procmail filter together with the
> existing MTA (and .forward rule, I assume)?
>
It's currently possible to use .qmail/.forward files on people.a.o, but
that's deprecated and will be removed by the end of the year. The plan
is to only allow specifying a forwarding address(es).
[jira] Commented: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991331#comment-12991331 ]
Dawid Weiss commented on INFRA-3403:
------------------------------------
I decided to simply try and see if this works... and it does. Here's a sample of my config:
{noformat}
[@minotaur ~]$ cat .forward
"|exec /usr/local/bin/procmail || exit 75"
[@minotaur ~]$ cat .procmailrc
0:
{
:0fhw:
|/usr/bin/perl -pe 's/^(Subject: \[jira\] )([^:]+:)+(.*)/Subject:$3/g'
:0
!another-email@gmail.com
}
{noformat}
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991762#comment-12991762 ]
#asfinfra IRC Bot commented on INFRA-3403:
------------------------------------------
<danielsh> The plan is to have all committers email processed entirely by the MX's eventually, and letting $anyone run procmail on the MX's won't fly. Patches^WIdeas welcome.
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991351#comment-12991351 ]
Dawid Weiss commented on INFRA-3403:
------------------------------------
Ugh... Darn. Procmail really is a lifesaver in this case because there are virtually no alternatives to this problem. Basically, the options are:
1) modify gmail to support conversation headers in e-mails. [not possible for obvious reasons]
2) modify Apache JIRA to send update e-mails with constant subject header [can be done, but requires manual template tweaking. Also, some people may not like this and it's a global change],
3) use local filtering [temporarily works fine].
I don't see any other ways to achieve the desired outcome. If you can suggest something, I'd definitely try it.
While I do understand the security issues resulting from local filtering, I'm sure procmail/ mta can be configured to use a jailbox or something of this kind. Going back to non-threaded JIRA messages will be very inconvenient (for me and perhaps others).
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-3403) procmail e-mail processing (JIRA mails
and gmail threads issue).
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-3403.
------------------------------------
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991358#comment-12991358 ]
Tony Stevenson commented on INFRA-3403:
---------------------------------------
Dawid,
Like I said, we are evaluating. But for your sake I would look at alternatives if you have any, just in case we do decide to implement this.
This is not a security issue, but more one of providing resources. Allowing users to store mail locally complicates the setup. So forcing all users to forward all mail outside of the ASF means we can simplify the whole email infrastructure, and move all the effort out to the MXs.
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991372#comment-12991372 ]
Dawid Weiss commented on INFRA-3403:
------------------------------------
Thanks Tony. Still, consider my vote for keeping procmail anyway, even if local mail storage is unavailable. I know next to zero about e-mail infrastructure, but the above .forward is actually using a regular unix pipeline to filter messages. Procmail is then used inside this pipeline to modify what's needed and then forward the e-mail to another address anyway.
If this can be preserved (no local mail storage, just filtering), it would be truly splendid. Thanks in advance.
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss resolved INFRA-3403.
--------------------------------
Resolution: Not A Problem
Seems to work out of the box. Hopefully didn't do anything bad ;)
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-3403) procmail e-mail processing (JIRA
mails and gmail threads issue).
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991343#comment-12991343 ]
#asfinfra IRC Bot commented on INFRA-3403:
------------------------------------------
<pctony> Dawid, we are currently in the process of evaluating come changes to the Apache email infrastructure. One of these changes is to no longer allow the use of procmail (or any other filtering mechanism) - i.e. mail forwarding only. So I cannot comment as to whether or not this will work in the next month or so, but I strongly suggest you look for alternatives to using local filtering on people.a.o
> procmail e-mail processing (JIRA mails and gmail threads issue).
> ----------------------------------------------------------------
>
> Key: INFRA-3403
> URL: https://issues.apache.org/jira/browse/INFRA-3403
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Infra Wishlist, JIRA, Mail (qmail)
> Reporter: Dawid Weiss
> Priority: Minor
>
> LONG(ISH) INTRODUCTION
> Hi. There's been an exchange of e-mails on the Lucene mailing list (started by me) about the issue gmail has with grouping (creating threads) out of JIRA notification e-mails. Apparently, gmail does not make use of standard e-mail headers and groups by e-mail subject ONLY (sadly, it doesn't seem like they will ever to anything about it). For those using gmail with high-volume projects like Lucene this creates a big headache because every update of each issue generates a new e-mail and there is no way to 'mute' an entire issue.
> A couple home-grown solutions have been suggested -- modifying subjects via IMAP directly on gmail accounts and (mine) modifying e-mail subject headers by piping e-mails through procmail.
> PROBLEM/QUESTION
> Is it possible/ allowed for apache committers (those having @apache.org e-mails) to use procmail on people.apache.org? What is the "correct" way of setting up a procmail filter together with the existing MTA (and .forward rule, I assume)?
> Thanks in advance for your help.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira