Skip to main content

Who your emails are sent from

Organizer Guide 3 min read

Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.

By default every email about your events is sent by EventMann, from our address. Configure your own outgoing mail server under Settings → Email → SMTP & Mail and attendees hear from you instead.

What you can do here

  • Pick a provider — Custom SMTP, Mailchimp, SendGrid, Mailgun, Postmark, Amazon SES or Brevo.
  • Set connection details — host, port and encryption for SMTP-style providers (Custom SMTP, Mailgun, Amazon SES), or an API key for the others.
  • Set your From name and address.
  • Send a test email — verifies the connection for real, to your own inbox, before you rely on it.

What gets sent through it

  • Sent as you, once configured: booking confirmations and tickets, event reminders, reschedule and cancellation notices, waitlist offers, invoices, surveys, announcements, cart reminders and marketing campaigns.
  • Always sent by EventMann: email verification, password resets and security alerts — those concern your EventMann account, not your event.
  • If you configure nothing: everything keeps working on our mail server. Replies simply come to us rather than to you, and your domain gets none of the sending reputation.

Good to know

  • Use a From address on the same domain as the account you authenticate with. Sending as your own domain through an unrelated provider makes SPF and DKIM disagree, and mailbox providers answer that with the spam folder.
  • Gmail and Microsoft 365 both need an app-specific password rather than your normal one; Mailgun, Brevo and Amazon SES likewise issue a dedicated SMTP secret that is different from their account API key.
  • For anything beyond a few hundred emails a day, a dedicated provider such as Brevo, SendGrid or Postmark will deliver far more reliably than a mailbox.
  • Re-saving without changing the password or API key keeps the one already stored — you do not need to retype a secret just to change the From name.

Troubleshooting

  • Test email fails with a credential error — for Gmail/Workspace, use an App Password from Google Account → Security → 2-Step Verification, not your account password (Google stopped accepting those for SMTP in 2022). For another provider, check you used its dedicated SMTP secret rather than a general API key.
  • Test email fails and mentions SMTP AUTH — on Microsoft 365 this means SMTP AUTH is disabled for the mailbox; an admin has to enable it under that mailbox's email app settings.
  • Test email cannot connect at all — check host and port: 587 for TLS, 465 for SSL; port 25 is blocked by most cloud providers.
  • Connects but the encryption looks wrong — match encryption to port: TLS with 587, SSL with 465.

Need more help with this topic?

Contact Support

We use cookies

We use cookies and similar technologies to personalise content, analyse traffic, and improve your experience. You can accept all, reject non-essential, or customise your preferences.