haraka-plugin-access-auth
Advanced tools
By default, this plugin expects the usernames used for authentication to be the email address they are authorized to send emails from. For example a user authenticated using the username user1@domain.com can only send emails from user1@domain.com but not user2@domain.com.
Configuration is stored in config/access_auth.ini and uses the INI style formatting. The following example allows a user authenticated as user1 to send emails from user1@domain.com and support@domain.com. If the username used for authentication is an email address, e.g., user@domain.com, that user can send from his own email address. The configuration supports regex matching, e.g. .*@doman.com allows the specific user to send emails on behalf of any user of domain.com.
Example:
[acl]
user1=user1@domain.com,support@domain.com
FAQs
Haraka plugin for access control by username
We found that haraka-plugin-access-auth demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.