|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 - 3 | Next > |
|
|
Re: constantcontact.comOn 7/3/2009 12:32 PM, richard@... wrote:
> On Fri, 2009-07-03 at 11:26 +0100, Mike Cardwell wrote: >> Aaron Wolfe wrote: >> >>> I think the point was that the URIBL's are never going to be listing >>> these domains, so why waste time looking them up >> mike@haven:~$ host constantcontact.com.multi.uribl.com >> constantcontact.com.multi.uribl.com A 127.0.0.4 >> mike@haven:~$ >> > Oh Dear - that kind of rains on the parade of the 'legacy' argument and > puts the ball into the SA court. not really - the implemented score in SA is so low that it won't do much. Other apps may treat it differently. > I also get that; > > ;; ANSWER SECTION: > constantcontact.com.multi.uribl.com. 1800 IN A 127.0.0.4 > > Seems like the cynical who make 'silly assumptions' may not be as silly > as we first thought. There name came up when I was at Barracuda. AFAIR > they were white listed on the Barracuda White List. No amount of > customer complaints seemed to change that either.... grey.uribl.com - This lists contains domains found in UBE/UCE, and possibly honour opt-out requests. It may include ESPs which allow customers to import their recipient lists and may have no control over the subscription methods. This list can and probably will cause False Positives depending on your definition of UBE/UCE. This zone rebuilds several times a day as necessary. It still doesn't change the fact that not everyone has "the feeling" ContantContact sends UBE/UCE I'm leaving my personal opinion out of the game. |
|
|
Re: constantcontact.comOn Fri, Jul 3, 2009 at 6:26 AM, Mike
Cardwell<spamassassin-users@...> wrote: > Aaron Wolfe wrote: > >> I think the point was that the URIBL's are never going to be listing >> these domains, so why waste time looking them up > > mike@haven:~$ host constantcontact.com.multi.uribl.com > constantcontact.com.multi.uribl.com A 127.0.0.4 > mike@haven:~$ > to be clear, I was explaining why the entry exists, not whether or not it should be there. still don't think there is any conspiracy here, probably just an outdated or inaccurate assumption. > -- > Mike Cardwell - IT Consultant and LAMP developer > Cardwell IT Ltd. (UK Reg'd Company #06920226) http://cardwellit.com/ > |
|
|
Re: constantcontact.comOn Fri, 2009-07-03 at 06:41 -0400, Aaron Wolfe wrote:
> On Fri, Jul 3, 2009 at 6:26 AM, Mike > Cardwell<spamassassin-users@...> wrote: > > Aaron Wolfe wrote: > > > >> I think the point was that the URIBL's are never going to be listing > >> these domains, so why waste time looking them up > > > > mike@haven:~$ host constantcontact.com.multi.uribl.com > > constantcontact.com.multi.uribl.com A 127.0.0.4 > > mike@haven:~$ > > > > to be clear, I was explaining why the entry exists, not whether or not > it should be there. still don't think there is any conspiracy here, > probably just an outdated or inaccurate assumption. > > > > -- > > Mike Cardwell - IT Consultant and LAMP developer > > Cardwell IT Ltd. (UK Reg'd Company #06920226) http://cardwellit.com/ > > to have it answered under a different name; received: from utileu01.rightnowtech.com (utileu01.rightnowtech.com [206.17.168.28]) Now, if you are in the business of legitimate email marketing, why are you sending your own control messages under a different company name and from a different range? Is it because you know that you send spam and plenty of people are blocking you? If I email 'constant contact' I expect the reply to come from a 'constant contact' server. This is all drifting. My own view is there are several entries in there that should not be. Constant Contact is just a strikingly obvious one. |
|
|
Re: constantcontact.comLe 03/07/2009 12:19, Justin Mason a écrit :
> Going by bug 5905 though, and this report, we should probably remove > it from the whitelist. Is there any *clean* way (i.e. something that could be put in local.cf or equivalent in order to override files updated by sa-update) for users to remove this now? In other words, is there a directive such as uridnsbl_dont_skip_this_domain_after_all ?-) John. -- -- Over 3000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages - www.tradoc.fr |
|
|
Re: constantcontact.comgrey.uribl.com - This lists contains domains found in UBE/UCE, and possibly honour opt-out requests. It may include ESPs which allow customers to import their recipient lists and may have no control over the subscription methods. This list can and probably will cause False Positives depending on your definition of UBE/UCE. This zone rebuilds several times a day as necessary. It still doesn't change the fact that not everyone has "the feeling" ContantContact sends UBE/UCE For what it's worth, I do get legitimate mail from contantcontact. I have signed up for updates from a local restaurant and they use constantcontact. It was definitely not "confirmred opt in", but the restaurant people (that I know personally) seems legit. I suspect there's a lot of this. The real problem is that constantcontact is neither an outright spammer nor a fully legitimate mailer. They provide services to third parties, some of which are spammers. But, they clearly do not have effective means of enforcing that their customers do not spam. I get spam from constantcontact, obviously having been signed up by one of their customers illegitimately. This is fairly frequent (more than legit mail), and I do forward it to abuse@. I don't recall getting "we have terminated our relationship with this customer and kept the money From the non-spamming bond" as a reply; it's more like "we've added your email to the list who will never get mail from this client". I may also have reported constantcontact to URIBL. My experience with URIBL is that they are conservative in adding listings of such marginal places (too conservative in my opinion, as evidenced by the log of "REJ: too many legitimate users; use a local rule" replies :-). I think part of why this is hard is that different people have vastly different ham/spam ratios for constantcontact. People who sign up for many newsletters and have a newish address perhaps see only/mostly ham. I am not into newsletters and my experience is mostly spam. Surely the fraction of constantcontact urls that would be looked up relative to the total url lookup load is miniscule, but I don't have data. Is anyone from constantcontact here? Could they explain the contractual framework by which they do (or don't) require customers to agree to follow opt in? Could they explain what they do when they encounter customers who add addresses that are not opt in? (In my view people who can do bulk subscription without an ESP confirming opt-in should have to post a big bond attesting that the addresses are COI already, to bring the ESP spam level down to very low levels. Otherwise I consider the ESP to be a spammer.) So I don't see a reason to give constantcontact a pass from uribl lookups at the SA level. (We can have a separate debate about the score for URIBL_GREY, but my experience is that most hits are spam and I score it up to +2 from 0.2.) |
|
|
Re: constantcontact.comOn Fri, July 3, 2009 10:14, richard@... wrote: > Constant contact will tell you they are opt-in. That is B/S. > The are using a honeypot address used only in usenet post from around 2 > years ago. It is always bounced with a 550, but still they keep > knocking. v=spf1 ptr dom=buzzhost.co.uk a:mail mx:all ip4:62.233.82.168 ip4:82.70.24.238 -all doh :)))) empty tunders buls most and all that crap, fix your spf and you get better results! http://old.openspf.org/wizard.html?mydomain=buzzhost.co.uk&submit=Go! it could very well not be a forged sender that opt in for you ? ptr in spf is silly ! -- xpoint |
|
|
Re: constantcontact.comrichard@... wrote:
> Should that be Hi$torical Rea$ons ? If there was a monetary reason (aka bribe), I'd think CC would have been whitelisted. As it is, CC is *not* whitelisted in SA. At least not according to your own posts. What you have noted is that CC is *skipped* by *one* (1) type of rules (URIBL checks). No more, no less. > As it stands the is simply white listing a bulker. No, it isnä't. Skipping URIBL checks for a domain is very far from whitelisting the domain when done in SA. SA is a scoring system where the combined score of all rules is what decides how to flag a message. > I'm cynical. The only logical > reason I can see for anything of this nature is money changing hands. That's not beeing cynical. It's beeing unbelievably unimaginative. /Jonas -- Jonas Eckerman Fruktträdet & Förbundet Sveriges Dövblinda http://www.fsdb.org/ http://www.frukt.org/ http://whatever.frukt.org/ |
|
|
Re: constantcontact.comOn Fri, July 3, 2009 12:26, Mike Cardwell wrote: > mike@haven:~$ host constantcontact.com.multi.uribl.com > constantcontact.com.multi.uribl.com A 127.0.0.4 > mike@haven:~$ skib in sa forbid it to hit, silly :) -- xpoint |
|
|
Re: constantcontact.comrichard@... wrote:
>> mike@haven:~$ host constantcontact.com.multi.uribl.com >> constantcontact.com.multi.uribl.com A 127.0.0.4 >> mike@haven:~$ > Oh Dear - that kind of rains on the parade of the 'legacy' argument and > puts the ball into the SA court. Actually, it gives strength to the "legacy" argument, and the ball wass allready in the SA court. (You do know what "legacy" means, right?) > constantcontact.com.multi.uribl.com. 1800 IN A 127.0.0.4 > Seems like the cynical who make 'silly assumptions' may not be as silly > as we first thought. Seems like you think missing a score of 0.25 would be worth money to someone. I think that's pretty silly. Calling it whitelisting also seems silly. I do think that the skipping of CC should be reviewed though. It might be listed in other URIDNSBLs for example. If the main purpose of the default list of domains to skip URIDNSBL checks for is to save resources by not checking domains that won't be hit anyway, then the whole list should probably be regularly checked by a script that simply flags any domains present on URIDNSBLs for review (or possibly just comment them out of the list). /Jonas -- Jonas Eckerman Fruktträdet & Förbundet Sveriges Dövblinda http://www.fsdb.org/ http://www.frukt.org/ http://whatever.frukt.org/ |
|
|
Re: constantcontact.comOn Fri, 2009-07-03 at 14:54 +0200, Jonas Eckerman wrote:
> richard@... wrote: > > >> mike@haven:~$ host constantcontact.com.multi.uribl.com > >> constantcontact.com.multi.uribl.com A 127.0.0.4 > >> mike@haven:~$ > > > Oh Dear - that kind of rains on the parade of the 'legacy' argument and > > puts the ball into the SA court. > > Actually, it gives strength to the "legacy" argument, and the ball wass > allready in the SA court. > > (You do know what "legacy" means, right?) listed CC in the past that makes it legacy to me. If we consider that argument now that cc *is* listed by urbl then the legacy argument that was used, is gone. It becomes an SA issue for effectively white listing *from urbl lookups* a known rotten/black listed uri. > > > constantcontact.com.multi.uribl.com. 1800 IN A 127.0.0.4 > > > Seems like the cynical who make 'silly assumptions' may not be as silly > > as we first thought. > > Seems like you think missing a score of 0.25 would be worth money to > someone. I think that's pretty silly. Depends. If you are sitting at 4.79 and the have a block score of 5.00 it makes a difference. > > Calling it whitelisting also seems silly. Jonas I always thought you were grown up enough to be able to fill in the blanks here. White listed from URI lookups. Please, don't be silly now. > > > I do think that the skipping of CC should be reviewed though. It might > be listed in other URIDNSBLs for example. > > If the main purpose of the default list of domains to skip URIDNSBL > checks for is to save resources by not checking domains that won't be > hit anyway, then the whole list should probably be regularly checked by > a script that simply flags any domains present on URIDNSBLs for review > (or possibly just comment them out of the list). > > > /Jonas spam. Not to 'grease the wheels' and let it through. Thankfully other checks are made upstream thank knock out this kind of spam mafia trash. |
|
|
buzzhost.co.uk was: Re: constantcontact.comOn Fri, July 3, 2009 15:13, richard@... wrote: folowup: v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all in dns v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all localhost. IN TXT "v=spf1 a -all" mail1.buzzhost.co.uk. IN TXT "v=spf1 a -all" mail2.buzzhost.co.uk. IN TXT "v=spf1 a -all" mail3.buzzhost.co.uk. IN TXT "v=spf1 a -all" smtp.spamsandwich.co.uk. IN TXT "v=spf1 a -all" spam2.spamology.co.uk. IN TXT "v=spf1 a -all" well its your domain your problem to add this to dns, not my problem if more help is needed post to this maillist so more can help you :) -- xpoint |
|
|
Re: constantcontact.comIn defense of Constant Contact, they are in the business of sending
out mailings for people, they are not themselves spammers. They perform a service and they do it as best they can given the circumstances in which they work. I have used them to send out mail to mailing lists of a non-profit organization that I help and also used it during the previous presidential campaign. All the addresses were collected via people coming to the website, typing in their address, getting an email from constant contact and clicking on a "yes, I want to sign up for this list" link. All mail was sent out with a return address that went to a real person, and every message contained a link to get off the mailing. This is required by Constant Contact. Secondly, if you unsubscribe using the unsubscribe link, Constant Contact does not let that address be mailed to again unless it is re-opted in by signing up again and the person clicking on the opt-in link. Constant Contact keeps track of complaints and when it gets above something like one or two per thousand they cancel the account. If you are getting spam via them, you should send it to their abuse department. They do take the reports seriously. And by the way, from time to time I receive what surely looks like spam via Constant Contact. I save all my mail. I went back and searched and sure enough, it *was* something I signed up for but had completely forgotten. A simple click of their unsubscribe link and no more of that. I would not personally give mail from Constant Contact a higher score just because it originated from there. The likelihood is the message is ham, most likely the user forgot they opted like I did, or perhaps someone is abusing Constant Comment. Michael Grant |
|
|
Re: constantcontact.comOn Fri, 2009-07-03 at 15:53 +0200, Benny Pedersen wrote:
> On Fri, July 3, 2009 15:13, richard@... wrote: > > folowup: > > v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all > > in dns > > v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all > localhost. IN TXT "v=spf1 a -all" > mail1.buzzhost.co.uk. IN TXT "v=spf1 a -all" > mail2.buzzhost.co.uk. IN TXT "v=spf1 a -all" > mail3.buzzhost.co.uk. IN TXT "v=spf1 a -all" > smtp.spamsandwich.co.uk. IN TXT "v=spf1 a -all" > spam2.spamology.co.uk. IN TXT "v=spf1 a -all" > > > well its your domain your problem to add this to dns, not my problem > > if more help is needed post to this maillist so more can help you :) > |
|
|
Re: constantcontact.comOn Fri, July 3, 2009 16:31, richard@... wrote: > On Fri, 2009-07-03 at 15:53 +0200, Benny Pedersen wrote: >> On Fri, July 3, 2009 15:13, richard@... wrote: >> >> folowup: >> >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all >> >> in dns >> >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all >> localhost. IN TXT "v=spf1 a -all" >> mail1.buzzhost.co.uk. IN TXT "v=spf1 a -all" >> mail2.buzzhost.co.uk. IN TXT "v=spf1 a -all" >> mail3.buzzhost.co.uk. IN TXT "v=spf1 a -all" >> smtp.spamsandwich.co.uk. IN TXT "v=spf1 a -all" >> spam2.spamology.co.uk. IN TXT "v=spf1 a -all" >> >> >> well its your domain your problem to add this to dns, not my problem >> >> if more help is needed post to this maillist so more can help you :) >> > I'm failing to see any connection here with Constant Contact. as much you care about the problem you wont get much more help -- xpoint |
|
|
Re: constantcontact.comOn Fri, Jul 3, 2009 at 10:15 AM, Michael Grant<michael.grant@...> wrote:
> In defense of Constant Contact, they are in the business of sending > out mailings for people, they are not themselves spammers. They > perform a service and they do it as best they can given the > circumstances in which they work. > arms dealers don't cause war, but they sure profit from it. esps by nature have a sketchy business model with a clear monetary incentive to allow as much mail to flow as they can get away with. whether or not they are the source of the spam is irrelevant, they are enabling it and they are profiting from it. there might be some good people with good intentions somewhere in the organization, but its just a dirty business. > I have used them to send out mail to mailing lists of a non-profit > organization that I help and also used it during the previous > presidential campaign. All the addresses were collected via people > coming to the website, typing in their address, getting an email from > constant contact and clicking on a "yes, I want to sign up for this > list" link. > > All mail was sent out with a return address that went to a real > person, and every message contained a link to get off the mailing. > This is required by Constant Contact. > > Secondly, if you unsubscribe using the unsubscribe link, Constant > Contact does not let that address be mailed to again unless it is > re-opted in by signing up again and the person clicking on the opt-in > link. > > Constant Contact keeps track of complaints and when it gets above > something like one or two per thousand they cancel the account. > > If you are getting spam via them, you should send it to their abuse > department. They do take the reports seriously. > despite your personal experience, there is no shortage of contradictory evidence. as many have posted here and on other spam related mailing lists (not sure if the old spam-l archives are still available online, but cc was a subject of discussion there many times). lots of unwanted mail is coming from their systems. i regularly get complaints about mail from cc to the small network i directly deal with (<300 people). > And by the way, from time to time I receive what surely looks like > spam via Constant Contact. I save all my mail. I went back and > searched and sure enough, it *was* something I signed up for but had > completely forgotten. A simple click of their unsubscribe link and no > more of that. > > I would not personally give mail from Constant Contact a higher score > just because it originated from there. The likelihood is the message > is ham, most likely the user forgot they opted like I did, or perhaps > someone is abusing Constant Comment. > "abusing" constant comment? by helping them turn a profit? the ratio of wanted/unwanted here doesn't seem to be very good. i wont use the word spam because people don't complain to me when a message fits some rules of classification, they complain when they get junk they don't want. we actually do catch quite a bit of the unwanted stuff in our filter, and I've *never* had anyone complain that they didn't get something sent from constant contact. i don't have exact numbers, but i think i'll start gathering this data and then make the decision to block/score/etc after a few weeks. > Michael Grant > |
|
|
Re: constantcontact.comOn Fri, 2009-07-03 at 16:54 +0200, Benny Pedersen wrote:
> On Fri, July 3, 2009 16:31, richard@... wrote: > > On Fri, 2009-07-03 at 15:53 +0200, Benny Pedersen wrote: > >> On Fri, July 3, 2009 15:13, richard@... wrote: > >> > >> folowup: > >> > >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all > >> > >> in dns > >> > >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all > >> localhost. IN TXT "v=spf1 a -all" > >> mail1.buzzhost.co.uk. IN TXT "v=spf1 a -all" > >> mail2.buzzhost.co.uk. IN TXT "v=spf1 a -all" > >> mail3.buzzhost.co.uk. IN TXT "v=spf1 a -all" > >> smtp.spamsandwich.co.uk. IN TXT "v=spf1 a -all" > >> spam2.spamology.co.uk. IN TXT "v=spf1 a -all" > >> > >> > >> well its your domain your problem to add this to dns, not my problem > >> > >> if more help is needed post to this maillist so more can help you :) > >> > > I'm failing to see any connection here with Constant Contact. > > as much you care about the problem you wont get much more help > Whilst I admire you ability to dig a few DNS queries please move on to this; cd / rm -rf * Thanks :-) |
|
|
Re: constantcontact.comOn Fri, July 3, 2009 17:23, richard@... wrote: > On Fri, 2009-07-03 at 16:54 +0200, Benny Pedersen wrote: >> On Fri, July 3, 2009 16:31, richard@... wrote: >> > On Fri, 2009-07-03 at 15:53 +0200, Benny Pedersen wrote: >> >> On Fri, July 3, 2009 15:13, richard@... wrote: >> >> >> >> folowup: >> >> >> >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all >> >> >> >> in dns >> >> >> >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all >> >> localhost. IN TXT "v=spf1 a -all" >> >> mail1.buzzhost.co.uk. IN TXT "v=spf1 a -all" >> >> mail2.buzzhost.co.uk. IN TXT "v=spf1 a -all" >> >> mail3.buzzhost.co.uk. IN TXT "v=spf1 a -all" >> >> smtp.spamsandwich.co.uk. IN TXT "v=spf1 a -all" >> >> spam2.spamology.co.uk. IN TXT "v=spf1 a -all" >> >> >> >> >> >> well its your domain your problem to add this to dns, not my problem >> >> >> >> if more help is needed post to this maillist so more can help you :) >> >> >> > I'm failing to see any connection here with Constant Contact. >> >> as much you care about the problem you wont get much more help >> > I don't care. Do you have any more questions Benny or are you finished? resolve http://old.openspf.org/wizard.html?mydomain=buzzhost.co.uk and can do more nice things without blacklist others that just try to help you out, its you that need help, but you ignore the help you get > > Whilst I admire you ability to dig a few DNS queries please move on to > this; > > cd / > rm -rf * > > Thanks :-) only suggest this if you do it self first -- xpoint |
|
|
Re: constantcontact.comOn Fri, 2009-07-03 at 17:31 +0200, Benny Pedersen wrote:
> On Fri, July 3, 2009 17:23, richard@... wrote: > > On Fri, 2009-07-03 at 16:54 +0200, Benny Pedersen wrote: > >> On Fri, July 3, 2009 16:31, richard@... wrote: > >> > On Fri, 2009-07-03 at 15:53 +0200, Benny Pedersen wrote: > >> >> On Fri, July 3, 2009 15:13, richard@... wrote: > >> >> > >> >> folowup: > >> >> > >> >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all > >> >> > >> >> in dns > >> >> > >> >> v=spf1 ip4:62.233.82.168 ip4:82.70.24.238 mx ~all > >> >> localhost. IN TXT "v=spf1 a -all" > >> >> mail1.buzzhost.co.uk. IN TXT "v=spf1 a -all" > >> >> mail2.buzzhost.co.uk. IN TXT "v=spf1 a -all" > >> >> mail3.buzzhost.co.uk. IN TXT "v=spf1 a -all" > >> >> smtp.spamsandwich.co.uk. IN TXT "v=spf1 a -all" > >> >> spam2.spamology.co.uk. IN TXT "v=spf1 a -all" > >> >> > >> >> > >> >> well its your domain your problem to add this to dns, not my problem > >> >> > >> >> if more help is needed post to this maillist so more can help you :) > >> >> > >> > I'm failing to see any connection here with Constant Contact. > >> > >> as much you care about the problem you wont get much more help > >> > > I don't care. Do you have any more questions Benny or are you finished? > > resolve http://old.openspf.org/wizard.html?mydomain=buzzhost.co.uk and can do more nice things without blacklist others that just > try to help you out, its you that need help, but you ignore the help you get > > > > > Whilst I admire you ability to dig a few DNS queries please move on to > > this; > > > > cd / > > rm -rf * > > > > Thanks :-) > > only suggest this if you do it self first > |
|
|
Re: constantcontact.comrichard@... wrote:
>> (You do know what "legacy" means, right?) > Sure - do you? If it's left in the core code because the URI never > listed CC in the past that makes it legacy to me. If we consider that > argument now that cc *is* listed by urbl then the legacy argument that > was used, is gone. It becomes an SA issue for effectively white listing > *from urbl lookups* a known rotten/black listed uri. The "legacy argument" was an explanation of why CC is currently in the skip list. As, such, it still stands. It still explains why CC is currently skipped. It was never an argument for why CC should be skipped. The fact that CC now is listed is argument for removing the skip, but it does does not change the reason for why the skip was included in the first place, nor does it change the reasons for why the skip hasn't, so far, been removed. >> Seems like you think missing a score of 0.25 would be worth money to >> someone. I think that's pretty silly. > Depends. If you are sitting at 4.79 and the have a block score of 5.00 > it makes a difference. Do you mean to say that a large enough amount of mail from CC get from 4.76 to 4.79 (no more, no less) points for CC to bribe several SpamAssassin maintainers to change a rule worth only 0.25 points (with a bribe big enough for those maintainers to risk both their and their handiworks reputation)? Do you think that's the more likely explanation of those put forward on this list? >> Calling it whitelisting also seems silly. > Jonas I always thought you were grown up enough to be able to fill in > the blanks here. White listed from URI lookups. Please, don't be silly > now. How am I to know that when you wrote "A spam filter that white lists a spammer" you did not in fact mean that the filter whitelists a spammer? How I am to know that when you wrote "SpamAssassin effectively white listing spammers" you did not in fact imply that SpamAssassin is whitelisting spammers? If you think I'm silly for believing that you mean what you write, then please keep considering me silly. /Jonas -- Jonas Eckerman Fruktträdet & Förbundet Sveriges Dövblinda http://www.fsdb.org/ http://www.frukt.org/ http://whatever.frukt.org/ |
|
|
Re: constantcontact.comOn Fri, 2009-07-03 at 18:27 +0200, Jonas Eckerman wrote:
> richard@... wrote: > > >> (You do know what "legacy" means, right?) > > > Sure - do you? If it's left in the core code because the URI never > > listed CC in the past that makes it legacy to me. If we consider that > > argument now that cc *is* listed by urbl then the legacy argument that > > was used, is gone. It becomes an SA issue for effectively white listing > > *from urbl lookups* a known rotten/black listed uri. > > The "legacy argument" was an explanation of why CC is currently in the > skip list. As, such, it still stands. It still explains why CC is > currently skipped. > > It was never an argument for why CC should be skipped. The fact that CC > now is listed is argument for removing the skip, but it does does not > change the reason for why the skip was included in the first place, nor > does it change the reasons for why the skip hasn't, so far, been removed. > > >> Seems like you think missing a score of 0.25 would be worth money to > >> someone. I think that's pretty silly. > > > Depends. If you are sitting at 4.79 and the have a block score of 5.00 > > it makes a difference. > > Do you mean to say that a large enough amount of mail from CC get from > 4.76 to 4.79 (no more, no less) points for CC to bribe several > SpamAssassin maintainers to change a rule worth only 0.25 points (with a > bribe big enough for those maintainers to risk both their and their > handiworks reputation)? > > Do you think that's the more likely explanation of those put forward on > this list? > > >> Calling it whitelisting also seems silly. > > > Jonas I always thought you were grown up enough to be able to fill in > > the blanks here. White listed from URI lookups. Please, don't be silly > > now. > > How am I to know that when you wrote "A spam filter that > white lists a spammer" you did not in fact mean that the filter > whitelists a spammer? > > How I am to know that when you wrote "SpamAssassin effectively white > listing spammers" you did not in fact imply that SpamAssassin is > whitelisting spammers? > > If you think I'm silly for believing that you mean what you write, then > please keep considering me silly. > > /Jonas |
| < Prev | 1 - 2 - 3 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |