6 messages in net.sourceforge.lists.courier-usersRE: [courier-users] DomainKeys
FromSent OnAttachments
Randy "PerlStalker" SmithDec 23, 2004 8:02 am 
Julian MehnleDec 23, 2004 10:08 am 
Ben KennedyDec 23, 2004 10:36 am 
Randy "PerlStalker" SmithDec 23, 2004 10:58 am 
Bill TaroliDec 23, 2004 1:27 pm 
Alessandro VeselyJan 14, 2007 8:48 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] DomainKeysActions...
From:Julian Mehnle (bu@mehnle.net)
Date:Dec 23, 2004 10:08:40 am
List:net.sourceforge.lists.courier-users

Randy "PerlStalker" Smith [perl@falconsroost.alamosa.co.us] wrote:

I am continuing my quixotic attempt to stop spam from coming into my mail server. Having seen the "effectiveness" of SPF, I'm now looking into implementing DomainKeys (http://antispam.yahoo.com/domainkeys).

If you think that SPF or DK will stop spam, you're certainly on the wrong track. These are sender authentication technologies, and if spammers use their own domains in the sender address (which is actually what we want), none of these technologies will be able to stop their spam.

SPF and DK are supposed to stop sender address forgery, not spam. If you are disappointed in SPF due to this misconception, you will be disappointed in DomainKeys, too.

Sender authentication can indirectly help with stopping spam, though. If you know the sender address to be authentic, you can use reputation systems (domain-based blacklists, for instance) to decide whether to accept a message.

I know I can add DomainKey checks with a courierfilter but I can't sign keys that way. Has someone done this with courier-mta or are there plans to add this fuctionality to courier-mta in the future?

Courierfilters cannot currently modify messages, so Courier would have to be modified to either allow the former or to directly support DomainKeys message signing.