ISP Mail Server HowTo - Revision history

Sertonix: replace /etc/init.d with rc-service

2023-11-17T10:13:01Z

replace /etc/init.d with rc-service

← Older revision		Revision as of 10:13, 17 November 2023
Line 23:		Line 23:
	Stop and remove mini_httpd, and move ACF to lighttpd; We are setting this up to be a multi-domain virtual web server (replace host.example.com with the actual domain):		Stop and remove mini_httpd, and move ACF to lighttpd; We are setting this up to be a multi-domain virtual web server (replace host.example.com with the actual domain):

	~~/etc/init.d/~~mini_httpd stop		rc-service mini_httpd stop
	apk del mini_httpd		apk del mini_httpd
	mkdir -p /var/www/domains/host.example.com/www		mkdir -p /var/www/domains/host.example.com/www
Line 119:		Line 119:
	Stop and remove mini_httpd; start lighttpd, test		Stop and remove mini_httpd; start lighttpd, test

	~~/etc/init.d/~~mini_httpd stop		rc-service mini_httpd stop
	rc-update del mini_httpd		rc-update del mini_httpd
	apk del mini_httpd		apk del mini_httpd
	rc-update add lighttpd		rc-update add lighttpd
	~~/etc/init.d/~~lighttpd start		rc-service lighttpd start

	At this point you should be able to see ACF being served with lighttpd (Note: this will work well with alpine 1.10. With earlier versions there will be problems.) <nowiki>https://host.example.com/acf/</nowiki>		At this point you should be able to see ACF being served with lighttpd (Note: this will work well with alpine 1.10. With earlier versions there will be problems.) <nowiki>https://host.example.com/acf/</nowiki>
Line 132:		Line 132:

	apk add acf-postgresql postgresql-client		apk add acf-postgresql postgresql-client
	~~/etc/init.d/~~postgresql setup		rc-service postgresql setup
	~~/etc/init.d/~~postgresql start		rc-service postgresql start
	rc-update add postgresql		rc-update add postgresql

Line 350:		Line 350:

	newaliases # so postfix is happy...		newaliases # so postfix is happy...
	~~/etc/init.d/~~postfix start		rc-service postfix start
	rc-update add postfix		rc-update add postfix

Line 440:		Line 440:

	Start dovecot		Start dovecot
	~~/etc/init.d/~~dovecot start		rc-service dovecot start
	rc-update add dovecot		rc-update add dovecot

Line 474:		Line 474:
	rc-update add clamd		rc-update add clamd
	rc-update add clamsmtpd		rc-update add clamsmtpd
	~~/etc/init.d/~~clamd start		rc-service clamd start
	~~/etc/init.d/~~clamsmtpd start		rc-service clamsmtpd start
	* Verify clamsmtp is listening on port 10025:		* Verify clamsmtp is listening on port 10025:
	cmd\|netstat -anp \| grep clamsmtp		cmd\|netstat -anp \| grep clamsmtp
Line 522:		Line 522:
	</pre>		</pre>
	* Restart dovecot		* Restart dovecot
	~~/etc/init.d/~~dovecot restart		rc-service dovecot restart
	* Edit /etc/postfix/main.cf and add:		* Edit /etc/postfix/main.cf and add:
	# TLS Stuff -- since we allow SASL with tls only, we have to set up TLS first		# TLS Stuff -- since we allow SASL with tls only, we have to set up TLS first
Line 690:		Line 690:
	Restart Postfix and Dovecot:		Restart Postfix and Dovecot:

	~~/etc/init.d/~~postfix restart		rc-service postfix restart
	~~/etc/init.d/~~dovecot restart		rc-service dovecot restart

	'''TODO''' This will cause over-quota emails to bounce. Which could be a source of backscatter. We need a way of checking quota limits after RBL checking but before the message is accepted in the queue.		'''TODO''' This will cause over-quota emails to bounce. Which could be a source of backscatter. We need a way of checking quota limits after RBL checking but before the message is accepted in the queue.
Line 730:		Line 730:

	<pre>		<pre>
	~~/etc/init.d/~~postfix restart		rc-service postfix restart
	~~/etc/init.d/~~dovecot restart		rc-service dovecot restart
	</pre>		</pre>

