Henrik K wrote:
First we should test if there actually are such FPs and not speculate. ;)
There are FPs by nature. Some of the accounts are legitimate accounts
co-opted by spammers to send the phishing attempts to compromise more
accounts.
Use the list with caution, and pay attention to
On 5/19/2009 4:02 PM, Jesse Thompson wrote:
Henrik K wrote:
First we should test if there actually are such FPs and not speculate. ;)
There are FPs by nature. Some of the accounts are legitimate accounts
co-opted by spammers to send the phishing attempts to compromise more
accounts.
Use
Yet Another Ninja wrote:
from the descriptions you are using, you are speaking about a totally
different BL... this is not the one in googlegroups.
ah, my bad. I didn't know that the term 'EmailBL' was used generically.
Jesse
--
Jesse Thompson
Division of Information Technology,
On Tue, May 12, 2009 at 05:23:07PM -0400, Charles Gregory wrote:
Still no description of how an address is chosen for inclusion in
the RBL blacklist itself. Particularly where the (often forged)
From header is being used, how does the list avoid FP's?
First we should test if there actually
On Wed, 13 May 2009, Henrik K wrote:
Still no description of how an address is chosen for inclusion in
the RBL blacklist itself.
Still wouldn't mind knowing this, unless you fear it would sharing a
secret with spammers that they could use to get around this test...
First we should test if
On 5/12/2009 4:32 PM, Marc Perkel wrote:
I'm not using your plugin yet but using it from Exim instead and it's
working well. Lots of hist. I suppose we'll find out if there's any
false positives.
Here's how you do it in Exim
set acl_c_from_address = ${lc:${address:$h_From:}}
set
Yet Another Ninja wrote:
On 5/12/2009 4:32 PM, Marc Perkel wrote:
I'm not using your plugin yet but using it from Exim instead and it's
working well. Lots of hist. I suppose we'll find out if there's any
false positives.
Here's how you do it in Exim
set acl_c_from_address =
I'm not using your plugin yet but using it from Exim instead and it's
working well. Lots of hist. I suppose we'll find out if there's any
false positives.
Here's how you do it in Exim
set acl_c_from_address = ${lc:${address:$h_From:}}
set acl_c_from_address_hash = ${md5:$acl_c_from_address}
On Tue, 12 May 2009, Marc Perkel wrote:
Here's how you do it in Exim
your idea is a has a MASSIVE drawback.
It queries the mailbl for EVERY address...
That's not the whole code that I'm using. I'm just demonstrating the
concept of how you would make it usable from Exim. I have a lot of
On 5/12/2009 5:37 PM, Charles Gregory wrote:
On Tue, 12 May 2009, Marc Perkel wrote:
Here's how you do it in Exim
your idea is a has a MASSIVE drawback.
It queries the mailbl for EVERY address...
That's not the whole code that I'm using. I'm just demonstrating the
concept of how you would
I haven't been following the long thread about this plugin.
When I followed the links and examined the code/docs, I
found that I really didn't have a sense of WHAT this plugin
does.
At first I thought it was checking for spam 'reply' e-mail addresses
within the body of an e-mail (the often
On 5/12/2009 5:45 PM, Charles Gregory wrote:
I haven't been following the long thread about this plugin.
When I followed the links and examined the code/docs, I
found that I really didn't have a sense of WHAT this plugin
does.
At first I thought it was checking for spam 'reply' e-mail
On Tue, 12 May 2009, Yet Another Ninja wrote:
Oh.. you must have skipped the first 52 lines of EmailBL.pm
No I can *now* see the two lines that say where the module gathers
addresses from. If they were there before, my apologies. But I read that
section of the module pretty closely.
13 matches
Mail list logo
