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

Disabled accounts should probably be inaccessible by all means possible #105

Closed
rimas-kudelis opened this issue Jan 21, 2016 · 6 comments
Closed

Comments

@rimas-kudelis
Copy link
Collaborator

A few nights ago I suddently came to realization that even if we disable account, mail for it can still be checked out over IMAP and/or POP3, if the admin just follows our instructions.

Perhaps we should update these instructions to actually take into account the enabled/disabled status of the account (or even domain) which the user attempts to access? What do you folks think?

@Udera
Copy link
Collaborator

Udera commented Jan 22, 2016

And you need to disable smtp-auth.

One could imagine different use cases, where you only give a temporary
error on smtp deliveries and disable sending but allow the user to
access the mailbox. Or you want only to disable IMAP/POP-login (also via
webmail) but still receive incoming mails. To cover all possible cases,
we would need more options.

I'm not in favor of a particular solution. To disable all possible
access is perhaps the most expected solution.

On 2016-01-21 15:32, Rimas Kudelis wrote:

A few nights ago I suddently came to realization that even if we
disable account, mail for it can still be checked out over IMAP and/or
POP3, if the admin just follows our instructions.

Perhaps we should update these instructions to actually take into
account the enabled/disabled status of the account (or even domain)
which the user attempts to access? What do you folks think?

Reply to this email directly or view it on GitHub [1].

Links:

[1] #105

@rimas-kudelis
Copy link
Collaborator Author

Yeah, that's what I tend to think as well. More granularity is a nice idea, but I suppose it can wait till next release.

@soujak
Copy link
Contributor

soujak commented Feb 12, 2016

I think that decoupling authentications of transfer and of delivery services is a good thing, but not in both ways.

When a domain is disabled, one may typically want to allow access to MDA for users and administrators, in order to enable a smooth data migration (which may take hours or even days). This make perfectly sense to me.

But I do not see how the other way around would make sense: why one should allow receiving email for a domain without giving access to mailboxes? The only use case I am able to imagine is a quite particular one --- a site administrator who wants to intimidate an insolvent postmaster without completely disable his/her email service.

@rimas-kudelis
Copy link
Collaborator Author

I'm pretty sure we can't come up with every situation possible.
However, like I said before, I think for now we could just update our instructions so that disabled accounts would really be fully disabled (as opposed to having only delivery disabled for them).

@runout-at
Copy link
Contributor

Is this this solved by #159 ? (at least for v2.3)
Because we have only one enabled field we can't control different services like imap/smtp at the moment. (for v2.3.1 or future)

In exim auth checks the enabled field.
For dovecot it got into the instructions

@Udera
Copy link
Collaborator

Udera commented Jul 23, 2016

Yes, looks like it is solve and we deactivated the account completely. Lets open a new issue for more granular setting in a future version.

@Udera Udera closed this as completed Jul 23, 2016
@Udera Udera removed the question label Jul 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants