[enhancement]: Allow infinite number of DKIM keys about mail-server HOT 12 CLOSED

As Williamdes recommend making possible to lookup DKIM key in a database made easier and flexible the process to generate, manage, etc. LDAP and MYSQL could be a good solution.

from mail-server.

Hi,

Is it possible in mail-server to store DKIM information using the CLI as in early versions of smtp-server?

Sincerely Maykel

from mail-server.

This has been implemented in v0.7.0.

from mail-server.

you know very well your email system and we only know up to the limits of your documentation wish is very short, there are not forums, communities or anything else commenting on this, what left us struggling trying to implement this newly solution. I have being expecting for months and improvement in the documentation but no luck. You could create the best tool but if people does not know how to use it it become useless

That seems a bit harsh. There is discussions here on Github and Discord, both of which @mdecimus is very active in. You can also browse the source code to see how things work. In comparison to many other projects the documentation here is fantastic and I can tell that a lot of time has been spent on it which is an often overlooked skill.

from mail-server.

Not currently but this feature will be re-introduced once the web admin is developed.

from mail-server.

Amazing job with the web interface.
One question I cant find out how could these be implemented from the web interface in order to pull the signature from a DB like LDAP or Mysql as williamdes suggested for a multidomain environment. for authentication and storage it is really easy to create a db other than the internal one but for DKIM similar options does not exist.
Sincerely Maykel

from mail-server.

Signatures can be retrieved from local files or environment variables but not from a custom database. If you want to retrieve the keys from an external source make sure these settings are defined as local keys.

from mail-server.

If you want to retrieve the keys from an external source make sure these settings are defined as local keys.

do you have an example of this that you could share? or at least it it possible in this last version of mail-server store DKIM information in rustDB using the CLI as in early versions of smtp-server?

Sincerely Maykel

from mail-server.

do you have an example of this that you could share?

Here is the documentation that explains how to define a key as local.

or at least it it possible in this last version of mail-server store DKIM information in rustDB using the CLI as in early versions of smtp-server?

DKIM keys are stored in the database by default. However they are stored in the internal databases and it is not possible to retrieve them from a user defined table.

from mail-server.

If you want to retrieve the keys from an external source make sure these settings are defined as local keys.

This doesn't make sense my question was looking for flexibility and accessibility no how to manually continuing hardcoding dynamic values in the config file every time it is need it.
In the stalwart documentation it talk about dkim multidomain but again it show that values has to be manually created in the config file. In another topic in the documentation you mention that

Stalwart Mail Server supports storing configuration settings in any of the supported [data stores]. This is particularly useful in distributed environments

again doesn't make sense. how a distributed environment will be able to access variables or keys only defined in a local file?

from mail-server.

This doesn't make sense my question was looking for flexibility and accessibility no how to manually continuing hardcoding dynamic values in the config file every time it is need it.

Not needed, use * if you want to make all keys local or keyname.* to make only some of your keys local.

how a distributed environment will be able to access variables or keys only defined in a local file?

They don't, a distributed database such as FoundationDB is used to store the shared configuration.

from mail-server.

you know very well your email system and we only know up to the limits of your documentation wish is very short, there are not forums, communities or anything else commenting on this, what left us struggling trying to implement this newly solution. I have being expecting for months and improvement in the documentation but no luck. You could create the best tool but if people does not know how to use it it become useless

from mail-server.