|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
22 Dec 2018, 12:14 PM | #1 |
Essential Contributor
Join Date: May 2018
Posts: 478
|
Question about fileinto vs. keep
Based on some condition I want to file a incoming email into the INBOX and mailbox X. So I can write,
Code:
if ...test condition... { fileinto "INBOX"; keep; } Code:
if ...test condition... { fileinto "INBOX.X"; } Fine, that's what I want. However if I open one of these copies, doesn't matter which, it gets marked as read in both mailboxes! Not what I was expecting. On the other hand deleting one does not delete the other. Is this the way these are supposed to behave? I'm not saying it's wrong necessarily. It's just a bit confusing about how the single message filed into two distinct mailboxes are not entirely treated as two distinct copies. It could be I just don't fully understand fileinto's relationship with keep. Last edited by xyzzy : 22 Dec 2018 at 12:25 PM. |
23 Dec 2018, 07:02 AM | #2 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
Folder targeting
The sieve language provides an implicit “keep” which by default saves a message into the initial target folder. Fastmail allows the target folder when sieve execution starts to be set in three ways:
Copying without side effects https://tools.ietf.org/html/rfc3894 Your first sieve fragment is not needed in most cases if you are not using subdomain or plus+addressing. The default action is to “keep” without any action on your part. The sieve fragment will have two effects:
If you want to file a copy of a message in a certain folder and also let it be automatically filed into the target folder (by default Inbox), all you need to do is include the “:copy” tag as described in RFC3894. For example, this code will file a message which matches he test condition into both the Inbox and X folders: Code:
If ...test condition... { fileinto :copy “INBOX.X”; } |
23 Dec 2018, 08:03 AM | #3 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
Conversation mode
Quote:
https://www.fastmail.com/help/receiv...ersations.html In Conversation view mode the idea is that once you read a conversation thread all copies of messages are marked as read (until a new message arrives, marking the conversation unread until you read any message in that conversation). Fastmail is in the process of changing their user interface to JMAP. See: https://www.fastmail.com/help/guides...date-2018.html At this time, I see a different user interface on my PC (using a browser), my iPad (using a browser), and my iPad (using the Fastmail app). I see some differences on how conversations are being shown with these different user interfaces. Bill |
|
23 Dec 2018, 01:01 PM | #4 | |||
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
Another strange thing. In that Conversations document it states: Quote:
Quote:
Thanks for the other post too. I forgot about the fileinto :copy. I'll have to experiment to see if that causes any different behavior. I just want to keep both copies entirely independent. |
|||
23 Dec 2018, 02:38 PM | #5 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,929
|
Quote:
http://emdforum.sent.com/Mail_Prefer...references.PNG I can see some differences in how this works on my PC, iOS browser, and iOS app. And after some testing I think there are bugs. I will file a report with Fastmail. Bill |
|
23 Dec 2018, 05:38 PM | #6 | ||
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
Quote:
|
||