#81 policy lookup does TXT lookup instead of MX

v2.3.2
closed-fixed
3
2007-11-30
2007-10-29
Chris Behrens
No

According to draft-ietf-dkim-ssp-01.txt section 4.4, if there's a DNS return other than NOERROR to TXT lookup of _ssp._domainkey.domain,
one "MUST" do an MX lookup on 'domain' to see if it 'exists'. The dkim-milter code actually does a 2nd TXT lookup, instead. There _is_ a comment that says any resource record could be used, but that they picked MX. That with the fact that the word "MUST" is used above, I think dkim-milter should probably really do an MX lookup, even though the current code will function properly.

Discussion

  • Logged In: YES
    user_id=1048957
    Originator: NO

    Will verify this with the author and then figure out what action is necessary, if any.

     
    • priority: 5 --> 3
    • assigned_to: nobody --> sm-msk
     
  • Logged In: YES
    user_id=1048957
    Originator: NO

    Though that point means my code will work, the fact that it's labeled "non-normative discussion" means I'm out-of-spec by doing TXT instead of MX there so I'll have to update it.

     
  • Logged In: YES
    user_id=1048957
    Originator: NO

    Fixed for v2.4.0. Betas will start later today.

     
    • status: open --> closed-fixed
     
  • Logged In: YES
    user_id=1048957
    Originator: NO

    v2.4.0 released, containing a fix for this.