Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cyrus-sasl wrong plugin dir configuration #378

Closed
xmerlin opened this issue Apr 9, 2024 · 3 comments
Closed

cyrus-sasl wrong plugin dir configuration #378

xmerlin opened this issue Apr 9, 2024 · 3 comments
Assignees

Comments

@xmerlin
Copy link

xmerlin commented Apr 9, 2024

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/

@jperkin jperkin self-assigned this Apr 23, 2024
@jperkin
Copy link
Collaborator

jperkin commented Apr 23, 2024

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.

@xmerlin
Copy link
Author

xmerlin commented Apr 23, 2024

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.

@jperkin
Copy link
Collaborator

jperkin commented Apr 24, 2024

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.

@jperkin jperkin closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants