The smtps_port option was added in #2268 / #2269. However the option was not documented because use of STMPS was not encouraged, and STARTTLS was the way to go.

However RFC 8314 now recommends STMPS over STARTTLS (#2522). We should document:

• that setting listen to the special port 465 creates an SMTPS server instead of a regular one.
• that the above 'special port' can be changed

Is it possible to run this in one (or more) Docker containers? I'd really like to know.

I suppose I could try to write a docker-compose file but my knowledge of Docker, networking, email standards, etc are not up to the task. So I'd feel more comfortable if someone more knowledgeable could pick up this task.

I had a lovely experience installing this via Docker. Kudos.

However, when I got to http://localhost:3000/ I only see a sign in button. I can't figure out how to sign up to the system.

I've tried http://localhost:3000/admins/sign_up but it redirects to /sign_in

Is their any other documentation that explains the sign up process?

Also, I'm very interested in using this to send mail in my

If one were to compile the qmail code with -Wall -Werror, the following error is produced:

./compile tcpto.c
tcpto.c: In function ‘tcpto_err’:
tcpto.c:139:34: error: ‘firstwhen’ may be used uninitialized in this
function [-Werror=maybe-uninitialized]
      if ((firstpos < 0) || (when < firstwhen))
                            ~~~~~~^~~~~~~~~~~~

Is there a conditio

The documentation steps are simple:

$ docker-compose stop
$ docker-compose rm
$ docker pull maxking/mailman-core:$tag
$ docker pull maxking/mailman-web:$tag
$ docker-compose up -d

Make sure that you use the appropriate -f docker-compose.yaml file in all the above commands.

To provide an easier way to install the cloud MTA build tool on MacOS or Linux machines it would be nice to have an own Homebrew Tap containing a formula for Homebrew (Package Manager for MacOS & Linux).

SAP has already provided such a Tap for SapMachine.

To help myself I created a Tap containing the mbt here: https://gith

• Create a documentation for the library at https://midi-smtp-server.readthedocs.io/
• Write more examples
• Write more documentation
• Cookbook example for Rocket.Chat
• SMTP Agent for https://github.com/huginn/huginn

For now comment out them

https://github.com/milter-manager/milter-manager/blob/master/doc/reference/milter-manager-docs.sgml#L61-L84

Errors like following:

../xml/milter-client-context.xml:177: parser error : error parsing attribute name
: ((<xxfi_negotiate|URL:https://www.milter.org/developers/api/xxfi_negotiate>))
                   ^

This is RD in gtk-doc style comment.
We should co

It'd be nice to see dead bodies be present in the server longer than normal. My idea was to keep the dead bodies present for a total of 3 IRL days, before they "decompose" and are removed from the server. This, however, should have an option for server owners to modify how long dead bodies should be on the server before being removed, as a technique to reduce some server lag.

Thoughts?

It seems that all web apps in https://github.com/SAP-samples/cf-mta-examples/tree/master/content-deployment/content specify destinations in the xs-app.json file. If these destinations are not set up, the webapps cannot be used as the approuter will throw an exception.

So the sample is ok if it should only be used to demonstrate the cf deploy ./ but it's not suited to show how to use the h