Messages with this flag set are not visible to IMAP or POP clients. Keeping certain messages private (hidden). This flag allows users to grant access to their Mailboxes to others while To those users who have the Admin Access Right for this Mailbox. Messages with this flag set are visible only to the Mailbox Account owner and This flag helps mail clients to send only one MDN report for each message. This flag is set when an MDN ("read report") for the message has been sent. This flag is set when a copy of the message was sent (redirected) to someone. Mark some Mailbox messages first, and then delete ("expunge") all marked messages from the Mailbox. This flag is set for messages that were marked for deletion. This flag is set for messages that have not been sent yet. This flag is explicitly set and reset with mail client applications. This message to the user as an important one).
This flag is set to attach a "flag" to the message (for example, a mail client can show This flag is set when a reply was sent for this message. It can be set automatically as a result of certain Mailbox access operations,Īnd it can be set and reset explicitly with mail client applications. This flag is set when the message was read by a client. The following table lists the predefined message flags along with their IMAP and Negative names: Reset a certain flag or to look for messages that do not have that flag set. They can also use "negative names" to instruct the server to Several components (such as Automated Rule, CG/PL programs, etc.)Ĭan access message flags by name. Some flags are set automatically, even when the access protocol used does not support flag modification.įor example, the Seen flag is set automatically when the message is being read using Such as IMAP, MAPI, XIMSS, WebUser Interface, Message is being stored in the Mailbox, and they can be updated using Mailbox access protocols and methods, Messages in Mailboxes have individual flags. Two Mailboxes with names that differ in case only. When these file systems are used for CommuniGate ProĪccount/Mailbox storage, the Mailbox names are still case-sensitive, but you cannot create Some file systems (NTFS, for example) provideĬase-insensitive file naming conventions. In this case a new empty INBOX Mailbox will be created automatically. You can rename the INBOX Mailbox, though. It is impossible to delete the INBOX Mailbox. You can later create the regular ABCDEF Mailbox and the "storage" entity for your The name ABCDEF will be listed, but will notīe "selectable" - and you will not be able to store messages in the ABCDEF Mailbox. Use the ABCDEF/ name as the new Mailbox name to create only theĭirectory entity with the ABCDEF name. You can, though, create the "directory" entity without creating the "mail storage" entity: The "directory"Įntity is created automatically, as soon as you try to create the first sub-Mailbox. Storing messages, one - for serving as a "directory" for the nested Mailboxes. This feature is implemented by providing two "invisible" Mailbox entities - one for Mailbox X and at the same time you can create sub-Mailboxes X/Y, X/Z for that Is the name of the sub-Mailbox important "inside" the INBOX Mailbox.ĬommuniGate Pro allows you to store messages in some The CommuniGate Pro Server uses the slash ( /) symbol as the hierarchy separator: In the same way as you can created a file directory inside some other file directory. Mailboxes can be "nested": for any Mailbox "A" you can create a sub-Mailbox "B". Or XIMSS mailer application or using the WebUser Interface. The System and/or DomainĪdministrator can specify additional Mailboxes to be created at that time.Ī user can create a Mailbox using an IMAP, MAPI, When an Account is created, its INBOX Mailbox is automatically created.
0 kommentar(er)
