FrontendUsers and expired users/Front End File Management

[virgo]

I'm trying to understand, if Frontend users module actually does something with users "expires" property. Currently expired users can still log in. That by itself would not be an issue, because I can use Custom Content module to show them different content.
But our webpage would also provide downloads to users, that should only be available to logged in and not expired users. I'm currently using Uploads module for those downloads (I could not find another, that would actually limit access to file by direct link, if user is not logged in/not in specific group). Unfortunately that module also does not check for expiry date.
Does anyone have any recommendation, how to work around it?

[Dr.CSS]

I've used FEU a lot and have an idea you think of expire as something different than it is...

Where is it and what do you think it should/does do..?

[virgo]

I've used FEU a lot and have an idea you think of expire as something different than it is...

Where is it and what do you think it should/does do..?

Under FEU every user has "Expires" date. It seems to me, that currently it doesn't do anything. If the expires in in the past users can still log in. It can be read and used but by default it doesn't seem to be doing anything.
Now, I actually like the idea, that expired (expires date is in the past) user can log in (I'm using !ccUser::expired() to protect part of page the expired users should not have access to). Although, it would be nice, if there was a property to set this behavior.
What would be nice, if other FEU based modules would also have support for different behavior for expired users.
For example, we are using Front End File Management (Uploads) for protected downloads. Where category has matching FEU group. So that users from another group cannot download file, even if thet know file id. But it would be also useful, if I could mark it to be available only for not expired users from that group.

[Dr.CSS]

I would think if they were expired they just wouldn't be able to log in, wouldn't think you would have to set anything in the {tag} or use any !ccUser::expired() (which I'm not even sure is a call for custom content)...