You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which feature or improvement would you like to request?
I'd like to see this feature: It would be great to be possible to store different keys in different in-memory store.
Currently, only one in-memory store can be used. However, out of all the keys to be stored in the in-memory store, the two BAYES spam filter related keys need to be configured differently (e.g., in terms of persistence) than other keys. Therefore, it would be very handy if Stalwart supports the use of two in-memory stores at the same time, so that the two BAYES keys can be stored in a separate Redis instance or even another type of in-memory store.
Is your feature request related to a problem?
I'm having a problem with...
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Har-Kuun
changed the title
🚀: Store different keys in different in-memory stores
Store different keys in different in-memory stores
Jan 24, 2025
Har-Kuun
changed the title
Store different keys in different in-memory stores
[enhancement]: Store different keys in different in-memory stores
Jan 24, 2025
Which feature or improvement would you like to request?
I'd like to see this feature: It would be great to be possible to store different keys in different in-memory store.
Currently, only one in-memory store can be used. However, out of all the keys to be stored in the in-memory store, the two BAYES spam filter related keys need to be configured differently (e.g., in terms of persistence) than other keys. Therefore, it would be very handy if Stalwart supports the use of two in-memory stores at the same time, so that the two BAYES keys can be stored in a separate Redis instance or even another type of in-memory store.
Is your feature request related to a problem?
I'm having a problem with...
Code of Conduct
The text was updated successfully, but these errors were encountered: