marley.umd.edu is a set of on-campus, highly-available mail relays, available for any staff/faculty at UMD to use with a dedicated service account they can request and manage in SIMS. This is often the simplest option for most applications, it is available to any IP space (on-campus, cloud, other networks), and allows sending as any @umd.edu email address.
Marley is rate-limited by default to 100 recipients per hour per server, this can be increased by opening a ticket.
Please see Send Email using an SMTP Relay Service Account for more information about configuring your application to use Marley with a service account.
If your application is on-campus, marley.umd.edu is also available as an unauthenticated relay. This does require placing your device’s IP address into an allowlist, please see the Send a Document to Email using Printers on Campus article on configuring your device to use Marley without authentication. Similar to Authenticated Marley - you can send as any @umd.edu address.
Google Service Accounts provide real Google Accounts that can send and receive email. By default, they can only send email as the account. This is the only option we provide for applications that need to receive email.
Setting up any Google Service Account will require working with DIT to enable access.
When contacting DIT, please provide the following:
To request a Google Service Account, see the Request and Manage UMD Google Service Accounts article.
Rate limits imposed by Google vary based on how your application is relaying email. Most applications use the default Gmail SMTP relay, which has a limit of 2,000 messages per day, per user. The other option is to use the Google Workspace SMTP relay, which has a limit of 10,000 messages per day, per user.
It is possible to relay mail through our IronPort relays (relay.mail.umd.edu). It requires your server to have a static, public IP address with a process to periodically review and renew. Prior of using the relay.mail.umd.edu, you would need to submit a request to the DIT Service Desk at 301.405.1500 or email itsupport@umd.edu.
Please note - emails relayed through IronPort will not be DKIM-signed by IronPort, and will not pass SPF when sent to umd.edu recipients. This means umd.edu recipients will see a Google could not verify this sender icon when viewing the email. Emails to external recipients will pass SPF and appear as authenticated. If your application supports DKIM, you can configure DKIM in your application.
We strongly recommend migrating your application to use Authenticated Marley instead, detailed above, to allow your emails to be verified as legitimate umd.edu emails when sent to umd.edu addresses.