Email for standalone servers

From techdocs
Revision as of 10:35, 23 October 2023 by Plinich (talk | contribs) (Created page with "Various individuals and groups within CSE run their own servers "in the cloud" (read: AWS) which need email capability. Email can be managed completely (i.e., sending and receiving) on the server, or some or all of the management can be offloaded to an email hosting service (e.g., Rackspace, where CSE has an account). In this article we talk about the the different possibilities and which might be more appropriate in some use cases than others. * Create an...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Various individuals and groups within CSE run their own servers "in the cloud" (read: AWS) which need email capability.

Email can be managed completely (i.e., sending and receiving) on the server, or some or all of the management can be offloaded to an email hosting service (e.g., Rackspace, where CSE has an account). In this article we talk about the the different possibilities and which might be more appropriate in some use cases than others.


  • Create an SPF record for the server's sending domain containing its IP address
  • Using PostFix to send email
    • Configure the full domain in /etc/hostname
  • Mailboxes managed by Rackspace
    • The cseunsw.tech domain mail exchangers (MX)
    • Using Rackspace's email servers to send email as a single user
      • Sending email using curl
      • Using PostFix
    • Rackspace mailboxes
      • Simple email, not Exchange
      • Picking up email using IMAP
      • Forwarding email from a cse.unsw.edu.au address using mlalias
  • Configuring a server to send email as cse.unsw.edu.au
    • Add IP address to authorisedsenders.cseunsw.tech TXT record
    • /etc/postfix/main.cf