Authorized contacts
Identify who can approve DNS changes, account creation, account removal, and migration windows.
Security and trust
Concrete safeguards for a service that carries business conversations.
Logamail's trust story is practical: domain records, account boundaries, AI approval controls, sending controls, migration handling, and clear escalation paths.
Domain authentication
Setup reviews MX routing, SPF authorization, DKIM signing, and DMARC policy so receiving and sending are not treated as guesswork.
Mailbox access
Admins decide which mailboxes exist, which role addresses route to which accounts, and when a mailbox should be suspended or removed.
Sending behavior
Business mailboxes should operate within responsible rate limits. Campaign-style sends include unsubscribe handling and domain-readiness checks.
Migration boundaries
Migration uses source IMAP details supplied by the business and imports into selected destination mailboxes. Spam and trash can be excluded to avoid bringing unnecessary mail forward.
Support escalation
DNS, migration, delivery, and account-access issues are routed to support with the domain, mailbox, sender, recipient, timestamp, and error message when available.
AI assistance
AI can prepare drafts, routing suggestions, task summaries, and technical handoffs, while external replies, account changes, and code changes remain subject to human approval.
Human review
Mailbox changes, migration timing, DNS switches, and sensitive support cases should be reviewed by an authorized business contact before production changes are applied.
Operational controls
What Logamail asks teams to define before launch.
Role address owners
Assign sales@, support@, billing@, and other role addresses to real people or shared queues.
Retention expectations
Decide which historical mail should be imported and how closed employee mailboxes should be handled.
Sender identity
Use consistent display names, signatures, and reply-to behavior so customers know who is contacting them.
High-risk cases
Escalate billing disputes, account ownership changes, suspicious links, and delivery failures to a human reviewer.
Launch validation
Send test messages, verify replies, inspect authentication headers, and confirm calendar invitations before rollout.