meshStack

meshStack

  • User Docs
  • Administrator Docs
  • API Docs
  • Release Notes
  • Feedback

›Operations

Getting Started

  • How to get started with meshStack
  • AWS S3 Quickstart Guide
  • AKS Platform Quickstart Guide
  • AKS Developer Platform Guide

Concepts

  • Overview
  • Administration Roles
  • Onboarding
  • meshWorkspaces
  • meshProjects
  • meshTenants
  • Replication Configuration
  • Delete Tenants
  • meshUsers
  • meshPlatforms
  • Landing Zones
  • Open Service Brokers (OSB)
  • Guide: Emergency Users
  • Managing Tags
  • Policies
  • Unmanaged Tenants
  • meshStack Settings
  • Workspace Services
  • API Users
  • DNS and SSL Certificates
  • Customizing
  • Product Feedback Collection

Identity & Access

  • Identity and Access Management
  • Identity Provider
  • Identity Lookup
  • Authorization
  • User & Group LDAP Synchronisation
  • User & Group SCIM Synchronisation

Building Blocks

  • Building Blocks
  • Private Runners
  • Terraform/OpenTofu state managed by meshStack
  • Permission Delegation on AWS
  • Connecting meshStack and a Pipeline

Metering & Billing

  • Cost Management
  • Configuration

Amazon Web Services

  • Integration
  • Landing Zones
  • Metering
  • SSO Setup
  • Reserved Instances & Savings Plans Guide

Microsoft Azure

  • Integration
  • Landing Zones
  • Metering

Google Cloud Platform

  • Integration
  • Landing Zones
  • Metering

Cloud Foundry

  • Integration
  • Metering

Kubernetes

  • Integration
  • Landing Zones
  • Metering

GitHub

  • Pipeline Automation
  • Repository Provisioning

OpenShift

  • Integration
  • Landing Zones
  • Metering

OpenStack

  • Integration
  • Metering

OSB Services

  • Integration
  • Metering
  • meshcloud OSB API Profile
  • Tenant Services
  • Tutorial: Implement a Broker

Operations

  • Managed Service
  • Email
  • Logging & Auditing
  • Monitoring & Telemetry
  • Backup
  • Security FAQ

Guides

  • How to integrate a meshPlatform into meshStack
  • How to manually integrate AWS as meshPlatform
  • How to manually integrate Azure as meshPlatform
  • How to manually integrate GCP as meshPlatform
  • How to create your own platform
  • How to manage partner level permissions
  • How to use scoped API keys
  • How to setup and manage a Building block
Edit

Email

For all email based communication (e.g. for workspace registration or workspace user invitations) meshStack will use the configured SMTP server.

Tip for enterprise meshStacks: you can configure a custom e-mail footer by creating an object in the messages configuration below using mapKey mail.footer. Any valid HTML can be set as a value here. Contact your customer success team to get it set up.

The following configuration options are available at mesh.meshfed.mail:

Dhall Type
{-
The configured smtp mail server is used by meshfed to
send out notifications.

enabled:
If True, meshfed will send out mails.

username:
Username meshfed uses to log in at SMTP server.

password:
Password meshfed uses to log in at SMTP server.

host:
SMTP server address that meshfed connects to.

port:
The port that the SMTP server listens on.

sender:
address:
Address that is shown as "sender"
reply-to:
Address that is shown as "replyTo"

smtp:
ssl:
If True, enables SSL encryption (must be supported by SMTP server)

starttls:
If True, enables STARTTLS encryption (must be supported by SMTP server)

auth:
If True, enables authentication (must be supported by SMTP server)

theme:
logo:
href:
Location of the logo file

url:
Url that the image links to

button-color:
Color hex code for buttons

messages:
List of mappings to configure template messages

-}

{ enabled : Bool
, username : Text
, host : Text
, port : Natural
, sender : { address : Text, reply-to : Optional Text }
, smtp :
{ ssl : { enable : Bool }, starttls : { enable : Bool }, auth : Bool }
, theme : { logo : { href : Text, url : Text }, button-color : Text }
, messages : List { mapKey : Text, mapValue : Text }
}

FAQ

Which mails is meshStack sending out and to whom?

Application Team receive mails when

  • Workspace created
  • Workspace permissions created, updated or removed
  • Project permissions created, updated or removed
  • Project Payment Method Assignment missing
  • Budget exceeded
  • Executing Building Block succeeded

Platform Operators receive mails when

  • Building Block requires input (Recipients are defined per Building Block definition)

Optionally meshStack sends out mails to fixed set of recipients configured in dhall when

  • Tenant marked for deletion
  • Tenant created
  • Replication failed

Can the style of the mails be influenced? For example via HTML?

Button color and logo are configurable. The theme.messages templates support HTML elements like <br>.

Can BCC be added

No. meshStack does not support adding addresses on BCC.

Last updated on 4/16/2024
← Managed ServiceLogging & Auditing →
  • FAQ
    • Which mails is meshStack sending out and to whom?
    • Can the style of the mails be influenced? For example via HTML?
    • Can BCC be added
meshStack
Docs
User DocumentationAdministrator DocumentationSecurity FAQ
Get in Touch
SupportWebsiteLinkedIn
More
Release NotesGitHub
Copyright © 2025 meshcloud GmbH