You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Joe Schaefer (Closed) (JIRA)" <ji...@apache.org> on 2012/03/25 05:12:42 UTC

[jira] [Closed] (INFRA-4506) Customized bounce notification for openoffice.org domain

     [ https://issues.apache.org/jira/browse/INFRA-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Schaefer closed INFRA-4506.
-------------------------------

    Resolution: Fixed

All set.
                
> Customized bounce notification for openoffice.org domain
> --------------------------------------------------------
>
>                 Key: INFRA-4506
>                 URL: https://issues.apache.org/jira/browse/INFRA-4506
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Mail (qmail)
>            Reporter: Rob Weir
>            Priority: Critical
>
> The legacy OpenOffice.org project had an email forwarding service.  Similar to what we do with Apache, project volunteers were given openffice.org email addresses which would forward to their real addresses.    Based on previous ASF Board discussions, we will not be migrating this forwarding service to Apache.  And oracle is telling us that they will be shutting down the legacy forwarding service after March 15th.  At the same time the legacy mailing lists will be shutdown.  These also have openoffice.org email addresses.
> What we're hoping can be done is something like the following:
> 1) On or soon after March 15th, we update MX DNS records for openoffice.org so such traffic gets routed to Apache rather than Oracle
> 2)  We bounce back all such openoffice.org emails received
> 3) This is the key part.  We don't want just a generic bounce error message.  We want to bounce back with a custom response, one where we can explain the shutdown and direct the user to a project webpage where we can give a directory of where the new addresses are.  So legacy security list would map to the new ooo-security list, etc.  We just want to give the link to the mappings.  We don't want to automate the forwarding due to the large amount of spam the legacy lists receive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira