Request: Please sign this list's messages via DKIM or SPF

lst_hoe02 at lst_hoe02 at
Tue Apr 5 03:34:52 EDT 2016

Zitat von Binarus via Info-cyrus <info-cyrus at>:

> On 04.04.2016 18:12, Sebastian Hagedorn via Info-cyrus wrote:
>> Personally, I think that's a phenomenally stupid approach. As long  
>> as you can't show me an RFC that says you MUST or even SHOULD use  
>> SPF or DKIM, you're breaking SMTP.
> I think it's a phenomenally intelligent approach. I can't see in  
> which way SMTP is broken by using DKIM or SPF. The DKIM signature is  
> in an additional header (additional headers *are* allowed by the  
> RFCs), and signing and checking usually is done by milters (I am  
> sure that you know them). If a message is rejected by the receiving  
> MTA due to failing SPF or DKIM, the sender will get a DSN (which is  
> perfectly in conformance with the RFCs).
> By the way, many people use all sorts of mail filtering and DSNs  
> (and do so since 20 years and more) without an RFC saying they  
> SHOULD or MUST do so. Are all people which use any sort of mail  
> filter breaking SMTP as well?
> Could you please give an example of an SMTP RFC which is violated by  
> SPF or DKIM?
> Regards,
> Binarus
>>> Due to the exponential increase of spam, we generally have to reject all
>>> messages which are not secured by SPF or DKIM, and we know a lot of other
>>> people who do the same (by the way, this has proven to be extremely
>>> effective in our case). When our MTA encounters such a message, it
>>> rejects it and returns a bounce message to the pretended sender,
>>> notifying him about the problem.

The "we generally have to reject all messages which are not secured by  
SPF or DKIM" mean you want to force others to use non standard headers  
so in fact you are breaking SMTP RFC.

It is your server so your rules, but don't complain if other do not  
agree with you.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5840 bytes
Desc: S/MIME Cryptographic Signature
URL: <>

More information about the Info-cyrus mailing list