Dovecot - Revision history

Woozle: /* Debugging */

2020-10-23T14:33:29Z

Debugging

← Older revision		Revision as of 14:33, 23 October 2020
Line 45:		Line 45:
	– then edit the 01-dovecot-postfix.conf file and change "cmusieve" to "sieve". --[[User:Woozle\|Woozle]] 17:41, 23 May 2010 (UTC)		– then edit the 01-dovecot-postfix.conf file and change "cmusieve" to "sieve". --[[User:Woozle\|Woozle]] 17:41, 23 May 2010 (UTC)
	===Debugging===		===Debugging===
			See also:[[openssl]]

	[https://wiki.dovecot.org/TestInstallation TestInstallation] has some good basic diagnostics. If the connection gives errors not described there, then you need to (a) confirm where the configuration is stored by running this:<source lang=bash>doveconf -n \| head -n 1</source> (see [https://doc.dovecot.org/configuration_manual/quick_configuration/ Quick Configuration]).		[https://wiki.dovecot.org/TestInstallation TestInstallation] has some good basic diagnostics. If the connection gives errors not described there, then you need to (a) confirm where the configuration is stored by running this:<source lang=bash>doveconf -n \| head -n 1</source> (see [https://doc.dovecot.org/configuration_manual/quick_configuration/ Quick Configuration]).

	===Theories===		===Theories===
	"<u>auth default { socket listen { master { path =</u> ''filespec''" '''creates''' the socket (or provides the service, or however you want to describe it); a ''different'' part of dovecot tries to access that socket by default unless you override it with "<u>auth external { socket connect { master { path =</u> ''filespec''". '''Where is this documented??'''		"<u>auth default { socket listen { master { path =</u> ''filespec''" '''creates''' the socket (or provides the service, or however you want to describe it); a ''different'' part of dovecot tries to access that socket by default unless you override it with "<u>auth external { socket connect { master { path =</u> ''filespec''". '''Where is this documented??'''

Woozle: /* Errors */

2020-10-19T18:10:42Z

Errors

← Older revision		Revision as of 18:10, 19 October 2020
Line 51:		Line 51:
	* [[Failed to initialize SSL server context: Can't load DH parameters]] - received when attempting to connect (I think)		* [[Failed to initialize SSL server context: Can't load DH parameters]] - received when attempting to connect (I think)
	* [[SSL routines:ssl3_get_record:wrong version number]]		* [[SSL routines:ssl3_get_record:wrong version number]]
			* [[write:errno=104]]

	==Links==		==Links==
	===Reference===		===Reference===

Woozle at 21:39, 18 October 2020

2020-10-18T21:39:55Z

← Older revision		Revision as of 21:39, 18 October 2020
Line 44:		Line 44:
	Fatal: Plugin cmusieve not found from directory /usr/lib/dovecot/modules/lda		Fatal: Plugin cmusieve not found from directory /usr/lib/dovecot/modules/lda
	– then edit the 01-dovecot-postfix.conf file and change "cmusieve" to "sieve". --[[User:Woozle\|Woozle]] 17:41, 23 May 2010 (UTC)		– then edit the 01-dovecot-postfix.conf file and change "cmusieve" to "sieve". --[[User:Woozle\|Woozle]] 17:41, 23 May 2010 (UTC)
			===Debugging===
			[https://wiki.dovecot.org/TestInstallation TestInstallation] has some good basic diagnostics. If the connection gives errors not described there, then you need to (a) confirm where the configuration is stored by running this:<source lang=bash>doveconf -n \| head -n 1</source> (see [https://doc.dovecot.org/configuration_manual/quick_configuration/ Quick Configuration]).
	===Theories===		===Theories===
	"<u>auth default { socket listen { master { path =</u> ''filespec''" '''creates''' the socket (or provides the service, or however you want to describe it); a ''different'' part of dovecot tries to access that socket by default unless you override it with "<u>auth external { socket connect { master { path =</u> ''filespec''". '''Where is this documented??'''		"<u>auth default { socket listen { master { path =</u> ''filespec''" '''creates''' the socket (or provides the service, or however you want to describe it); a ''different'' part of dovecot tries to access that socket by default unless you override it with "<u>auth external { socket connect { master { path =</u> ''filespec''". '''Where is this documented??'''
			==Errors==
			* [[Failed to initialize SSL server context: Can't load DH parameters]] - received when attempting to connect (I think)
			* [[SSL routines:ssl3_get_record:wrong version number]]
	==Links==		==Links==
	===Reference===		===Reference===
Line 52:		Line 56:
	* [http://www.dovecot.org/ official site]		* [http://www.dovecot.org/ official site]
	** [http://wiki.dovecot.org/FrontPage wiki]		** [http://wiki.dovecot.org/FrontPage wiki]
	*** [~~http~~://~~wiki2~~.dovecot.org/~~QuickConfiguration~~ Quick Configuration]		*** [https://doc.dovecot.org/configuration_manual/quick_configuration/ Quick Configuration]

Woozle: /* Reference */ quick config link

2015-04-09T20:59:31Z

Reference: quick config link

← Older revision		Revision as of 20:59, 9 April 2015
Line 52:		Line 52:
	* [http://www.dovecot.org/ official site]		* [http://www.dovecot.org/ official site]
	** [http://wiki.dovecot.org/FrontPage wiki]		** [http://wiki.dovecot.org/FrontPage wiki]
			*** [http://wiki2.dovecot.org/QuickConfiguration Quick Configuration]

Woozle: sample configurations

2011-06-08T20:39:24Z

sample configurations

← Older revision		Revision as of 20:39, 8 June 2011
Line 28:		Line 28:
	* In the server I just configured, the SSL settings were in "conf.d/01-dovecot-postfix.conf". Tentatively: '''ssl_cert_file''' should be set to the certificate you receive from the certificate signer (e.g. [[OptimumSSL]]), and '''ssl_key_file''' should be set to the private key you generated earlier (when you also generated the CSR). --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)		* In the server I just configured, the SSL settings were in "conf.d/01-dovecot-postfix.conf". Tentatively: '''ssl_cert_file''' should be set to the certificate you receive from the certificate signer (e.g. [[OptimumSSL]]), and '''ssl_key_file''' should be set to the private key you generated earlier (when you also generated the CSR). --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)
	* This year, '''ssl_cert_file''' was the certificate as sent via email (2 certificates with some text between them); '''ssl_key_file''' was the key file I newly generated for the CSR for this certificate. (Possibly I could have re-used the one from last year, but I couldn't see any advantage to that, and I wasn't sure if it would even work.) Although explanations elsewhere might make you think that '''ssl_cert_file''' would need to be the server certificate plus the intermediate file, the intermediate file contained at least 2 or 3 certificates and '''ssl_cert_file''' only contained 2, one of which was the server certificate. So either some of those intermediate certificates are unnecessary or else I don't understand how this file works. --[[User:Woozle\|Woozle]] 18:01, 17 February 2011 (EST)		* This year, '''ssl_cert_file''' was the certificate as sent via email (2 certificates with some text between them); '''ssl_key_file''' was the key file I newly generated for the CSR for this certificate. (Possibly I could have re-used the one from last year, but I couldn't see any advantage to that, and I wasn't sure if it would even work.) Although explanations elsewhere might make you think that '''ssl_cert_file''' would need to be the server certificate plus the intermediate file, the intermediate file contained at least 2 or 3 certificates and '''ssl_cert_file''' only contained 2, one of which was the server certificate. So either some of those intermediate certificates are unnecessary or else I don't understand how this file works. --[[User:Woozle\|Woozle]] 18:01, 17 February 2011 (EST)
			===Sample Configurations===
			* Woozle:
			** [[User:Woozle/files/dovecot/dovecot.conf\|dovecot.conf]]
			** [[User:Woozle/files/dovecot/auth.d/01-dovecot-postfix.auth\|auth.d/01-dovecot-postfix.auth]]
	==Notes==		==Notes==
	For Ubuntu 10.04 (whatever version of dovecot that corresponds to), some of the settings in [[dovecot.conf]] have been pushed out to sub-files. When dovecot is paired with [[Postfix]], the files appear to be:		For Ubuntu 10.04 (whatever version of dovecot that corresponds to), some of the settings in [[dovecot.conf]] have been pushed out to sub-files. When dovecot is paired with [[Postfix]], the files appear to be:

Woozle: some SMW markup; start of s section on SASL

2011-06-08T11:43:06Z

some SMW markup; start of s section on SASL

← Older revision		Revision as of 11:43, 8 June 2011
Line 1:		Line 1:
	==~~Overview~~==		{{#set:page type=article}}
	[[category:software]][[Dovecot]] is [[email server]] [[software]]. {{wikipedia\|Dovecot (software)}} describes it as just a [[POP3]] and [[Internet Mail Access Protocol\|IMAP]] server, but [[Ubuntu]] packages it as a "stack" which provides both [[Mail Transfer Agent\|MTA]] and [[Mail Delivery Agent\|MDA]] functionality.		{{#set:thing type=software}}
			{{#set:architecture=server}}
			{{#set:license=open source}}
			[[category:software]]
			==About==
			[[Dovecot]] is [[email server]] [[software]]. {{wikipedia\|Dovecot (software)}} describes it as just a [[POP3]] and [[Internet Mail Access Protocol\|IMAP]] server, but [[Ubuntu]] packages it as a "stack" which provides both [[Mail Transfer Agent\|MTA]] and [[Mail Delivery Agent\|MDA]] functionality.

	===Helper Binaries===		===Helper Binaries===
Line 11:		Line 16:
	Binaries include:		Binaries include:
	* [[/deliver]]: can be used by [[Postfix]] when delivering mail to user mailboxes		* [[/deliver]]: can be used by [[Postfix]] when delivering mail to user mailboxes
			===SASL===
			'''SASL''' stands for [[Simple Authentication and Security Layer]].
			* [http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL Postfix and Dovecot SASL] (Dovecot wiki)
	===SSL===		===SSL===
	See [[Secure Sockets Layer]] for related information.		See [[Secure Sockets Layer]] for related information.

Woozle: /* SSL */ more notes from this year's successful install

2011-02-17T23:01:34Z

SSL: more notes from this year's successful install

← Older revision		Revision as of 23:01, 17 February 2011
Line 19:		Line 19:
	* In theory, you should be able to create your own subfile and add these settings to it; I have not tested this. --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)		* In theory, you should be able to create your own subfile and add these settings to it; I have not tested this. --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)
	* In the server I just configured, the SSL settings were in "conf.d/01-dovecot-postfix.conf". Tentatively: '''ssl_cert_file''' should be set to the certificate you receive from the certificate signer (e.g. [[OptimumSSL]]), and '''ssl_key_file''' should be set to the private key you generated earlier (when you also generated the CSR). --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)		* In the server I just configured, the SSL settings were in "conf.d/01-dovecot-postfix.conf". Tentatively: '''ssl_cert_file''' should be set to the certificate you receive from the certificate signer (e.g. [[OptimumSSL]]), and '''ssl_key_file''' should be set to the private key you generated earlier (when you also generated the CSR). --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)
			* This year, '''ssl_cert_file''' was the certificate as sent via email (2 certificates with some text between them); '''ssl_key_file''' was the key file I newly generated for the CSR for this certificate. (Possibly I could have re-used the one from last year, but I couldn't see any advantage to that, and I wasn't sure if it would even work.) Although explanations elsewhere might make you think that '''ssl_cert_file''' would need to be the server certificate plus the intermediate file, the intermediate file contained at least 2 or 3 certificates and '''ssl_cert_file''' only contained 2, one of which was the server certificate. So either some of those intermediate certificates are unnecessary or else I don't understand how this file works. --[[User:Woozle\|Woozle]] 18:01, 17 February 2011 (EST)

	==Notes==		==Notes==
	For Ubuntu 10.04 (whatever version of dovecot that corresponds to), some of the settings in [[dovecot.conf]] have been pushed out to sub-files. When dovecot is paired with [[Postfix]], the files appear to be:		For Ubuntu 10.04 (whatever version of dovecot that corresponds to), some of the settings in [[dovecot.conf]] have been pushed out to sub-files. When dovecot is paired with [[Postfix]], the files appear to be:

Woozle: SSL

2010-12-11T19:08:26Z

SSL

← Older revision		Revision as of 19:08, 11 December 2010
Line 11:		Line 11:
	Binaries include:		Binaries include:
	* [[/deliver]]: can be used by [[Postfix]] when delivering mail to user mailboxes		* [[/deliver]]: can be used by [[Postfix]] when delivering mail to user mailboxes
			===SSL===
			See [[Secure Sockets Layer]] for related information.
			* [http://wiki.dovecot.org/SSL Dovecot SSL]
			** [http://wiki.dovecot.org/SSL/DovecotConfiguration Dovecot SSL configuration]

			None of the documentation seems to mention the fact that many of these settings are in sub-files (see [[#Notes]], below), and your changes to dovecot.conf will be ignored if they are overridden in one of these files -- so edit that file instead.
			* In theory, you should be able to create your own subfile and add these settings to it; I have not tested this. --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)
			* In the server I just configured, the SSL settings were in "conf.d/01-dovecot-postfix.conf". Tentatively: '''ssl_cert_file''' should be set to the certificate you receive from the certificate signer (e.g. [[OptimumSSL]]), and '''ssl_key_file''' should be set to the private key you generated earlier (when you also generated the CSR). --[[User:Woozle\|Woozle]] 14:08, 11 December 2010 (EST)
	==Notes==		==Notes==
	For Ubuntu 10.04 (whatever version of dovecot that corresponds to), some of the settings in [[dovecot.conf]] have been pushed out to sub-files. When dovecot is paired with [[Postfix]], the files appear to be:		For Ubuntu 10.04 (whatever version of dovecot that corresponds to), some of the settings in [[dovecot.conf]] have been pushed out to sub-files. When dovecot is paired with [[Postfix]], the files appear to be:

Woozle: /* Notes */ a theory about the brontosaurus

2010-10-08T16:05:27Z

Notes: a theory about the brontosaurus

← Older revision		Revision as of 16:05, 8 October 2010
Line 24:		Line 24:
	Fatal: Plugin cmusieve not found from directory /usr/lib/dovecot/modules/lda		Fatal: Plugin cmusieve not found from directory /usr/lib/dovecot/modules/lda
	– then edit the 01-dovecot-postfix.conf file and change "cmusieve" to "sieve". --[[User:Woozle\|Woozle]] 17:41, 23 May 2010 (UTC)		– then edit the 01-dovecot-postfix.conf file and change "cmusieve" to "sieve". --[[User:Woozle\|Woozle]] 17:41, 23 May 2010 (UTC)
			===Theories===
			"<u>auth default { socket listen { master { path =</u> ''filespec''" '''creates''' the socket (or provides the service, or however you want to describe it); a ''different'' part of dovecot tries to access that socket by default unless you override it with "<u>auth external { socket connect { master { path =</u> ''filespec''". '''Where is this documented??'''

	==Links==		==Links==

Woozle: /* Notes */ actually, sometimes they're not loaded at all.

2010-10-08T16:01:12Z

Notes: actually, sometimes they're not loaded at all.

← Older revision		Revision as of 16:01, 8 October 2010
Line 18:		Line 18:

	There doesn't seem to be any official documentation on how these files are invoked, but the last comment in [https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/590408 this forum post] implies that these files are read first and then may be overridden by [[/dovecot.conf]] (or possibly they are only loaded if the corresponding settings are missing, but this seems like a more fragile approach and so less likely).		There doesn't seem to be any official documentation on how these files are invoked, but the last comment in [https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/590408 this forum post] implies that these files are read first and then may be overridden by [[/dovecot.conf]] (or possibly they are only loaded if the corresponding settings are missing, but this seems like a more fragile approach and so less likely).

			'''Warning''': Sometimes these files are totally not being looked at, and you have to paste their contents (...well, the auth.d/ one at least) into dovecot.conf. We really need to know what the mechanism is for loading these files.

	If you are experiencing an error where dovecot complains that it can't find [[cmusieve]] – like this:		If you are experiencing an error where dovecot complains that it can't find [[cmusieve]] – like this: