Connecting other services to Tranet Mail
Groupware, dashboards, and other clouds — when it’s fine, and when it isn’t
You can connect Tranet Mail to other tools — a company Nextcloud, groupware, a dashboard, or another mail service. Whether that’s a good idea comes down to one simple question.
The one question to ask
Does the service run on hardware you or your company own and control?
If yes, connecting it is fine — your credentials never leave your premises. If it runs on someone else’s public cloud, your Tranet Mail password and a copy of your messages will end up on their servers.
Fine: services you host yourself
Any mail app or service you run and host on your own premises, under your control, is a safe way to add another window into your mailbox. The connection stays inside your own infrastructure — nothing is handed to an outside company.
Examples: a company Nextcloud with its Mail app, an on-premises groupware server, or an internal client you operate.
To connect a self-hosted service, point its mail settings at Tranet Mail using the details below:
- Add a mail account in the service (e.g. Nextcloud → Mail → add account).
- Choose IMAP, and enter the manual settings below.
- Username is your full email address; the host is
mx1.tranet.netfor both incoming and outgoing.
Not recommended: public cloud services
Connecting Tranet Mail to a public cloud service — for example Gmail’s “Check mail from other accounts,” Outlook.com, Yahoo, or a hosted “unified inbox” app — hands your Tranet Mail username, password, and a copy of your messages to that provider. From then on your mail lives on their servers too, under their terms, outside your control.
Here is why we advise against it:
Practical
You lose the direct, private path Tranet Mail is built to give you. Mail now makes an extra hop through a third party, which can add delay, break threading or folders, and means an outage or policy change at that provider disrupts your mail even when Tranet Mail is running normally. You also then depend on two providers instead of one.
Privacy
The provider stores and processes a full copy of your messages and contacts on its own servers. It can scan and index that content for its own purposes as permitted by its terms, and its staff and subprocessors may have technical access. Mail you intended to keep between you and Tranet Mail is now also in a company you have no relationship with regarding that mailbox.
Security
Your Tranet Mail password is stored on the provider’s systems. That widens your exposure well beyond your own devices: a breach, insider misuse, or leaked credential anywhere in that provider’s chain now reaches your mailbox, and because plain mail access relies only on username and password, a stolen credential can be used from anywhere. You cannot revoke a single device the way an app-specific setup would allow.
In some cases this is also your network password. If your mailbox sign-in is the same as your Active Directory / Windows network login (true for some Tranet domains), handing it to a third-party cloud exposes not just your email but your network account — and everything that account can reach. If you are unsure whether your mail and network passwords are linked, assume they are and do not connect such a service.
Legal and compliance
Routing your mail through a third-party cloud can breach IT-usage or confidentiality policies, and for regulated data (for example under GDPR, HIPAA, or client-confidentiality obligations) it can create an unauthorized transfer of personal or privileged information to a processor you have not vetted or contracted with. That may be a compliance violation in its own right, independent of whether any breach ever occurs.
Business and insurance
If your organization carries cyber liability insurance, moving credentials and mail to an unvetted third party can affect your coverage or complicate a claim. Confirm with your insurer before doing it. This is the same concern described on the Outlook page.
Bear in mind, too, that if such a connection leads to a loss, any recovery would lie against that third-party provider under its own terms — which typically cap or exclude damages — and not against Tranet. Weigh that before entrusting your mail to a service you have not vetted.
If you must connect such a service anyway, treat your Tranet Mail password as no longer private: change it if you ever stop using the service, and turn on two-factor authentication in webmail.
Manual settings
Use these when connecting any client or service to Tranet Mail.
| Incoming (IMAP) | mx1.tranet.net port 993 SSL/TLS |
|---|---|
| Outgoing (SMTP) | mx1.tranet.net port 465 SSL/TLS |
| Username | your full email address |
| Password | your mailbox password |
If the service only offers STARTTLS: incoming port 143, outgoing port 587.
Disclaimer. Tranet Mail connects your email directly and privately between you and our servers. No email system, including Tranet Mail, is immune to compromise, and we do not guarantee against all risk; keeping your account secure is a shared responsibility. Choosing to connect a service that routes your messages or credentials through Microsoft, Google, or any other third-party cloud is your decision and outside Tranet’s control. Tranet Inc. accepts no liability — implied, explicit, or otherwise — for exposure, loss, or damages arising from that choice. By making that choice, you agree to indemnify and hold harmless Tranet Inc., including for the cost of defending any resulting claim. If your organization carries cyber liability insurance, confirm with your insurer before connecting such a service.
Monitoring notice. Tranet may, as a courtesy and on a best-effort basis, detect and report when your account is accessed persistently from a third-party or cloud provider rather than your own device or premises. This monitoring is provided without warranty; it may be incomplete, inaccurate, or delayed, it identifies infrastructure and not intent, and it creates no obligation on Tranet to detect, prevent, or notify you of any particular access. You remain responsible for your own account security.