You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2012/06/13 08:51:44 UTC
[Bug 6806] New: Public Blacklist for Email addresses
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
Priority: P2
Bug ID: 6806
Assignee: dev@spamassassin.apache.org
Summary: Public Blacklist for Email addresses
Severity: enhancement
Classification: Unclassified
OS: Linux
Reporter: frank.urban@commerzbank.com
Hardware: PC
Status: NEW
Version: unspecified
Component: spamassassin
Product: Spamassassin
Hi,
today most SPAM passing SpamAssassin is send from real existing Freemail
addresses.
I'm now looking for a way to put them on a public Blacklist and not in our own
SpamAssassin config.
In a first step I thought check_rbl_envfrom can help here, but I seemed that
only the domain is checked here and not the whole address.
Because the @ can not be part of a DNS name I think thats the problem here.
So the next idear is to build a hash code for each email address and put this
code on a blacklist, but how can this handeled by SpamAssassin?
Frank
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
--- Comment #4 from Frank Urban <fr...@commerzbank.com> ---
I read now this old discussion and try to understand what they have done
But out of my understanding that was much more as I think that we need.
I don't want to check addresses in the body of the mail for example
I still reporting my SPAMs to a IP blacklist. There they are filtering out the
IPs from the Freemailer.
But in such a case this mail was a SPAM send from a real existing Freemailer
mailbox and so I asked them to put these email addresses to a separate
blacklist. Thats all is no problem.
The only think I need is now a SpamAssasin Plugin check the FROM address from a
email again this blacklist.
Sounds not too difficult for me.
--
You are receiving this mail because:
You are the assignee for the bug.
Re: [Bug 6806] New: Public Blacklist for Email addresses
Posted by Jose Borges Ferreira <un...@gmail.com>.
On Wed, Jun 13, 2012 at 10:11 PM, Benny Pedersen <me...@junc.org> wrote:
> Den 2012-06-13 22:43, Jose Borges Ferreira skrev:
>
>> You can consider http://www.dkim-**reputation.org/<http://www.dkim-reputation.org/>[4] that goes a
>> step forward.
>>
>
> not sure here
>
> I was referring to the fact that is not limited to freemail domains but to
all domains that support DKIM. DKIM can assure that email is from the
domain it claims to be.
>
> Not truly sure about the project status and/or the quality of that
>> reputation they provide but, at least, you can take a look on the SA
>> plugin they provide.
>>
>
> it needs more public testing works, both on client and server side to be
> usefull, currently the sa plugin supports more then one dkim-rep server to
> be queried, but there is no public source to support it
>
>
> The original email from Frank asked:
"build a hash code for each email address and put this code on a blacklist,
but how can this handeled by SpamAssassin?" .
The dkim-reputation project has solve that problem and the SA plugins they
provide show how can it be handled.
Build a reputation system is a completely different thing, although the
opendkim project (started in version 2.5.0 ) has some simple implementation
of a reputation system.
Re: [Bug 6806] New: Public Blacklist for Email addresses
Posted by Benny Pedersen <me...@junc.org>.
Den 2012-06-13 22:43, Jose Borges Ferreira skrev:
> You can consider http://www.dkim-reputation.org/ [4] that goes a
> step forward.
not sure here
> Not truly sure about the project status and/or the quality of that
> reputation they provide but, at least, you can take a look on the SA
> plugin they provide.
it needs more public testing works, both on client and server side to
be usefull, currently the sa plugin supports more then one dkim-rep
server to be queried, but there is no public source to support it
Re: [Bug 6806] New: Public Blacklist for Email addresses
Posted by Jose Borges Ferreira <un...@gmail.com>.
You can consider http://www.dkim-reputation.org/ that goes a step forward.
Not truly sure about the project status and/or the quality of that
reputation they provide but, at least, you can take a look on the SA plugin
they provide.
José Borges Ferreira
On Wed, Jun 13, 2012 at 7:51 AM,
<bu...@bugzilla.spamassassin.org>wrote:
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
>
> Priority: P2
> Bug ID: 6806
> Assignee: dev@spamassassin.apache.org
> Summary: Public Blacklist for Email addresses
> Severity: enhancement
> Classification: Unclassified
> OS: Linux
> Reporter: frank.urban@commerzbank.com
> Hardware: PC
> Status: NEW
> Version: unspecified
> Component: spamassassin
> Product: Spamassassin
>
> Hi,
>
> today most SPAM passing SpamAssassin is send from real existing Freemail
> addresses.
> I'm now looking for a way to put them on a public Blacklist and not in our
> own
> SpamAssassin config.
> In a first step I thought check_rbl_envfrom can help here, but I seemed
> that
> only the domain is checked here and not the whole address.
> Because the @ can not be part of a DNS name I think thats the problem here.
> So the next idear is to build a hash code for each email address and put
> this
> code on a blacklist, but how can this handeled by SpamAssassin?
>
> Frank
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
>
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
Frank Urban <fr...@commerzbank.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #8 from Frank Urban <fr...@commerzbank.com> ---
ok. Closed
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
Frank Urban <fr...@commerzbank.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |frank.urban@commerzbank.com
--- Comment #2 from Frank Urban <fr...@commerzbank.com> ---
Hi,
thanks for this.
I found only some discussions out of 2009 but this seemed to be a dead project.
Is it that you are talking about?
Frank
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
--- Comment #6 from Frank Urban <fr...@commerzbank.com> ---
(In reply to comment #5)
> (In reply to comment #4)
> > I read now this old discussion and try to understand what they have done
> > But out of my understanding that was much more as I think that we need.
> > I don't want to check addresses in the body of the mail for example
>
> You'd want this for a simple reason: sender uses a non Freemail addr and
> the Freemailer drop box is in the msg body and you'd miss that.
> Same applies to other relevant headers.
I get every day around 20 mails from my users regarding SPAMs passing the
filter. 18 of them are send directly from Freemailers
So I'm only interested in blocking them. SPAMs send with non Freemailer
addresse are not the problem here.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
--- Comment #3 from AXB <ax...@gmail.com> ---
(In reply to comment #2)
> Hi,
> thanks for this.
> I found only some discussions out of 2009 but this seemed to be a dead
> project.
> Is it that you are talking about?
> Frank
yep - It died because nobody was willing/able to make it happpen.
I'm sure there are several such Emailbl setups being run privately.
(I run one for a couple of friends & $dayjob)
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
--- Comment #5 from AXB <ax...@gmail.com> ---
(In reply to comment #4)
> I read now this old discussion and try to understand what they have done
> But out of my understanding that was much more as I think that we need.
> I don't want to check addresses in the body of the mail for example
You'd want this for a simple reason: sender uses a non Freemail addr and the
Freemailer drop box is in the msg body and you'd miss that.
Same applies to other relevant headers.
> I still reporting my SPAMs to a IP blacklist. There they are filtering out
> the IPs from the Freemailer.
> But in such a case this mail was a SPAM send from a real existing Freemailer
> mailbox and so I asked them to put these email addresses to a separate
> blacklist. Thats all is no problem.
> The only think I need is now a SpamAssasin Plugin check the FROM address
> from a email again this blacklist.
> Sounds not too difficult for me.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
--- Comment #1 from AXB <ax...@gmail.com> ---
To handle this you'll need a custom plugin to do the hashing/lookups
All this has been discussed many moons ago, there was a proof of concept BL
zone, etc..
Search the SA user's list archive for "Emailbl"
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6806] Public Blacklist for Email addresses
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6806
--- Comment #7 from AXB <ax...@gmail.com> ---
This should be moved to the sa-users list and Bug closed.
--
You are receiving this mail because:
You are the assignee for the bug.