www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <j...@apache.org>
Subject [jira] Created: (INFRA-3403) procmail e-mail processing (JIRA mails and gmail threads issue).
Date Sat, 29 Jan 2011 21:17:46 GMT
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


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.


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.

View raw message