Qmqpd - Revision history

Ebroch at 06:04, 4 April 2024

2024-04-04T06:04:06Z

← Older revision		Revision as of 00:04, 4 April 2024
Line 141:		Line 141:
	Install the binaries and man pages:		Install the binaries and man pages:

	$ su Password: rootpassword # make setup-mini ./install-mini #		$ su Password: rootpassword
			# make setup-mini ./install-mini
			#

	Configure the mini-qmail installation:		Configure the mini-qmail installation:

	# ./config-mini smarthost domain plusdomain localhostname\		# ./config-mini smarthost domain plusdomain localhostname\ > smarthostip
	> smarthostip
	#		#
	Putting smarthost into control/me. . .		Putting smarthost into control/me. . .
Line 156:		Line 158:
	For example, if the smart host is mail.example.com, with an IP address of 192.168.1.4, and the mini-qmail host is null.example.com, you might use something like this:		For example, if the smart host is mail.example.com, with an IP address of 192.168.1.4, and the mini-qmail host is null.example.com, you might use something like this:

	# ./config-mini mail.example.com example.com example.com null.example.com \		# ./config-mini mail.example.com example.com example.com null.example.com \> 192.168.1.4
	> 192.168.1.4
	Putting mail.example.com into control/me. . .		Putting mail.example.com into control/me. . .
	Putting example.com into control/defaultdomain. . .		Putting example.com into control/defaultdomain. . .

Ebroch at 06:01, 4 April 2024

2024-04-04T06:01:18Z

← Older revision		Revision as of 00:01, 4 April 2024
Line 125:		Line 125:
	Build the mini-qmail Makefile:		Build the mini-qmail Makefile:

	$ make -f Makefile.mini sed '/^auto_uids\.c:/,/^$/d' qmail-1.03/Makefile > Makefile cat Makefile.mini > Makefile while read file; \ do \ echo ''; \ echo "$file: qmail-1.03/$file"; \ echo "cat qmail-1.03/$file > $file"; \ done < FILES.qmail > Makefile		$ make -f Makefile.mini sed '/^auto_uids\.c:/,/^$/d' qmail-1.03/Makefile > Makefile cat Makefile.mini > Makefile while read file; \
			do \
			echo ''; \
			echo "$file: qmail-1.03/$file"; \
			echo "cat qmail-1.03/$file > $file"; \
			done < FILES.qmail > Makefile
	$		$

	Build the mini-qmail binaries and man pages:		Build the mini-qmail binaries and man pages:

	$ make mini cat qmail-1.03/warn-auto.sh > warn-auto.sh cat warn-auto.sh config-mini.sh \ \| sed s}QMAIL}"'sed 1q conf-qmail'"}g \ ... nroff -man envelopes.5 > envelopes.0 cat qmail-1.03/forgeries.7 > forgeries.7 nroff -man forgeries.7 > forgeries.0		$ make mini cat qmail-1.03/warn-auto.sh > warn-auto.sh cat warn-auto.sh config-mini.sh \
			\| sed s}QMAIL}"'sed 1q conf-qmail'"}g \
			... nroff -man envelopes.5 > envelopes.0 cat qmail-1.03/forgeries.7 > forgeries.7 nroff -man forgeries.7 > forgeries.0
	$		$
	Install the binaries and man pages:		Install the binaries and man pages:
Line 137:		Line 144:
	Configure the mini-qmail installation:		Configure the mini-qmail installation:

	# ./config-mini smarthost domain plusdomain localhostname\ > smarthostip		# ./config-mini smarthost domain plusdomain localhostname\
			> smarthostip
	#		#
	Putting smarthost into control/me. . .		Putting smarthost into control/me. . .
Line 148:		Line 156:
	For example, if the smart host is mail.example.com, with an IP address of 192.168.1.4, and the mini-qmail host is null.example.com, you might use something like this:		For example, if the smart host is mail.example.com, with an IP address of 192.168.1.4, and the mini-qmail host is null.example.com, you might use something like this:

	# ./config-mini mail.example.com example.com example.com null.example.com \ > 192.168.1.4 Putting mail.example.com into control/me. . . Putting example.com into control/defaultdomain. . . Putting example.com into control/plusdomain. . . Putting null.example.com into control/idhost. . . Putting 192.168.1.4 into control/qmqpservers. . .		# ./config-mini mail.example.com example.com example.com null.example.com \
			> 192.168.1.4
			Putting mail.example.com into control/me. . .
			Putting example.com into control/defaultdomain. . .
			Putting example.com into control/plusdomain. . .
			Putting null.example.com into control/idhost. . .
			Putting 192.168.1.4 into control/qmqpservers. . .
	#		#

Ebroch at 05:52, 4 April 2024

2024-04-04T05:52:35Z

