Configure and test delivery
After uploading v188, run Admin → Database updates. Open Admin → Email delivery → Configure sender and SMTP. Enter the public HTTPS site address, sender email and name, optional reply-to, SMTP host, port, username and password. Choose STARTTLS (usually 587) or implicit TLS (usually 465), as specified by your provider. Certificate verification stays enabled.
Use a sender authorized by the provider, configure its SPF DNS record, enable DKIM signing and align DMARC with the sender domain. These are provider/DNS tasks; the app cannot guarantee inbox placement. Hosting server mail remains available.
Saving requires a recent sign-in and sends nothing. Passwords are stored in private auth-settings.php outside public/; preserve this file on deployment. Blank password retains the saved secret. Changing the SMTP server or username requires its password again.
Return to Email delivery and choose Send a test email to my account. Check your inbox and spam folder. This sends only to the signed-in administrator.
Acceptance notifications
Accepting a company invitation queues one notification to the campaign owner. System and GM invitations notify the issuer. Password, email-link, Google and Discord acceptance use the same claim path. Notifications contain the accepting account and company, never the invite token.
Messages send after the claim commits. A delivery failure does not undo acceptance. Email delivery lists queued, failed and accepted messages and lets administrators retry. Pending messages after an interrupted request require admin review. An interrupted sending state can be retried after five minutes with confirmation, since the provider may already have received it.
Sent means accepted by the sending mail server. Review provider logs for delivery or authentication failures. Retry cannot guarantee exactly-once delivery after a network interruption.