Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F399F10E32 for ; Sun, 9 Mar 2014 22:30:49 +0000 (UTC) Received: (qmail 29306 invoked by uid 500); 9 Mar 2014 22:30:49 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 29253 invoked by uid 500); 9 Mar 2014 22:30:49 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 29245 invoked by uid 99); 9 Mar 2014 22:30:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Mar 2014 22:30:48 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Mar 2014 22:30:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=FXoR8ewHIlVuiuFp0ewhAZ7VTvR5vN/ZYMlYhABouq0=; b=BrtgI4xbLQUukPhSrswrdN8UVsj6K0I8x0AJQaBpbrwrppwNZ/NipijDRCDFU90Jiz5F5LN+bPEBABU5+7iXk+GXGobsKz9ujn+8DbxSUcHqEbEFB0caEFqrDOU/i0d5AMAUQ54mjoef1SNur2iILXpY18/KFgbSDaug1SOxrHA=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-4.v29.ch3.sourceforge.com) by sfs-alluradaemon-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WMmEf-0007tr-5W for allura-dev@incubator.apache.org; Sun, 09 Mar 2014 22:30:21 +0000 Content-Type: multipart/related; boundary="===============4284650583027266071==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "wellread1" Reply-To: "[allura:tickets] " <7230@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #7230 Legitimate posts containing links blocked Message-ID:

In-Reply-To: <5313fd0c1be1ce12f4edb5f8.tickets@allura.p.sourceforge.net> References: <5313fd0c1be1ce12f4edb5f8.tickets@allura.p.sourceforge.net> Date: Sun, 09 Mar 2014 22:30:21 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============4284650583027266071== Content-Type: multipart/alternative; boundary="===============4250508646882442306==" MIME-Version: 1.0 --===============4250508646882442306== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To assist your de-bugging I have posted another example of a blocked post. It is the post immediately preceding this one marked "Post awaiting moderation". It does not contain links but includes an escape character and some Preformatted Text. --- ** [tickets:#7230] Legitimate posts containing links blocked** **Status:** open **Milestone:** forge-backlog **Created:** Mon Mar 03, 2014 03:54 AM UTC by wellread1 **Last Updated:** Sun Mar 09, 2014 10:27 PM UTC **Owner:** nobody Periodically legitimate post containing links are blocked on Allura based forums. Can you describe the rules regarding the density, frequency and/or quantity of links that are permissible in a post so that a legitimate poster can avoid being blocked? Alternatively, is there a way of representing a link so that it easily recognized as a link but is not flagged as link? I will follow-up this post with a post that caused a problem on the KeePass forum. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============4250508646882442306== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

To assist your de-bugging I have posted another example of a blocked post. It is the post immediately preceding this one marked "Post awaiting moderation". It does not contain links but includes an escape character and some Preformatted Text.


[tickets:#7230] Legitimate posts containing links blocked

Status: open
Milestone: forge-backlog
Created: Mon Mar 03, 2014 03:54 AM UTC by wellread1
Last Updated: Sun Mar 09, 2014 10:27 PM UTC
Owner: nobody

Periodically legitimate post containing links are blocked on Allura based forums. Can you describe the rules regarding the density, frequency and/or quantity of links that are permissible in a post so that a legitimate poster can avoid being blocked? Alternatively, is there a way of representing a link so that it easily recognized as a link but is not flagged as link?

I will follow-up this post with a post that caused a problem on the KeePass forum.


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============4250508646882442306==-- --===============4284650583027266071==--