Line 761:		Line 761:

	* restart lighttpd to verify the new php libraries are used		* restart lighttpd to verify the new php libraries are used
	~~/etc/init.d/~~lighttpd restart		rc-service lighttpd restart

	* Point your browser to <nowiki>https://host.example.com/roundcube/installer</nowiki>		* Point your browser to <nowiki>https://host.example.com/roundcube/installer</nowiki>
Line 1,159:		Line 1,159:
	<pre>		<pre>
	rc-update add slapd default		rc-update add slapd default
	~~/etc/init.d/~~slapd start		rc-service slapd start
	</pre>		</pre>

Line 1,188:		Line 1,188:
	In order to enable php-ldap support you need to restart lighttpd server		In order to enable php-ldap support you need to restart lighttpd server

	~~/etc/init.d/~~lighttpd restart		rc-service lighttpd restart

	Edit /usr/share/webapps/roundcube/config/main.inc.php:		Edit /usr/share/webapps/roundcube/config/main.inc.php:
Line 1,241:		Line 1,241:
	Ensure the busybox cron service is started and is configured to auto-start:		Ensure the busybox cron service is started and is configured to auto-start:

	~~/etc/init.d/~~cron start		rc-service cron start
	rc-update add cron default		rc-update add cron default

Zcrayfish: Rescued a dead link.

2023-08-30T21:40:51Z

Rescued a dead link.

