[jira] [Commented] (INFRA-6361) Configure email on allura-vm.apache.org

["Dave Brondsema (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727333#comment-13727333 ] 

Dave Brondsema commented on INFRA-6361:
---------------------------------------

Per infrastructure@ thread, domain will be allura.forge.apache.org
                
> Configure email on allura-vm.apache.org
> ---------------------------------------
>
>                 Key: INFRA-6361
>                 URL: https://issues.apache.org/jira/browse/INFRA-6361
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: VMWare
>            Reporter: Tim Van Steenburgh
>
> Our app needs to be able to send and receive email. 
> WHY
> We intend to move our daily development to this Apache-hosted Allura instance, and therefore need email handling to be working correctly.
> SENDING
> 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. 
> RECEIVING
> 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: 
> 123@tickets.allura.p.allura-vm.apache.org
> 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: http://www.atlassian.com/software/jira