What should you ask to see during a KumoMTA setup walkthrough? Bring a short list of the tasks you expect to handle after the handover.
Useful examples include locating your domain and IP settings, understanding where provider rules are maintained, and checking how delivery events reach your...
Considering a migration because delivery has become difficult? Start with two separate lists: the problems you are seeing today and the capabilities you want from the new setup.
For each current problem, record the affected destinations, when it began and a few redacted error examples. For the...
A useful way to scope your KumoMTA setup: split your requirements into three columns.
1. What you already have working.
2. What you need configured for the new setup.
3. What requires a custom integration or migration.
For example, note your sending application, existing domains and IPs...
Planning an MTA migration? Put the cutover checkpoints in writing before choosing a date.
List what must be checked before the move, who will approve the switch, and what would make you postpone it. Include the sending application, domain and IP assignments, authentication settings, and any...
Before buying a KumoMTA configuration package, decide what a useful handover should cover for your team.
Write down who will make routine edits, where your configuration notes will be kept, and which checks you want to walk through before taking over. Ask how future changes should be recorded...
Delivery problems started after a change? Bring a short timeline to the troubleshooting discussion.
Note when the issue first appeared, what changed around that time, which destinations are affected, and whether the same symptoms occur across all sending domains or only part of the setup...
Have a custom sending setup? Make a list of the parts that differ from a standard installation before choosing a configuration package.
Examples to mention in your enquiry include multiple sending applications, existing routing requirements, custom event handling, or an established deployment...
Do you have several email infrastructure problems competing for attention?
Put them into a short priority list before commissioning work. Describe the issue that affects your operation most, the changes you are planning, and the improvements that can wait.
For each item, note what you are...
When evaluating an email delivery UI, start with the tasks you want to perform.
Write down the questions you expect to answer during a normal working day. For example: what is waiting to send, where can I review delivery events, and which configuration changes will still need an administrator...
An infrastructure project needs more than a server login. It needs a clear list of who can approve and make the required changes.
Before arranging a KumoMTA setup or migration, identify who manages your hosting, DNS, sending application and current MTA. Note any access restrictions or change...
Comparing quotes for an email infrastructure project? Give each provider the same brief.
Include your current MTA and sending application, IP/domain count, approximate volume, and the problem or change you need help with. Then ask what the quoted work includes: investigation, configuration...
Planning to use the configuration package with MailWizz? Include the application side in your enquiry.
Tell me whether this is a new installation or an existing sending setup, how the application is hosted, and which parts you already have working. Also mention any custom extensions or...
What would make your MTA migration a success?
Before discussing the move, write down three things: what must keep working, what you want to improve, and how you will check the result.
For example, your requirements might include keeping an existing sending application, retaining a particular...
Who will maintain your KumoMTA setup after it is installed?
That is a useful question to settle before buying a configuration package. If you will operate it yourself, list the routine changes you expect to make. If a developer or administrator will manage it, include them in the setup...
Need help with a delivery problem? Make your first message a short incident brief. It gives us a clearer starting point for deciding what needs investigation.
Include:
• What changed, and when you first noticed the problem.
• Which mailbox providers are affected.
• A recent error or deferral...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.