VRFYDMN_LDAP(5)

πŸ’– vrfydmn_ldap πŸ’–

okay bestie, welcome to vrfydmn_ldap, section 5 of the vrfydmn Manual ✨ this is the glow-up guide to making vrfydmn go look up your mail stuff in an LDAP database 🧚 no cap, it's lowkey iconic.


✨ NAME ✨

vrfydmn_ldap β€” lookup RFC5322 From:-addresses in an LDAP database. 🫢


🌸 SYNOPSIS 🌸

vrfydmn -l ldap:///etc/vrfydmn/ldap.cfg

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” vrfydmn uses lists and tables to look up mail related informations. and a lookup table? it can absolutely be an LDAP database. main character energy fr fr πŸ‘‘

to use LDAP lookups, you point it at a file that holds your LDAP connection and query configuration. that path must be given when vrfydmn is invoked on the command line:

vrfydmn -l ldap:///etc/vrfydmn/ldap.cfg

πŸŽ€ OPTIONS πŸŽ€

  • base (default: None) β€” the RFC2253 base DN at which to conduct the search, e.g.
base = ou=maildomains,dc=example,dc=com
  • bindmethod (default: None) β€” the method used when binding to the LDAP server. valid options are simple or sasl.
  • cacert (default: None) β€” specifies the file that contains certificates for all of the Certificate Authorities the client will recognize.
cacert = /etc/ssl/certs/cacerts.pem
  • cert (default: None) β€” specifies the file that contains the client certificate.
cert = /etc/ssl/certs/mail.example.com-crt.pem
  • filter (default: None) β€” the RFC2254 filter used to search the directory, e.g.
filter = (domain=*)
  • host (default: None) β€” the name of the host running the LDAP server, e.g.
host = 127.0.0.1, ldap.example.com
  • key (default: None) β€” specifies the file that contains the private key that matches the certificate stored in the cert file. currently, the private key must not be protected with a password, so it is of critical importance that the key file is protected carefully. πŸ”₯ protect that file like it's your phone passcode bestie
key = /etc/ssl/private/mail.example.com-key.pem
  • reqcert (default: demand) β€” specifies what checks to perform on server certificates in a TLS session, if any. the <level> can be specified as one of the following keywords:
    • never β€” the client will not request or check any server certificate. πŸ’€
    • allow β€” the server certificate is requested. if no certificate is provided, the session proceeds normally. if a bad certificate is provided, it will be ignored and the session proceeds normally. πŸ™ˆ
    • try β€” the server certificate is requested. if no certificate is provided, the session proceeds normally. if a bad certificate is provided, the session is immediately terminated. 😭
    • demand β€” the server certificate is requested. if no certificate is provided, or a bad certificate is provided, the session is immediately terminated. this is the default setting. periodt βœ‹
  • result_attrs (default: None) β€” the name of the attribute whose value the query should return.
result_attrs = domain
  • saslmech (default: None) β€” the mechanism outgoing's LDAP client should use, when it sasl-binds to the remote LDAP server. valid options are currently PLAIN or EXTERNAL.
  • scope (default: None) β€” the LDAP search scope: sub, base, or one.
  • usetls (default: No) β€” a Boolean option to enable or disable usage of TLS when connecting to the LDAP server. valid options are Yes or No.

πŸ’œ SEE ALSO πŸ’œ

vrfydmn(8)


πŸ’€ BUGS πŸ’€

there are no known bugs so far 😌 (we ate, honestly). please submit bugs to https://github.com/croessner/vrfydmn/issues.


πŸ‘‘ AUTHOR πŸ‘‘

Christian Roessner <c@roessner.co> wrote the program. 🫢

Patrick Ben Koetter <p@sys4.de> wrote this man page. ✨


🌈 RESOURCES 🌈

vrfydmn's home is at https://github.com/croessner/vrfydmn.


πŸ“ COPYING πŸ“

Copyright (C) 2014-2015 Christian Roessner. Free use of this software is granted under the terms of the GNU General Public License (GPL).


k that's the whole thing bestie, go configure ur LDAP and slay πŸ’… vrfydmn_ldap version 0.4, dated 02/09/2015 β€” mwah, ily, bye πŸŽ€