Tag: Webmail

  • How to organize business mailboxes

    Laptop showing a webmail interface in a professional office, with organized mailboxes, folders and business email accounts.

    Why Mailbox Organization Matters

    Email is one of the core communication tools of every business. Quotes, customer requests, invoices, partnerships, orders and internal discussions all pass through it.

    When everything ends up in one generic mailbox, or when employees use personal email accounts for company communication, information is easily lost. A message may remain unanswered, the wrong reply may be sent, or the history of a conversation may disappear.

    A clear mailbox structure is not a luxury. It helps the business work more clearly, more quickly and more professionally.

    Start with Business Roles

    The best starting point is to organize email around business functions, not only around individual names.

    info@mybrand.com
    sales@mybrand.com
    support@mybrand.com
    billing@mybrand.com
    hr@mybrand.com
    marketing@mybrand.com

    This helps customers know where to send their request and helps your team understand who is responsible for each communication flow.

    If everything goes to info@, it may look simple at first. As message volume grows, however, it becomes harder to separate sales, support, billing and urgent customer requests.

    When Should You Use Personal Mailboxes?

    Personal business mailboxes still have a place inside a company. Addresses such as maria@mybrand.com or john@mybrand.com are useful for direct professional communication.

    They should not, however, become the main public addresses for critical business functions. If all sales requests go to one employee and that person is unavailable, changes role or leaves the company, continuity is lost.

    Public business functions should remain connected to role-based addresses such as sales@, support@ and billing@.

    Shared Mailbox or Separate Account?

    A shared mailbox is useful when more than one person needs to view and reply to the same stream of communication. For example, support@ may be handled by the entire support team.

    A separate mailbox is more appropriate when communication is personal or belongs to a specific role with restricted access, such as management, accounting or HR.

    Rule of thumb: When communication belongs to a company function, use a role-based mailbox. When it belongs to a specific person, use a personal mailbox.

    Aliases Are Your Friend

    Not every address needs to be a separate mailbox. In many cases, an alias is enough.

    For example, you can have:

    contact@mybrand.com
    hello@mybrand.com
    office@mybrand.com

    and route all of them to info@mybrand.com.

    This lets you keep several easy public-facing addresses without creating dozens of separate mailboxes that need to be checked, secured and maintained individually.

    Do Not Use One Mailbox for Everything

    The classic mistake is sending everything through info@: quotes, technical support, CVs, orders, billing questions and general enquiries.

    This can work only at the very beginning. Later, it creates delays, wrong priorities and missed messages.

    The solution is not to create endless mailboxes. The solution is to build clear communication flows for the main functions of your business.

    Use Folders and Rules

    Even the right mailbox can become chaotic without folders, filters and rules.

    Quotes
    Customers
    Invoices
    Support
    Pending
    Completed

    Rules can automatically move messages, flag important senders or separate system notifications from real customer requests.

    The goal is not to hide emails. The goal is to find what you need quickly.

    Be Careful with Access Permissions

    Not everyone should have access to everything. Mailbox access should be based on each person’s role inside the business.

    billing@ → accounting team
    hr@ → HR or management
    support@ → support team
    sales@ → sales team

    This reduces the risk of mistakes, protects sensitive information and gives you better control over internal communication.

    Backup and Security

    Business mailboxes often contain critical information: contracts, quotations, invoices, customer data and internal decisions. It is not enough for them to exist. They need to be protected.

    Strong passwords, MFA where available, properly configured SPF, DKIM and DMARC, careful access management and a reliable backup or retention policy are essential.

    Email is a key part of business continuity. If access is lost or important messages are deleted, the problem is not just technical. It becomes operational.

    Common Mistakes

    1. Everything goes to info@: simple at first, unmanageable later.
    2. Using personal Gmail accounts for company work: poor branding, lower trust and loss of control.
    3. Using the same password across accounts: a serious security risk.
    4. No folder structure: makes searching and continuity harder.
    5. No backup or retention policy: one accidental delete can become a serious problem.

    Frequently Asked Questions

    Do I need a separate mailbox for every employee? Usually yes. It provides clear identity, better security and easier management.

    Which is better, an alias or a new mailbox? Use an alias when you simply need another public address that routes to the same recipient. Use a separate mailbox when you need independent access and storage.

    Should everyone have access to support@? Not necessarily. Access should be granted only to the team members who actually need it.

    Conclusion

    A well-organized email system does more than make daily work easier. It protects the business, improves customer support and allows the team to grow without creating communication chaos.

    The right mailbox structure presents a more professional image externally and creates better order internally.

    Want to organize your business email properly?

    Easy can help you build a secure, scalable mailbox structure tailored to your team’s needs.

    Learn more at Easy →
  • When Parallels Became Odin: A Rebrand with Hosting Ambitions

    When Parallels Became Odin: A Rebrand with Hosting Ambitions

    A new name, a familiar mission

    When Parallels Became Odin: A Rebrand with Hosting Ambitions — parallels
    When Parallels Became Odin: A Rebrand with Hosting Ambitions — odin

    Key fact

    On March 25, 2015, at World Hosting Days 2015, Parallels — the company best known for control panel products such as Plesk — announced it would continue its business under the new name Odin. The rebrand expands the company’s positioning while keeping existing services intact.

    The technology world loves a dramatic rename, but not all rebrands are purely cosmetic. When Parallels unveiled its new identity as Odin during World Hosting Days 2015, the announcement was positioned as more than a change of label: it was a statement about direction. Odin would keep the familiar tools partners rely on — Plesk control panels, SiteBuilder, cloud web hosting and webmail management — while broadening its solutions to reach larger and more specialised business groups.

    Why the rebrand matters

    A name change can be a signal of strategic evolution. In Odin’s case the company emphasised three practical points:

    • It is not abandoning existing products or customers — services are preserved and expanded rather than retired.
    • It aims to offer more specialised solutions beyond a single control panel, addressing broader hosting, cloud and business needs.
    • The rebrand was unveiled at a major industry event (World Hosting Days), underlining a global ambition.

    What Odin brings to the table

    Partners and hosting providers who already knew Parallels for Plesk and related tools were reassured that the familiar building blocks remain. At the same time, Odin positioned itself as a provider of a wider portfolio:

    • Plesk and other control-panel technologies as core management tools.
    • Cloud web hosting platforms and hosting resources for growing sites and services.
    • Site building and webmail management integrated into broader hosting stacks.
    • New, more specialised offerings designed to target larger enterprise and business groups.

    What it means for partners in Greece

    As the company re-emerged under the Odin name, existing partnerships continued. The local Platinum partner — one of Odin’s closest allies in the region — highlighted pride in staying alongside the vendor through the change. For partners this generally translates to:

    • Continuity of service and compatibility with existing deployments.
    • Potential access to a broader product set aimed at enterprise and specialised use cases.
    • Opportunities to expand offerings to customers without disrupting current operations.

    Practical steps for hosting providers

    If you’re an ISP, reseller or hosting company that relies on Parallels-era products, consider these practical checks:

    1. Confirm roadmap and support commitments for your current control-panel and hosting stack.
    2. Review new Odin solutions for features that could unlock higher-value customers.
    3. Plan communications to reassure end customers that services and billing are unaffected by the name change.
    4. Evaluate integration or migration paths only if new offerings offer concrete business advantages.

    Conclusion

    Rebrands can be risky, but they can also reflect real strategic shifts. Odin’s transition from Parallels — announced publicly at World Hosting Days on March 25, 2015 — made a clear point: the company intended to broaden its scope while preserving the tools that partners depend on. For hosting providers and partners, the sensible response is to verify continuity, explore new opportunities in the expanded portfolio, and communicate stability to customers as the vendor evolves.