You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2009/08/19 15:42:29 UTC
[Bug 6181] New: Add option to automatically coral-ify sa-update URIs
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
Summary: Add option to automatically coral-ify sa-update URIs
Product: Spamassassin
Version: 3.2.5
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: sa-update
AssignedTo: dev@spamassassin.apache.org
ReportedBy: jhardin@impsec.org
Add a flag to the config to tell sa-update to coral-ify the update URIs, e.g.:
http://daryl.dostech.ca/sa-update/sare/90_2tld.cf/
is rewritten to:
http://daryl.dostech.ca.nyud.net:8080/sa-update/sare/90_2tld.cf/
I know some have seen problems with Coral, but I've been running sa-update with
coral-ified URIs for a while now and I haven't seen any issues. I suspect
problems are due to your site being "close" to a dodgy cache.
This would be a kindness to third-party rules publishers, and would allow
sa-update to automatically keep the MIRRORED.BY files current without breaking
Coral use at those sites wishing to use Coral.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
Mark Martinec <Ma...@ijs.si> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Undefined |3.4.0
--- Comment #2 from Mark Martinec <Ma...@ijs.si> ---
This topic has been revived on the ML recently.
Just bringing-up the last-changed date on this PR.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
--- Comment #1 from John Hardin <jh...@impsec.org> 2009-08-19 06:44:28 PST ---
This would also allow coral-ifying URIs retrieved from DNS TXT records...
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
Mark Martinec <Ma...@ijs.si> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|3.4.0 |Future
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
Kevin A. McGrail <km...@pccc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kmcgrail@pccc.com
--- Comment #3 from Kevin A. McGrail <km...@pccc.com> ---
(In reply to comment #2)
> This topic has been revived on the ML recently.
> Just bringing-up the last-changed date on this PR.
I'm also reaching out to ASF Board unofficially to see if using Coral is
something ASF would frown upon. I sent a note about this on the 4th and pinged
again today.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
--- Comment #6 from Kevin A. McGrail <km...@pccc.com> ---
(In reply to Kevin A. McGrail from comment #5)
> (In reply to Kevin A. McGrail from comment #4)
> > I haven't gotten an unofficial response so I will add this as a question in
> > our next quarterly report to the board if Coral is something we can consider
> > using officially for the project.
> >
> > My gut tells me that they will kibash this because we should ideally be
> > using ASF resources...
>
> Added to quarterly report for feedback from Board.
Preliminary feedback:
As long as the master copy is on ASF hardware, I don't see this
as a board level issue. I would encourage talking directly
with the infrastructure team as they are genuinely curious as
to why the existing mirrors aren't sufficient
(http://www.apache.org/info/how-to-mirror), and have in the
past been willing to support working with external providers
for special cases (e.g., http://s.apache.org/sf-aoo-1).
Anyone remember why Infra didn't like our current sa-update mirror system?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
--- Comment #4 from Kevin A. McGrail <km...@pccc.com> ---
I haven't gotten an unofficial response so I will add this as a question in our
next quarterly report to the board if Coral is something we can consider using
officially for the project.
My gut tells me that they will kibash this because we should ideally be using
ASF resources...
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6181] Add option to automatically coral-ify sa-update URIs
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6181
--- Comment #5 from Kevin A. McGrail <km...@pccc.com> ---
(In reply to Kevin A. McGrail from comment #4)
> I haven't gotten an unofficial response so I will add this as a question in
> our next quarterly report to the board if Coral is something we can consider
> using officially for the project.
>
> My gut tells me that they will kibash this because we should ideally be
> using ASF resources...
Added to quarterly report for feedback from Board.
--
You are receiving this mail because:
You are the assignee for the bug.