kalob3: DKIM/Domain Keys Signature?

[Johannes Graumann]

Thanks for your input. I will forgo this for now ...

Joh

Kolab Users wrote:

>  
> 
> Hi Joh,
> 
> DKIM is a little harder to setup than SPF, SPF only
> requires that you define a TXT record in your DNS. DKIM requires that
> plus signed messages on the outbound mail server (the "last" one in your
> outbound network communicating to the destination MTA).
> 
> It must be
> your last as you can't have the email header modified after DKIM
> signing.
> 
> There's plenty of references on how to do this if you search
> the net, but you'll need more technical knowledge to implement if you
> wish to go that route.
> 
> DKIM signing would really only help spam forged
> as coming from your domain, which may not be a problem unless your a
> large email provider that spammers wish to forge.
> 
> DKIM checks inbound
> are useful though, we use those for our customers to determine spammers
> forging yahoo and gmail addresses.
> 
> On 2013-02-18 20:52, Johannes
> Graumann wrote:
> 
>> Hello,
>> 
>> I have been testing a kolab3/Debian
> wheezy set up using
>> http://www.allaboutspam.com/email-server-testOne
> of the comments that comes back is:
>> 
>>> Email does not contain any
> DKIM/Domain Keys Signature and the published Domain Keys policy does not
> specify whether to accept or reject unsigned Emails. Signing your
> Outbound emails and clearly specifying a policy to accept signed emails
> will minimize chances of your Email being considered as SPAM.
>> 
>> To
> the experienced admins here: is this worth implementing? And if so: what
> 
>> might an implementation (preferably on Debian) look like and consist
> from?
>> 
>> Thanks for your input.
>> 
>> Sincerely, Joh
>> 
>>
> _______________________________________________
>> Kolab-users mailing
> list
>> Kolab-users at kolab.org
>>
> https://www.intevation.de/mailman/listinfo/kolab-users
> 
> --
> 
> Thanks,
> 
> Michael.