Service/smtp - Revision history

Chimosky: switch to sunjammer.sl.o as I changed the cert because of mta-sts

2026-02-24T07:31:59Z

switch to sunjammer.sl.o as I changed the cert because of mta-sts

← Older revision		Revision as of 03:31, 24 February 2026
Line 4:		Line 4:
	! hostname !! service !! port !! function		! hostname !! service !! port !! function
	\|-		\|-
	\| ~~smtp~~.sugarlabs.org \|\| smtp \|\| 25 \|\| Local delivery (plain SMTP)		\| sunjammer.sugarlabs.org \|\| smtp \|\| 25 \|\| Local delivery (plain SMTP)
	\|-		\|-
	\| ~~smtp~~.sugarlabs.org \|\| [http://www.faqs.org/rfcs/rfc2476.html submission] \|\| 587 \|\| SMTP with STARTTLS, legacy		\| sunjammer.sugarlabs.org \|\| [http://www.faqs.org/rfcs/rfc2476.html submission] \|\| 587 \|\| SMTP with STARTTLS, legacy
	\|-		\|-
	\| ~~smtp~~.sugarlabs.org \|\| [https://tools.ietf.org/html/rfc6409 submissions] \|\| 465 \|\| Email relay (SMTP with SSL, password authentication required)		\| sunjammer.sugarlabs.org \|\| [https://tools.ietf.org/html/rfc6409 submissions] \|\| 465 \|\| Email relay (SMTP with SSL, password authentication required)
	\|}		\|}

Pikurasa: Instructions for set up in Thunderbird

2024-06-14T02:53:03Z

Instructions for set up in Thunderbird

← Older revision		Revision as of 22:53, 13 June 2024
Line 97:		Line 97:

	Ensure your private keys are on hostname.		Ensure your private keys are on hostname.

			== Set up ==

			=== Thunderbird ===

			These are the settings for setting up SMTP with Thunderbird. Note that you use your LDAP username and password, and that the username __'''does not'''__ have "@sugarlabs.org" at the end.

			{\|class=wikitable
			! Server name !! Port !! Connection security !! Authentication method !! User name
			\|-
			\| smtp.sugarlabs.org \|\| 587 \|\| STARTTLS \|\| Normal Password \|\| your LDAP username -- AND WITHOUT @SUGARLABS.ORG AT THE END!
			\|}

			Example:

			[[File:Screenshot from 2024-06-13 22-45-20.png\|thumb\|left\|example of smtp set up in thunderbird ]]

	== See also ==		== See also ==

Chimosky at 15:15, 30 July 2023

2023-07-30T15:15:43Z

← Older revision		Revision as of 11:15, 30 July 2023
Line 83:		Line 83:

	# Contents of KeyTable with both keys		# Contents of KeyTable with both keys
	selector1._domainkey.hostname.~~domain-name~~ hostname.domain-name:selector1:/path/to/selector1/private/*.key		selector1._domainkey.hostname.sugarlabs.org hostname.domain-name:selector1:/path/to/selector1/private/*.key
	selector2._domainkey.hostname.~~domain-name~~ hostname.domain-name:selector2:/path/to/selector2/private/*.key		selector2._domainkey.hostname.sugarlabs.org hostname.domain-name:selector2:/path/to/selector2/private/*.key

	# Contents of SigningTable		# Contents of SigningTable
	*@hostname.domain-name selector1._domainkey.hostname.~~domain-name~~		*@hostname.domain-name selector1._domainkey.hostname.sugarlabs.org
	*@hostname.domain-name selector2._domainkey.hostname.~~domain-name~~		*@hostname.domain-name selector2._domainkey.hostname.sugarlabs.org

	Then add a DKIM record for the second selector		Then add a DKIM record for the second selector

Chimosky at 15:14, 30 July 2023

2023-07-30T15:14:22Z

@@ Line 67: / Line 67: @@
 Your entry would look like this
-   default._domainkey.hostname      TXT     "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
+   selector1._domainkey.hostname      TXT     "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
-   _adsp._domainkey.hostname        TXT     "dkim=unknown"
+   _adsp._domainkey.hostname          TXT     "dkim=unknown"
-Ensure your private key is on hostname and specify the path to it when using a tool like opendkim - /etc/opendkim.conf -, with
+When using an ed25519 key, you'll need to add a fallback RSA key for backward compatibility.
-the user and group of the key set to opendkim.
 == See also ==

Chimosky at 13:05, 29 July 2023

2023-07-29T13:05:47Z

← Older revision		Revision as of 09:05, 29 July 2023
Line 71:		Line 71:

	Ensure your private key is on hostname and specify the path to it when using a tool like opendkim - /etc/opendkim.conf -, with		Ensure your private key is on hostname and specify the path to it when using a tool like opendkim - /etc/opendkim.conf -, with
	the user and group of the key ~~being~~ opendkim.		the user and group of the key set to opendkim.

	== See also ==		== See also ==

Chimosky: Make a and m bold.

2023-07-29T12:51:53Z

Make a and m bold.

← Older revision		Revision as of 08:51, 29 July 2023
Line 41:		Line 41:
	_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"		_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

	The a and mx values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined		The '''a''' and '''mx''' values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
	for hostname.		for hostname.

Chimosky at 12:50, 29 July 2023

2023-07-29T12:50:40Z

← Older revision		Revision as of 08:50, 29 July 2023
Line 52:		Line 52:
	To test DKIM, send an email to autorespond+dkim@dk.elandsys.com		To test DKIM, send an email to autorespond+dkim@dk.elandsys.com


			To generate an ed25519 key to use for DKIM, you can use openssl

			# Generate ed25519 key
			$ openssl genpkey -algorithm ed25519 -out dkim_private.pem
			# Generate public key from private key
			$ openssl pkey -in dkim_private.pem -pubout -out dkim_public.pem

			For ed25519 keys, the p value in the DKIM record must only contain the BASE64 encoded public key, without an ASN.1 structure

			$ openssl asn1parse -in dkim_public.pem -offset 12 -noout -out /dev/stdout \| openssl base64
			VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo=

			Your entry would look like this

			default._domainkey.hostname TXT "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
			_adsp._domainkey.hostname TXT "dkim=unknown"

			Ensure your private key is on hostname and specify the path to it when using a tool like opendkim - /etc/opendkim.conf -, with
			the user and group of the key being opendkim.

	== See also ==		== See also ==

Chimosky: Use mask instead of int value

2023-07-29T12:31:18Z

Use mask instead of int value

← Older revision		Revision as of 08:31, 29 July 2023
Line 39:		Line 39:

	hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"		hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
	_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/64 a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"		_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

	The a and mx values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined		The a and mx values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined

Chimosky: Add SPF entry example.

2023-07-29T12:26:34Z

Add SPF entry example.

← Older revision		Revision as of 08:26, 29 July 2023
Line 35:		Line 35:

	Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.		Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

			You can add an spf record in the zone file in the form

			hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
			_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/64 a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

			The a and mx values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
			for hostname.

			Also maintain spacing and formatting for each section you add in the zone file.

	== DKIM ==		== DKIM ==

Bernie at 06:35, 29 July 2023

2023-07-29T06:35:03Z

← Older revision		Revision as of 02:35, 29 July 2023
Line 30:		Line 30:
	* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.		* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

	* All email ~~for~~ the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''		* All email originating from the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''

	== SPF ==		== SPF ==

	Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] ~~record~~.		Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

	== DKIM ==		== DKIM ==