Skip to content

cyrus-sasl wrong plugin dir configuration #378

Description

@xmerlin

In your message, you have indicated ${PLUGINDIR} as the default path for plugin modules, but this is incorrect.

Actually, Cyrus-SASL searches for configuration files like smtpd.conf in /opt/local/etc/sasl2/

Activity

  1. self-assigned this
    on Apr 23, 2024
  2. jperkin commented on Apr 23, 2024

    @jperkin
    Collaborator

    I think it's correct, though perhaps the wording could do with some work. For the configuration file it says:

    The configuration files for applications using the sasl2 libraries
    used to be in ${PLUGINDIR}/, but are now expected in
    ${PKG_SYSCONFDIR}/. You need to move them after upgrading the pkg.
    

    The modules themselves definitely live in ${PLUGINDIR}, so the other part of the MESSAGE also seems correct:

    ${PKGNAME} will use the following directory as the default
    path to its plugin modules:
    
            ${PLUGINDIR}
    
    The search path for plugin modules can be customized by setting the
    SASL_PATH variable to a colon-delimted list of directories in the shell
    environment.
    

    I'm generally against MESSAGE files as they often aren't helpful, and I wonder if this one is causing more problems than it helps, even though it's technically correct.

  3. xmerlin commented on Apr 23, 2024

    @xmerlin
    Author

    In theory, it is correct; in practice, it gives the user a wrong and misleading indication since the file needs to be written in a different directory.

  4. jperkin commented on Apr 24, 2024

    @jperkin
    Collaborator

    I've removed the offending text from the MESSAGE file. The cvs->git conversion process is currently having difficulties so I can't link to the change, but it will be in the next trunk build.

  5. added a commit that references this issue on Feb 6, 2025
  6. added a commit that references this issue on Jul 29, 2025
  7. added a commit that references this issue on May 22, 2026
  8. added a commit that references this issue on Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions