Bug 9587 - Unsubscribe from packagers@group.mageia.org
Summary: Unsubscribe from packagers@group.mageia.org
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Others (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
Depends on:
Reported: 2013-04-01 20:14 CEST by Olav Vitters
Modified: 2014-05-08 18:05 CEST (History)
4 users (show)

See Also:
Source RPM:
Status comment:


Description Olav Vitters 2013-04-01 20:14:48 CEST
I seem to be getting random personal email addressed to packagers@group.mageia.org. I do not want any Mageia emails that aren't publicly archived (Bugzilla / mailing list) and can easily be filtered (header in the email).

For now I'm deleting these emails by checking if the To: matches packagers@group.mageia.org, but this is rather error prone (cc + bcc).

Please remove me from this list/alias.


Steps to Reproduce:
Comment 1 Nicolas Vigier 2013-04-01 20:29:42 CEST
It's not possible to remove someone from the alias without also removing the user from the ldap group.

But I agree there was recently too many emails sent to this address which should have been sent to the mailing list instead. I think this is because the address is listed on this page :

Maybe it should be removed from this page, to list only the mailing lists.

CC: (none) => boklm

Nicolas Vigier 2013-04-01 20:30:51 CEST

CC: (none) => mageia-webteam

Comment 2 Thomas Backlund 2013-04-01 20:34:43 CEST
or maybe atleast set reply to the -dev ml

CC: (none) => tmb

Comment 3 Oliver Burger 2013-04-03 13:31:23 CEST
All in all I found 5 - in words FIVE - threads in my gmail account, which were addressed to the packagers@ address, including the mail about this bug report, so I have to wonder...

CC: (none) => oliver.bgr

Comment 4 Nicolas Vigier 2013-09-21 15:55:37 CEST
The packagers group email has been removed from the contact page.

Resolution: (none) => OLD

Nicolas Vigier 2014-05-08 18:05:58 CEST

CC: boklm => (none)

Note You need to log in before you can comment on or make changes to this bug.