← Older revision		Revision as of 23:52, 3 April 2024
Line 108:		Line 108:

	$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz		$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz
	—08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz		—08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz => 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . .connected
	=> 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . .connected
	HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar]		HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar]
	0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174]		0K -> . . .. . .[100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved[6174/6174]
	$		$

Ebroch at 05:50, 4 April 2024

2024-04-04T05:50:17Z

← Older revision		Revision as of 23:50, 3 April 2024
Line 109:		Line 109:
	$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz		$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz
	—08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz		—08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz
	=> 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . .		=> 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . .connected
	~~connected!~~ HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar]		HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar]
	0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174]		0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174]
	$		$

Ebroch at 05:49, 4 April 2024

2024-04-04T05:49:24Z

← Older revision		Revision as of 23:49, 3 April 2024
Line 107:		Line 107:
	Download the mini-qmail kit using a Web browser or command-line tool. At the time of this writing, the current version is 0.63:		Download the mini-qmail kit using a Web browser or command-line tool. At the time of this writing, the current version is 0.63:

	$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz —08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz => 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . . connected! HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar] 0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174]		$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz
			—08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz
			=> 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . .
			connected! HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar]
			0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174]
	$		$

Line 134:		Line 138:
	Configure the mini-qmail installation:		Configure the mini-qmail installation:

	# ./config-mini smarthost domain plusdomain localhostname\ > smarthostip # Putting smarthost into control/me. . . Putting domain into control/defaultdomain. . . Putting plusdomain into control/plusdomain. . . Putting localhostname into control/idhost. . . Putting smarthostip into control/qmqpservers. . .		# ./config-mini smarthost domain plusdomain localhostname\ > smarthostip
			#
			Putting smarthost into control/me. . .
			Putting domain into control/defaultdomain. . .
			Putting plusdomain into control/plusdomain. . .
			Putting localhostname into control/idhost. . .
			Putting smarthostip into control/qmqpservers. . .
	#		#

Ebroch at 05:41, 4 April 2024

2024-04-04T05:41:46Z

← Older revision		Revision as of 23:41, 3 April 2024
Line 107:		Line 107:
	Download the mini-qmail kit using a Web browser or command-line tool. At the time of this writing, the current version is 0.63:		Download the mini-qmail kit using a Web browser or command-line tool. At the time of this writing, the current version is 0.63:

	$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz —08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz => 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . . connected! HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar] 0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174] $		$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz —08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz => 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . . connected! HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar] 0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174]
			$

	Unpack the kit and change to its directory:		Unpack the kit and change to its directory:
Line 121:		Line 122:
	Build the mini-qmail Makefile:		Build the mini-qmail Makefile:

	$ make -f Makefile.mini sed '/^auto_uids\.c:/,/^$/d' qmail-1.03/Makefile > Makefile cat Makefile.mini > Makefile while read file; \ do \ echo ''; \ echo "$file: qmail-1.03/$file"; \ echo "cat qmail-1.03/$file > $file"; \ done < FILES.qmail > Makefile $		$ make -f Makefile.mini sed '/^auto_uids\.c:/,/^$/d' qmail-1.03/Makefile > Makefile cat Makefile.mini > Makefile while read file; \ do \ echo ''; \ echo "$file: qmail-1.03/$file"; \ echo "cat qmail-1.03/$file > $file"; \ done < FILES.qmail > Makefile
			$

	Build the mini-qmail binaries and man pages:		Build the mini-qmail binaries and man pages:

Ebroch at 05:40, 4 April 2024

2024-04-04T05:40:58Z

Ebroch at 05:36, 4 April 2024

2024-04-04T05:36:07Z

