This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
From time to time a virus infected mail gets delivered through the nbdev mailing list. This should not happen at all! Virus checking for mailing lists should be standard, not a feature IMHO.
I don't think any virus checking system can ever be 100% accurate and safe; my guess is that Collab are already virus checking mails, but inevitably 1 slips through now and then. Collab ?
I'm sure they don't. In the last one or two months I got at least two or three Klez infected mails through nbdev mailing list. As you can see on http://hq.mcafeeasap.com/topviruses.asp Klez is not at all an unknown virus. Or if they really do, they should probably change their software. Norton AntiVirus catchs this virus.
As dev@openide moderator, I often get bounced messages with virus attachments, which I reject. So AFAIK it works already, but I don't know the details.
Currently we do not scan for viruses in mailing list messages, these are primarily caught by list moderators or removed from the system by our operations department. There are two internal issues entered to address this problem. One is a comprehensive scanning/archive removal/denial of attachment by admins solution (PCN 6642) which has not yet been targeted. The second is for the ability to accept or deny attachments for lists (PCN5880) and is targeted for Truckee.
Sorry to say that, but PCN5880 sounds more like a work around than a real solution for the problem. A mailing list (especially an open-source one) that sends out infected mails is a problem that should be taken more seriously IMO.
Your comments are duly noted. The issue you mention is a workaround we felt was necessary to provide while the more complete solution was under development.
This feature request is targeted for a Truckee release of SourceCast. During the upgrade to that release we can verify this issue or reopen if necessary.
Closing- will confirm during upgrade.
> This feature request is targeted for a Truckee release > of SourceCast. During the upgrade to that release we > can verify this issue or reopen if necessary. Where's the "Close-before-fix" policy for www-issues is described and agreed? Please close only after actual fix. It's about a month it's fixed while it's actually not. Or is it? Is Truckee already used at netbeans.org? Where's the release plan?
Maxym - personally I agree with you, issues should not be closed until the fix is available for the user. This is the way netbeans.org/Collab issues have always worked. Collab are currently evaluating their procedures over all their clients; I am pushing for us to keep using this procedure. nb.org is not yet using "Truckee"; there is no release plan up, I'll request something be put on the site - see issue 27447.
A target milestone has not yet been assigned to this issue. Our plan is to update the issue as soon as we have more information from Product Management. The support team does check on these issues regularly. Please let us know if there are any additional considerations for this feature or concerns on the timeframe for the next update. Thanks, Jan
No changes to for either of the two enhancement requests reported in this issue. ** The scanning/archive removal/denial of attachment request(PCN 6642)is still not yet targeted for a release. ** The request for the ability to accept or deny attachments for lists (PCN5880) issue is still tentatively targeted for Truckee. Our plan is to provide another status update in 2 weeks. Please let us know if there are concerns about the timeframe for the next update. Jan
Update: This is still under consideration for Truckee. Action Plan: Awaiting more information from Engineering. Next Update: WIthin 2 weeks. Thanks, Kristen
Update: We haven;t had an update from Engineering on this issue yet. Action Plan: Continue to check in on this regularly. Next Update: By 12-13-02 Thanks, Kristen
update: i requested that management updated both internal issues: pcn 6642 and 5880. next update: in three weeks.
update: the management set a tentative milestone - plan truckee 2 - for internal issue pcn 6642 (virus checking for incoming sourcecast artifacts/attachments) action plan: i asked management again to confirm milestone next update: upon confirmation from management
update: the management team discussed the 'resources to think about addressing this in Truckee 2'. Internal issue pcn 5880 - virus/spam control; application attachment filters - was upgraded from plan truckee to plan truckee 2. action plan: continue monitoring internal issue for updates
update: i'd deliver the management position: 'Truckee 2 planning, to the point where we have a list of what we are going to do in the release as well as a schedule,...will not be to that point until mid April.'
Hi Jack, I have asked for the developments on virus filtering. I will update this issue upon engineering response or by 4/20. Thanks, Eric
2 months after 20th/4, any update ?
I have not received an update to this internal issue since the update of this is planned for truckee2. I just reminded product management of this issue as well. I hope to have an update by 6/24. Eric
Apparently filtering of attachments based on MIME type is already in place on some lists, though the list of allowed MIME types is not quite correct, see issue 34739. Leaving this isssue open to track the comprehensive virus scanning soloution we are all looking forward to.
Update: Setting the status of this issue to Resolved,Fixed. The solution for this issue has a target milestone of Truckee 3 plan. Action Plan: CollabNet support will review this issue during the upgrade to this release to confirm its resolution. If there are problems with the solution we will reopen this issue. If the solution appears to be working, we will reassign the issue to the original poster, requesting confirmation The original poster can then set the status to "Closed" or "Reopened" if necessary. Next Update: CollabNet support will review this issue during the staging process for the next upgrade.
CollabNet support - please verify which version of CEE this is fixed in (currently identified as Truckee 3), and associate the version number to release name. Thanks, Eric
Yes it was considered in Truckee3 but given the level of work, currenlty this is been considered for any of the future release and not yet decided on which release. Will update again once that is fixed.
This is been fixed in one of the future versions and this should be in resolved later queue. So reopening to move there.
moving now..
Pls let us know what future version this is fixed in, thanks.
Hi, The enhancement request has been considered for Rubicon release of CEE 5.0 . Support will continue to monitor this internally & review it in the corresponding release. Thanks, Raji Support Operations
Hi The requested feature is fixed in Rubicon. 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. Best Regards, Vathsan Support Operations.
Marking the issue as Resolved FIXED.
Setting TM
We recently moved out from Collabnet's infrastructure