You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jeff Turner (JIRA)" <ji...@apache.org> on 2006/12/19 02:24:24 UTC

[jira] Resolved: (INFRA-412) Implement proper mail-to-jira bridge

     [ http://issues.apache.org/jira/browse/INFRA-412?page=all ]

Jeff Turner resolved INFRA-412.
-------------------------------

    Resolution: Fixed
      Assignee: Jeff Turner

Done a while back, and now documented at https://svn.apache.org/repos/asf/infrastructure/trunk/jira/replybyemail

> Implement proper mail-to-jira bridge
> ------------------------------------
>
>                 Key: INFRA-412
>                 URL: http://issues.apache.org/jira/browse/INFRA-412
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: JIRA
>         Environment: hermes, ajax
>            Reporter: Leo Simons
>         Assigned To: Jeff Turner
>
> Right now the mail-to-jira functionality is not implemented very well. (see http://issues.apache.org/jira/browse/INFRA-352 for background.) Something like the following should happen:
> 1) create a 'jiramail' user on ajax
> 2) make 'jiramail' receive jira@apache.org mail
>   2a) set up a .qmail file on hermes that forwards to jiramail@ajax.apache.org, Serge, Noel, and Jeff
>   2b) open up ajax for smtp traffic from hermes
> 3) create a .forward on ajax that invokes procmail for jiramail
> 4) we create a .procmailrc on ajax that pushes mail to a maildir folder
> 5) jira can do all the processing it needs on ajax
> Most of these tasks require the roots on hermes and ajax to implement them, some others require apmail, and some require jira admin functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira