#77 doesn't handle a selector pointing to multiple TXT records

v2.3.2
closed-fixed
3
2008-03-20
2007-10-25
No

'nuff said. Should cycle through all of them.

Discussion

    • priority: 5 --> 3
     
  • Logged In: YES
    user_id=1048957
    Originator: YES

    Actually, there's no guidance that this MUST or SHOULD be done in either RFC4871 or the SSP draft. RFC4871 says the results are undefined, but provides some guidance if an implementor chooses to cycle through all of them; the SSP draft has addressing this case listed as a to-do item for future versions.

    Accordingly, dropping priority. This won't be resolved until after 2.4.0.

     
  • Logged In: YES
    user_id=1048957
    Originator: YES

    v2.5.1 will return an error code if multiple TXT records are returned.

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

    v2.5.1 released. New status code is DKIM_STAT_MULTIDNSREPLY.