bug report: postconf: fatal: -P option requires service_name[/type[/parameter]] about docker-mailserver HOT 8 CLOSED

But what I mean is that I don't know how "bad it can affect the data", in a way that I would notice only months later, for example.

It should only affect /etc/postfix/master.cf config. When you down + up that will get recreated again. So since you noticed it and quickly resolved it by recreating the container without the error present anymore there shouldn't be any issues going forward.

That file is configuration for routing mail delivery (ports 25, 465, 587), anti-virus milter, etc. Basically "I've got a connection, what should I do?", so your service should only have been temporarily affected with connections during that time.

possibly if you have a postfix-master.cf

There is an empty postfix-master.cf in my ./config mount, that DMS seems to at least touch it (leaving it empty, but updating the date modified).

That's odd, it should not be creating that file, but it doesn't expect it to be empty either if it was already there 😅

Presumably something in the logic there triggered it to read a line without proper content calling postconf -P.

I don't see why it'd affect the modified timestamp of the file though. If your filesystem updates atime, that'd happen from a read.

Only way a write should be happening AFAIK is if you mounted directly to /etc/postfix/master.cf which would be bad.

from docker-mailserver.

There is an empty postfix-master.cf in my ./config mount,

If it's empty and you are not using it, get rid of it 👍

from docker-mailserver.

Thank you for your replies.

I've deleted the postfix-master.cf file in the config folder, recreated the container, and so far so good.
The file wasn't recreated there.
And no error log.

from docker-mailserver.

Please note that this response was created using generative AI, leveraging previously available information from the repository. This information may be helpful. However, it is our strong recommendation that you carefully consider the information before blindly applying it.

This response is generated only once - you will not be able to interact with the glime-ai.

El error que estás viendo en los registros, postconf: fatal: -P option requires service_name[/type[/parameter]], indica que hay un problema con la configuración de Postfix en tu archivo postfix-main.cf o postfix-master.cf. Este error ocurre cuando la opción -P de postconf no se usa correctamente.

Para resolver este problema, asegúrate de que todas las líneas en tu archivo postfix-master.cf sigan el formato correcto: <service_name>/<type>/<parameter>. Aquí hay algunos pasos que puedes seguir para depurar y corregir este problema:

1. Revisa tu archivo postfix-master.cf:

   • Asegúrate de que cada línea siga el formato correcto. Por ejemplo:

     submission/inet/smtpd_reject_unlisted_recipient=no
     

2. Verifica el archivo user-patches.sh:

   • Si estás utilizando un script user-patches.sh para aplicar configuraciones personalizadas, asegúrate de que las líneas que usan postconf -P también sigan el formato correcto.

3. Ejecuta postconf -Mf:

   • Dentro del contenedor, ejecuta postconf -Mf sin argumentos para ver las opciones activas de master.cf. Esto puede ayudarte a identificar cualquier configuración incorrecta.

4. Aumenta la verbosidad de los registros:

   • Configura la variable de entorno LOG_LEVEL a debug o trace para obtener más detalles en los registros. Esto puede proporcionar más información sobre dónde está ocurriendo el problema.

Aquí tienes un ejemplo de cómo debería verse una configuración correcta en postfix-master.cf:

# adjust the submission "reject_unlisted_recipient" option
submission/inet/smtpd_reject_unlisted_recipient=no

Si necesitas más ayuda, puedes consultar la documentación de depuración de Docker Mailserver aquí.

This comment was generated by Glime.

from docker-mailserver.

I updated this:

smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks

(although I don't think this would have fixed it)

Then I restarted the container:

docker compose down mailserver && docker compose up -d

And the error didn't appear this time.

from docker-mailserver.

Just upgraded now the other machine I have (using down and up -d too), already with the updated smtpd_sender_restrictions as per my last message.

The error appeared too:

postconf: fatal: -P option requires service_name[/type[/parameter]]

Then I recreated the container again, and the error didn't appear.

Not sure why this happens on the very first run, on the upgrade, and how bad it is that this happens.

from docker-mailserver.

The error is related to /etc/postfix/master.cf, possibly if you have a postfix-master.cf, or we may internally use it to configure some changes during startup.

It could also be triggered by user-patches.sh if using the postconf method.

Not sure why this happens on the very first run, on the upgrade, and how bad it is that this happens.

Was the down before the upgrade + up?

There was quite a lot of changes with v14 release, be sure to have a backup copy of your data when upgrading to new major versions. Our tests don't always catch everything unfortunately 😓

from docker-mailserver.

Was the down before the upgrade + up?

Yep - I mentioned that several times in my messages above :)

be sure to have a backup copy of your data when upgrading to new major versions

Yeah, I do.
But what I mean is that I don't know how "bad it can affect the data", in a way that I would notice only months later, for example.

possibly if you have a postfix-master.cf

There is an empty postfix-master.cf in my ./config mount, that DMS seems to at least touch it (leaving it empty, but updating the date modified).

from docker-mailserver.