How it works
Business email, DNS and mail apps
Fix blocked sending (Relay access denied)
If receiving works but sending shows Relay access denied, open the outgoing SMTP settings. Use port 587, STARTTLS, Normal password and your full email address as username. Port 25 is for server-to-server delivery, not mail apps. Ensure this account actually uses that outgoing server. Use the mailbox password, which can differ from your dashboard password. Never share passwords in a ticket. Automatic setup in mail apps uses the domain’s autoconfig/autodiscover CNAME and SRV records (see Configure DNS records). They work even if the website is hosted outside Devora. Existing accounts may need a one-time SMTP correction.
Open the account or project menu
Open Business email in the account menu or within a project. Projects organize the link and suggest connected domains. Use a domain you own; the application’s free subdomain is not your business email domain.
Review the subscription and payment
Email is separate from hosting, billed in BRL per mailbox for 30-day periods, without a free trial. Choose the quantity and review price and quota. Generate and pay Pix: only payment confirmed with the provider activates mailboxes. Pending payment or clicking a button grants no access. The actual owner administrator has a server-validated courtesy action that creates no invoice.
Understand upgrades and renewals
Increasing quantity during a paid period credits the proportional remaining time and starts a new 30-day period after payment. Renewing the same quantity adds 30 days to the current expiry. Quantity reductions must wait until the active period ends; do not delete accounts to bypass licensing.
Add and verify your domain
Add your domain, optionally selecting its project. First publish only the ownership TXT at _devora-mail.yourdomain and verify it. With an active service and valid proof, the panel configures the mail domain and provides DKIM. A domain already on the mail server requires explicit owner-administrator adoption; existing mailboxes are never imported or overwritten automatically.
Configure DNS records
Click a domain row for DNS settings and create exactly these records: TXT _devora-mail.yourdomain = verification token; MX yourdomain 10 mail.bytsend.com (incoming mail); TXT yourdomain "v=spf1 mx ~all" (SPF, authorizes sending); TXT _dmarc.yourdomain "v=DMARC1; p=none" (DMARC); and the DKIM TXT, which appears after verification (signs messages). For automatic setup in Outlook, Thunderbird and mobile: CNAME autoconfig.yourdomain and autodiscover.yourdomain → discover.devoracloud.com; SRV _autodiscover._tcp 0 0 443 discover.devoracloud.com; SRV _imaps._tcp 0 1 993 mail.bytsend.com; SRV _submission._tcp 0 1 587 mail.bytsend.com. These records work even if the website is hosted outside Devora. Keep a single SPF record by merging authorized services. Website CNAME records do not configure email. Plan migration before changing an existing MX.
Create a mailbox
After domain verification, choose Add mailbox, select the domain, enter the name before @ and a password of at least 12 characters. Mailbox count cannot exceed the license. Passwords are not returned by the API or stored as plaintext in Cloud. Use Change password when needed. Retry failed creation with the same address and password; existing accounts cannot be overwritten.
Use webmail, Outlook or mobile
Use Open webmail or configure Outlook, Thunderbird or mobile: full email address as username, mailbox password, incoming IMAP mail.bytsend.com port 993 with SSL and outgoing SMTP mail.bytsend.com port 587 with STARTTLS and authentication. Automatic setup depends on the app and version. The mailbox password is independent from your Cloud password.
Check quota and service validity
Quota applies per mailbox and appears before payment. Admin price and quota edits apply to new orders and renewals. At expiry, managed-account access is suspended while messages are preserved; renewal restores service. Existing unmanaged mailboxes are not changed by this lifecycle.
Manage imported mailboxes
Imported mailboxes: after an administrator links an existing mailbox, it appears under Email accounts. Messages and the current password remain on the server; importing does not migrate or recreate the mailbox. Linking a project organizes the account without changing its email address. Owner-administrator courtesy creates no charge.
Change the password securely
Change password: open Business email, find the address under Email accounts and choose Change password. Enter a new password of 12–128 characters and click Save password. The previous password cannot be displayed. After a successful save, update the password in Outlook, mobile and other mail apps; new webmail logins also use it. Changing the password preserves messages and does not change your Cloud login password.
Troubleshoot and get help
For your AI or support, provide domain, affected address, login/sending/receiving failure, time, error, service state and whether webmail works. Never provide passwords or private message content. Test sending and receiving with an external address after DNS setup.
Update routing after migration
Routing and migration: use the server hostname, public IP and webmail currently shown in the panel, not an old IP from screenshots. MX targets a DNS hostname, not an IP. Administrators update addresses in Admin → Business email. This updates instructions; it does not migrate mailboxes or change DNS. With the same hostname, clients keep MX while the administrator updates server A/AAAA. A changed hostname requires updating MX and mail apps. Configure the private connection and key in Admin → Integrations. Refresh and reopen the domain for current instructions.