Skip to main content

132.15 breaks pam_imunify for dovecot

Answered

Comments

8 comments

  • cPRex Jurassic Moderator

    Hey there!  Can you provide me with some additional details?  While the update was pushed just last night I don't have much to go on with this information.  I'd need to know which specific log you're seeing this in, and if possible, what action in the interface or mail client triggers this behavior.

    If this is something you can reproduce it would be best to create a ticket so we can examine this as soon as possible.

    0
  • cPRex Jurassic Moderator

    I did just check /var/log/maillog on an active server running Imunify360 and I'm not seeing this particular error message there.

    0
  • cPRex Jurassic Moderator

    Update - we've been able to reproduce this and I'll have some more details soon.

    0
  • cPRex Jurassic Moderator

    We're currently tracking this through case CPANEL-50784 and we're also working with the Imunify team as well as this doesn't seem to be happening across all machines.  If I hear any other updates I'll be sure to post!

    0
  • incubatec

    I have done some comparisons and as the relevant binaries are identical between .14 and .15, it probably boils down to the change in the sequence of passdb that were first introduced in .15.

    Is this the relevant fix in .16?

    • Fixed CPANEL-50784: Fix request parsing fallback logic when integrations to dovecot don’t set a namespace in the auth request.
    0
  • cPRex Jurassic Moderator

    incubatec - yes, that fix in in 132.0.16, which will get bumped to Stable in January.

    0
  • cPRex Jurassic Moderator

    Update - this is resolved in version 132.0.17 which will be the next release!

    0

Please sign in to leave a comment.