docker-mail | Docker image with a full-fledged e | Continuous Deployment library

The 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.

This 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, submission is generally used with STARTTLS, 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.

This is because you can't access service through 127.0.0.1. If your services on the same network you will able to access it by the links directive you passed, like change your address from 127.0.0.1 to mailcatcher. If your services in different networks - you can open ports on service that you need to call and then access it by machine local ip address (not the 127.0.0.1 but by the your physical/virtual machine ip address in local network)