Forwards incoming emails to Telegram users/channels based on configurable routing rules. Built with Node.js.

npm install
cp .env.example .env
# Edit .env with your settings (optional, defaults work for local testing)
npm start

• Web UI: http://127.0.0.1:3000
• SMTP server: port 2525 (configurable in .env)

1. Open Telegram and chat with @BotFather
2. Send /newbot and follow the prompts to create a bot
3. Copy the bot token (looks like 123456789:ABCdefGHIJK...)

1. Send any message to your new bot on Telegram
2. Visit in your browser: https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates
3. Look for "chat":{"id":123456789} — that number is your chat ID
4. For groups, it's a negative number like -1001234567890

Open the Web UI at http://127.0.0.1:3000:

1. Bots tab — Add your bot token (name it whatever you like)
2. Rules tab — Create a routing rule:
   • Select the bot
   • Enter the chat ID
   • Set a sender pattern (e.g., * for all email, *@yourdomain.com for a domain)
3. Settings tab — Read the full configuration reference

Point any email client or script at your server:

# Using swaks (https://jetmore.org/john/code/swaks/)
swaks --to test@localhost --from [email protected] --server 127.0.0.1:2525 --body "Hello from SMTP2TG"

If everything is configured correctly, the email appears in your Telegram chat.

• Plain SMTP (default): No TLS, no auth. Set SMTP_PORT=25 for standard. Only use on localhost or trusted networks.
• STARTTLS: Set SMTP_TLS_CERT and SMTP_TLS_KEY with SMTP_SECURE=false. Offers opportunistic TLS on port 587.
• SMTPS: Set SMTP_SECURE=true with cert and key. TLS required on connect (port 465 style).
• With Auth: Add SMTP_AUTH_USERS=user1:pass1,user2:pass2. Supports PLAIN and LOGIN auth.

Set DEFAULT_BOT_ID and DEFAULT_CHAT_ID in .env to forward all emails that don't match any explicit rule to a fallback chat. This acts as a catch-all — no rules needed. If both are set and a matching rule also exists, the email still goes to the rule destination (the wildcard only fires when zero rules match).

The server scans incoming email subjects and bodies for severity keywords and tags forwarded messages with visual indicators:

• 🔴 CRITICAL — breach, compromised, exploit, ransomware
• 🟠 HIGH — urgent, critical, alert, asap, immediate, incident
• 🟡 MEDIUM — warning, attention, notice
• 🟢 LOW — info, fyi, newsletter

Fully configurable via SEVERITY_KEYWORDS in .env. The highest-severity match wins and appears in the Telegram message header.

Rules use glob-style patterns matching against the sender's email address:

Matching is case-insensitive. All enabled matching rules fire, so a single email can be forwarded to multiple chats.

sudo bash install.sh

This installs Node.js, copies the app to /opt/smtp2telegram, installs dependencies, creates a systemd service, and starts it.

sudo bash update.sh

Copies updated files, reinstalls deps, and restarts the service.

[Unit]
Description=SMTP to Telegram
After=network.target

[Service]
Type=simple
User=nobody
WorkingDirectory=/opt/smtp2telegram
ExecStart=/usr/bin/node server.js
Restart=on-failure

[Install]
WantedBy=multi-user.target

• The web UI has no authentication by default. Set ADMIN_PASSWORD in .env if exposing it beyond localhost.
• When running without SMTP auth, bind to 127.0.0.1 only (SMTP_HOST=127.0.0.1) to prevent open relay abuse.
• Bot tokens are stored in the SQLite database. Restrict file access to the data/ directory.
• Email content passes through your server — run it on infrastructure you control.