Difference between revisions of "Service/smtp"

From Sugar Labs
Jump to navigation Jump to search
(update to the current state)
Line 6: Line 6:
 
| smtp.sugarlabs.org || smtp      || 25  || Local delivery (plain SMTP)
 
| smtp.sugarlabs.org || smtp      || 25  || Local delivery (plain SMTP)
 
|-
 
|-
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587  || Email relay (SMTP with STARTTLS, password authentication required)
+
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587  || SMTP with STARTTLS, legacy
 
|-
 
|-
| smtp.sugarlabs.org || smtps      || 465  || Email relay (SMTP with SSL, password authentication required)
+
| smtp.sugarlabs.org || [https://tools.ietf.org/html/rfc6409 submissions]  || 465  || Email relay (SMTP with SSL, password authentication required)
 
|}
 
|}
  
Line 28: Line 28:
 
* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''
 
* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''
  
* We prefer to use the [http://www.faqs.org/rfcs/rfc2476.html submission] port 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.
  
* smtp.sugarlabs.org is *not* the MX for the sugarlabs.org.
+
* 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.'''
Google Apps handles our domain and forwards to smtp.sugarlabs.org for unknown users
 
 
 
* Just for those of you wanting to use just one email client (namely gmail in this case), you can simply add a second account to run through gmail (say user@activitiycentral.com or user@sugarlabs.org) and it will then allow you to choose which account you'd like to send from.
 
 
 
To do this you need to login to your gmail account and then go the following url (it is not easy to spot): https://mail.google.com/mail/?tab=om#settings/accounts
 
Choose '''send mail from another address'''; follow the instructions for sending out via smtp.sugarlabs.org
 
  
 
== 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] record.
 
If you send email with sugarlabs.org in the From: header, then you '''must''' submit it to our
 
SMTP server.
 
  
 
== DKIM ==
 
== DKIM ==
  
Our domain publishes a '''test''' [http://en.wikipedia.org/wiki/DKIM DKIM] key. All outgoing email
+
Our domain publishes a [http://en.wikipedia.org/wiki/DKIM DKIM] key.
is signed, but at this time verifiers will ignore our DKIM signature.
 
  
 
To test DKIM, send an email to autorespond+dkim@dk.elandsys.com
 
To test DKIM, send an email to autorespond+dkim@dk.elandsys.com
  
In anticipation of switching on strict DKIM verification, all email for the sugarlabs.org domain
 
must be submitted to our SMTP server. Failure to do so may result in your email being occasionally
 
blocked by spam filters.
 
  
 
== See also ==
 
== See also ==

Revision as of 14:36, 8 July 2020

Hostnames

hostname service port function
smtp.sugarlabs.org smtp 25 Local delivery (plain SMTP)
smtp.sugarlabs.org submission 587 SMTP with STARTTLS, legacy
smtp.sugarlabs.org submissions 465 Email relay (SMTP with SSL, password authentication required)

Hosted on

Machine/sunjammer

Administrative contact

  • postmaster AT sugarlabs DOT org

Sysadmins

Notes

  • Users with a Sugar Labs shell account on sunjammer can use our SMTP relay for personal email submission. Any abuse will be prosecuted.
  • The 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.

SPF

Our domains use a non-strict (~all) SPF record.

DKIM

Our domain publishes a DKIM key.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com


See also