← Older revision		Revision as of 21:40, 30 August 2023
Line 478:		Line 478:
	* Verify clamsmtp is listening on port 10025:		* Verify clamsmtp is listening on port 10025:
	cmd\|netstat -anp \| grep clamsmtp		cmd\|netstat -anp \| grep clamsmtp
	* [~~https~~://~~memberwebs~~.~~com~~/stef/software/clamsmtp/postfix.html Following the clamsmtp instructions]~~{{dead link}}~~		* [http://thewalter.net/stef/software/clamsmtp/postfix.html Following the clamsmtp instructions]
	** edit {{path\|/etc/postfix/main.cf}} and add:		** edit {{path\|/etc/postfix/main.cf}} and add:
	content_filter = scan:[127.0.0.1]:10025		content_filter = scan:[127.0.0.1]:10025

Sertonix: update links & use https

2023-08-25T20:25:01Z

update links & use https

Zcrayfish: /* WebMail (RoundCube) */ Removed unneeded hyperlinks

2021-12-20T14:30:55Z

WebMail (RoundCube): Removed unneeded hyperlinks

← Older revision		Revision as of 14:30, 20 December 2021
Line 763:		Line 763:
	/etc/init.d/lighttpd restart		/etc/init.d/lighttpd restart

	* Point your browser to https://host.example.com/roundcube/installer		* Point your browser to <nowiki>https://host.example.com/roundcube/installer</nowiki>
	* Start installation		* Start installation

Line 800:		Line 800:

	* Follow the instructions in step 2 of the install to copy the files to the server		* Follow the instructions in step 2 of the install to copy the files to the server
	* You should now be able to get to roundcube at https://host.example.com/roundcube		* You should now be able to get to roundcube at <nowiki>https://host.example.com/roundcube</nowiki>

Zcrayfish: /* Virus Scanning */ Marked a dead link. Used path template

2021-12-20T14:28:37Z

Virus Scanning: Marked a dead link. Used path template

← Older revision		Revision as of 14:28, 20 December 2021
Line 463:		Line 463:

	* Install clamav and clamsmtp:		* Install clamav and clamsmtp:
	apk add acf-clamav clamsmtp		{{cmd\|apk add acf-clamav clamsmtp}}
	* Edit the /etc/clamav/clamd.conf file if desired (not necessary in most cases)		* Edit the {{path\|/etc/clamav/clamd.conf}} file if desired (not necessary in most cases)
	* Edit /etc/clamsmtpd.conf and verify the following lines		* Edit {{path\|/etc/clamsmtpd.conf}} and verify the following lines
	OutAddress: 10026		OutAddress: 10026
	Listen: 127.0.0.1:10025		Listen: 127.0.0.1:10025
Line 477:		Line 477:
	/etc/init.d/clamsmtpd start		/etc/init.d/clamsmtpd start
	* Verify clamsmtp is listening on port 10025:		* Verify clamsmtp is listening on port 10025:
	netstat -anp \| grep clamsmtp		cmd\|netstat -anp \| grep clamsmtp
	* [http://memberwebs.com/stef/software/clamsmtp/postfix.html Following the clamsmtp instructions]		* [http://memberwebs.com/stef/software/clamsmtp/postfix.html Following the clamsmtp instructions]{{dead link}}
	** edit /etc/postfix/main.cf and add:		** edit {{path\|/etc/postfix/main.cf}} and add:
	content_filter = scan:[127.0.0.1]:10025		content_filter = scan:[127.0.0.1]:10025
	** edit /etc/postfix/master.cf and add		** edit {{path\|/etc/postfix/master.cf}} and add
	# AV scan filter (used by content_filter)		# AV scan filter (used by content_filter)
	scan unix - - n - 16 smtp		scan unix - - n - 16 smtp

Zcrayfish: /* Create a domain in PostfixAdmin and test */ Removed unneeded hyperlink. Use path template.

2021-12-20T14:25:40Z

Create a domain in PostfixAdmin and test: Removed unneeded hyperlink. Use path template.

← Older revision		Revision as of 14:25, 20 December 2021
Line 356:		Line 356:
	=== Create a domain in PostfixAdmin and test ===		=== Create a domain in PostfixAdmin and test ===

	Go to http://host.example.com/postfixadmin/		Go to <nowiki>http://host.example.com/postfixadmin/</nowiki>

	Log in using the superadmin account, create a domain for the local box (e.g. example.com), and create a user mailbox (e.g. root).		Log in using the superadmin account, create a domain for the local box (e.g. example.com), and create a user mailbox (e.g. root).
Line 368:		Line 368:


	In /var/log/mail.log (or /var/log/messages, if you still have busybox syslogd running) you should see the message queued. The message should be in /var/mail/domains/example.com/root/new		In {{path\|/var/log/mail.log}} (or {{path\|/var/log/messages}}, if you still have busybox syslogd running) you should see the message queued. The message should be in {{path\|/var/mail/domains/example.com/root/new}}

	== Install Dovecot ==		== Install Dovecot ==

Zcrayfish: /* Install PostfixAdmin */ Removed unneeded hyperlinks

2021-12-20T14:23:49Z

Install PostfixAdmin: Removed unneeded hyperlinks

← Older revision		Revision as of 14:23, 20 December 2021
Line 193:		Line 193:
	$CONF['special_alias_control'] = 'YES';		$CONF['special_alias_control'] = 'YES';
	$CONF['fetchmail'] = 'NO';		$CONF['fetchmail'] = 'NO';
	$CONF['user_footer_link'] = "http://host.example.com/postfixadmin";		$CONF['user_footer_link'] = "<nowiki>http://host.example.com/postfixadmin</nowiki>";
	$CONF['footer_link'] = 'http://host.example.com/postfixadmin/main.php';		$CONF['footer_link'] = '<nowiki>http://host.example.com/postfixadmin/main.php</nowiki>';
	$CONF['create_mailbox_subdirs_prefix']="";		$CONF['create_mailbox_subdirs_prefix']="";
	$CONF['used_quotas'] = 'YES';		$CONF['used_quotas'] = 'YES';
Line 203:		Line 203:
	sed -i -e 's/change-this-to-your.domain.tld/example.com/g' /var/www/domains/host.example.com/www/postfixadmin/config.inc.php		sed -i -e 's/change-this-to-your.domain.tld/example.com/g' /var/www/domains/host.example.com/www/postfixadmin/config.inc.php

	Go to https://host.example.com/postfixadmin/setup.php		Go to <nowiki>https://host.example.com/postfixadmin/setup.php</nowiki>

	Create the password hash, add it to the config.inc.php file		Create the password hash, add it to the config.inc.php file

	Go back to https://host.example.com/postfixadmin/setup.php		Go back to <nowiki>https://host.example.com/postfixadmin/setup.php</nowiki>

	Create superadmin account.		Create superadmin account.

Zcrayfish: /* Set up Lighttpd + PHP */ Remove unneeded hyperlink

2021-12-20T14:22:39Z

Set up Lighttpd + PHP: Remove unneeded hyperlink

← Older revision		Revision as of 14:22, 20 December 2021
Line 125:		Line 125:
	/etc/init.d/lighttpd start		/etc/init.d/lighttpd start

	At this point you should be able to see ACF being served with lighttpd (Note: this will work well with alpine 1.10. With earlier versions there will be problems.) https://host.example.com/acf/		At this point you should be able to see ACF being served with lighttpd (Note: this will work well with alpine 1.10. With earlier versions there will be problems.) <nowiki>https://host.example.com/acf/</nowiki>

	== Install Postgresql ==		== Install Postgresql ==

John3-16: Updated link for ISP Mail Server 2.x HowTo to version 3.x

2017-09-16T23:54:14Z

Updated link for ISP Mail Server 2.x HowTo to version 3.x

← Older revision		Revision as of 23:54, 16 September 2017
Line 1:		Line 1:
	{{Obsolete\|To setup a mail server using Alpine Linux 2.x, see [~~http://wiki.alpinelinux.org/wiki/ISP_Mail_Server_2.x_HowTo~~ ISP Mail Server 2.x HowTo]}}		{{Obsolete\|To setup a mail server using Alpine Linux 3.x, see [[ISP Mail Server 3.x HowTo]]}}
	== A Full Service Mail Server ==		== A Full Service Mail Server ==

Dubiousjim: remove Category:Server

2012-03-24T15:40:31Z

remove Category:Server

← Older revision		Revision as of 15:40, 24 March 2012
Line 1,299:		Line 1,299:

	[[Category:Mail]]		[[Category:Mail]]
	~~[[Category:Server]]~~
	[[Category:PHP]]		[[Category:PHP]]
	[[Category:SQL]]		[[Category:SQL]]

← Older revision		Revision as of 20:25, 25 August 2023
Line 159:		Line 159:
	Download PostfixAdmin from Sourceforge. When these instructions were written, 2.3 was the current release, so (replace host.example.com with the actual domain):		Download PostfixAdmin from Sourceforge. When these instructions were written, 2.3 was the current release, so (replace host.example.com with the actual domain):

	wget ~~http~~://downloads.sourceforge.net/project/postfixadmin/postfixadmin/postfixadmin-2.3.2/postfixadmin-2.3.2.tar.gz		wget https://downloads.sourceforge.net/project/postfixadmin/postfixadmin/postfixadmin-2.3.2/postfixadmin-2.3.2.tar.gz
	tar zxvf postfixadmin-2.3.2.tar.gz		tar zxvf postfixadmin-2.3.2.tar.gz
	mkdir -p /var/www/domains/host.example.com/www/postfixadmin		mkdir -p /var/www/domains/host.example.com/www/postfixadmin
Line 478:		Line 478:
	* Verify clamsmtp is listening on port 10025:		* Verify clamsmtp is listening on port 10025:
	cmd\|netstat -anp \| grep clamsmtp		cmd\|netstat -anp \| grep clamsmtp
	* [~~http~~://memberwebs.com/stef/software/clamsmtp/postfix.html Following the clamsmtp instructions]{{dead link}}		* [https://memberwebs.com/stef/software/clamsmtp/postfix.html Following the clamsmtp instructions]{{dead link}}
	** edit {{path\|/etc/postfix/main.cf}} and add:		** edit {{path\|/etc/postfix/main.cf}} and add:
	content_filter = scan:[127.0.0.1]:10025		content_filter = scan:[127.0.0.1]:10025
Line 571:		Line 571:
	=== Mailbox Quotas ===		=== Mailbox Quotas ===

	In the default configuration, PostfixAdmin knows about quotas, but they are not enforced. Documentation on the web mentions the [~~http~~://vda.sourceforge.net vda patch to postfix] to enforce quotas. The only bad thing... its a ''patch''. Postfix and Dovecot are both conservative systems, so if the patch isn't in the upstream source, we'll assume there's a good reason. There is a way of using quotas without patches - and it involves using dovecot's [~~http~~://~~wiki~~.dovecot.org/~~LDA~~ deliver] lda for local delivery.		In the default configuration, PostfixAdmin knows about quotas, but they are not enforced. Documentation on the web mentions the [https://vda.sourceforge.net vda patch to postfix] to enforce quotas. The only bad thing... its a ''patch''. Postfix and Dovecot are both conservative systems, so if the patch isn't in the upstream source, we'll assume there's a good reason. There is a way of using quotas without patches - and it involves using dovecot's [https://doc.dovecot.org/admin_manual/mda/ deliver] lda for local delivery.

	Note: As of Jan 2010, the documention is confusing, with multiple versions of dovecot, PostfixAdmin, and Mysql referenced. These instructions apply to:		Note: As of Jan 2010, the documention is confusing, with multiple versions of dovecot, PostfixAdmin, and Mysql referenced. These instructions apply to:
Line 670:		Line 670:
	chmod 600 /etc/dovecot/dovecot-dict-quota.conf		chmod 600 /etc/dovecot/dovecot-dict-quota.conf

	Side note: [~~http~~://~~wiki~~.dovecot.org/~~Quota~~/~~Dict~~ The Dovecot Quota Documentation] mentions the need for a trigger with pgsql. This was created in the PostfixAdmin install, which is why you instantiated the pgsql language when creating the database. If not, you will need to create the trigger, to reference the quota2 table, not the quota table mentioned in the dovecot docs.		Side note: [https://doc.dovecot.org/configuration_manual/quota_plugin/ The Dovecot Quota Documentation] mentions the need for a trigger with pgsql. This was created in the PostfixAdmin install, which is why you instantiated the pgsql language when creating the database. If not, you will need to create the trigger, to reference the quota2 table, not the quota table mentioned in the dovecot docs.


Line 697:		Line 697:
	=== WebMail (RoundCube) ===		=== WebMail (RoundCube) ===

	[~~http~~://roundcube.net/ RoundCube] is an "ajax /Web2.0" web-mail client. These instructions are for the Alpine Linux 1.10 repository		[https://roundcube.net/ RoundCube] is an "ajax /Web2.0" web-mail client. These instructions are for the Alpine Linux 1.10 repository

	* Verify that you have at least the following in /etc/postfix/main.cf. Unless you have followed the Relay for Authenticated Users section above, set '''smtpd_tls_auth_only = no''', otherwise leave it set to '''yes''':		* Verify that you have at least the following in /etc/postfix/main.cf. Unless you have followed the Relay for Authenticated Users section above, set '''smtpd_tls_auth_only = no''', otherwise leave it set to '''yes''':
Line 1,110:		Line 1,110:

	# This is needed for proper representation of MD5-CRYPT format stored in database		# This is needed for proper representation of MD5-CRYPT format stored in database
	# see more details in ~~http~~://strugglers.net/~andy/blog/2010/01/23/openldap-and-md5crypt/		# see more details in https://strugglers.net/~andy/blog/2010/01/23/openldap-and-md5crypt/
	password-hash {CRYPT}		password-hash {CRYPT}
	password-crypt-salt-format "$1$%.8s"		password-crypt-salt-format "$1$%.8s"
Line 1,254:		Line 1,254:
	'''Note:''' These steps can be done ''in addition to'' the default lighttpd configuration above, which allows you to access the ACF, PostfixAdmin and Roundcube interfaces as subfolders of one web service.		'''Note:''' These steps can be done ''in addition to'' the default lighttpd configuration above, which allows you to access the ACF, PostfixAdmin and Roundcube interfaces as subfolders of one web service.

	'''Note:''' If you provide SSL access for multiple domain site you may need to follow ~~http~~://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:SSL#SSL-on-multiple-domains in order to provide multi-domain certificates. If you would like to redirect hosts to their secure equivalents use the following instructions ~~http~~://redmine.lighttpd.net/projects/lighttpd/wiki/HowToRedirectHttpToHttps.		'''Note:''' If you provide SSL access for multiple domain site you may need to follow https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:SSL#SSL-on-multiple-domains in order to provide multi-domain certificates. If you would like to redirect hosts to their secure equivalents use the following instructions https://redmine.lighttpd.net/projects/lighttpd/wiki/HowToRedirectHttpToHttps.

	This server hosts three separate web applications, and these can be handled as three ''different'' virtual domains on the same web server. They will be distinguished by their DNS names, so you can choose domains for the three separate services (or at least the ones you want to publish):		This server hosts three separate web applications, and these can be handled as three ''different'' virtual domains on the same web server. They will be distinguished by their DNS names, so you can choose domains for the three separate services (or at least the ones you want to publish):