You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2011/07/13 23:42:02 UTC
[jira] [Closed] (INFRA-3771) CMS commit email flooding
[ https://issues.apache.org/jira/browse/INFRA-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed INFRA-3771.
--------------------------------
Resolution: Fixed
Assignee: David Blevins
Fixed for OpenEJB via tweaking asf-mailer.conf.
If anyone else would like this for their project, just file a JIRA and assign it to me.
> CMS commit email flooding
> -------------------------
>
> Key: INFRA-3771
> URL: https://issues.apache.org/jira/browse/INFRA-3771
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: CMS, Subversion
> Reporter: David Blevins
> Assignee: David Blevins
> Priority: Minor
>
> Not sure how things are setup, but would excellent if we could lower the threshold on when commit messages from ' /websites/staging/' get sent as one email because it exceeds the cap.
> Typically I see:
> [This commit notification would consist of 71 parts,
> which exceeds the limit of 50 ones, so it was shortened to the summary.]
> We're getting bit as we're right at 49 with '/websites/staging/openejb'. Maybe a limit of 40 instead?
> I don't think anyone would realistically review even 40 pages of generated html, but that's another issue I suppose.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira