Issue 26770 - allbugs digest contains non bugs e-mails
Summary: allbugs digest contains non bugs e-mails
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: CEE Rubicon
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-21 08:29 UTC by pavel
Modified: 2021-05-27 19:28 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2004-03-21 08:29:30 UTC
Hi,

after I entered comment to #i26025#, this digest was distributed via allbugs-digest:

--- cut here ---
allbugs Digest 21 Mar 2004 08:19:36 -0000 Issue 6460

Topics (messages 187637 through 187638):

[l10n-issues] [Issue 26025]  define LANGUAGE_GAELIC for Gaelic
        187637 by: pjanik.openoffice.org

[www-issues]  Fwd: failure notice / HATA UYARISI!
        187638 by: Ali Cimen
--- cut here ---

Why is there an mail *without* IZ number? Do you allow non-IZ mails there? I
hope not. That e-mail had almost 100 kB :-(
Comment 1 pavel 2004-03-25 21:09:06 UTC
Louis, please dispatch this e-mail to the right person.

Thanks (and sorry for bothering you directly ;-).
Comment 2 stx123 2004-03-26 09:27:11 UTC
Hi Pavel,
the good news is that allbugs@ooo does allow only messages from other lists like
issues@www, issues@sw, issues@<project> ... It's of the type sublist.

The bad news is that issues@<project> are unmoderated lists.
In your case a SPAM message was sent to issues@openoffice.org and from there
delivered to allbugs@ooo
Comment 3 lsuarezpotts 2004-03-31 22:37:44 UTC
reassigning to pjanik for review, but I think we should close this as wontfix.
louis
Comment 4 pavel 2004-04-01 04:27:01 UTC
Louis ;-)

No, the problem now is: "issues@ooo" allows e-mails not coming from IZ.

Adding this to signature of each e-mail:

--- cut here ---
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://www.openoffice.org/project_issues.html#notification
--- cut here ---

is false sense of security. Reject all e-mail to all issues@ not coming from IZ
to prevent spam.
Comment 5 lsuarezpotts 2004-04-01 05:14:52 UTC
Hi
very well, I will redirect this to support, as an RFE.
The ideal would be for all email then to have ban lists. We don't have that now.

Support: please take this on as an RFE for SourceCast.
louis

Comment 6 Unknown 2004-04-03 03:30:41 UTC
Have filed a request internally
Will update as soon as a reponse is received from the engineers

-Mohan
Comment 7 pavel 2004-05-02 11:49:27 UTC
Any update?
Comment 8 Unknown 2004-05-03 21:50:20 UTC
This is still in the engineering queue, I have just asked for an update on this
issue.
Eric
Comment 9 pavel 2004-08-01 00:04:38 UTC
And the result is?
Comment 10 Unknown 2004-08-02 19:07:05 UTC
Engineers are currently discussing the feasibility of this enhancement request.

Meanwhile a work around has been suggested-

-designate one or more persons to moderate the list
-have the legitimate users join the list (or have the moderators force-join 
them when they first see a message)
-the moderators would have to approve all submissions by people not members of 
the list
-the moderators would have to disapprove any spam (i.e., read at least far 
enough to see if it is spam)

Please inform us regarding the feasibility of this work around while the 
engineers are still looking into the feature request.
Comment 11 Unknown 2004-08-19 12:52:53 UTC
The suggestion above was not in consideration of open-source sites such as OO, 
hence it is not really very practical in this venue.
Comment 12 pavel 2005-10-08 18:09:46 UTC
What is the status of this issue?
Comment 13 Unknown 2005-10-24 23:37:02 UTC
pjanik,

I have queried the engineers regarding the status of this issue. Will get back
to you as soon as I get a response from them.

Thanks,
Karishma-Helpdesk
Comment 14 Unknown 2006-01-06 00:01:57 UTC
Hi pjanik
               Engineers have not yet come to a conclution with this issue,I 
have queried them for an update.Will get back to you as soon as they respond 
to me.

Regards,
Karthik-Support Operations
Comment 15 Unknown 2006-03-24 09:23:09 UTC
Hi,

The issue is with the product managemenet team for analyzing the possibilities
of the enhancement requested. Will get back to you as soon as we have an update.

Regards,
Jeeva
Support Operations
Comment 16 Unknown 2007-01-05 10:12:31 UTC
To CRM
Comment 17 Unknown 2007-01-09 17:25:40 UTC
Hi,

Accepted the case and working on it.

Thanks,
Pritha
Support Operations.
Comment 18 Unknown 2007-01-15 23:25:12 UTC
Hi,

We are discussing with it internally. Will update you with relevant information
ASAP. 


Thanks,
Pritha
Support Operations.
Comment 19 Unknown 2007-04-24 11:34:45 UTC
In the new Discussion Service we have a feature to Reject Headers/Content .
Using the facility of regular expressions we can reject header/content for
specific mailing list . However the only catch is that this feature would work
only for moderated list.

Moving this issue to the resolved later queue . Please reopen if necessary.
Comment 20 Unknown 2007-05-04 10:11:35 UTC
Also in the Discussion Service if issues@ is an unmoderated (or moderated or
trusted for that matter) discussion and email posting is disabled, then only
emails posted by IZ/PT (with envelop sender admin@domain) will be accepted. All
other emails posted to this list will bounce.
Comment 21 Unknown 2007-09-19 10:26:07 UTC
Updating the issue with the appropriate milestone.
Comment 22 Unknown 2008-02-25 14:05:20 UTC
Hi

This feature is fixed in Rubicon and I have verified the same on a test box
carrying the latest version. I shall close this case for now. Please feel free
to re-open, if the functionality does not satisfy your expectation when site
gets upgraded to Rubicon version of CEE.

Regards,
Vathsan
Support Operations.
Comment 23 Unknown 2008-02-26 20:58:29 UTC
Re-opening the issue.
Comment 24 Unknown 2008-02-26 20:58:45 UTC
Marking the issue as Resolved LATER.
Comment 25 Unknown 2009-01-23 09:59:37 UTC
CollabNet Support is currently reviewing the issues under Resolved-Later. If the
issues are fixed currently in any of the present CEE releases, then it will be
marked as Resolved-Fixed.

There might be a few issues which might not be in our future roadmap which might
be closed as Wontfix unless it does not lie under any custom request.
Comment 26 Unknown 2009-01-23 10:00:47 UTC
It is available in rubicon & hence marking it as fixed