Ticket #165 (closed bug: wontfix)
Disable perl6-internals@perl.org mailing list.
Reported by: | pmichaud | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | website | Version: | |
Severity: | medium | Keywords: | web |
Cc: | Language: | ||
Patch status: | Platform: |
Description
We continue to get messages addressed to the <perl6-internals@…> mailing list, even though it has long been obsolete. I propose that we change the address to provide an auto-response message like the following:
The <perl6-internals@perl.org> mailing list is no longer active. Please re-send your message to one of the following destinations (and possibly update your address book accordingly): - If your message is a bug report or patch for Parrot, enter a new ticket at http://trac.parrot.org/ (registration required). - If your message is a bug report or patch for Rakudo Perl, send the message to <rakudobug@perl.org>. You might also want to check http://rt.perl.org/ to see if the bug has already been reported. - If your message is about the Parrot virtual machine, send it to <parrot-dev@lists.parrot.org>. - If your message is about Rakudo Perl or any other Perl 6 implementation, send it to <perl6-compiler@perl.org>. - If you have a question about how something should work in Perl 6, send the message to <perl6-users@perl.org>. - If your message is a Perl 6 language design comment or issue, send it to <perl6-language@perl.org>. - If none of the above seem to apply to you, then <perl6-compiler@perl.org> is often a reasonably safe default for Perl 6 related items, and <parrot-dev@parrot.org> is a safe default for Parrot related items. Thank you, The Management
We might also wish to do a similar thing for the <parrot-porters@…> and <parrotbug@…> addresses.
Pm
Change History
Note: See
TracTickets for help on using
tickets.