What makes certificate-based digital signatures so secure? With a certificate-based digital signature, every signer is issued a digital ID in the form of a certificate from a trust service provider (TSP), such as a certificate authority (CA). When signing a document, the signer’s identity is re-validated and the signature is cryptographic. Once finished, SigPlusLCD will display the signature as a string (by default), but can be changed to return the signature as a file. The developer can then use the SigString or.SIG file in conjunction with the SigPlus ActiveX control for continuing work with the signature (see SigPlus ActiveX documentation for further details on SigPlus.ocx). Overview Download ActiveMQ 5.11.0 Release. Apache ActiveMQ 5.11.0 resolves more than 130 issues, mostly bug fixes and improvements. It is build with and requires jdk 1.7. New Features in 5.11.0. Destination import/export for lock down mode AMQ-5218; Dynamic camel root loading AMQ-5351. MQTT - QOS2 mapped to virtual topics AMQ-5290.
Signatures are not added by a program from the CodeTwo Exchange Rules family.
There might be several reasons for such behavior. The most probable causes and adequate solutions are described below.
If you work in an environment with more than one Exchange server, make sure that the Exchange Rules Pro Service component is installed on all the servers with the following roles:
Detailed installation instructions are available in the user's manual of your CodeTwo software:
CodeTwo Exchange Rules Pro CodeTwo Exchange Rules.
Emails processed by servers without the Exchange Rules Pro Service will not be stamped with signatures.
Tip
To list all your machines with Microsoft Exchange Server and their roles, follow the instructions from this Knowledge Base article.
If many Exchange Servers are handling your mail flow, you need to enter a CodeTwo Exchange Rules license key on each server with the Mailbox (in the case of Exchange Server 2019, 2016 and 2013) or Hub Transport (Exchange Server 2010 and 2007) role in your environment. Otherwise, CodeTwo Exchange Rules will process only those emails that pass through the licensed servers.
You will receive a separate license key for every server. Detailed instructions on how to activate the program are available in the user's manual of your software version:
CodeTwo Exchange Rules Pro CodeTwo Exchange Rules.
Tip
You can check which servers are licensed by clicking the Server Monitor button on the program’s toolbar (Fig. 1.).
Fig. 1. Checking if all Exchange servers are licensed.
Each time you finish configuring rules in our program, you have to save the changes or the rules will not be applied. This is not done automatically to prevent you from unwanted modifications. You have to click the Submit changes button every time you want to apply the settings to all of your servers.
By default, the Editor opens with an HTML tab that allows you to design a signature for most of email clients. However, some messages are sent in the RTF (e.g. meeting requests) or Plain Text (especially from mobile devices) format. Ensure that you have configured all formats of your signatures. All CodeTwo Exchange Rules family products (standard and Pro) have the Convert button available in the Editor for easy conversion between formats.
The CodeTwo Exchange Rules Transport Agent is a part of the Exchange Rules Pro Service set of services and is responsible for processing all your messages. It may happen that although you selected the Exchange Rules Pro Service component when installing the program, the Transport Agent has not been installed together with other services.

