PFQUEUE.CONF(5)

πŸ’– PFQUEUE.CONF(5) πŸ’–

okay bestie, welcome to the pfqueue.conf manual page, straight out of the File Formats Manual section. this is the glow-up guide for your pfqueue configuration file, and honestly? it's giving "tiny file, huge power". let's get into it ✨


🌸 NAME 🌸

pfqueue.conf β€” the pfqueue configuration file. that's it, that's the name, she's simple and she serves πŸ’…


πŸŽ€ FULL PATH πŸŽ€

/etc/pfqueue.conf or ~/.pfqueue

two homes, one queen πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea 🍡 β€” pfqueue can be configured by storing its options in configuration files. it's not complicated, she's just organized.

at startup, the vibe check goes like this:

  1. if /etc/pfqueue.conf is present, it gets read, and the options are set accordingly. ✨
  2. then, if a .pfqueue file is present in the user's home directory, that gets read too, and its options are set accordingly β€” overriding the ones stored in /etc/pfqueue.conf. your personal file said "not today" to the system one 😀
⚠️ and note, bestie: the resulting settings are then overridden by command line options. command line stays the final boss, no cap. πŸ‘‘

🌈 SYNTAX 🌈

an option can be set using the option=value syntax. simple, clean, iconic.

any line starting with a hash sign (#) will be discarded β€” that's your comment line, she's invisible, she's a ghost, she said "don't perceive me" πŸ™ˆ


✨ OPTIONS ✨

okay this is the main character section, let's go one by one 🫢

  • backends_path=<path> β€” the backends absolute path. same as the -B option in the command line. πŸ“‚
  • backend_name=<string> β€” the default backend to use. same as the -b option. 🎯
  • mta_config=<path_or_file> β€” use a custom MTA configuration. heads up: some MTA need a directory, others need a file β€” know your MTA, bestie. same as -c. πŸ—‚οΈ
  • mta_bin=<path> β€” path to the MTA executables. same as -p. πŸ”§
  • max_messages=<number> β€” the maximum number shown in a queue. same as -m. πŸ“¬
  • use_envelope=<yes/no> β€” start reading from/to fields from the envelop. same as -e if set to yes. πŸ’Œ
  • default_queue=<number> β€” use this queue at startup. see the -q option for details. πŸš€
  • scan_limit=<number> β€” scan the queue for <number> seconds at max. same as -l. ⏱️
  • scan_delay=<number> β€” seconds between queue scans. same as -d. ⏳
  • autorefresh=<number> β€” seconds between screen refreshes. same as -s. πŸ”„
  • use_colors=<yes/no> β€” use colors. same as -n. obviously you're saying yes, it's giving aesthetics 🎨
  • remote_host=<host> β€” the host to connect to, when using the socket backend. same as -r. 🌐

πŸ‘‘ AUTHOR πŸ‘‘

Stefano Rivoir <s.rivoir@gts.it>


and that's the whole page, bestie!! no crumbs left, we ate and left no evidence πŸ’…βœ¨

this little legend comes from the January 19, 2006 era, filed under PFQUEUE.CONF(5) β€” old school, still slaying, periodt πŸŽ€πŸ’–

πŸ“¦ where this page comes from