专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像 官方专业版轩辕镜像 官方专业版官方专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题
其他
关于我们网站地图

官方QQ群: 1072982923

mattmckenzy/mail2gotify Docker 镜像 - 轩辕镜像

mail2gotify
mattmckenzy/mail2gotify
mattmckenzy
0 次下载
📦 一套镜像服务,解决研发 / 测试 / 生产三套环境
镜像简介版本下载
📦 一套镜像服务,解决研发 / 测试 / 生产三套环境

Mail2Gotify

Simple stand-alone service that hosts an STMP server, receives mail and redirects them to a Gotify instance.

Description

This application will let you redirect mail to your gotify instance. It can help aggregate notifications from services or systems that don't support Gotify.

Usage

Simply fill up the necessary configuration variables, host the service and expose the configured port.

TLS 1.2 or 1.3 is mandatory and Mail2Gotify will need a certificate to function. You can choose to point the "CertLocation" variable to a valid PEM or PKCS7 certificate, or leave it empty to have Mail2Gotify cerate a self-signed one. Keep in mind, however, that self-signed certificates might not be accepted by certain applications, such as pfSense's notifications service. For PEM certificate types, it can also support encrypted or seperate key file certificates if the configuration is properly filled out.

Create a Gotify Application if necessary and point your email notifier to the host and port, using the Gotify App name as the authentication user and the Gotify App token as the authentication password. You can also append a dash and priority number to the application name, i.e. "pfSense-6", to change the priority level of the Gotify notification. Default priority is 5.

Configuration

Configuring the service is done either the appsettings.json found at "/Mail2Gotify", or with associated environment variables (great for docker). Here's a list and small description of available configuration variables:

VariableDefaultDescription
Logging:LogLevel:DefaultDebugDefault .NET logging level.
Logging:LogLevel:MicrosoftWarningDefault .NET Microsoft logging level.
Logging:LogLevel:Microsoft.Hosting.LifetimeInformationDefault .NET Microsoft Hosting logging level.
Services:Gotify:ServiceUriGotify's service uri.
Services:Gotify:HeaderX-Gotify-KeyGotify's authentication header to use (the default is typically correct).
Services:Mail2Gotify:HostAddressThe address on which this service resides.
Services:Mail2Gotify:HostPort587The port that this service will use to receive mail through SMTP.
Services:Mail2Gotify:CacheDirectoryThe directory to use for persistent caaching (bind with docker for permanency).
Services:Mail2Gotify:CertLocationThe location for the certificate used for TLS encryption. If left empty, Mail2Gotify will create a self-signed certificate using the "Services:Certificate:Name" and "Services:Certificate:Password" variables shown below.
Services:Mail2Gotify:KeyLocationThe location of the PEM key file certificate used for TLS encryption. Only used when CertType is "PEM".
Services:Mail2Gotify:CertPasswordThe password of the PEM file if it is encrypted. Only used when CertType is "PEM".
Services:Mail2Gotify:CertTypePEMThe type pf certificate used for TLS encryption. Either "PEM" or "PKCS7".
Services:SelfSignedCertificate:NameMail2GotifyThe name used for the creation of the self-signed certificate used for the SMTP server's TLS encryption.
Services:SelfSignedCertificate:PasswordThe password used for the creation of the self-signed certificate.

Docker

Here's how I configure my installation :

docker-compose.yaml
yaml
version: "3"

volumes:
  cache:

services:
  mail2gotify:
    container_name: mail2gotify
    environment:
      - Services:Mail2Gotify:HostAddress=localhost
      - Services:Mail2Gotify:CacheDirectory=/cache
      - Services:Mail2Gotify:CertLocation=/certs/exampledomain.crt    
      - Services:Mail2Gotify:KeyLocation=/certs/exampledomain.key     
      - Services:Gotify:ServiceUri=[***]
      - TZ=America/Toronto
    image: mattmckenzy/mail2gotify:latest
    volumes:
      - cache:/cache
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - /mnt/docker/storage/volumes/nginx_data/_data/keys:/certs
    restart: always
    ports:
      - "587:587"
    network_mode: "host"

Release Notes

1.1.4
  • Added configuration options to support new certificate types.

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

登录仓库拉取

通过 Docker 登录认证访问私有仓库

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

Docker Compose

Docker Compose 项目配置

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

MacOS OrbStack

MacOS OrbStack 容器配置

宝塔面板

在宝塔面板一键配置镜像

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

极空间

极空间 NAS 系统配置服务

爱快路由

爱快 iKuai 路由系统配置

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

专属域名拉取

无需登录使用专属域名

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

轩辕镜像免费版与专业版有什么区别?

免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。

轩辕镜像支持哪些镜像仓库?

专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。

流量耗尽错误提示

当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。

410 错误问题

通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。

manifest unknown 错误

先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。

镜像拉取成功后,如何去掉轩辕镜像域名前缀?

使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
mattmckenzy/mail2gotify
官方博客Docker 镜像使用技巧与技术博客
热门镜像查看热门 Docker 镜像推荐
一键安装一键安装 Docker 并配置镜像源
咨询镜像拉取问题请 提交工单,官方技术交流群:1072982923
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
咨询镜像拉取问题请提交工单,官方技术交流群:
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
官方邮箱:点击复制邮箱
©2024-2026 源码跳动
官方邮箱:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.