89
125
here. For example, if an email is deleted by the blacklist, the following
90
126
rules will not have any influence on this email.</tip>
128
</entry>--><!-- English entry:
129
<entry id="filters_rules">
130
<title>Rules: Filter Rules</title>
131
<para>This is the main rules screen. From here you can create new rules by
132
clicking on the "New Rule" button; rearrange the rule order by clicking on
133
the up and down arrows or entering new rule positions in the "Move" column;
134
enable and disable specific rules by clicking on the icon in the "Enabled"
135
column; and edit individual rules by clicking on the icon in the "Edit"
136
column or on the rule name.</para>
138
<tip>Please note, that the rules are executed in the order displayed
139
here. For example, if an email is deleted by the blacklist, the following
140
rules will not have any influence on this email.</tip>
142
</entry>--><!-- English entry:
143
<entry id="filters_rules">
144
<title>Rules: Filter Rules</title>
145
<para>This is the main rules screen. From here you can create new rules by
146
clicking on the "New Rule" button; rearrange the rule order by clicking on
147
the up and down arrows or entering new rule positions in the "Move" column;
148
enable and disable specific rules by clicking on the icon in the "Enabled"
149
column; and edit individual rules by clicking on the icon in the "Edit"
150
column or on the rule name.</para>
152
<tip>Please note, that the rules are executed in the order displayed
153
here. For example, if an email is deleted by the blacklist, the following
154
rules will not have any influence on this email.</tip>
92
156
</entry>--></entry>
93
157
<entry id="forward" md5="876cd0cf20642eab9a06d58a2eaad95c" state="changed">
94
158
<title>P�rs�t�t</title>
213
341
be performed on that message. Filters can be very useful for automatically
214
342
deleting unwanted mail, or making your mail account more managable by
215
343
storing related messages into different folders.</para>
344
</entry>--><!-- English entry:
346
<title>Filter Rule</title>
347
<para>A rule is the basic building block of your mail filters, it consists
348
of one or more conditions and one or more actions. When a message is sent
349
to you, it is processed through the conditions of your filter rules, if the
350
conditions that you specify are met, then the actions that you specify will
351
be performed on that message. Filters can be very useful for automatically
352
deleting unwanted mail, or making your mail account more managable by
353
storing related messages into different folders.</para>
354
</entry>--><!-- English entry:
356
<title>Filter Rule</title>
357
<para>A rule is the basic building block of your mail filters, it consists
358
of one or more conditions and one or more actions. When a message is sent
359
to you, it is processed through the conditions of your filter rules, if the
360
conditions that you specify are met, then the actions that you specify will
361
be performed on that message. Filters can be very useful for automatically
362
deleting unwanted mail, or making your mail account more managable by
363
storing related messages into different folders.</para>
216
364
</entry>--></entry>
217
365
<entry id="rule-action" md5="774acc549f6ddfd52871f957de2deee5" state="changed">
218
366
<title>Filtra likums: Darb�ba</title>
291
439
<heading>Reject this message with reason</heading>
292
440
<para>The original message will be discarded, and a new message will be
293
441
sent to the sender with the text that you specify.</para>
442
</entry>--><!-- English entry:
443
<entry id="rule-action">
444
<title>Filter Rule: Action</title>
445
<para>These are the possible actions to take if an incoming message matches
446
the specified conditions. Note that all of these options may not be
447
available to you - only the options that work with the underlying filtering
448
software will be shown.</para>
449
<heading>Deliver this message into my INBOX</heading>
450
<para>The message will be saved in your INBOX. This is the default
452
<heading>Deliver to this mailbox</heading>
453
<para>The message will be delivered to the specified folder.</para>
454
<heading>Discard this message</heading>
455
<para>The message will be silently deleted. Neither you nor the sender will
456
receive notification that this has happened.</para>
457
<heading>Redirect this message to</heading>
458
<para>The message will be sent to the email address that you specify. No
459
copy of the message will remain in this account.</para>
460
<heading>Deliver to my INBOX and redirect to</heading>
461
<para>The message will be sent to the email address that you specify, and a
462
copy of the message will remain in your INBOX.</para>
463
<heading>Reject this message with reason</heading>
464
<para>The original message will be discarded, and a new message will be
465
sent to the sender with the text that you specify.</para>
466
</entry>--><!-- English entry:
467
<entry id="rule-action">
468
<title>Filter Rule: Action</title>
469
<para>These are the possible actions to take if an incoming message matches
470
the specified conditions. Note that all of these options may not be
471
available to you - only the options that work with the underlying filtering
472
software will be shown.</para>
473
<heading>Deliver this message into my INBOX</heading>
474
<para>The message will be saved in your INBOX. This is the default
476
<heading>Deliver to this mailbox</heading>
477
<para>The message will be delivered to the specified folder.</para>
478
<heading>Discard this message</heading>
479
<para>The message will be silently deleted. Neither you nor the sender will
480
receive notification that this has happened.</para>
481
<heading>Redirect this message to</heading>
482
<para>The message will be sent to the email address that you specify. No
483
copy of the message will remain in this account.</para>
484
<heading>Deliver to my INBOX and redirect to</heading>
485
<para>The message will be sent to the email address that you specify, and a
486
copy of the message will remain in your INBOX.</para>
487
<heading>Reject this message with reason</heading>
488
<para>The original message will be discarded, and a new message will be
489
sent to the sender with the text that you specify.</para>
294
490
</entry>--></entry>
295
491
<entry id="rule-combine" md5="15a1cee3a778b72560a03aea738c4b28" state="changed">
296
492
<title>Filtra likums: Kombin�t opcijas</title>
329
525
<heading>Or</heading>
330
526
<para>If you select OR, the specified actions will be executed if at least
331
527
one of the conditions is met.</para>
528
</entry>--><!-- English entry:
529
<entry id="rule-combine">
530
<title>Filter Rule: Combine Options</title>
531
<para>You may define multiple conditions within a single rule. You may
532
group them together logically using "and"/"or". You may not create complex
533
filters containg both types of conditions.</para>
534
<heading>And</heading>
535
<para>If you select AND, an incoming message must match every condition
536
that you specify in order for the actions to be executed.</para>
537
<heading>Or</heading>
538
<para>If you select OR, the specified actions will be executed if at least
539
one of the conditions is met.</para>
540
</entry>--><!-- English entry:
541
<entry id="rule-combine">
542
<title>Filter Rule: Combine Options</title>
543
<para>You may define multiple conditions within a single rule. You may
544
group them together logically using "and"/"or". You may not create complex
545
filters containg both types of conditions.</para>
546
<heading>And</heading>
547
<para>If you select AND, an incoming message must match every condition
548
that you specify in order for the actions to be executed.</para>
549
<heading>Or</heading>
550
<para>If you select OR, the specified actions will be executed if at least
551
one of the conditions is met.</para>
332
552
</entry>--></entry>
333
553
<entry id="rule-mark" md5="ecabf7aaede106b7dd32a2aee05cee57" state="changed">
334
554
<title>Filtra likums: Atz�m�t v�stuli</title>
573
805
<heading>Greater than</heading>
574
806
<para>This is a relational test which will compare the value you specify
575
807
and the value in the message header numerically.</para>
808
</entry>--><!-- English entry:
809
<entry id="rule-matches">
810
<title>Filter Rule: Matches</title>
811
<para>There are 3 components to each condition in a rule. The first is the
812
field to examine. The second is the type of comparison to perform. The
813
third is the value to which the field should be compared. There are a few
814
different types of comparisons that can be performed. The comparisons
815
available for any given field will depend on both the type of the field and
816
what the underlying filtering software can handle. Thus, all potential
817
matching options listed below may not appear for a given field.</para>
818
<heading>Contains</heading>
819
<para>Will be considered to be true if the specified string is found
820
anywhere on the line. Example: user@example would match
821
joe_user@example.com</para>
822
<heading>Doesn't Contain</heading>
823
<para>Will be considered to be true if the specified string is not found
824
anywhere on the line. Example: user@example would not match
825
joe_user@example.com</para>
826
<heading>Is</heading>
827
<para>Will be considered to be true if the specified string matches the
828
line exactly. Example: user@example.com is user@example.com</para>
829
<heading>Isn't</heading>
830
<para>Will be considered to be true if the specified string does not match
831
the line exactly. Example: user@example is not user@example.com</para>
832
<heading>Begins with</heading>
833
<para>Will be considered to be true if the specified string matches the
834
beginning of the line. Example: user@example will match
835
user@example.com</para>
836
<heading>Doesn't begin with</heading>
837
<para>Will be considered to be true if the specified string does not match
838
the beginning of the line. Example: user@example.com will not match
840
<heading>Ends with</heading>
841
<para>Will be considered to be true if the specified string matches the end
842
of the line. Example: example.com will match user@example.com</para>
843
<heading>Doesn't end with</heading>
844
<para>Will be considered to be true if the specified string does not match
845
the end of the line. Example: horde.org will not match
846
user@example.com</para>
847
<heading>Exists</heading>
848
<para>Will be considered to be true if the specified header exists in the
849
message, regardless of what its value is.</para>
850
<heading>Doesn't Exist</heading>
851
<para>Will be considered to be true if the specified header does not exist
852
in the message.</para>
853
<heading>Regex</heading>
854
<para>Regex allows you to use complex POSIX compatible regular expressions
855
to compare against message headers. Example: "Received from [*\.*\.*\.*] by
856
(hosta|hostb).example.com*" would match "Received from [172.16.100.1] by
857
hosta.example.com on Tuesday"</para>
858
<heading>Matches</heading>
859
<para>Matches is similar to contains, with the exception that you may use *
860
and ? as wildcards. An * will match any number of characters, and a ? will
861
match exactly one charater. Example: "*user?@example.com" will match both
862
"user1@example.com" and "otheruser2@example.com"</para>
863
<heading>Doesn't match</heading>
864
<para>Doesn't match is the same as matches except that it will evaluate to
865
false if the specified value matches the string in the message
867
<heading>Less than</heading>
868
<para>This is a relational test which will compare the value you specify
869
and the value in the message header numerically.</para>
870
<heading>Less than or equal to</heading>
871
<para>This is a relational test which will compare the value you specify
872
and the value in the message header numerically.</para>
873
<heading>Equal to</heading>
874
<para>This is a relational test which will compare the value you specify
875
and the value in the message header numerically.</para>
876
<heading>Greater than or equal to</heading>
877
<para>This is a relational test which will compare the value you specify
878
and the value in the message header numerically.</para>
879
<heading>Greater than</heading>
880
<para>This is a relational test which will compare the value you specify
881
and the value in the message header numerically.</para>
882
</entry>--><!-- English entry:
883
<entry id="rule-matches">
884
<title>Filter Rule: Matches</title>
885
<para>There are 3 components to each condition in a rule. The first is the
886
field to examine. The second is the type of comparison to perform. The
887
third is the value to which the field should be compared. There are a few
888
different types of comparisons that can be performed. The comparisons
889
available for any given field will depend on both the type of the field and
890
what the underlying filtering software can handle. Thus, all potential
891
matching options listed below may not appear for a given field.</para>
892
<heading>Contains</heading>
893
<para>Will be considered to be true if the specified string is found
894
anywhere on the line. Example: user@example would match
895
joe_user@example.com</para>
896
<heading>Doesn't Contain</heading>
897
<para>Will be considered to be true if the specified string is not found
898
anywhere on the line. Example: user@example would not match
899
joe_user@example.com</para>
900
<heading>Is</heading>
901
<para>Will be considered to be true if the specified string matches the
902
line exactly. Example: user@example.com is user@example.com</para>
903
<heading>Isn't</heading>
904
<para>Will be considered to be true if the specified string does not match
905
the line exactly. Example: user@example is not user@example.com</para>
906
<heading>Begins with</heading>
907
<para>Will be considered to be true if the specified string matches the
908
beginning of the line. Example: user@example will match
909
user@example.com</para>
910
<heading>Doesn't begin with</heading>
911
<para>Will be considered to be true if the specified string does not match
912
the beginning of the line. Example: user@example.com will not match
914
<heading>Ends with</heading>
915
<para>Will be considered to be true if the specified string matches the end
916
of the line. Example: example.com will match user@example.com</para>
917
<heading>Doesn't end with</heading>
918
<para>Will be considered to be true if the specified string does not match
919
the end of the line. Example: horde.org will not match
920
user@example.com</para>
921
<heading>Exists</heading>
922
<para>Will be considered to be true if the specified header exists in the
923
message, regardless of what its value is.</para>
924
<heading>Doesn't Exist</heading>
925
<para>Will be considered to be true if the specified header does not exist
926
in the message.</para>
927
<heading>Regex</heading>
928
<para>Regex allows you to use complex POSIX compatible regular expressions
929
to compare against message headers. Example: "Received from [*\.*\.*\.*] by
930
(hosta|hostb).example.com*" would match "Received from [172.16.100.1] by
931
hosta.example.com on Tuesday"</para>
932
<heading>Matches</heading>
933
<para>Matches is similar to contains, with the exception that you may use *
934
and ? as wildcards. An * will match any number of characters, and a ? will
935
match exactly one charater. Example: "*user?@example.com" will match both
936
"user1@example.com" and "otheruser2@example.com"</para>
937
<heading>Doesn't match</heading>
938
<para>Doesn't match is the same as matches except that it will evaluate to
939
false if the specified value matches the string in the message
941
<heading>Less than</heading>
942
<para>This is a relational test which will compare the value you specify
943
and the value in the message header numerically.</para>
944
<heading>Less than or equal to</heading>
945
<para>This is a relational test which will compare the value you specify
946
and the value in the message header numerically.</para>
947
<heading>Equal to</heading>
948
<para>This is a relational test which will compare the value you specify
949
and the value in the message header numerically.</para>
950
<heading>Greater than or equal to</heading>
951
<para>This is a relational test which will compare the value you specify
952
and the value in the message header numerically.</para>
953
<heading>Greater than</heading>
954
<para>This is a relational test which will compare the value you specify
955
and the value in the message header numerically.</para>
576
956
</entry>--></entry>
577
957
<entry id="rule-name" md5="ed8e3b8044b7e1a681b259fa605dc9ee" state="changed">
578
958
<title>Filtra likums: Nosaukums</title>
added
removed
locale/lv_LV/help.xml
