QMQP-SOURCE(1)

πŸ“¦
version 3.11.7 Β· 2 versions
  • 3.11.7 Β· arch rolling, debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 11.0 Β· nixpkgs unstable
, in arch rolling, debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– QMQP-SOURCE πŸ’– β€” the qmqp-source(1) page, but make it make sense

okay bestie, so this is qmqp-source, and it lives in the General Commands Manual section 1. it's a parallelized QMQP test generator. that's the whole vibe. let's go πŸ’…


✨ NAME ✨

qmqp-source β€” parallelized QMQP test generator


πŸ¦‹ SYNOPSIS πŸ¦‹

qmqp-source [options] [inet:]host[:port]

qmqp-source [options] unix:pathname

🌸 DESCRIPTION 🌸

so like, qmqp-source connects to the named host and TCP port (default 628) and yeets one or more messages at it β€” either sequentially or in parallel, your call. the program speaks the QMQP protocol. and the connections can go to UNIX-domain</> and IPv4 or IPv6 servers. IPv4 and IPv6 are the default.

⚠️ not me dropping the biggest warning first: this is an unsupported test program. no attempt is made to maintain compatibility between successive versions. it's giving chaos energy, fr fr. use it to test, don't build your whole life on it πŸ’€

πŸŽ€ Arguments πŸŽ€

  • -4 β€” connect to the server with IPv4. this option has no effect when Postfix is built without IPv6 support. (iykyk)
  • -6 β€” connect to the server with IPv6. this option is not available when Postfix is built without IPv6 support. she's simply not invited πŸ™ˆ
  • -c β€” display a running counter that gets incremented every time a delivery completes. it's the little number that goes up πŸ“ˆ
  • -C count β€” when a host sends RESET instead of SYN|ACK, try count times before giving up. the default count is 1. specify a larger count to work around a problem with TCP/IP stacks that send RESET when the listen queue is full. like, give her a few more chances bestie 🫢
  • -f from β€” use the specified sender address (default: <foo@myhostname>).
  • -l length β€” send length bytes as the message payload. heads up: the length includes the message headers. don't forget the headers, she counts everything πŸ’…
  • -m message_count β€” send the specified number of messages (default: 1).
  • -M myhostname β€” use the specified hostname or [address] in the default sender and recipient addresses, instead of the machine hostname. main character energy: you get to pick the name ✨
  • -r recipient_count β€” send the specified number of recipients per transaction (default: 1). recipient names are generated by prepending a number to the recipient address.
  • -s session_count β€” run the specified number of QMQP sessions in parallel (default: 1). multitasking queen πŸ‘‘
  • -t to β€” use the specified recipient address (default: <foo@myhostname>).
  • -R interval β€” wait for a random period of time 0 <= n <= interval between messages. and no cap: suspending one thread does not affect other delivery threads. she's independent πŸ’…
  • -v β€” make the program more verbose, for debugging purposes. say more, bestie πŸ—£οΈ
  • -w interval β€” wait a fixed time between messages. and same deal: suspending one thread does not affect other delivery threads.

πŸ”₯ SEE ALSO πŸ”₯


πŸ‘‘ LICENSE πŸ‘‘

the Secure Mailer license must be distributed with this software. periodt. πŸ“œ


πŸ’œ AUTHOR(S) πŸ’œ

Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA

Wietse Venema Google, Inc. 111 8th Avenue New York, NY 10011, USA


okay that's the whole page bestie πŸŽ€ that's QMQP-SOURCE(1) from the General Commands Manual, signed off at the bottom with the same QMQP-SOURCE(1) you saw at the top β€” iconic symmetry, no cap πŸŒˆπŸ’–πŸ¦‹