New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS Policy & Send Only #464
Comments
That's a nice howto - I'm too ignorant to know if there's a demand for the feature from anyone else - I just have a system wide TLS policy. |
I think this could very interesting, if it allows to have a default policy and exceptions from that. I'd most definitely have a use case for that. |
if you're deferring the TLS parameters to an SQL query, then it'd be fairly easy to use an SQL union to apply a system wide default if there's nothing else specified - e.g.
|
you are very right right, but unfortunately we'd need an additional select wrapper around that union in order to be able to apply an ORDER BY 'id' BEFORE the LIMIT 1. We can not be sure in which order the 2 parts of the union are executed, so the default rule might be returned first and the specific rule would be "limited away"
|
Yes, i had wondered if an ORDER BY would be needed; TIL etc :-) |
I came across an article on the internet describing a functionality of postfix that seemed interesting to me
https://gist.github.com/ibqn/22b9c1726dae656f295a9060fb758d15
there is a TLS Policy field per domain, the question is this interesting to integrate in PostfixAdmin if so then I want to try to realize this. If there is no interest in generating it, I would like to know how I can make an extra function that you can continue to use even though PostfixAdmin is further expanded without this functionality.
Another function that I would be interested in is to add a field to the mailbox to indicate whether, for example, it is only allowed to send and is not able to receive. Is this a function that is interesting to integrate in PostfixAdmin or should this also become a separate function.
The text was updated successfully, but these errors were encountered: