saslfinger(1)

πŸ“¦ version 2.1.28, in debian bookworm, ubuntu jammy

πŸ’– saslfinger(1) β€” the group chat guide πŸ’–

okay bestie, welcome to the saslfinger manual page, live from the General Commands Manual, section 1, and she is the little utility you need when Postfix SMTP AUTH is acting up and you're like "why 😭". Sit down, grab a strawberry πŸ“, we're doing this together.


✨ NAME ✨

saslfinger β€” a utility to collect SMTP AUTH relevant configuration for Postfix πŸ’…


🌸 SYNOPSIS 🌸

saslfinger [-chs]

πŸ¦‹ DESCRIPTION πŸ¦‹

so saslfinger is a utility to collect SMTP AUTH relevant configuration for Postfix. that's the whole vibe. πŸŽ€

depending on how you run it, it will search for information on server-side or client-side SMTP AUTH configuration settings in Postfix and Cyrus SASL. literally just depends on the flags you give her. icon behavior, no cap.


πŸ‘‘ OPTIONS πŸ‘‘

  • -c β€” if you run saslfinger with the option -c it will collect data required for client-side SMTP AUTH. and what is client-side SMTP AUTH, you ask? it's when the Postfix smtp daemon uses SMTP AUTH to authenticate itself with a remote mail server that offers SMTP AUTH. yes bestie, Postfix is out here introducing herself to other servers. main character energy fr fr. ✨

saslfinger will try to telnet to all hosts listed in smtp_sasl_password_maps, if it may read smtp_sasl_password_maps 🫢

the telnet test verifies your host is able to reach the remote servers and shows what AUTH mechanisms they offer β€” in some cases this is required to debug client-side SMTP AUTH. so like, it's not extra, it's necessary. iykyk.

⚠️ important: by default smtp_sasl_password_maps must be read-only to root, since these maps contain the usernames and passwords to authenticate. if you run saslfinger as root access will be no problem, but saslfinger will fail if you lack the permissions to access smtp_sasl_password_maps. πŸ’€

if you want to run the telnet test, but don't want to run saslfinger as root, change permissions of smtp_sasl_password_maps so that the user running saslfinger may access smtp_sasl_password_maps while you debug. temporary chaos, we love her πŸ™ˆ

*note: you don't need to worry about saslfinger doing anything with the username or password stored next to the remote hosts in your smtp_sasl_password_maps; saslfinger completely ignores these informations! she is NOT nosy. she is a respectful queen. πŸ‘‘

  • -h β€” if you run saslfinger with the option -h it will print a little help message that tells you about the options you can use. tiny, cute, helpful. the little sister energy we needed. πŸŽ€
  • -s β€” if you run saslfinger with the option -s it will collect data required for server-side SMTP AUTH. and server-side SMTP AUTH is when the Postfix smtpd daemon offers SMTP AUTH to mail clients. she's the one hosting, she's the one providing, she's the one saying "come in, authenticate, you're welcome here" πŸ’–

πŸŽ€ FILES πŸŽ€

  • saslfinger β€” the script you need to run. ✨
  • saslfinger.1 β€” the man page you are currently reading. hi bestie, you're here πŸ’…

🌈 AUTHOR 🌈

Patrick Koetter, <patrick.koetter@state-of-mind.de>, http://www.state-of-mind.de

you will find the newest version of saslfinger at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/ πŸ¦‹


πŸ› BUGS πŸ›

please report bugs to <patrick.koetter@state-of-mind.de> β€” be nice, be specific, be a good citizen 🫢


and that's the page, bestie!! πŸŽ‰ this lil guide comes to you from the Manuals collection, hanging out in the User section as saslfinger(1) β€” so if you ever need her again, you know exactly where to find her. slay, go debug your SMTP AUTH, you've got this πŸ’–βœ¨πŸŒΈπŸ¦‹πŸ’…

πŸ“¦ where this page comes from