Difference between revisions of "Service/smtp"
< Service
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
== Notes == | == Notes == | ||
| − | * Users with a | + | * Users with a Sugar Labs [[Service/shell|shell account]] on can use our SMTP relay for personal email submission. Any abuse will be prosecuted. |
* Preferably use the [http://www.faqs.org/rfcs/rfc2476.html submission] port for email relay. Unauthenticated and unencrypted connections are not allowed to relay. | * Preferably use the [http://www.faqs.org/rfcs/rfc2476.html submission] port for email relay. Unauthenticated and unencrypted connections are not allowed to relay. | ||
Revision as of 12:47, 21 November 2010
Hostnames
| hostname | service | port | function |
|---|---|---|---|
| smtp.sugarlabs.org | smtp | 25 | Local delivery (plain SMTP) |
| smtp.sugarlabs.org | submission | 587 | Email relay (SMTP with STARTTLS, password authentication required) |
| smtp.sugarlabs.org | smtps | 465 | Email relay (SMTP with SSL, password authentication required) |
Hosted on
Administrative contact
- postmaster AT sugarlabs DOT org
Sysadmins
Notes
- Users with a Sugar Labs shell account on can use our SMTP relay for personal email submission. Any abuse will be prosecuted.
- Preferably use the submission port for email relay. Unauthenticated and unencrypted connections are not allowed to relay.
- smtp.sugarlabs.org is *not* the MX for the sugarlabs.org.
Google Apps handles our domain and forwards to smtp.sugarlabs.org for unknown users
SPF
Our domains use a non-strict (~all) SPF record.
If you send email with sugarlabs.org in the From: header, then you MUST submit it to our SMTP server.
DKIM
Our domain publishes a test DKIM key. All outgoing email is signed, but at this time verifiers will ignore our DKIM signature.
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.