Bug 60328 - Please delete Spam Mails from list archives
Summary: Please delete Spam Mails from list archives
Status: RESOLVED WONTFIX
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: Mailing lists (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: fd.o Admin Massive
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-05 14:09 UTC by Nino
Modified: 2015-09-18 10:33 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Comment 1 Florian Effenberger 2013-02-05 14:25:47 UTC
Only Tollef can delete mails out of the archives, the FDO archives are outside the control of TDF admins. However, I'm not sure if deleting spam isn't going to be an overly tedious task...
Comment 2 Marc Pare 2013-02-10 18:34:31 UTC
Is this even going to be seen by Tollef?

If not could someone either post the bug on the appropriate Bugzilla list or just close the bug. Spam is out of our control. Right?

Marc
Comment 3 Todd 2013-11-05 18:09:04 UTC
Please report this as a security bug!

LibreOffice_4.1.3_Linux_x86-64_rpm.tar.gz
Scientific Linux 6.4, 64 bit
Xfce 8.4
Firefox 25, 64 bit

Over on 
http://en.libreofficeforum.org/node/6957#comment-28495
When I press the "MARK as Spam" button, I get:

An HTTP error 0 occurred.
http://en.libreofficeforum.org/flag/flag/spam_flag_comment/28495?destination=node%2F6957&token=c0887299ce068d4ea1e347b9b35e502d

These things could easily carry payloads.   Please hurry up and fix!

Many thanks,
-T
Comment 4 Florian Effenberger 2013-11-05 18:10:38 UTC
libreofficeforum.org is neither hosted nor operated by TDF - you need to contact the forum admins
Comment 5 Daniel Stone 2015-09-18 10:33:53 UTC
Unfortunately Mailman's method for regenerating archives involves destroying old permalinks whilst it does so. So we tend to avoid it unless it's really unbelievably serious. Sorry.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.