If the API call returned more than one pmail entry, inject an "all"
entry which, if selected, drops the user parameter and loads the
quarantine mails of all users from the backend.
The webinterface has only some issues regarding deselection (all in
the grid header or if we need to deselect due to the search filtering
out some elements) - for that the underlying issue was found and a
widget toolkit patch was provided.
The rest seems now pretty performant, albeit more than a few 100k
mails may become a problem here. But, in such big setups the mail
admin won't tinker to much whith the users mail anyway, if they are
even alowed to do so depending on their jurisdictions privacy laws
and companies privacy policy.
So, basically this is more for evaluation or for smaller setups but
got quite often requested, and as there's not more data
exposed/returned then already available I see no real argument
against it.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Deselect those entries which got filtered out, to avoid doing
some action (delete, deliver) on hidden records.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
by not saving the position across time or email changes, since that
makes no real sense. (The user cannot really know what will be selected,
in contrast to when the mails will be deleted etc.)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
using an explicit load on time change and queryMode 'local', we can
enable typeAhead (and related settings) to let the user type in an email
which will be autocompleted by the loaded list.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
when an e-mail is selected and an action goes through,
select the e-mail on the position the old one was,
this way, one does not have to reselect an e-mail after
an action is done
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
optimized a few string
EMail/Email/E-mail -> E-Mail
No Data in Database/No data in database. -> No data in database
etc.
removed 'Outlook 2007' from gettext
added some strings to gettext where they were missing
(e.g. Active, etc.)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
so that when we have the same timespan when we change the quarantine,
as long as we do not reload the browser window
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
so that when there is no email in the quarantine for the selected
timeframe, we now get the feedback that there is no data
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this changes the login/logout/cookie behaviour
if you go to /quarantine
you get to the loginview
except you have a valid cookie
or you have a ticket via url (this takes precedence)
when you have a valid login
you go to the quarantineview
else if you have not a quarantine ticket
you get to the mainview
else
you get to the loginview
also adds a logout button to the quarantineview
and moves the viewchange/logout logic to the Application.js
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this component is a refactored version of the PMG.SpamList
component, but it incorporates the logic and layout for
changing dates/emails from the PMG.SpamQuarantine component
additionally, it has some logic to show/hide the email selection box
via a config property ('emailSelection')
this will be used for the SpamQuarantine in admin/user view and
for the virus quarantine
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
