Docker-MailServer | ONLYOFFICE Mail Server is a full-featured mail server | Email library
kandi X-RAY | Docker-MailServer Summary
kandi X-RAY | Docker-MailServer Summary
ONLYOFFICE Mail Server is a full-featured mail server solution developed on the base of the iRedMail package, containing the following components: Postfix, Dovecot, SpamAssassin, ClamAV, OpenDKIM, Fail2ban.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Docker-MailServer
Docker-MailServer Key Features
Docker-MailServer Examples and Code Snippets
Lines of Code : 42License : Non-SPDX (NOASSERTION)
Copydocker network create --driver bridge onlyoffice
sudo docker run --net onlyoffice -i -t -d --restart=always --name onlyoffice-document-server \
-v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice \
-v /app/onlyoffice/DocumentServer/data:/v echo "[mysqld]
sql_mode = 'NO_ENGINE_SUBSTITUTION'
max_connections = 1000
max_allowed_packet = 1048576000" > /app/onlyoffice/mysql/conf.d/onlyoffice.cnf
echo "CREATE USER 'onlyoffice_user'@'localhost' IDENTIFIED BY 'onlyoffice_pass';
CREATE USER sudo mkdir -p "/app/onlyoffice/mysql/conf.d";
sudo mkdir -p "/app/onlyoffice/mysql/data";
sudo mkdir -p "/app/onlyoffice/mysql/initdb";
sudo mkdir -p "/app/onlyoffice/CommunityServer/data";
sudo mkdir -p "/app/onlyoffice/CommunityServer/logs";
sudo Community Discussions
Trending Discussions on Docker-MailServer
QUESTION
I am migrating a tvial docker mail server from one system to another. I set this up some time ago, and vaguely remember the steps, but not every detail. I copied my mail data and mail state volumes to the new system, but when I went to run docker on the new system I was confused. The old system shows this in docker compose:
...ANSWER
Answered 2020-Jul-26 at 08:40The resources are prefixed with the project(deployment) name.
This can be specified using the -p flag when you run the docker-compose up command. If not specified, the project name defaults to the name of the directory to whom your docker-compose.yaml file belongs to.
Official documentation here: https://docs.docker.com/compose/reference/envvars/#compose_project_name . Relevant extract for the question:
COMPOSE_PROJECT_NAME:
Sets the project name. This value is prepended along with the service name to the container on start up. For example, if your project name is myapp and it includes two services db and web, then Compose starts containers named myapp_db_1 and myapp_web_1 respectively.
QUESTION
I understand that there are several options to choose from when using an e-mail server. E.g. 25 and 587 for opt-in encryption and 465 for enforced encryption.
docker-mailserver, a popular docker mailserver container describes ports 587, 465, 143 and 993 specifically as submission and retrieval ports.
The actual server to server communication is apparently established using port 25 on both sides.
Is this a common implementation?
My understanding until now was, that the actual communication (for outgoing emails) is done over port 587 or 465.
Encouraged by the exposed-port explanation of the above mentioned container I now figured that the whole retrival, submission and transfer process works (extremely simplified) like this:
Use port 25,465 or 587 to send email from client to transmitting mailserver.
The transmitting mailserver sends the email over port 25 to the recipients mailserver.
The recipient then receives the email on port 143 or 993 from his/her mailserver (assumed IMAP/s is used) and shows it accordingly in his/her mail client.
Is this correct? If so, is it even possible to send emails from a mailserver whose ISP blocked port 25 that users of common mail services like GMail, Yahoo etc. can receive?
...ANSWER
Answered 2020-May-03 at 19:51This is more of a network administration question, than a programming question, so may be considered off topic. That being said:
The SMTP protocol is used for two different, but similar purposes: Message Submission, and Message Transission.
Message Submission is done by an MSA, Message Submission Agent, generally on behalf of an end user, but perhaps on perhaps of a script or process. Traditionally, these are clients like Thunderbird, Apple Mail, or the email client on your phone. In modern practice, this is generally done authenticated (with user credentials) and encrypted on ports 465 or 587.
- Port 465,
SMTPS(smtp-secure, by analogy with https) is technically deprecated, but widely used. It is used for SMTP over TLS, where the encryption is encrypted from connection until termination. - Port 587,
submissionis generally used withSTARTTLS, where the connection is first made unencrypted, but upgraded shortly thereafter using a special command.
Both these ports generally accept mail from a user with credentials, for any destination, and will hold and relay these for the user. For example, if you connect to smtp.gmail.com on port 465 or 587, and authenticate as user@gmail.com, it will allow you to submit email for anyone, as long as it is from user@gmail.com.
Message Transmission is done by an MTA, Message Transmission Agent, generally on behalf of all the users of a site or service. Relaying is done between sites on port 25, with opt-in STARTTLS encryption. Authentication is not generally done, but there is a complicated system of reputation tracking, firewalls, and blacklists generally used behind the scenes. Usually only mail for a specific site is accepted on this port. For example, if you connect to one of gmail.com's MX servers (for example, gmail-smtp-in.l.google.com as of this writing) on port 25, and it thinks you are a trustworthy IP, it will accept mail from anyone to any gmail address (subject to further scanning). It will refuse to relay to anyone offsite.
Message Retrieval is generally done by IMAP on ports 143 (with STARTTLS) or 993 (with TLS from connection). This is a pull service used by an end-user (generally) to retrieve emails being held by an MTA on their behalf. POP3 is also used (on 110 and 995) by some sites, but it is a much less capable protocol.
Traditionally, submission and transmission were both done on port 25 without authentication, but that's a no go on the modern internet. It was split into transmission and submission so network resources could be better controlled. As you may have discovered, many ISPs and cloud services restrict port 25 so end-users cannot act as transmitters without their consent, and so relaying happens either through their servers or some other service that will take responsibility.
This, through this model, gmail users can generally only submit via gmail's submission server, and other users must submit through their services server, and spammers can't just set up a server anywhere to transmit messages to gmail. If they do and their ISP hasn't firewalled it, their reputation will shortly be trashed and be placed on many blacklists.
Additionally, a lot of this doesn't even happen over the traditional protocols anymore. If you use Google services and clients, you will likely be using a custom protocol tunneled over HTTPS, or the public GMAIL REST protocol. If you're using Microsoft, they have no less than 3 email protocols: Exchange ActiveSync, Exchange Web Services, and Microsoft Graph/Outlook MAIL Rest API, all using HTTPS.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Docker-MailServer
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
