Skip to content
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

blocklist feature #255

Open
runout-at opened this issue May 4, 2018 · 2 comments
Open

blocklist feature #255

runout-at opened this issue May 4, 2018 · 2 comments

Comments

@runout-at
Copy link
Contributor

I just had a look into the blocklist feature and will come up with some questions/issues:

  • Is this feature really used by people?
  • It can only block full mail adresses.
  • Would it be nice to act like the local_blacklist file in Debian but per user?
  • Could it be used as White- & Blacklist?
  • The domain_id field in the blocklist table should be unnecesary (would need fix in routers).
  • The on_blocklist field in the users table seems not to be used.
@Udera
Copy link
Collaborator

Udera commented May 8, 2018

If we want this for users, this feature should be accessible via webinterface (webmail). Even in this case it would probably better to have a sieve filter (more flexibility) and put this into a folder with undesired mails.

For the server and/or domain admin it could be nice to have certain blacklists. But I don't know if there is a real need....

@runout-at
Copy link
Contributor Author

Do you mean we should drop it in future vexim releases?

I'm not happy with the present PHP interface as the 2 submit buttons on the account page are confusing for most people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants