Discuss August 2004

discuss@lists.surbl.org

56 participants
207 discussions

Redirection service - rg3.net, listed in WS.
by Patrik Nilsson 07 Aug '04

07 Aug '04

Hi, rg3.net is listed in WS. It is a redirection service, redirecting third level domains like polimidia.rg3.net. They might have spammy third level domains, but they do have non-spammy ones as well. Not sure whitelisting the second level domains is the best way to handle these kind of redirection services though. If they are whitelisted, we can't blacklist third levels below those domains that are spammy, right? Wouldn't it be better if we could treat these kind of third level redirectors similarly to the way we treat subdelegated country domains - checking the third level domain rather than the second? Extending what is done in RegistrarBoundaries.pm for URIDNSBL would probably be easier than doing something similar in SpamCopURI though. Patrik

3 4

Errors with spamassassin --lint
by Mailing List 07 Aug '04

07 Aug '04

RHEL 3.0 + SpamAssassin 2.63 + SpamCopURI 0.20 or 0.21 Using the spamcop_uri.cf file from the package at http://www.fsl.com/support/index.html Here is the output: [root@mailgw spamassassin]# spamassassin --lint Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri snurl.com *.snurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri snipurl.com *.snipurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri tinyclick.com *.tinyclick.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri babyurl.com *.babyurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri lin.kz *.lin.kz Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri *.v3.net Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri shorl.com *.shorl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri tinyurl.com *.tinyurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri xurl.us Failed to compile URI SpamAssassin tests, skipping: (syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule SPAMCOP_URI_RBL, line 1, near "eval:" syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule OB_URI_RBL, line 1, near "eval:" syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule OB_URI_RBL, line 6, near "} }" ) When I use the spamcop_uri.cf file that comes with the 0.21 distribution I get the following output: [root@mailgw spamassassin]# spamassassin --lint Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri snurl.com *.snurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri snipurl.com *.snipurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri tinyclick.com *.tinyclick.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri babyurl.com *.babyurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri lin.kz *.lin.kz Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri *.v3.net Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri shorl.com *.shorl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri tinyurl.com *.tinyurl.com Failed to parse line in SpamAssassin configuration, skipping: open_redirect_list_spamcop_uri xurl.us Failed to compile URI SpamAssassin tests, skipping: (syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule SPAMCOP_URI_RBL, line 1, near "eval:" syntax error at /usr/share/spamassassin/20_uri_tests.cf, rule URI_OFFERS, line 215, near "; }" ) If I remove the spamcop_uri.cf file, spamassassin --lint goes well. I have fairly the same setup on other boxes and don't have the problem. Kindest regards, Guy

4 4

Re: quickinspirations.com
by Jeff Chan 06 Aug '04

06 Aug '04

On Friday, July 30, 2004, 5:17:43 PM, Bitz wrote: > quickinspirations.com I went ahead and whitelisted quickinspirations.com . The site has potential for spam since it allows anyone to send their messages to anyone else, but it also probably has some legitimate uses so it probably should be whitelisted. I am writing to them about it. Looks like it was on WS. They do not look like a big time spammer, so the WS data folks should check how it got on. Jeff C. -- Jeff Chan mailto:jeffc@surbl.org http://www.surbl.org/

1 0

rsync access
by Andy Dills 06 Aug '04

06 Aug '04

Let me start by thanking everybody for their efforts with surbl...we just recently added it in to our filtering, and it's improved spamassassin dramatically. I'm a bit skeptical of the long term value, because I already see an increase of one-run-only domains. Just another $10 they have to pay to send out their spam. But regardless, it's kicking some ass right now, and every tool helps. We get a good bit of mail though (2-3mm), and would like rsync access so we can serve the zones ourselves. I filled out a request, but no luck. Somebody on vacation or something? :) So, if somebody who can enable that could contact me offlist, it would be much appreciated. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 1

RE: [SURBL-Discuss] ANNOUNCE: Mail::SpamAssassin::SpamCopURI 0.22
by Chris Santerre 06 Aug '04

06 Aug '04

>-----Original Message----- >From: Eric Kolve [mailto:ekolve@comcast.net] >Sent: Thursday, August 05, 2004 4:24 PM >To: discuss(a)lists.surbl.org; announce(a)lists.surbl.org >Subject: [SURBL-Discuss] ANNOUNCE: Mail::SpamAssassin::SpamCopURI 0.22 > > >SpamCopURI 0.22 has been released. > >This fixes any incompatibilities 2.64 users may have seen when >trying to install. > >0.22 Thu Aug 5 13:09:15 PDT 2004 > - Updated Makefile.pl to support 2.64 and including > PerMsgStatus.pm from 2.64 release. Install > process now figures out what version you have > and installs correct patched version of PerMsgStatus.pm. > >SpamCopURI now supports both 2.63 and 2.64 version of SA. > >Package is on both sourceforge and CPAN: > >http://sourceforge.net/projects/spamcopuri/ > I'm contimplating trying to look at the source and seeing if it will work with SA 2.43 just for fun! I'm still running it, and getting great results. :) --Chris

