Two separate things: how mail leaves your server, and what the mail says. Get delivery working first — editing templates that never arrive wastes an afternoon.

Choose a mail provider

WBAMS ships several. Open Settings → General → Mail and choose one.

SMTP
Any mail server that speaks SMTP, including your own host’s. The general-purpose choice.
Mailgun / SendGrid / SparkPost
Delivery services with an API key. Better deliverability and real bounce handling.
Microsoft Graph
Send through a Microsoft 365 tenant. Requires Friendly URLs and a System URL to be configured first.
PHP Mail
Hands the message to the server’s local mail command. Convenient, and the most likely to land in spam.
Do not use PHP Mail for customer email.

It sends without authentication from whatever address you set, which is precisely the pattern spam filters reject. Use it only to get an installation working, then move to SMTP or a delivery service.

Configure SMTP

  1. SMTP Host — your mail server’s hostname.
  2. SMTP Port — 465 with SSL, or 587 with TLS. The default is 465.
  3. SMTP SSL Type — SSL for 465, TLS for 587. Never None.
  4. SMTP Authentication — Password for a normal mailbox, or OAuth2 for Google Workspace and Microsoft 365.
  5. SMTP Username and SMTP Password — the mailbox credentials. For Google or Microsoft with two-factor, this must be an app password, not the account password.
  6. Save, then press the test button. Fix a failure here before doing anything else.

OAuth2 instead of a password

Choosing OAuth2 reveals a callback URL, a client ID and a client secret. Register the callback URL exactly as shown at your provider, paste the client credentials, and complete the connection to obtain the token. The token field is read-only because WBAMS fills it.

Configure a delivery service

  1. Create an API key in the provider’s dashboard with permission to send.
  2. Paste it into the provider’s field — for Mailgun this is the Mailgun Private API Key, and you must also choose the Mailgun Region, US or EU. The wrong region fails every send.
  3. Verify your sending domain at the provider. This is where SPF, DKIM and DMARC records are set.
  4. Save and run the configuration test.

The sender address

Set the system email name and address in Settings → General. It must be an address at a domain you control and have authorized to send — sending as a Gmail or Yahoo address you do not own is the single most common cause of mail being rejected outright.

Edit the templates

  1. Open Settings → Email Templates.
  2. Pick the type — product, invoice, support, general — then the template.
  3. Edit sender, recipients, subject and body. Merge fields are listed beside the editor and click to insert.
  4. Save, and use the preview to check the merge fields resolve.
Never rename a template.

WBAMS looks templates up by name. Rename one and the message stops being sent — it does not send under a new title, it does not error, it simply never arrives. Edit the subject instead; that is what the customer sees.

Prove delivery

  1. Run the mail provider test. It proves the connection, not delivery.
  2. Create a test customer at an address on a different mail provider from your own — if you run Google, test to Outlook.
  3. Trigger a real message: generate an invoice, or send the welcome email.
  4. Confirm it arrived, and check whether it landed in spam. Arriving in spam is a failure, not a pass.
  5. Read Platform → Email log and confirm the entry says sent.
If mail sends but lands in spam, the problem is DNS, not WBAMS.

Publish SPF, DKIM and DMARC records for your sending domain. No mail setting in the product substitutes for them.