My message about s - p - a - m has itself been flagged as spam- meanwhile, I am still getting bombarded. If we can't talk about it here where can we talk about it? What now?

Rob

caltrade,

theres nothing that says you cannot talk about spam here.

However, I received an email that contained the content of what you tried to post, and I can assure you that THAT wasnt going to fly.

Copying and pasting raw links that youve gotten as spam here accomplishes absolutely nothing except providing yet another site for the spammers to have their links on, broken or not And, I would have just needed to delete them upon seeing them.

The early text in your attempt to post said:

"Hi, I have the exact same problem is someone could address it."

And then you mentioned having a keyword problem...I see plenty, the domain names themselves. Look again.

The urls are all different- in every message, and they all are broken so I'm not sure what the purpose is. I am getting several every hour and they are not stopping- help- is there anything I can do!

Rob

hi guys, please don't argue here ^^;;

I'm really needing help about the problem I posted. Hope someone can help out?

Peace to all!

I get the same error (I'm on 0.9.1). It is weird... I have maybe 6 or 7 stories (I'm nog much of a blogger to be honoust) and only 1 of those stories gets the regular spam reply with a couple of dozen links. And it gets those more often every day. Really annoying. Here is the complete error I get :

Remote error: Invalid return payload: enable debugging to examine incoming payload (XML error: junk after document element at line 2) (2)

Done.

I cannot reproduce this with 0.9.2 on demo.b2evolution.net.

So, I guess you would have to enable debugging (set $debug = 1 in /conf/_advanced.php) to see what happens.

Try this one http://b2evolution.net/news/2006/05/12/the_new_central_antispam_blacklist

Stulle wrote:

Try this one http://b2evolution.net/news/2006/05/12/the_new_central_antispam_blacklist

Thanx... I used teh 0.9.1 solution and now it works. Now I'm just wondering why the last update was 2005-07-15 :-)