Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SpamAssassin: devel

[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup

 

 

SpamAssassin devel RSS feed   Index | Next | Previous | View Threaded


bugzilla-daemon at bugzilla

May 15, 2012, 5:14 AM

Post #1 of 8 (252 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #1 from Mark Martinec <Mark.Martinec [at] ijs> ---
> My intentions is to ONLY include official 2ltlds in RegistrarBoundaries and
> move the rest (vanity) to file based (20_aux_tlds.cf) which makes it easier
> to maintain and can be updated via sa-update.
>
> Before I start the ugly task I'd like to hear any comments regarding the
> proposal.

Sounds good to me.

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:16 AM

Post #2 of 8 (244 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

Kevin A. McGrail <kmcgrail [at] pccc> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |kmcgrail [at] pccc

--- Comment #2 from Kevin A. McGrail <kmcgrail [at] pccc> ---
Also sounds good to me though having a way to override everything via a cf
(which I don't think we currently have) would be ideal. I wonder if ALL of
this shouldn't be updateable via sa-update?

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:30 AM

Post #3 of 8 (247 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #3 from AXB <axb.lists [at] gmail> ---
(In reply to comment #2)
> Also sounds good to me though having a way to override everything via a cf
> (which I don't think we currently have) would be ideal. I wonder if ALL of
> this shouldn't be updateable via sa-update?

override? don't understand what you want to overide.

uridnsbl_skip_domain would pretty much overide these

don't think it's a good idea to update .pm stuff via sa-update. Too many
variables which can break it.

If required we can quick temp updates via 20_aux_tlds.cf and and use RB only in
releases

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:34 AM

Post #4 of 8 (245 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #4 from Kevin A. McGrail <kmcgrail [at] pccc> ---
(In reply to comment #3)
> (In reply to comment #2)
> > Also sounds good to me though having a way to override everything via a cf
> > (which I don't think we currently have) would be ideal. I wonder if ALL of
> > this shouldn't be updateable via sa-update?
>
> override? don't understand what you want to overide.
>
> uridnsbl_skip_domain would pretty much overide these
>
> don't think it's a good idea to update .pm stuff via sa-update. Too many
> variables which can break it.
>
> If required we can quick temp updates via 20_aux_tlds.cf and and use RB only
> in releases

I don't mean to distribute the .pm file via sa-update. I mean that perhaps the
list of TLDs should be in a cf file and not in a pm file. So if .xyzpdq tld is
released tomorrow, we can just update that cf file via sa-update and not have
to do a new release.

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:39 AM

Post #5 of 8 (246 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #5 from AXB <axb.lists [at] gmail> ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Also sounds good to me though having a way to override everything via a cf
> > > (which I don't think we currently have) would be ideal. I wonder if ALL of
> > > this shouldn't be updateable via sa-update?
> >
> > override? don't understand what you want to overide.
> >
> > uridnsbl_skip_domain would pretty much overide these
> >
> > don't think it's a good idea to update .pm stuff via sa-update. Too many
> > variables which can break it.
> >
> > If required we can quick temp updates via 20_aux_tlds.cf and and use RB only
> > in releases
>
> I don't mean to distribute the .pm file via sa-update. I mean that perhaps
> the list of TLDs should be in a cf file and not in a pm file. So if .xyzpdq
> tld is released tomorrow, we can just update that cf file via sa-update and
> not have to do a new release.

gooood morning KAM :)

we already have this: 20_aux_tlds.cf
https://svn.apache.org/repos/asf/spamassassin/trunk/rules/20_aux_tlds.cf

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:42 AM

Post #6 of 8 (247 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #6 from Kevin A. McGrail <kmcgrail [at] pccc> ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > Also sounds good to me though having a way to override everything via a cf
> > > > (which I don't think we currently have) would be ideal. I wonder if ALL of
> > > > this shouldn't be updateable via sa-update?
> > >
> > > override? don't understand what you want to overide.
> > >
> > > uridnsbl_skip_domain would pretty much overide these
> > >
> > > don't think it's a good idea to update .pm stuff via sa-update. Too many
> > > variables which can break it.
> > >
> > > If required we can quick temp updates via 20_aux_tlds.cf and and use RB only
> > > in releases
> >
> > I don't mean to distribute the .pm file via sa-update. I mean that perhaps
> > the list of TLDs should be in a cf file and not in a pm file. So if .xyzpdq
> > tld is released tomorrow, we can just update that cf file via sa-update and
> > not have to do a new release.
>
> gooood morning KAM :)
>
> we already have this: 20_aux_tlds.cf
> https://svn.apache.org/repos/asf/spamassassin/trunk/rules/20_aux_tlds.cf

I know but I'm thinking that this option "My intentions is to ONLY include
official 2ltlds in RegistrarBoundaries and move the rest (vanity) to file based
(20_aux_tlds.cf) " only allows for new entries and not removals/changes.


So I'm wondering why it isn't solely in the cf file with nothing in the .pm?

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:51 AM

Post #7 of 8 (246 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #7 from AXB <axb.lists [at] gmail> ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > (In reply to comment #2)
> > > > > Also sounds good to me though having a way to override everything via a cf
> > > > > (which I don't think we currently have) would be ideal. I wonder if ALL of
> > > > > this shouldn't be updateable via sa-update?
> > > >
> > > > override? don't understand what you want to overide.
> > > >
> > > > uridnsbl_skip_domain would pretty much overide these
> > > >
> > > > don't think it's a good idea to update .pm stuff via sa-update. Too many
> > > > variables which can break it.
> > > >
> > > > If required we can quick temp updates via 20_aux_tlds.cf and and use RB only
> > > > in releases
> > >
> > > I don't mean to distribute the .pm file via sa-update. I mean that perhaps
> > > the list of TLDs should be in a cf file and not in a pm file. So if .xyzpdq
> > > tld is released tomorrow, we can just update that cf file via sa-update and
> > > not have to do a new release.
> >
> > gooood morning KAM :)
> >
> > we already have this: 20_aux_tlds.cf
> > https://svn.apache.org/repos/asf/spamassassin/trunk/rules/20_aux_tlds.cf
>
> I know but I'm thinking that this option "My intentions is to ONLY include
> official 2ltlds in RegistrarBoundaries and move the rest (vanity) to file
> based (20_aux_tlds.cf) " only allows for new entries and not
> removals/changes.
>
>
> So I'm wondering why it isn't solely in the cf file with nothing in the .pm?

-1 for that.

Plus, do we know how this could affect speed, or if it could break apps using
the API.

the data in the .pm is very static and a default set should be provided.

--
You are receiving this mail because:
You are the assignee for the bug.


bugzilla-daemon at bugzilla

May 15, 2012, 5:55 AM

Post #8 of 8 (246 views)
Permalink
[Bug 6795] RegistrarBoundaries.pm "Two-Level TLDs" cleanup [In reply to]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6795

--- Comment #8 from Kevin A. McGrail <kmcgrail [at] pccc> ---
> -1 for that.
>
> Plus, do we know how this could affect speed, or if it could break apps
> using
> the API.
>
> the data in the .pm is very static and a default set should be provided.


I leave it to you to decide since you are taking on the task but wanted my
thoughts understood.
regards,
KAM

--
You are receiving this mail because:
You are the assignee for the bug.

SpamAssassin devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.