To check if the CodeTwo Exchange Rules Transport Agent has been installed on your machine, open Exchange Management Shell and execute the following command:
Look for the CodeTwo Exchange Rules entry. If it is not displayed, install the agent manually.
You have plenty of rules defined and you are not sure if a user whose messages are not stamped with signatures is defined in any of the rules' conditions or you would like to confirm that this user is not excluded in the Exceptions tab. The easiest way to verify it is to create a new, separate rule only for that user and move it to the top of the list of rules. It will allow the program to process the newly created rule as the first one, so that you can be sure that the rule is executed for this particular user.
This is not a solution itself, but a diagnostic step that allows you to verify if emails sent by this user are processed by the software at all. If it turns out that the rule adds signatures correctly for the user, you need to carefully check all of the other rules' conditions, exceptions and options, to find where the signature processing might be interrupted. If the signature is still not applied, consider checking the other reasons mentioned in this article.
The licensing mechanism assigns a license to each SMTP email address for which a rule is applied at least once by the software. Once the number of the licenses you purchased has been exceeded, any new SMTP email addresses will not be processed by the software (signatures will not be added to the corresponding messages). What is more, even if a user with a corresponding SMTP email address is no longer active in your AD, this person might still be assigned a license. Resetting the licensing counter is the easiest way to restart counting the license consumption, omitting the inactive users.
Another reason to why signatures are not added may be related to complex conditions defined for a particular rule. If you are adding several conditions, the logical operators between them are extremely important and have to be properly selected. By default, each consecutive condition is added with the AND operator. Always make sure that this is the right operator, as sometimes you may need the OR logical relationship between certain conditions. In the graphical view it may not always be that obvious of what to expect, so please always double-check the result with the mathematical notation appearing automatically at the bottom of the window, in the status area (Fig. 2.).
Fig. 2. Conditions' matrix.
Double check if some of the rules' options do not stop the email processing flow unexpectedly (Fig. 3.). Improper settings of this section may prevent consecutive rules from being executed. You may decide whether subsequent rules should be processed or not depending on the processing result of a rule positioned higher on the list of rules. It might sometimes happen that one of the defined rules is accidentally set to stop the program from processing any subsequent rules regardless of the rule's processing result (i.e. regardless if the rule is applied or not, the subsequent rules will not be executed at all).
Fig. 3. Rule options.
If, for example, you add a user to an AD group and this group is defined inside a rule's condition, it may not be detected instantly by CodeTwo software. The reason is simple - by default, any changes to AD are refreshed every hour. You may, however, manually enforce immediate refresh or adjust this mechanism to suit your needs, following the guidelines described in this article.
Carefully check all the conditions, exceptions and options of a rule that is not applied and send a test message that overlaps with the rule's criteria. Give it a unique subject, like “test_message01” to be able to trace it inside the program logs. If the signature is not appended, you can open the program logs and easily search for the test message by providing the message subject. Once you find it, you may verify the conditions' statuses inside the log file; these statuses explain why and at which point the signature processing was stopped.
A signature block (often abbreviated as signature, sig block, sig file, .sig, dot sig, siggy, or just sig) is a personalized block of text automatically appended at the bottom of an email message, Usenet article, or forum post.
An email signature is a block of text appended to the end of an email message often containing the sender's name, address, phone number, disclaimer or other contact information.
'Traditional' internet cultural .sig practices assume the use of monospaced ASCII text because they pre-date MIME and the use of HTML in email. In this tradition, it is common practice for a signature block to consist of one or more lines containing some brief information on the author of the message such as phone number and email address, URLs for sites owned or favoured by the author—but also often a quotation (occasionally automatically generated by such tools as fortune), or an ASCII art picture. Among some groups of people it has been common to include self-classification codes.
Most email clients, including Mozilla Thunderbird, the built-in mail tool of the web browser Opera, Microsoft Outlook and Outlook Express, and Eudora, can be configured to automatically append an email signature with each new message. A shortened form of a signature block (sometimes called a 'signature line'), only including one's name, often with some distinguishing prefix, can be used to simply indicate the end of a post or response. Most email servers can be configured to append email signatures to all outgoing mail as well.
An email signature generator is an app or an online web app that allows users to create a designed email signature using a pre-made template (with no need for HTML coding skills).
Signature blocks are also used in the Usenet discussion system.
Businesses often automatically append signature blocks to messages—or have policies mandating a certain style. Generally they resemble standard business cards in their content—and often in their presentation—with company logos and sometimes even the exact appearance of a business card. In some cases, a vCard is automatically attached.
In addition to these standard items, email disclaimers of various sorts are often automatically appended. These are typically couched in legal jargon, but it is unclear what weight they have in law, and they are routinely lampooned.[3][4]
Business emails may also use some signature block elements mandated by local laws:
While criticized by some as overly bureaucratic, these regulations only extend existing laws for paper business correspondence to email.
The Usenet news system standards say that a signature block is conventionally delimited from the body of the message by a single line consisting of exactly two hyphens, followed by a space, followed by the end of line (i.e., in C-notation: '-- n').[8][9][10] This latter prescription, which goes by many names, including 'sig dashes', 'signature cut line', 'sig-marker', 'sig separator' and 'signature delimiter', allows software to automatically mark or remove the sig block as the receiver desires.
Most Usenet clients (including, for example, Mozilla Thunderbird) will recognize the “dash dash space” delimiter in a news article and will cut off the signature below it when inserting a quote of the original message into the composition window for a reply. Although the Usenet standards strictly apply only to Usenet news articles, this same delimiter convention is widely used in email messages as well, and email clients (such as K-9 and Opera Mail) commonly use it for recognition and special handling of signatures in email.
On web forums, the rules are often less strict on how a signature block is formatted, as Web browsers typically are not operated within the same constraints as text interface applications. Users will typically define their signature as part of their profile. Depending on the board's capabilities, signatures may range from a simple line or two of text to an elaborately constructed HTML piece. Images are often allowed as well, including dynamically updated images usually hosted remotely and modified by a server-side script. In some cases avatars or hackergotchis take over some of the role of signatures.
With FidoNet, echomail and netmail software would often add an origin line at the end of a message. This would indicate the FidoNet address and name of the originating system (not the user). The user posting the message would generally not have any control over the origin line. However, single-line taglines, added under user control, would often contain a humorous or witty saying. Multi-line user signature blocks were rare.
However, a tearline standard for FidoNet was included in FTS-0004[12] and clarified in FSC-0068[13] as three dashes optionally followed by a space optionally followed by text.