Emanuele Aliberti

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti commented  · 

    I was referring to a feature similar to the basic versiong in CMIS repositories. Versioning can be enabled/disabled per file. It is not available for folders, but only for files("documents"). When it is enabled, you store as many revisions of a file as you like. By default, the most recent (or "current" one) is shown. You can remove old versions.

    See a more formal definition in CMIS spec. 1.0:

    http://docs.oasis-open.org/cmis/CMIS/v1.0/os/cmis-spec-v1.0.html#_Toc243905415

    Emanuele Aliberti shared this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  6. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti commented  · 

    I was asked if it was possible to create such limited administrator-like users, from the CIO of a company who has some co-workers to whom he does not want to delegate full SG queue management, but just let them review the quarantine and the retry queue, to report back to him about what they found. There is no such a role in current SG release.

    An ACL system would probably be more appropriate for the task, but just limiting existing roles could probably be easier and less expensive to implement for Alt-N in a future release of Security Gateway.

    Thanks for your reply.

    Emanuele Aliberti shared this idea  · 
  7. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  8. 66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti commented  · 

    You could use the extended IMAP4rev1 client you already developed for Outlook Connector to connect the remote instance of WorldClient to the MDaemon server.

  9. 219 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hello,

    Thank you everyone for submitting and supporting this idea. We will consider this for future versions of MDaemon.

    In case anyone is interested we have published a whitepaper on a system we setup here in an acitve/passive cluster. While it does not accomplish everything requested it does provide redundancy.

    http://static.altn.com/Collateral/How-To-Quick-Start-Guide/US_MDaemon-Mail-Server_Configure-High-Availability_How-To-Quick-Start-Guide.pdf

    Thanks,
    Arron

    Emanuele Aliberti commented  · 

    You could use the extended IMAP4rev1 (that you already developed for Outlook Connector) to mirror a mailbox between two or more MDaemon servers running in shared-domain mode.

    Emanuele Aliberti commented  · 

    Extend the functionality of "shared domain" in MDaemon.
    First, extend it to perform as a limited HTTP/IMAP/POP3 proxy.
    Add a new mailbox attribute: a user's home server, where a mailbox is located permanently.
    When a client connects to a server of the shared domain group, if the logging-in user is in his/her home server, behave as usual and complete local authentication. If it is not, user MINGER to query other server in the shared domain group. As soon as you find the loggin-in user's home server, authenticate using the pending session credentials provided by the client. If remote authentication succeeds, proxy the client protocol to the remote (home) server.

  10. 173 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti commented  · 

    Or, at least, please, keep the message files on the file system, but move all metadata (header, message parts structure/offsets, indexes, references, renditions, ...) in to a database.

  11. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  12. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  13. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  14. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 
  15. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emanuele Aliberti shared this idea  · 

Feedback and Knowledge Base