Sorry Mike, I thought I posted the part when I edited my Message about the Email generation script. I guess I cut to much. oops..

Yeah it does a great job, I was impressed with the addys, but it does suck some resources... Trading one resource hog for another doesn't work very well.... Maybe let it generate a static page of 500 addresses, using a cron job to update the list or do it manually...

Searching logs can find the bot, I've seen an article on how to block them.. But like teleport pro, I just turn off the obey robot text and continue taking what I want off a website.. So that clearly isn't going to work... Nor will ip blocking. Not to a dedicated spammer...

Encoders seem to easy, I would think they could read them..One php generator example is here :
Paul Gregg's Email Encoder

Obfuscators would probably be the best bet for xoops. But if it's incorporated into XOOPS the variable should be named by the admin.. Each site is completely different in how they do it. So they would have to figure out the pattern process for each site rather then just a one for all solution
for all sites..

Well I'll be one playing with it, on a javaside anyway ( not much of a php writer yet ).. It will include a .js file and I'll have to dig through the XOOPS files. ugh...

But first I got a new motherboard and processers screaming to be stuffed into my box

Quote:

Hell yeah, that's always nice isn't it?

Well I downloaded a couple of email extractors, and scanned these forums and my site with the email generator.. The generator worked great, aside from the bandwidth issues.. However the program gives the path of where the emails were extracted from.. And can be figured out and blocked easy to continued scanning.. So I guess the only alternative to protecting members email adys is to scramble them a bit.. Changing the me@mail.com with an icon and function call I guess..

One good thing however I pointed the extractor to the members list to get addys and no go.. Thats good.. The forums for example gave alot of returns... So I guess the best solution is to not make your addy public until a solution is figured out.

That should be a relatively good fix there....the icon and function call idea. It would be quite simple in fact and offer a good amount of protection.

You're Hired, haha.. I just hope future releases address this. You invest so much time in creating a website and user base just to have some idiot snatch them up in ten minutes.. ####...

What r These ####, did I type a bad word ?
Sorry, I can't even remember what word is was..


Hey now I remember now the word was s u c k s... Why is that word blocked.. Man, Thats been bugging me for 23 hrs and 12 min.. Yeah, Yeah I know I need to Unplug for a while, whew...

Devs, i think this function should be part of the RC3.1 release... security is a top issue IMHO. I still get these mails, and can't do much about them...

Herko

lol, yeah the #### is a bad word....shame on you, lol. No but seriously this would be great to implement in the new version. I would like to see what ono thinks about it. Maybe he has a better idea?

I recently found a unknown crawler in my XOOPS Stats list..I went to This Site...Stating Quote:

sorry to bring back an old thread but I'm starting to get tiwan spam on my xoops-only email. it's coming from t988.com.tw. is anyone else getting this? It has been going on for about a week now and this is my 3rd spam from them.

Full headers