pam_gromox — a PAM plugin to authenticate with Gromox


This module forwards authentication requests to the Gromox service plugins which themselves may pick MySQL or LDAP as a backend. pam_gromox is meant to be used in conjunction with non-Gromox SMTP/IMAP/etc. server processes that may be logically located before Gromox services and serving as accelerators.

Incantation in /etc/pam.d/smtp

Gromox accounts are not mapped from or to any Unix accounts, so the module that is present in the default /etc/pam.d/smtp module list within Linux distributions is not suitable and can be wholly replaced. In otherwords, /etc/pam.d/smtp need just contain:

auth required
account required

(pam_gromox does not provide a usable “account” handler, therefore “account required” would do nothing. The PAM framework always starts out with an initial deny policy, so at least one module needs to be called to make the PAM request succeed. For this reason, if there are no other “account” modules listed, should be used.)

Configuration directives in /etc/gromox/pam.cfg

Colon-separated list of directories in which further configuration files, especially those used by plugin instances, will be searched.
Default: /etc/gromox/pam:/etc/gromox
If pam_gromox detects the absence of a password but presence of a PAM conversation function, it will attempt to retrieve the password that way, and in doing so, will show this label just ahead of the nonechoing password prompt.
Default: Password:
If set to yes, service plugins that fail to load on startup are ignored. If set to no, the daemon will exit if any plugin cannot be loaded.
Default: no
Path to a text file which lists the filenames of service plugins to load, one per line.
Default: (unspecified)
Path to a secondary directory where service plugins will be loaded from if a primary search in standard directories (as per was unsuccessful.
Default: /usr/lib/gromox

See also