www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding (JIRA)" <j...@apache.org>
Subject [jira] Closed: (INFRA-1041) Old Subscriber Links for the Velocity mailing lists are broken.
Date Tue, 30 Jan 2007 03:55:33 GMT

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

Roy T. Fielding closed INFRA-1041.

    Resolution: Fixed

Added the following

% cat /home/apmail/.qmail-jakarta-velocity-user-default
|bouncesaying 'This mailing list has moved to: user at velocity.apache.org'

and a similar message for the dev address.

Note, however, that many users don't even see bounce messages because they
are frequently blocked as spam.

> Old Subscriber Links for the Velocity mailing lists are broken.
> ---------------------------------------------------------------
>                 Key: INFRA-1041
>                 URL: https://issues.apache.org/jira/browse/INFRA-1041
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mailing Lists
>            Reporter: Henning Schmiedehausen
>            Priority: Minor
> After our TLP move, whenever you send mail to velocity-user-subscribe@jakarta.apache.org,
the answer is
> <velocity-user-subscribe@jakarta.apache.org>:
> Sorry, no mailbox here by that name. (#5.1.1)
> I know that this is intentional and technically the right thing, because this list is
now user@velocity and user-subscribe@velocity, however that address is referenced in numerous
articles, books and web pages and just sending out a "this does not exist" doesn't send the
right message to a potential user.
> Can we either get an alias (just as with velocity-user@jakarta) or a more meaningful
error message (that would be preferable but probably harder to do (don't know about qmail,
with sendmail you could just add a line to the access file)?
> See VELOCITY-498 for a bug report.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message