pmcenter

A telegram bot helping you process private messages.

Documentation Language

• English

• 简体中文

Table of Contents

• 🌲 Branches
• 🔨 Features
• 📻 Setting Up Your Own pmcenter
  • ⚙️ Prerequisites
  • 📥 Build pmcenter Yourself
  • 📩 Use Pre-compiled Binaries
  • ✅ ReadyToRun Version
  • 🐋 Use Docker
• 🔧 Configuring
  • ⚒️ pmcenter Settings
    • 📄 Note
    • ⛵ Changing File Location
• 🚀 Starting
• 🔩 Commands
• ❔ FAQ
• 🔺 Disclaimer

Branches

Currently, there're 2 branches:

• pmcenter-lazer: the freshest code with latest features, like Chrome Canary. However, stability is NOT guaranteed.
• master: stable branch. The pmcenter-lazer branch will be merged into it once it's ready for an update.

Features

• 🚉 Cross-platform support from Windows to Linux and Raspian
• 🛡️ High stability and availability
• 📡 SOCKS5 proxy support
• 🚧 Powerful anti-spamming system
  • 💬 Multiple filtering modes
    • 🔣 Regular expression mode
    • 🔠 Full word matching mode
  • 👤 Blocking by User ID
  • 🔄 Automatic blocking by message count
  • ☑️ Support for manual blocking
• 📺 Daily maintenance, all on Telegram
  • 📥 Automatic updates
    • 🕑 Optional auto update check
    • ➡️ Manual update check
  • 🔄 Restarting bot
  • 🌐 Switching languages
  • 🗃 Reading/Writing configurations
  • 💻 Getting system status
• ℹ️ Real message source display
• 🆔 Support the new privacy mode introduced in Telegram 5.5.0
• ... and more!

Setting Up Your Own pmcenter

The following content will guide you through the installation process.

Prerequisites

• Microsoft .NET Core 3.1 (Runtime / SDK, see instructions below)
• Git (optional, see instructions below)
• Yes! You can also use Docker to run pmcenter.

Refer to Microsoft for installation guides.

Many Linux distributions have .NET Core SDK available as a package.

Don't worry if your distribution doesn't have a package handy, you can still download binaries or use pmcenter R2R version.

Build pmcenter Yourself

You need to install .NET Core SDK to finish this.

Run this script to clone, build and initiate your own pmcenter:

git clone https://github.com/Elepover/pmcenter.git --depth=1
cd pmcenter/pmcenter
dotnet restore
dotnet publish -c Release
cp -R bin/Release/netcoreapp3.1/publish ../
cd .. && mv publish build
cd build
dotnet pmcenter.dll

You can also use ./pmcenter (macOS & Linux) or .\pmcenter.exe to launch pmcenter.

Add --setup option when launching pmcenter to launch setup wizard.

The compiled binaries will be put in the pmcenter/build folder in your working directory.

Use Pre-compiled Binaries

Only .NET Core Runtime is required in this step.

Run this script to download and initiate your own pmcenter:

mkdir pmcenter
cd pmcenter
wget https://ci.appveyor.com/api/projects/Elepover/pmcenter/artifacts/pmcenter.zip
unzip pmcenter.zip
dotnet pmcenter.dll

ReadyToRun Version

It's another kind of pre-compiled binary bundle, except you will need: exactly NOTHING additional.

Plus, Ahead-of-Time compilation is enabled, so do expect some performance increase using this edition.

Drawback: automatic updates are NOT available.. yet. It'll be available later.

For some Linux distributions, you may need some extra libraries installed, check out this Microsoft documentation for more info.

Steps:

• Download the correct version here according to your OS and its architecture
• Extract it
• Run ./pmcenter (macOS & Linux) or .\pmcenter.exe (Windows) and you're good to go!

Use Docker

The following snippet will help you download sample configurations for the pmcenter in docker to use.

For pmcenter-lazer, use the elep0ver/pmcenter:lazer image

For pmcenter-lazer, use the elep0ver/pmcenter:lazer image

