As we showed you in the Getting Started section, you can perform tests using the if command on incoming messages to determine whether an email should be affected by a requirecommand. In addition to the ifcommand, there are other test commands that allow you to structure your script in a simple way. See full list on protonmail.com Using the on , andsenderheader. You can extract different parts of the email flags: 1. :localpart— the part before the at symbol (@) 2. :domain— the part after the at symbol (@) 3. :all— the whole s the use of this command: In summary, this script will put everything sent from the domain northpark.example.com in PaperPeople and springfield.example.com in YellowPeople. Moreover, no matter what domain an email is sent from, if the part before @ is equal to chef (e.g. ), then the message will be flagged. Another interesting usage is to automatically store everything sent to one protonmail.com When a test evaluates two values, it is possible to specify how this comparison is done using different flags called comparators. Beforehand, we already used two comparators: :is and :contains, which checks that the given string is exactly equal to the specific value, and that the specific value contains the given string, as in the following test. The comparator :matches can also be used to define a more specific format. It will compare both values from the beginning to the end, just like the comparator :is. However, in the case of :matches, the value that you defined can contain the values ? and *. The question mark will match one character, and the star (called wildcard) will match zero or more characters. With this format, you can create this test: In this example, the test will succeed if the subject of the message starts with mmph and then contains any character or characters after it. In other words, the email will be flagged when the subject begins with ‘mmph’. ‘mmph mmph’ an... See full list on protonmail.com You can also access information related to your account and ProtonMail context in general using extensions. For example, you can check if the sender ou can adjust the spam threshold. See full list on protonmail.com Matching on specific headers is also possible. For instance, to put all messages sent to lists (often they are marketing messages or newsletters), you can do: To sort social media emails into their own folder, you could write: Note that we use: instead of: As the latter checks if both x-facebook and x-linkedin-idhas been set. To actually look what value a header contains, you can use the headertest: Apart from the :is operation, which does an exact match, the header command also supports :matches, which matches using wildcards (e.g. “*@*.com” will match any email e :contains command, which checks if the header contains a given string. To design Sieve filters, it can be useful to retrieve the headers of an email. To do this in the ProtonMail web interface, you can click on the More menu (the arrow down button) and then View headers. A new window will open containing all the headers of the email. See full list on protonmail.com It is possible to treat large emails differently than small emails. For instance, you might want to flag large emails, so that you can delete them to save mailbox space. This can be accomplished in the following way: As you can see, units are available if you want to specify big sizes, by adding the letter corresponding to the expected unit just after the number. Three unit are available: K for a kibioctet (or 1024 bytes), M for a mebioctet (or 1 048 576 bytes) and G for a gibioctet (or 1 073 741 824 bytes). Please note that “over” in this case means greater than, and “under” means less than. This means that if a message has a size of exactly 1000 bytes, then neither nor will match. Note that Sieve filters don’t have access to the actual content and only show the encrypted size. See full list on protonmail.com You can execute different reactions to a message in Sieve. We already presented the actions fileinto, addflag, discard, and rejectin the previous sections. Here we will present more advanced actions. See full list on protonmail.com Packages Sieve supports the following extensions. You can refer to the official documentation for more information. Date 1. Usage: date 2. Description:Provides a way to check date information. 3. Documentation: https://tools.ietf.org/html/rfc5260 4. Implementation: The default comparator is i;ascii-numeric and not i;ascii-casemap. Indeed, date is not useful with the casemap comparator. 5. See: Vacation messages and Date tests Envelope 1. Usage: envelope 2. Description:Defines tests around the SMTP env... Tests Currentdate 1. Usage: 1. Description:Performs a test using the current date on the ProtonMail server 2. Package:date 3. See: List of supported actions and tests Date 1. Usage: 1. Description: Performs a test using the date described by a header. 2. Package:date 3. See: List of supported actions and tests HasFlag 1. Usage: 1. Description: Tests if a certain message has a certain flag. 2. Package:imap4flags 3. See: Getting Started Envelope 1. Usage: 1. Description:Tests if the specified part of... Actions Require 1. Usage: 1. Description:Loads a specified extension such that its methods or modifications can be used. 2. Package: 3. See: Getting started FileInto 1. Usage: 1. Description: Moves the message that is being processed to a certain folder. 2. Package: fileinto 3. See: Getting started Addflag 1. Usage: 1. Description:Adds the specified flag to the message that is being processed. 2. Package: imap4flags 3. See: Getting started Removeflag 1. Usage: 1. Description: Removes the spe... See full list on protonmail.com
Get Price