1 0

RE: [SURBL-Discuss] Errors with spamassassin --lint
by Mailing List 06 Aug '04

06 Aug '04

OK thanks, operationnal. Have a great day! -----Original Message----- From: discuss-bounces(a)lists.surbl.org [mailto:discuss-bounces@lists.surbl.org] On Behalf Of Eric Kolve Sent: Friday, August 06, 2004 11:50 To: SURBL Discussion list Subject: Re: [SURBL-Discuss] Errors with spamassassin --lint That should work. I would also clear out any copies of SpamCopURI.pm and then re-install. --eric

1 0

RE: [SURBL-Discuss] ya.com likely FP in WS
by Chris Santerre 06 Aug '04

06 Aug '04

Don't see it in my submissions. Just a few other domains ending like that. shaveyaMUNGED.com and such. --Chris >-----Original Message----- >From: Jeff Chan [mailto:jeffc@surbl.org] >Sent: Friday, August 06, 2004 7:46 AM >To: SURBL Discussion list >Subject: Re: [SURBL-Discuss] ya.com likely FP in WS > > >On Friday, August 6, 2004, 4:36:33 AM, Patrik Nilsson wrote: >> ya.com is listed in WS. > >> I can't find any recent NANAS reports where the domain is >used in uri's. >> They seem to be an ISP, with the domain showing up in >footers in legit mail >> when their webmail service is used. > >Thanks for the heads up. Looks like a legitimate, old (1995) ISP. >I've whitelisted it. > >WS folks, please find a way to keep ones like this off the list. > >Thanks, > >Jeff C. > >_______________________________________________ >Discuss mailing list >Discuss(a)lists.surbl.org >http://lists.surbl.org/mailman/listinfo/discuss >

1 0

RE: [SURBL-Discuss] Errors with spamassassin --lint
by Mailing List 06 Aug '04

06 Aug '04

Hi Erik, Ignoring the Conf.pm in my "download repository" and in "cpan's download repository /root/.cpan/build) I see the 2 following Conf.pm files: /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Conf.pm /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Conf.pm So I guess I could nuke Conf.pm and PerMsgStatus.pm in 5.8.0 and it should be OK? Thanks Guy -----Original Message----- From: discuss-bounces(a)lists.surbl.org [mailto:discuss-bounces@lists.surbl.org] On Behalf Of Eric Kolve Sent: Thursday, August 05, 2004 11:08 To: SURBL Discussion list Subject: Re: [SURBL-Discuss] Errors with spamassassin --lint It looks like you have two Conf.pm files floating around. Do a locate for 'Conf.pm', you probably have one from a previous perl install or SpamCopURI is going into the wrong place. You are looking for a directory that only has Conf.pm, PerMsgStatus.pm and SpamCopURI.pm. Remove all those files and try re-installing. --eric

2 1

Why is this?
by Doc Schneider 06 Aug '04

06 Aug '04

Why is MUNGED-m150.com being hit in SURBLs? I have one person on a list I host here who is always being tossed into spam for having their website over there. I suspect, since they're a free website provider, a lot of spamasshats use them. So can see why it is a questionable site. Is there anyway I can whitelist that site so it doesn't get caught by SURBL? Thanks, -Doc (D-Ninja)

2 4

Lag in multi.surbl.org
by ITReading ITReading 05 Aug '04

05 Aug '04

Please post when this is sorted out. Is the lag significant enough that I should consider switching back to the individual lists for everything except [ph]? Thanks in advance, Charles >Copied from <spamassassin-users(a)incubator.apache.org> >On Thursday, August 5, 2004, 2:50:59 PM, Nels Lindquist wrote: >> Is the multi.surbl.org synchronised dynamically to the individual >> lists, or is there some lag? >Yes, the source data in multi is generated at the same time as >the individual lists. The problem is that we currently have a >longish negative caching TTL on multi, which are are trying >to reduce to cut down on some of this lag that you noticed. >We hope to have it sorted out soon. >Jeff C. >-- >Jeff Chan >mailto:jeffc@surbl.org >http://www.surbl.org/

2 1

← Newer
1
...
14
15
16
17
18
19
20
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2004