wget https://raw.githubusercontent.com/Elepover/pmcenter/master/pmcenter.json
vim pmcenter.json # Edit the configurations (APIKey and OwnerID are required)
docker run -d -v $(pwd)/pmcenter.json:/opt/pmcenter/pmcenter.json --restart always elep0ver/pmcenter

Configuring

During the first run, pmcenter will automatically generate the pmcenter.json and pmcenter_locale.json file for you. Change the settings to set up.

Or, use setup wizard:

dotnet pmcenter.dll --setup

Note: Running pmcenter with root privileges is STRONGLY UNRECOMMENDED. We recommend you run pmcenter as a regular user.

pmcenter Settings

Proxy Configuration

Tip: After upgrades, you can send /saveconf command to the bot to fix missing new settings.

Note

• The variables like $1 in the Message_ReplySuccessful and other keys could be safely deleted, if you like.
• Emojis are supported, and were used by default.
• Currently the response of the /info command is unchangeable.
• Familiar with another language? Pull requests are welcome!
• Please think twice before turning on EnableMsgLink, it makes it possible for you to reply to messages that are forwarded anonymously or from channels, however, it will cost more and more of your storage space and memory as the storage grows and makes it slower for pmcenter to process configuration files.
• Now Message Links play an important role in pmcenter's basic functions. Turning it off is NOT recommended.

Changing File Location

On version 1.5.85.174 and later, pmcenter will check these two following environment variables on startup:

pmcenter_conf: pmcenter's configurations file's location.
pmcenter_lang: pmcenter's language file's location.

On these 3 scenarios, pmcenter will still use default location:

• The environment variable doesn't exist.
• The environment variable cannot be accessed.
• File not found.

Starting

After all these, you can start your own pmcenter safely by using this command:

dotnet pmcenter.dll

You can also use ./pmcenter (macOS & Linux) or .\pmcenter.exe to launch pmcenter if you compiled it yourself or chose R2R version.

You can write a systemd service to keep it running, even after the host machine's rebooting.

Commands

Please note: /restart command only works with a daemon that auto-restarts pmcenter when it exits. pmcenter cannot restart by itself.

Known Problems

OpenSSL Compatibility Problem

This problem only occurs on Linux, and will not occur on Windows.

When using older versions (earlier than PR #34443 (14 Feb, 2019)) of .NET Core 2.1, which is incompatible with OpenSSL 1.1+, pmcenter will throw the following exception:

System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. 
---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. 
---> System.TypeInitializationException: The type initializer for 'SslMethods' threw an exception. 
---> System.TypeInitializationException: The type initializer for 'Ssl' threw an exception. 
---> System.TypeInitializationException: The type initializer for 'SslInitializer' threw an exception. 
---> Interop+Crypto+OpenSslCryptographicException: error:0E076071:configuration file routines:MODULE_RUN:unknown module name

As is mentioned in issue #33179, there're several workarounds:

1. Find openssl.cnf and comment out the ssl_conf = ssl_sect line.
2. Upgrade to a newer (later than #34443) .NET Core 2.1 runtime.
3. Install OpenSSL 1.0.

FAQ

Why cannot I reply to anonymously forwarded messages?

Please enable the EnableMsgLink option in pmcenter's configurations file. Only messages forwarded when EnableMsgLink option is turned on can be replied.

You can NOT reply to the messages that were forwarded when EnableMsgLink option was disabled since their corresponding message links were missing.

For more information, refer to the configurations part.

Why pmcenter.json is too large?

Maybe your pmcenter instance has saved too many Message Links, try this following command:

/clearmessagelinks

Why pmcenter didn't restart when I use the /restart command?

The /restart command requires a daemon process or service manager (like systemd in some Linux distros), it cannot be restarted by itself. Check your system's configurations.

We also have a sample systemd service for you here.

Disclaimer

The program is licensed under Apache License (Version 2.0. Dependencies are licensed under MIT License) and comes with ABSOLUTELY NO WARRANTY. By using the program in any way, you acknowledge and confirm that the developer of the program is NOT RESPONSIBLE for service outage, data loss or any other rare unlisted incident caused by the program or any of its related code.