infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <>
Subject [jira] [Commented] (INFRA-6361) Configure email on
Date Fri, 20 Sep 2013 15:27:55 GMT


#asfinfra IRC Bot commented on INFRA-6361:

<pctony> this is now working, and puppet/svn have been updated accordingly.  Thanks
for the help tvansteenburgh.

> Configure email on
> ---------------------------------------
>                 Key: INFRA-6361
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: VMWare
>            Reporter: Tim Van Steenburgh
>            Assignee: Tony Stevenson
>         Attachments: postfix.patch
> Our app needs to be able to send and receive email. 
> We intend to move our daily development to this Apache-hosted Allura instance, and therefore
need email handling to be working correctly.
> Outbound email is for sending notifications to subscribed users when tickets and other
artifacts are updated. At this time, Allura does not have a mechanism for detecting or otherwise
handling bounced email. 
> Inbound email is parsed and used to automatically updated discussions on tickets and
other artifacts. We have a custom python smtp server for handling inbound email to the app
(port is configurable). The inbound addresses will need to be wild cards all the way down
to the sub-domain level. Here's an example inbound address: 
> Email sent to that address will update artifact 123 on the tool named 'tickets' in the
project 'allura' in the neighborhood 'p'.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message