On 2/25/06, Nuno Lopes [EMAIL PROTECTED] wrote:
Maybe throttling?
You know - if one IP:
1. sends a lot of comments in one day and
2. IP is not in a white list and
3. these comments are identical and
4. there is a short period between comment posts
these comments are grouped together
On Sat, 25 Feb 2006, Nuno Lopes wrote:
spam assasin is already there:
/opt/ecelerity/3rdParty/bin/spamassassin -L -e 8
Whats the version? I'll install the same version on my machine and do
some
tests.
[EMAIL PROTECTED] root]# /opt/ecelerity/3rdParty/bin/spamassassin --version
Hi Sean,
Sean Coates wrote:
[...]
I'd prefer the dual-opt-in-like behaviour where the user is mailed and
asked to confirm that he/she submitted the note.
After say 10 unconfirmed mails by a particular address, they could get
blacklisted.
+1 for this solution, if spamassasin does not work.
||*()*|| Hi, Nuno.
NL I don't like those annoying images either. But we must do something.. I'm
NL tired of receiving a lot of spam notes every day.
Maybe throttling?
You know - if one IP:
1. sends a lot of comments in one day and
2. IP is not in a white list and
3. these comments are identical
I realise that. So why don't we set it so you have to provide a valid
email to be able to submit a note?
M
Sean Coates wrote:
Another option (in the short-term) is to simply required a valid email
address (most of the spam seems to come from the default
'[EMAIL PROTECTED]' or
Maybe throttling?
You know - if one IP:
1. sends a lot of comments in one day and
2. IP is not in a white list and
3. these comments are identical and
4. there is a short period between comment posts
these comments are grouped together with some flag and become hidden
until somebody from
Its an idea..
Instead of the captcha image, we can use a similar system that is used in
the php.net e-mails. When a note is submited, we send an e-mail, and only
when the user clicks on the link, his note is accepted.
Nuno
- Original Message -
I realise that. So why don't we set it
On Tue, 21 Feb 2006, Sean Coates wrote:
I would oppose a CAPTCHA, they are evil.
Do you have a better solution?
Run the note's text through a spam checker on the server before posting
it...
Derick
On Tue, 21 Feb 2006, Sean Coates wrote:
I would oppose a CAPTCHA, they are evil.
Do you have a better solution?
Run the note's text through a spam checker on the server before posting
it...
Derick
OK, if you are able to setup that on the master server, please do so ;)
I'll then patch the
Run the note's text through a spam checker on the server before posting
it...
OK, if you are able to setup that on the master server, please do so ;)
I'll then patch the user notes script to use it (just tell me what I
need to run).
Spam checkers don't work (particularly well). Especially
On Sat, 25 Feb 2006, Nuno Lopes wrote:
On Tue, 21 Feb 2006, Sean Coates wrote:
I would oppose a CAPTCHA, they are evil.
Do you have a better solution?
Run the note's text through a spam checker on the server before posting
it...
Derick
OK, if you are able to setup that
spam assasin is already there:
/opt/ecelerity/3rdParty/bin/spamassassin -L -e 8
Piping user notes through spamassassin won't help--at least without some
special config that I don't know about.
For example, all notes would end up with headers like the following,
because they're not actually
On Sat, 25 Feb 2006, Nuno Lopes wrote:
On Tue, 21 Feb 2006, Sean Coates wrote:
I would oppose a CAPTCHA, they are evil.
Do you have a better solution?
Run the note's text through a spam checker on the server before posting
it...
Derick
OK, if you are able to setup that on the
[sorry for the previous incomplete e-mail]
spam assasin is already there:
/opt/ecelerity/3rdParty/bin/spamassassin -L -e 8
Piping user notes through spamassassin won't help--at least without some
special config that I don't know about.
man spamassassin says:
-C path, --configpath=path,
Piping user notes through spamassassin won't help--at least without some
special config that I don't know about.
man spamassassin says:
-C path, --configpath=path, --config-file=path
Path to standard configuration dir
Cool. Out of curiosity, what does your
actually its not a config file, its a config dir :)
I have many files in /usr/share/spamassassin, although not all are
needed for us.
Ok.. what directives are you using? (-:
Anyway, I think the best thing to do now is to implement a function to
pass the note through spamassassin and display
I did something like this in my quick tests:
Nevermind, I see you've got it under control.
S
On Sat, 25 Feb 2006, Nuno Lopes wrote:
spam assasin is already there:
/opt/ecelerity/3rdParty/bin/spamassassin -L -e 8
Whats the version? I'll install the same version on my machine and do some
tests.
[EMAIL PROTECTED] root]# /opt/ecelerity/3rdParty/bin/spamassassin --version
Just my 2 cents on the use of spamassassin, how will it react to PHP
code and the like?
M
Nuno Lopes wrote:
[sorry for the previous incomplete e-mail]
spam assasin is already there:
/opt/ecelerity/3rdParty/bin/spamassassin -L -e 8
Piping user notes through spamassassin won't help--at
Hi all,
user notes are spammed in recent days/weeks.
Should we protect the submission form in some sane way (CAPTCHA)?
Friedhelm
Spammers suck.
I would be in favour of implementing a basic mathematical
skill-testing question a la Lukas Smith's blog at
http://pooteeweet.org -- it is a protection method that is still
accessible to the visually impaired, unlike classic CAPTCHA.
Dan
On 2/21/06, Friedhelm Betz [EMAIL
On Tue, 21 Feb 2006, Dan Scott wrote:
Spammers suck.
I would be in favour of implementing a basic mathematical
skill-testing question a la Lukas Smith's blog at
http://pooteeweet.org -- it is a protection method that is still
accessible to the visually impaired, unlike classic CAPTCHA.
Derick Rethans wrote:
On Tue, 21 Feb 2006, Dan Scott wrote:
Spammers suck.
I would be in favour of implementing a basic mathematical
skill-testing question a la Lukas Smith's blog at
http://pooteeweet.org -- it is a protection method that is still
accessible to the visually impaired, unlike
How about this one, I've been experimenting with, uses plain HTML obfuscating
the code with various css techiques.
http://ren.dotgeek.org/ex/captchacss.php
http://ren.dotgeek.org/ex/captchacss.phps
Jared
I don't think that the math-test would prevent much spam.
It's very easy to
This CSS-obfuscation would generate problems with text-only readers
(lynx or braille terminals), so I don't think it's a good idea.
Viele Grüße
Sebastian
Am 21.02.2006 um 13:49 schrieb Jared Williams:
How about this one, I've been experimenting with, uses plain HTML
obfuscating the
Well atm, no lynx or braille terminals can submit a bug (afaik) so not sure how
much of a problem that is.
Jared
This CSS-obfuscation would generate problems with text-only
readers (lynx or braille terminals), so I don't think it's a
good idea.
Viele Grüße
Sebastian
Am
Sebastian-H. Picklum wrote:
Hmm, you are completely right. But it's still not that accessible for
our fellow programmers who are visually impaired.
I have 4961 messages in my PHP-Notes box that I simply haven't had the
motivation to check.
Note weeding is a tedious and thankless task, so I'm
Okay, posting to php-notes@ would be another solution.
But on the other hand: Why don't we check the submitted notes for
specific words that are only used in SPAM messages in the first place
and mark them as suspicious on [EMAIL PROTECTED] So the SPAM-Protection is
transparent and finding
+1 to If you experience difficulty with the CAPTCHA image, you can
submit a note by sending an email to [EMAIL PROTECTED]
There's no need to limit this option to the visually impaired; it's
also applicable to Mr. Joe Text Browser. :)
Agreed.
S
On Tue, 21 Feb 2006, Sean Coates wrote:
If we do go to a non-handicap-friendly (pardon my use of the word
handicap if it's not PC this week) solution, we could always add a
note along the lines of Note to the visually impaired: this form
contains spam protection in the form of a CAPTCHA
I would oppose a CAPTCHA, they are evil.
Do you have a better solution?
S
I don't like those annoying images either. But we must do something.. I'm
tired of receiving a lot of spam notes every day.
Using the same system as the bugs site seems to be the best choice.. because
my attempts to stop spam (by checking IPs blacklists and by using words
blacklist) didn't work
Another option (in the short-term) is to simply required a valid email
address (most of the spam seems to come from the default
'[EMAIL PROTECTED]' or 'php-general@lists.php.net').
M
Nuno Lopes wrote:
I don't like those annoying images either. But we must do something..
I'm tired of
Another option (in the short-term) is to simply required a valid email
address (most of the spam seems to come from the default
'[EMAIL PROTECTED]' or 'php-general@lists.php.net').
Haven't checked the code recently, but I'm pretty sure a blank name
results in php-general@lists.php.net and a
Sebastian-H. Picklum wrote:
Hmm, you are completely right. But it's still not that
accessible for
our fellow programmers who are visually impaired.
I have 4961 messages in my PHP-Notes box that I simply
haven't had the motivation to check.
Note weeding is a tedious and thankless
Ohhh. Since when do we have that? Seems that I missed the news... :-)
Sebastian
Am 21.02.2006 um 19:44 schrieb Sean Coates:
Sebastian-H. Picklum wrote:
Note weeding in the current form is really not that comfortable. An
interface where you can see all newly submitted notes that have
not
Sebastian-H. Picklum wrote:
Ohhh. Since when do we have that? Seems that I missed the news... :-)
It's been around for quite a while. 1.5 years, I'd guess. I blogged
about it a few months back.
S
Am 21.02.2006 um 19:57 schrieb Nuno Lopes:
...
BTW, I don't agree with an 'accept' system. With that, almost zero
notes will be approved each day, because no one will like to take
the responsability to approve a note. Delete/reject is much simpler
and provides a faster way to have good
38 matches
Mail list logo
