@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Improve documentation around using Mail stamps with Gmail
Summary: Ref T13069. See PHI54. Some of this behavior isn't entirely obvious, so give users a heads up in the documentation to help warn them about what is to come.
Test Plan: Read documentation.
Maniphest Tasks: T13069
Differential Revision: https://secure.phabricator.com/D19227
+21
+21
src/docs/user/userguide/mail_rules.diviner
+21
src/docs/user/userguide/mail_rules.diviner
···
43
43
is a list of attributes which describe the object the mail is about and the
44
44
actions which the mail informs you about.
45
45
46
+
Stamps and Gmail
47
+
================
48
+
46
49
If you use a client which can not perform header matching (like Gmail), you can
47
50
change the {nav Settings > Email Format > Send Stamps} setting to include the
48
51
stamps in the mail body and then match them with body rules.
52
+
53
+
When writing filter rules against mail stamps in Gmail, you should quote any
54
+
filters you want to apply. For example, specify rules like this, with quotes:
55
+
56
+
> "author(@alice)"
57
+
58
+
Note that Gmail will ignore some symbols when matching mail against filtering
59
+
rules, so you can get false positives if the body of the message includes text
60
+
like `author alice` (the same words in the same order, without the special
61
+
symbols).
62
+
63
+
You'll also get false positives if the message body includes the text of a
64
+
mail stamp explicitly in a normal text field like a summary, description, or
65
+
comment.
66
+
67
+
There's no way to avoid these false positives other than using a different
68
+
client with support for more powerful filtering rules, but these false
69
+
positives should normally be uncommon.