← Older revision		Revision as of 23:36, 3 April 2024
Line 1:		Line 1:
	[[User_Tips_%26_Tricks#QMQP\|Back]]		[[User_Tips_%26_Tricks#QMQP\|Back]]
	-- [https://flylib.com/books/en/3.116.1.61/1/#google_vignette Offsite]		-- [https://flylib.com/books/en/3.116.1.61/1/#google_vignette Offsite Doc]
	<pre>		<pre>
	QMQP is a protocol designed to be used by clients for queuing messages to a smart host that handles the delivery. This relieves clients of the burden of maintaining a queue and retrying temporarily undeliverable messages. The protocol is defined at http://cr.yp.to/proto/qmqp.html. QMQP is similar to QMTP in that it minimizes the round trips necessary for handing messages to servers, but it doesn't implement relay control—so access to QMQP servers must be restricted to trusted clients. QMQP usually uses port 628.		QMQP is a protocol designed to be used by clients for queuing messages to a smart host that handles the delivery. This relieves clients of the burden of maintaining a queue and retrying temporarily undeliverable messages. The protocol is defined at http://cr.yp.to/proto/qmqp.html. QMQP is similar to QMTP in that it minimizes the round trips necessary for handing messages to servers, but it doesn't implement relay control—so access to QMQP servers must be restricted to trusted clients. QMQP usually uses port 628.

Ebroch at 05:35, 4 April 2024

2024-04-04T05:35:40Z

← Older revision		Revision as of 23:35, 3 April 2024
Line 1:		Line 1:
	[[User_Tips_%26_Tricks#QMQP\|Back]]		[[User_Tips_%26_Tricks#QMQP\|Back]]
	--[https://flylib.com/books/en/3.116.1.61/1/#google_vignette Offsite]		-- [https://flylib.com/books/en/3.116.1.61/1/#google_vignette Offsite]
	<pre>		<pre>
	QMQP is a protocol designed to be used by clients for queuing messages to a smart host that handles the delivery. This relieves clients of the burden of maintaining a queue and retrying temporarily undeliverable messages. The protocol is defined at http://cr.yp.to/proto/qmqp.html. QMQP is similar to QMTP in that it minimizes the round trips necessary for handing messages to servers, but it doesn't implement relay control—so access to QMQP servers must be restricted to trusted clients. QMQP usually uses port 628.		QMQP is a protocol designed to be used by clients for queuing messages to a smart host that handles the delivery. This relieves clients of the burden of maintaining a queue and retrying temporarily undeliverable messages. The protocol is defined at http://cr.yp.to/proto/qmqp.html. QMQP is similar to QMTP in that it minimizes the round trips necessary for handing messages to servers, but it doesn't implement relay control—so access to QMQP servers must be restricted to trusted clients. QMQP usually uses port 628.

Ebroch at 05:35, 4 April 2024

2024-04-04T05:35:29Z

← Older revision		Revision as of 23:35, 3 April 2024
Line 1:		Line 1:
	[[User_Tips_%26_Tricks#QMQP\|Back]]		[[User_Tips_%26_Tricks#QMQP\|Back]]
	[https://flylib.com/books/en/3.116.1.61/1/#google_vignette Offsite]		--[https://flylib.com/books/en/3.116.1.61/1/#google_vignette Offsite]
	<pre>		<pre>
	QMQP is a protocol designed to be used by clients for queuing messages to a smart host that handles the delivery. This relieves clients of the burden of maintaining a queue and retrying temporarily undeliverable messages. The protocol is defined at http://cr.yp.to/proto/qmqp.html. QMQP is similar to QMTP in that it minimizes the round trips necessary for handing messages to servers, but it doesn't implement relay control—so access to QMQP servers must be restricted to trusted clients. QMQP usually uses port 628.		QMQP is a protocol designed to be used by clients for queuing messages to a smart host that handles the delivery. This relieves clients of the burden of maintaining a queue and retrying temporarily undeliverable messages. The protocol is defined at http://cr.yp.to/proto/qmqp.html. QMQP is similar to QMTP in that it minimizes the round trips necessary for handing messages to servers, but it doesn't implement relay control—so access to QMQP servers must be restricted to trusted clients. QMQP usually uses port 628.

← Older revision		Revision as of 23:40, 3 April 2024
Line 62:		Line 62:

	192.168.1.:allow :deny		192.168.1.:allow :deny

	Build the machine-readable version of the access control database,		Build the machine-readable version of the access control database,

Line 107:		Line 108:

	$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz —08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz => 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . . connected! HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar] 0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174] $		$ wget http://www.din.or.jp/~ushijima/mini-qmail-kit/mini-qmail-kit-0.52.tar.gz —08:32:32— http://www.din.or.jp/%7Eushijima/mini-qmail-kit/mini-qmail-kit-0.52 .tar.gz => 'mini-qmail-kit-0.52.tar.gz' Connecting to www.din.or.jp:80. . . connected! HTTP request sent, awaiting response. . . 200 OK Length: 6,174 [application/x-tar] 0K -> . . .. . . [100%] 08:32:36 (3.51 KB/s) - 'mini-qmail-kit-0.52.tar.gz' saved [6174/6174] $

	Unpack the kit and change to its directory:		Unpack the kit and change to its directory:

	$ zcat mini-qmail-kit-0.52.tar.gz \| tar xf - $ cd mini-qmail-kit-0.52 $		$ zcat mini-qmail-kit-0.52.tar.gz \| tar xf - $ cd mini-qmail-kit-0.52
			$

	Unpack the qmail tarball under the current directory:		Unpack the qmail tarball under the current directory:

	$ zcat /tmp/qmail-1.03.tar.gz \| tar xf - $		$ zcat /tmp/qmail-1.03.tar.gz \| tar xf -
			$

	Build the mini-qmail Makefile:		Build the mini-qmail Makefile:

	$ make -f Makefile.mini sed '/^auto_uids\.c:/,/^$/d' qmail-1.03/Makefile > Makefile cat Makefile.mini > Makefile while read file; \ do \ echo ''; \ echo "$file: qmail-1.03/$file"; \ echo "cat qmail-1.03/$file > $file"; \ done < FILES.qmail > Makefile $		$ make -f Makefile.mini sed '/^auto_uids\.c:/,/^$/d' qmail-1.03/Makefile > Makefile cat Makefile.mini > Makefile while read file; \ do \ echo ''; \ echo "$file: qmail-1.03/$file"; \ echo "cat qmail-1.03/$file > $file"; \ done < FILES.qmail > Makefile $

	Build the mini-qmail binaries and man pages:		Build the mini-qmail binaries and man pages:

	$ make mini cat qmail-1.03/warn-auto.sh > warn-auto.sh cat warn-auto.sh config-mini.sh \ \| sed s}QMAIL}"'sed 1q conf-qmail'"}g \ ... nroff -man envelopes.5 > envelopes.0 cat qmail-1.03/forgeries.7 > forgeries.7 nroff -man forgeries.7 > forgeries.0 $		$ make mini cat qmail-1.03/warn-auto.sh > warn-auto.sh cat warn-auto.sh config-mini.sh \ \| sed s}QMAIL}"'sed 1q conf-qmail'"}g \ ... nroff -man envelopes.5 > envelopes.0 cat qmail-1.03/forgeries.7 > forgeries.7 nroff -man forgeries.7 > forgeries.0
			$
	Install the binaries and man pages:		Install the binaries and man pages:

Line 124:		Line 132:
	Configure the mini-qmail installation:		Configure the mini-qmail installation:

	# ./config-mini smarthost domain plusdomain localhostname\ > smarthostip # Putting smarthost into control/me. . . Putting domain into control/defaultdomain. . . Putting plusdomain into control/plusdomain. . . Putting localhostname into control/idhost. . . Putting smarthostip into control/qmqpservers. . . #		# ./config-mini smarthost domain plusdomain localhostname\ > smarthostip # Putting smarthost into control/me. . . Putting domain into control/defaultdomain. . . Putting plusdomain into control/plusdomain. . . Putting localhostname into control/idhost. . . Putting smarthostip into control/qmqpservers. . .
			#

	For example, if the smart host is mail.example.com, with an IP address of 192.168.1.4, and the mini-qmail host is null.example.com, you might use something like this:		For example, if the smart host is mail.example.com, with an IP address of 192.168.1.4, and the mini-qmail host is null.example.com, you might use something like this:

	# ./config-mini mail.example.com example.com example.com null.example.com \ > 192.168.1.4 Putting mail.example.com into control/me. . . Putting example.com into control/defaultdomain. . . Putting example.com into control/plusdomain. . . Putting null.example.com into control/idhost. . . Putting 192.168.1.4 into control/qmqpservers. . . #		# ./config-mini mail.example.com example.com example.com null.example.com \ > 192.168.1.4 Putting mail.example.com into control/me. . . Putting example.com into control/defaultdomain. . . Putting example.com into control/plusdomain. . . Putting null.example.com into control/idhost. . . Putting 192.168.1.4 into control/qmqpservers. . .
			#

	Test the mini-qmail installation. If your username on the smarthost is carolyn, do this:		Test the mini-qmail installation. If your username on the smarthost is carolyn, do this:

	# echo to: carolyn \| /var/mini-qmail/bin/qmail-inject #		# echo to: carolyn \| /var/mini-qmail/bin/qmail-inject
			#

	Verify that the message was delivered to your mailbox on the smarthost.		Verify that the message was delivered to your mailbox on the smarthost.

Line 139:		Line 153:
	# ln -s /var/mini-qmail/bin/sendmail /usr/sbin/sendmail		# ln -s /var/mini-qmail/bin/sendmail /usr/sbin/sendmail
	#		#

	nullmailer		nullmailer
	nullmailer (http://www.untroubled.org/nullmailer/) is a simple MTA for null clients. It can use either SMTP or QMQP. It's similar to mini-qmail, except it implements a queue. If mini-qmail can't reach a server when a message is injected, it returns an error and the sending user or process is responsible for retrying the delivery later. nullmailer queues the message locally and automatically retries to send it to a server.		nullmailer (http://www.untroubled.org/nullmailer/) is a simple MTA for null clients. It can use either SMTP or QMQP. It's similar to mini-qmail, except it implements a queue. If mini-qmail can't reach a server when a message is injected, it returns an error and the sending user or process is responsible for retrying the delivery later. nullmailer queues the message locally and automatically retries to send it to a server.

	</pre>		</pre>