T-Text requests are handled in this container and use Google Translate API wiring instead of the old CGI host.
T-Mail now runs its translation routes inside this container instead of proxying a dead CGI host.
Translate mail drafts, pasted text, and live web pages from one local workspace.
The old service depended on Perl CGI scripts, retired Babelfish paths, and a host that no longer works reliably. This rebuild keeps the useful mail alias model, replaces translation calls with local Google-backed routes, and shows the output in the right panel instead of dropping users into broken legacy pages.
T-Sail fetches and translates pages from this container instead of handing users to a dead Babelfish path.
Mailbox delivery remains on the mail host, but the translation preview workflow is now local and explicit.
Mail flow
Build the alias and preview the translated copy before sending
What stays the same
Place the alias in the Cc: field. The mail host can still use that alias pattern for translated delivery workflows.
- Alias format:
source_target@t-mail.com - Right panel shows the exact alias and a translated draft preview
- The translation preview is local to this container and no longer depends on the broken legacy host
T-Text
Translate pasted text locally through the rebuilt T-Mail container
What changed
This request now stays inside the T-Mail container. The result page on the right is generated locally and uses Google Translate API wiring instead of the old CGI endpoint.
T-Sail
Translate a live web page locally instead of relying on the retired Babelfish path
What changed
The right panel now loads a page fetched and translated by this container. It no longer proxies the original T-Sail host or the broken Babelfish-era flow.
Mail access
Mailbox access stays on the mail host
Inbound mail host
Host: mail.medfetch.com
IMAP: 993 with TLS
SMTP: 465 SSL or 587 STARTTLS
Translation path
The translation tools no longer point at the old public T-Mail host. This container now owns text and web translation requests directly.
Mail rules
The historical delivery chain still depended on .forward, procmail, and generated helpers on the mail server. That remains operational reference until the mail-side pipeline is rebuilt to call the local translator explicitly.
FAQ
What the rebuilt service does now
Can I still use a Cc alias?
Yes. The alias pattern is preserved and shown in the preview panel. The rebuilt UI also lets you preview the translated draft before you send it.
Does T-Text still depend on the legacy CGI host?
No. T-Text now runs through the local container and is intended to use Google Translate API credentials attached to this deployment.
What happened to T-Sail?
The old Babelfish proxy path was effectively dead. T-Sail now fetches the page locally and translates visible content inside this container.
What still needs mail-side work?
The mailbox delivery chain is still separate from the web container. The public service now has a local translator, but the mailserver rules still need a later bridge if you want end-to-end automatic translated forwarding again.
Privacy
Privacy posture for the rebuilt container
This front end no longer forwards tool requests to the old public T-Mail host. Translation calls are intended to stay inside this container and go directly to your configured Google API credential.
Mailbox storage and message routing still live on the separate mail host. Until that path is rebuilt too, treat the mail-rule notes here as operational reference rather than a full in-container mail pipeline.